Release Notes

The online version of the Release Notes contains the latest updates.
This page summarizes the new or updated functionalities and known issues of
3.2. If you have questions, contact the
Agile Requirements Designer
Community forum

What's New in 3.2?

We’re excited to release an integration with BlazeMeter Scriptless Testing that gives you access to an advanced test execution engine for web applications. Other improvements in
3.2 include improved integration experiences with popular tools that you use, and enhancements that will give you more flexibility and control: Switching between Stored Path Types in subflows is now faster; you can now compute Custom Field values on path level; you have more flexibility in m-to-n mapping of subflow block inputs to start nodes; and you can import and export SAP Solution Manager diagrams with swim lanes.

BlazeMeter Integration - Introducing BlazeMeter as Test Execution Engine

Agile Requirements Designer
is now integrated with a test execution engine for GUI Functional Testing: BlazeMeter is an end-to-end testing platform for web applications which also offers Performance and API testing.
What can the BlazeMeter platform do for you? Testers install a free Chrome extension to record HTTP/S requests and user interactions while performing test steps in the web application under test. Based on the recording, the extension generates a JMeter and/or Selenium script and uploads it to, where your test team can edit, run, review, and share test suites. Read this blog by automation expert Marta Benach to see an example of Using Model-Based Testing to Generate BlazeMeter GUI Functional Tests in action!
The following BlazeMeter screenshot shows the Scriptless test editor. You see the list of test actions in the center, and the configured test scenario on the right side.
The Scriptless test editor in the BlazeMeter web interface
With the new BlazeMeter Automation integration, you can use ARD models to generate and export automation scripts, and run them as test cases in BlazeMeter.
The following screenshot shows the BlazeMeter Automation editor in
Agile Requirements Designer
, again with available test actions on the left side, and the configured test steps on the right side.
The Scriptless test editor in the BlazeMeter web interface
This means that the Scriptless test editor is now not only available for BlazeMeter GUI Functional Tests, but also for ARD Flows. Thanks to its user-friendly interface, even testers with little or no scripting experience can create and edit test scripts quickly and confidently.

Switch Stored Path Type

If you use flows with subflows, you know that each subflow contains stored paths of its own. For each Stored Path, you can define a Stored Path Type, and the Path Explorer generates different paths depending on which type you select for the subflows. In
Agile Requirements Designer
3.1 and older, whenever you changed subflow types and the subflows were reloaded, you had to regenerate paths manually, because
Agile Requirements Designer
only stored one path type at a time.
Agile Requirements Designer
3.2 on, all subflow paths are stored, and changing the Stored Path Type only switches which set is active for path generation. You don't have to regenerate paths manually any more. Note that, after switching the Stored Path Type, the Path Explorer still displays the previous stored paths; as in previous
Agile Requirements Designer
releases, it's your choice whether you want to delete stored paths or whether you want to add new paths to the existing ones.
For more information, see Store Paths.

Compute Path Custom Fields Values

As you know, you can set path custom fields to attribute references and export them. In
Agile Requirements Designer
3.2, this feature has been enhanced. You can now dynamically aggregate values from multiple blocks, and export a computed value on path level.
To compute the path-level value, you can use functions such as concatenation, min/max, sum, average and so on. The concatenate function supports custom separators, such as space, comma, and an escaped newline character.
To use this computed value, you export it to a field in a software lifecycle integration, or use it as variable value in automation snippets. You can also filter blocks by these custom field attributes.
For more information, see Define Custom Fields.

Support for m:n Mapping of Block Inputs to Subflow Start Nodes

The user interface for decision tables and subflows has been improved, including a new "Map subflow start blocks" dialog. Now you can select multiple specific inputs for each decision row, based on start nodes. 

SAP Solution Manager

SAP Solution Manager BPMN diagrams can contain Swim Lanes to represent separate processes and roles. To support Solution Manager diagrams,
Agile Requirements Designer
now includes a horizontal Swim Lane block in the toolbox under Other Shapes. Swim Lane blocks in
Agile Requirements Designer
are a purely visual background object with no semantic meaning for path generation.
The SAP Solution Manager integration is a beta feature. To use it, click Settings, go to the Beta Features tab, and enable "SAP Solution Manager" integration.
For more information, see Integrate with SAP Solution Manager.

The Latest Optimizer

In the Path Explorer, the Latest Optimizer combines a multitude of performance improvements: The Optimizer analyzes the flow and smartly picks the best fitting algorithm to achieve the requested coverage fastest. It's also faster when it generates paths for flows that contain loops and constraints; you no longer need to define loop settings manually.
For more information, see Path Explorer.

TDM Integration Using the TDMService

If you use Test Data Manager, you know that
Agile Requirements Designer
can connect to an existing TDM installation and benefit from TDM repository integration. The TDM integration helps you find or make test data, and includes other smart features such as Test Matching and Data Painter.
Use the new TDMService included with Test Data Manager to establish the connection with
. The legacy TDoD Service (also known as GTService) features are still included in ARD 3.2, but the old integrations will no longer be updated and no issues will be fixed.
For more information, see Managing Test Data.

Customer Enhancements

Flow Modelling
  • On the
    Application Links
    tab in the
    Block Properties
    Flow Properties
    , you can now attach any URI (such as ardflow://, file://, mailto://, https://, and many others) to your Flows by adding a
    General Link
    . Use this generic application link to reference any document that specifies a requirement -- including other Flows, Web URLs, spreadsheets, and any documents that are reachable from your intranet. You can open linked resources directly from
    Agile Requirements Designer
    Studio or from
    Agile Requirements Designer
    Insights using the application that is registered in the operating system to open this URI scheme. You can also filter by links, and you can export links to various lifecycle tool integrations.
  • Autosave lets you keep the most recent copy of each unsaved file. The default save interval is two minutes. If you enable this feature, Hub and local flows are always autosaved locally. Autosave is turned off by default: To enable this feature, go to
    Home > Settings > Standard Settings > Autosave
    and define an
    Autosave interval
    and an
    Autosave folder
    , and restart
  • You can now not only compare multiple versions of the same flow, but you can also compare any two opened flows. Right-click the Flow tab and use the Compare Opened Flows menu item.
  • The
    Manage > Revision History
    dialog for Hub Flows was improved, so that you can now see all project versions of one Flow.
Test Generation
  • In the Path Explorer, on the
    View Test Cases
    tab, we introduced an
    Export Paths to Spreadsheet
    button that lets you export stored paths from here. The
    Export Paths
    Export Paths to Spreadsheet
    buttons are now also easier to distinguish.
  • The Flow GUID is now available as an exportable automation parameter. This unique parameter is useful if you want to track whether a set of automation files were produced by the same Flow.
  • In the Rally Connector, you can now browse Rally Features, Capabilities, or Portfolio Items in
    Agile Requirements Designer
    Studio. To filter which of them you want to see in the Connectors dock, go to
    Home > General Config > Connectors Options > Rally
  • You can now choose for integrations whether you want to
    "check whether existing links can be updated"
    when exporting. When enabled, the exporter identifies whether generated test cases exist from prior exports, and the export dialog then offers to update these items, instead of creating them. This means when you regenerate and update paths, you no longer have to browse the tree manually to select the target project. Enable this feature in the
    General Configuration
    Connectors Options
    for the BlazeMeter, qTest, and Jira integrations.
  • When importing Microsoft Visio diagrams with unconnected blocks,
    Agile Requirements Designer
    now asks whether you want to connect orphaned blocks to Start and End blocks. You can now also import diagrams with swim lanes; vertical swim lanes will be transposed to horizontal.
  • The qTest integration now supports human-readable valid values and numeric identifiers for attributes, and you can separate multiple values with commas.
  • When exporting automation scripts,
    Agile Requirements Designer
    can now replace all special characters in strings by escaped HTML entities. Enable this feature under
    Settings > Standard Settings
    , by enabling the
    "Replace special characters with HTML entities in automation"
  • We made some BPMN importer improvements.
  • ALM 15.01 single-sign on (SSO) through API key authentication is now supported.
  • Agile Requirements Designer
    now remembers the path of your current configuration file. When you open a flow,
    Agile Requirements Designer
    either uses the last saved configuration file, or it informs you which configuration file is missing so you can replace it.
  • When running the installer script, you can now also define a client-side proxy URL.
  • In the
    Test Data
    window on the
    Test Factory
    tab, you can use the
    Test Data Filter Options
    window to filter your data. When you export filtered test data as a file,
    Agile Requirements Designer
    now exports the columns as defined by the filter.

Known Issues

: After I import an SAP Solution Manager (BPMN) diagram from
Agile Requirements Designer
, some of the edges crossing multiple swim lanes are not drawn.
: Make a small change to the diagram, for example, move the source or target block, until the arrow reappears. Delete this phantom arrow, and reconnect the source and target block with a new arrow, then save the diagram.
: After a longer period of inactivity, the folders in my ALM Connectors Dock appear empty and I cannot refresh them. There is no error message.
: The ALM authentication has expired. Please log out and back in again. Your ALM administrator can alter the configured timeout duration server-side.
: When exporting test cases from the Path Explorer to one of the lifecycle integrations, I get a warning "invalid characters found".
: Do not use apostrophes, single quotes, or double quotes when storing test names or test name templates for export. Such special characters may cause integration problems. Tip: Use the Recreate Stored Paths' Names and Descriptions button in the Path Explorer to rename paths quickly.