You can modify application details, such as the product rule that defines the content of the application that moves through the pipeline.

Do the following steps:

1. Do one of the following actions:

   • If the pipeline is not open, in the navigation pane of Deployment Manager, click PipelinesApplication pipelines, and then click the name of the pipeline.
   • If the pipeline is open, click the name of the pipeline.

2. Click ActionsPipeline settings.

3. Click Application details.

4. In the Development environment field, enter the URL of the development system, which is the system on which the product rule that defines the application package that moves through the repository is located.

5. In the Version field, press the Down arrow key and select the application version.

6. In the Product rule field, enter the product rule that defines the contents of the application.

7. In the Version field, enter the product rule version.

8. f you are using a separate product rule to manage test cases, in the Application test cases section, complete the following steps:

   1. To deploy test cases, select the Deploy test applications check box.

   2. In the Test application field, enter the name of the test application.

   3. In the Version field, enter the version of the test case product rule.

   4. In the Access group field, enter the access group for which test cases are run.

   5. In the Product rule field, enter the name of the test case product rule.

   6. From the Deploy until field, select the pipeline stage until which the test case product rule will be deployed.

      Note: When you use separate product rules for test cases and run a pipeline, the Run Pega unit tests, Enable test coverage, and Verify test coverage tasks are run for the access group that is specified in this section.

      For the Run Pega scenario tests task, the user name that you provide should belong to the access group that is associated with the test application.

9. If the application depends on other applications, in the Dependencies section, add those applications.

   1. Click Add.

   2. In the Application name field, press the Down arrow key and select the application name.

   3. In the Application version field, press the Down arrow key and select the application version.

   4. In the Repository name field, press the Down arrow key and select the repository that contains the production-ready artifact of the dependent application.

      If you want the latest artifact of the dependent application to be automatically populated, ensure that the repository that contains the production-ready artifact of the dependent application is configured to support file updates.

   5. In the Artifact name field, press the Down arrow key and select the artifact.

   For more information about dependent applications, see Listing product dependencies.

10. Click Save.

11. Run diagnostics to verify that your pipeline is configured correctly.

    For more information, see Diagnosing a pipeline.