Micro Focus ALM/Quality Center
- Last updated
- Save as PDF
Overview
Micro Focus Application Lifecycle Management (ALM) and Quality Center (QC) (formerly HPE ALM/QC) provide users with support for requirements, test, and defect management.
Testers and Testing Centers of Excellence rely on Micro Focus ALM/Quality Center to provide the infrastructure they need to execute their work.
Connector Setup Details
This section describes the basic steps needed to prepare your Micro Focus ALM/Quality Center instance for use with Viz.
Minimal User Permissions & Viz User
We recommend that you create a new user within your external tool, to be used only in 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.'
Connecting to the Micro Focus ALM/Quality Center Repository
Standard Authentication
Required Fields:
- URL
- Example Format: https://server.com:8080/qcbin
- Username
- Password
API Key Access
Required Fields:
- URL
- Example Format: https://server.com:8080/qcbin
- Client ID
- see Micro Focus ALM/Quality Center instructions here
- API Key Secret
- see Micro Focus ALM/Quality Center instructions here
Supported Artifacts
Supported Work Items
Supported Work Item Type |
Applicable Repository Versions |
Unique URL? |
---|---|---|
Defect |
Any supported repository version: |
Yes |
Supported Containers
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 |
Supported Field Types
Planview 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 |
Name Version Formatted ID |
|
|
Lookup list |
Type Subtype Direct Cover Status Priority |
|
|
Lookup list (multiple values) |
Target Release Target Cycle |
|
|
|
|
|