Srikanth Pothkanuri (poths1)
Principal Cloud Development Engineer
Pegasystems Inc.
poths1 Member since 2018 8 posts
Posted: June 13, 2020
Last activity: June 15, 2020
Posted: 13 Jun 2020 13:53 EDT
Last activity: 15 Jun 2020 6:51 EDT

Validating branch merge submitter

As part of pre-merge validations, we need to validate the branch submitter to make sure of below ones:

  1. Submitter has all the required privileges.
  2. Submitter is not a test operator or some generic operator.

Pega provides an extension point in the pre-merge process to accommodate above validations. Below are the steps to hook our custom validations in the merge process:

  1. Save a copy of the standard “pyValidateMergeOptions” to a RuleSet available to your application.
  2. Add the steps you want the system to perform to that copy.

Below example would explain a simple scenario where we maintain a list of operator ID’s and verify if the branch submitter operator ID is in the list before each merge.


  1. Save a copy of “pyValidateMergeOptions” to a RuleSet available to your application.
  2. Create a Decision table to store a list of operators as below:


              3. Validate the operator ID in the saved copy of “pyValidateMergeOptions” and set a error message on primary page.




This would stop the merge in the wizard showing the error message if the user is not authorized.



This is a frequently asked question about Deployment Manager. Find more answers here.

DevOps Developer Knowledge Share