Skip to main content

 –

Modifying postprocessing behavior in the branch merge process

Suggest edit Updated on November 15, 2021

Enhance the branch merge process by customizing the postprocessing behavior in the Merge Branches wizard. For example, you can configure the wizard to send an email notification with the status of the merge process, to keep stakeholders in the case automatically informed about the merge status.

Before you begin:
  1. Create a correspondence rule named MergeRuleSetsStatus. For more information, see Creating a rule and the Rule creation module on Pega Academy.
  2. Save a copy of the standard pyPostMergeInstances subprocess. For more information, see the Creating a class to organize your customizations section in Branch merge process customization.

In the following example, you want the system to send the project lead an email notification about the status of the merge process, so you use a Utility shape and the CorrNew activity.

Note: For information about other ways to send correspondence and notifications from this process, see Engaging and notifying stakeholders and Flow shapes.
  1. In Dev Studio, in the rule form of the saved copy of the pyPostMergeInstances subprocess, check out the rule.
  2. In the process diagram of the pyPostMergeInstances subprocess, add the Utility shape:
    1. On the Diagram tab, click Flow Shapes, and then select the Utility shape.
    2. Drag the Utility shape to the flow diagram, and place the shape based on the order of events in the process.
    3. Connect the Utility shape to the process by dragging a connector from a shape that precedes the utility activity in the process to the Utility shape, and then dragging the end point of the connector from the Utility shape to the connection point of the shape that follows the utility activity on the canvas.
  3. In the properties pane of the Utility shape, give a name to the shape, for example Send email to Project Lead, and then, in the Rule field, select the CorrNew activity.
  4. In the Parameters section, in the CorrName field, select the MergeRuleSetsStatus correspondence rule.
  5. In the PartyRole field, enter Project Lead.
  6. In the EmailSubject field, enter the following email subject: Status of Merge Branches operation.
  7. Submit the updated utility properties, and then save the process.
  8. Create a work parties rule in the PegaAccel-Management-Refactor-Instances-Merge apply to class, to define the parties that you want to receive the email. Specify the same Project Lead role that is in the Utility shape properties. For more information, see Defining case participants.
Result: When the merge process completes, the system performs the postprocessing step and sends an email to the project lead by using the work parties rule.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us