Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Merge branches customization

Suggest edit
Updated on April 5, 2022

You can enhance the merge process for your development team in various ways to comply with your organization's policies and procedures. You can:

  • Add preprocessing behavior
  • Add postprocessing behavior
  • Customize validation on the inputs in the Merge Branches wizard user interface

For preprocessing and postprocessing behavior, the flow rule that governs this process has two extension points as subprocesses at which you can add custom steps: pypre-mergeInstances and pyPostMergeInstances. By saving a copy of the standard rule and customizing your copy, you can override the generic behavior with custom behavior; for example:

  • Preprocessing: By customizing a copy of pypre-mergeInstances, you can provide processing that occurs before the wizard starts, such as verifying that a user's operator ID is performing the merge instead of a generic account.
  • Postprocessing: By customizing a copy of pyPostMergeInstances, you can provide processing that occurs after the wizard completes, such as sending an email notifying the team about the status of the merge.

For customized validation on inputs into the wizard user interface, you can override the extension point activity pyValidateMergeOptions.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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