Share this page

# OpenText Application Quality Management - Non Release Sub WF Subworkflow

The OpenText Application Quality Management - Non Release Sub WF subworkflow provides a modular process for change deployment that can communicate automatically with Quality Center. If no integration exists, a manual process is also provided. Figure 3-11 shows the subworkflow. OpenText Application Quality Management - Non Release Sub WF Subworkflow lists the important steps in the subworkflow and the user roles associated with those steps.

Figure 3-11. OpenText Application Quality Management - Non Release Sub WF subworkflow

Table 3-8. ALM - Non Release Sub WF subworkflow steps
Step Name | User Security | Description
--- | --- | ---
1. Approve Deployment to TEST | OpenText Application Quality Management - Change Manager | Coordinate the change implementation to the test environment.
4. Quality Process Mode | OpenText Application Quality Management - QA Manager | Determine the quality process mode, either automatic through Quality Center or manual.
5. Run Tests | OpenText Application Quality Management - Independent Tester | If manual mode is chosen in the Quality Process Mode step, the changes need to be manually tested based on test plans.
6. Quality Center Test Execution | OpenText Application Quality Management - Independent Tester | If Quality Center mode is chosen in the Quality Process Mode step, once QA signals through Quality Center that Test execution is complete, this step moves the workflow ahead.
8. Evaluate Quality | OpenText Application Quality Management - QA Manager | Approve/reject the quality of the change deployed to the test environment.
9. Impact & Resource Assessment Sub WF | (None) | Call a subworkflow to determine the impact on dependent infrastructure components and estimate the time and cost of resources, as described in OpenText Application Quality Management - Impact & Resource Assessment Sub WF Subworkflow.
15. Rework Change | OpenText Application Quality Management - Applications Development Manager | If the quality of the change deployed to the test environment is rejected, the change must be fixed.
10. Approve Deployment to LIVE | OpenText Application Quality Management - Change Manager | Coordinate the change implementation to the production environment.
14. Running Sanity Tests in Quality Center | OpenText Application Quality Management - Independent Tester | Run sanity tests in Quality Center.

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: