Release Notes

Summary of enhancements, fixes, and open issues for
Agile Requirements Designer
3.1.
ard31
This section summarizes the new or updated functionalities and known issues of
CA Agile Requirements Designer
3.1. If you have questions, contact the
Agile Requirements Designer
Community forum
. The online version of the Release Notes contains the latest updates.
What's New in 3.1?
This section summarizes the new or updated functionalities and known issues of CA Agile Requirements Designer 3.1, and the 3.1.1 patch. If you have questions, contact the Agile Requirements Designer Community forum. The online version of the Release Notes contains the latest updates.
If you are not using ARD Hub, you can upgrade ARD Studio 3.1 directly. If you are using ARD Hub, follow these steps:
  • To upgrade ARD Hub 3.0 to 3.1.1, upgrade ARD Hub first, then ARD Studio.
  • To upgrade ARD Hub 2.10 and earlier to 3.1.1, upgrade ARD Studio to
    3.0
    first, then upgrade ARD Hub to 3.1, then upgrade ARD Studio to 3.1.
For more information on how to run the upgrade script, see Upgrade, Reconfigure, or Back Up ARD Hub.
Support for Multiple Automation Configurations
ARD 3.1 supports multiple Automation Configurations, one per open flow. When you save a flow, you can choose to save the associated Automation Configuration path with the flow.
When you open a flow, and the associated Automation Configuration file is not found, you now get a clear warning that contains the last known path of the missing Configuration file.
Path Explorer Improvements
In the
Cost, Complexity and Coverage
window in the Path Explorer, we have changed the percentage calculation to represent the achieved coverage better. For Nodes and Edges coverage, we now always show items covered divided by the number of all items. To use the same approach for In/Out Edge Coverage and All Pairs Coverage, disable the "Take constraints into account" checkbox.
If you enable the "Take constraints into account" checkbox, then In/Out Edge Coverage and All Pairs Coverage must be recalculated, because we display the number representing covered items divided by the number of items that can be covered without violating the constraint.
Cooperative Optimization
The new Cooperative Optimization (beta feature) has replaced the Alternative Constructive Search option as the alternative heuristic algorithm to compute paths.
  • The Cooperative Optimization automatically chooses the best heuristics based on flow structure to improve performance. It is a best fit for flows with a high reliance on loops or constraints.
  • The Cooperative Optimization provides you with preliminary partial results even if you cancel the optimization before it completes.
  • The Cooperative Optimization does not require any Loop Settings. It always finds paths that cover all requested elements, and if a loop is needed to achieve that, it searches for a path with a loop.
You use the Cooperative Optimization, for example, when the default optimization has problems because the flow is very complex, has many constraints, or many loops.
Flow Version Comparison
In the Requirements Insight web interface, you can now compare Hub flow versions.
If a project has more than one version, click
Actions..., Compare
Version
on a version folder to open the
Compare Versions
dialog. After you select two versions to compare, the web interface shows you which flows exist only in one version or only in the other. Below that, it lists all flows that are different in the two versions, and whether they were modified, renamed, or moved.
Click the name of the flow to open it in the web interface, or click the Desktop icon to open the flow in the ARD Studio Desktop application. Hover the mouse over the Hierarchy icon to view the project path and version of a flow.
compare flow versions in the ARD web interface
From ARD 3.0 on, you can open Hub flows from ARD Studio in the ARD web UI. We have implemented bidirectional linking, this means in the ARD web UI, each flow now has a button "Open flow in ARD Studio".
Bidirectional linking is useful because you will want to include Flow Links as part of your requirements or test cases. When you export Flow links into Test Case through a software lifecycle tool integration (such as ALM, Jira, Rally), your team members can click the links to review the relevant flow in either the web UI, or in ARD Studio.
To get the Flow Link in ARD Studio, right-click an open Hub flow tab, or right-click a flow in the Hub connector, then use the context menu to copy the Flow Link. You can send the Flow Link to colleagues or include it in test requirements, stories, and defects. The recipient clicks the link to open the related flow in his ARD Studio.
Remember that the sender and the recipient of the Flow Link have to be connected to the same Hub. If an ARD protocol link does not work, the target flow was either deleted, or the recipient is not connected to the sender's Hub, or the ARD Hub Links feature is disabled in the ARD Studio Settings panel.
Tricentis qTest Integration
CA Agile Requirements Designer can now connect to a qTest server through the Connectors dock. Remember to define your integration configuration mapping when you connect to your qTest server for the first time.
Supported Features:
  • Configure default fields at first-time use.
  • Define custom fields if needed.
  • Browse the list of qTest test modules and folders for a qTest project.
  • Create Modules on the qTest server straight from ARD Studio.
  • Export Stored Paths to qTest as Test Cases.
  • Right-click a test case in ARD Studio to open it in your qTest web interface.
  • Add Requirement Links to blocks, flows, and paths (Requirements Traceability)

For more information, see Integrate with qTest.
Path Explorer: Generate Test Case Descriptions
When you generate and store multiple test cases (paths), you use template functions in the Path Template dialog to generate unique path names. From 3.1 on, you can now also generate path descriptions. The generated path description is visible as a non-editable field in the Details View in ARD Studio's Path Explorer.
For example, export the Path Description field to initialize the description field in an integrated lifecycle tool with custom text. The new Path Description template consists of a concatenated header, body, and footer. Available naming template functions include the chosen outputs of the path, unique numbering, the names of specific blocks in this path, and other useful functions.

Some function names were updated in 3.1. When you load a pre-3.1 flow that uses path name templates, the templates are converted to the 3.1 format. You cannot open a flow with functions that were converted to ARD 3.1 format in older releases.
generate path descriptions
We have added a detailed page in the Reference section of the documentation that contains all available Path Description variables, including examples. For more information, see Store Paths and Path Naming Template Functions.
ARD Hub Authentication through Okta and OpenID
ARD Hub synchronizes your user accounts through Keycloak, which has built-in support to connect to LDAP or Active Directory servers. If you have users in other stores, you can now configure an identity provider for OpenID (Google, Facebook, Twitter, GitHub, LinkedIn, Microsoft, Stack Overflow) and Okta. For more information, see Add Users to ARD Hub.
log on the ARD hub through openid
Miscellaneous New and Improved
  • The Connector Dock now remembers the last used URL and user name. If you also enable the Remember Password checkbox, the Connector Dock stores the last used password, and automatically logs you in to the lifecycle tool integration.
  • You can now search and replace flow variables.
  • Subflow Link Alerts: ARD Studio identifies Hub flows with broken subflow links and offers to update them.
  • Optimizer Path Construction Settings have been simplified.
  • New keyboard shortcuts in ARD Studio:
    • To close the current tab, use middle-mouse click, ctrl-W, or ctrl-F4.
    • To quit the ARD Studio application, press Alt-F4.
Resolved Issues in Patch 3.1.1
  • If you see unresolved values similar to
    ##External Link Details[p
    19
    ][m
    11
    ]##
    in your exported paths, apply the 3.1.1 patch to fix this issue.
  • The patch also fixes a defect that prevented some users from saving paths into specific path types in the Path Explorer.
  • If you need to extend the time-out for Test Data Manager operations for large projects, you can now configure it under
    Settings, Standard
    S
    ettings
    ,
    TDM connection timeout
    and
    Hub connection timeout
    .
  • When designing a flow, connecting a subflow edge that has no input available now resets all paths to ANY.
  • The subflow validation window has been improved to include the error message shown in the Block Properties.
  • Integrations: You can now control the default behavior how to export resolve conflicts under
    Configuration, Connectors Options, <
    any integration
    >, Default: Delete excess steps from server at export
    . This is relevant in situations where you export items from ARD, and later add or edit steps in a lifecylce tool. We recommend to add and edit steps in ARD only, because ARD and the lifecycle tools cannot automatically merge changes. When you re-export from ARD, external changes are overwritten. This setting is available for all Software Lifecycle Tool integrations.
  • Jira integration: Jira has a default limit of displaying at most 1000 issues per project, and at most 50 filters results. ARD Studio displays Jira items in the
    Connector
    tab tree in descending order, based on the last-updated date, newest first. You can now configure how many Jira items are loaded under
    Configuration, Connectors Options, Atlassian Jira,
    Maximum number of issues per project/filter
    . If you need to view more than 1000 Jira issues, increase the display limit. If ARD Studio runs out of memory on your system, decrease the display limit.
  • Jira integration: Jira has a flat project structure, and it supports verb relationships between issues, such as "A blocks B". In ARD Studio, Jira projects are displayed as a tree structure with verbless bidirectional relations between issues, such as "A blocks B" and "B is blocked by A". If you prefer the Jira way, you can now enable a flattened view under
    Configuration, Connectors Options, Atlassian Jira, Flatten the project tree
    .
Resolved Issues in Patch 3.1.2
This patch updates support for PLA customers. If you report telemetry data automatically, please update to
CA Agile Requirements Designer
3.1.2.
Known Issues
Symptom:
I am using a lifecycle tool integration and ARD hangs at startup without an error message.
Solution:
Check the project names loaded from the lifecycle tool and remove unescaped XML-reserved characters. For example, remove the brackets from strings such as
<INSERT_PROJECT_NAME_HERE>
.
Symptom:
Jira stopped using the
username
that I have defined as
reporter
in the integration configuration, and export fails.
Solution:
In April 2019, Atlassian has removed the
username
and
userKey
fields from their API. In your ARD Jira integration configuration, use your Atlassian account ID (
accountId
) instead. For more information, see the Atlassian deprecation notice.
Symptom:
  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.
Solution:
The ALM authentication has expired. Please log out and back in again. Your ALM administrator can alter timeout durations.
Symptom:
When exporting test cases from the Path Explorer to one of the lifecycle integrations, I get a warning "invalid characters found".
Solution:
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.