IBM Engineering Workflow Management (EWM) (formerly Rational Team Concert) includes work-item, build, and software configuration management along with planning tools, dashboards, and reports. Many organizations use EWM as their planning and reporting center. However, when members of the extended software development and delivery tool adopt specialist tools, the reports from EWM no longer reflect up-to-the-minute data.
IBM Engineering Test Management (ETM) (formerly Rational Quality Manager) is accessed via the IBM Engineering Workflow Management application. Therefore, IBM Engineering Test Management will have the same supported features, artifact types, field types, and functional limitations as IBM Engineering Workflow Management.
To access IBM ETM, you will configure a repository connection to IBM Engineering Workflow Management within the Viz application. See the instructions below for more details.
This section describes the basic steps needed to prepare your IBM Engineering Workflow Management instance for use with Viz.
We recommend that you create a new user within your external tool, to be used only for Viz. This is the user information you will enter when setting up your tool connection within Planview Viz. By creating a new user, you will ensure that the correct permissions are granted.
In general, your user account should have sufficient permissions to read artifacts in your tool.
Your user should have a secure password or token. Please be aware that Viz will not allow you to save a tool connection utilizing a weak password/token, such as 'tasktop.'
See instructions on how to create a new user in IBM Engineering Workflow Management.
Standard Authentication
Required Fields:
Kerberos/SPNEGO SSO
Required Fields:
Additional information can be found here:
Supported Work Item Type |
Applicable Repository Versions |
Unique URL? |
---|---|---|
Work items:
|
Any supported repository version: |
Yes |
Custom work item type |
Any supported repository version: |
Yes |
Containers that can be modeled as Flow Items |
Applicable Repository Versions |
Unique URL? |
---|---|---|
N/A |
||
Containers used to define which artifacts are included in an Artifact Set |
||
Projects |
Any supported repository version: |
N/A |
Planview Viz supports configuring rule-based modeling (i.e., conditional modeling) using the field types shown below.
Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not function properly.
Standard Field Type |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
Particular Repository Fields NOT Supported |
---|---|---|---|
String |
Small String Large String |
Formatted ID ID Revision |
|
Single Select |
Enumeration Team Area Project Area Process Area |
Filed Against Filed In Priority Resolution Severity Status Type |
|
Multi Select |
Enumeration List Team Area List Tags Project Area List Process Area List String List |
Tags |
|
Boolean |
Boolean |
Archived |
|