LinkedIn
Copied!

Table of Contents

Creating a business change pipeline

Version:

Only available versions of this content are shown in the dropdown

Business change pipelines are used to support everyday, business-as-usual changes to your application. This pipeline type allows users to respond to changing requirements by modifying and deploying application rules in a controlled manner. When you add a pipeline, you define all the stages and tasks that you want to do on each system. Pipelines are the first step in getting started with setting up a process for deploying a business change outside of an enterprise release.

The enterprise application specified in the Create application version task must have a major and a minor version defined to use a business change pipeline. See Application versioning in Pega for more information.
Applications being managed by a business change pipeline cannot automatically increment a minor version higher than v99. You must manually roll over your application version using the Create application version task, should your application or ruleset versions encounter this scenario.

Add a new business change pipeline

To add a new pipeline, follow the steps below:

  1. Click Pipelines.
  2. Click New on the top right.
  3. Select the business change pipeline template. Pipeline templates drive the required information needed to complete the creation of a pipeline. For more information, see Pipeline templates.
Remember to save your configuration if you choose to navigate away from any of the pipeline creation screens. Progress will be lost if configurations are not saved.

Configuring a new pipeline - Application Details

Application Packaging Environment

  1. Specify the environment URL from which the business changes will be merged and progressed in the Application packaging environment field and select or enter the Authentication profile to be used for connection to the application packaging environment.

Application Details

Application details specify the application that this pipeline progresses through.

  1. In the Application field, select the name of the overlay application.
  2. In the Version field, select the application version.
  3. In the Access group field, select the access group for which pipeline tasks are run.
    • This access group must be present on all candidate systems and have at least the sysadmin4 role.
  4. In the Product rule field, enter the name of the product rule that defines the contents of the application. See Configuring a product rule for more information.
  5. In the Version field, enter the product rule version.
  6. In the Pipeline name field, enter a unique name for the pipeline.

Deploy Application Test Cases

Complete the following steps to generate the artifact consisting of the test cases to run on a target environment:

  1. If you are using a separate product rule to manage your test cases, enable Configure application test cases in the Application test cases section to deploy your test case.
  2. In the Application field, select the name of the application.
  3. In the Version field, select the application version.
  4. In the Access group field, select the access group for which pipeline tasks are run.
    • This access group must be present on all candidate systems and have at least the sysadmin4 role.
  5. In the Product rule field, enter the name of the product rule that defines the contents of the application.
  6. In the Version field, enter the product rule version.

Dependencies

To configure dependent applications:

  1. Click Add in the Dependencies section.
  2. In the Application field, select the application name.
  3. In the Application version field, select the application version.
  4. In the Pipeline field, select the pipeline.
  5. In the Deployment field, select the deployment that contains the production-ready artifact of the dependent application. If you want the latest artifact of the dependent application to be automatically populated, select latest.

Merge Policy

To configure the target ruleset version used when merging branches:

  1. In the Choose the target ruleset, field, input your ruleset using the New ruleset version field.
  2. Enter the password to lock the ruleset version.

Configuring a new pipeline - Environment Details

Environments

  1. The default stages are populated based on the pipeline template created. See Pipeline templates for more information.
  2. In the Environment URL field for the system, press the Down arrow key and select the URL of the system.
  3. If you are using your own authentication profiles, in the Authentication Profile field for the system, press the Down arrow key and select the authentication profile that you want to communicate from the orchestration server to the system.
    • By default, the fields are populated with the DMAppAdmin authentication profile.
The pipeline model screen will support the addition of more than four stages.

Repositories

  1. In the Artifact management section, specify the development and production repositories through which the product rule that contains application contents moves through the pipeline.
  2. In the Development repository field, select the development repository.
  3. In the Production repository field, select the production repository.
  4. Click Next.

Configuring a new pipeline - Model Pipeline

From the model pipeline screen, you can tailor your stages and tasks to replicate the quality standard of the release process defined by your organization. You can modify the deployment process here by configuring tasks and modifying stages.

Business change pipelines offer a specific default use case, however this can be customized using the model pipeline screen.

For more information on adding, editing, or deleting a stage, see .

  1. Stages can be modified here by clicking the More icon on each stage.
  2. To add a stage, click the +Stage button. You can apply an environment template to each new stage. See Environment templates.
  3. To add a task to a stage, click the +Task button within a stage. The available tasks that you can add are specific to the associated stage. The available tasks that you can add are specific to the associated stage. For a list of task related information, see the Task catalog.
    1. The environment template assigned to a stage drives the availability of tasks. Mandatory tasks cannot be deleted.
  4. Input the enterprise application name for the input parameter of the Create application version task. SeeCreate application version task for more information.
    Configure the Application name input parameter for the Create
                            application version task.

Upgrade impact

Upgrading Deployment Manager can potentially impact the status of your business change pipeline. See the table below for any upgrade impact and how to resolve potential issues.

Created in version Upgraded to 5.1 Upgraded to 5.2 Upgraded to 5.3
4.x Recreate a new pipeline Recreate a new pipeline Recreate a new pipeline
5.1 Not applicable Recreate a new pipeline Recreate a new pipeline
5.2 Not applicable Not applicable Reuse the existing pipeline
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.