Discussion29Views×Close popoverSrikanth Pothkanuri (poths1) PEGA Principal Cloud Development Engineer Pegasystems Inc. IN View ProfileSend Message poths1 Member since 2018 8 posts PEGA Posted: June 13, 2020Last activity: June 15, 2020Posted: 13 Jun 2020 13:53 EDTLast activity: 15 Jun 2020 6:51 EDT Validating branch merge submitterAs part of pre-merge validations, we need to validate the branch submitter to make sure of below ones:Submitter has all the required privileges.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:Save a copy of the standard “pyValidateMergeOptions” to a RuleSet available to your application.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.Steps:Save a copy of “pyValidateMergeOptions” to a RuleSet available to your application.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 ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied!