Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Extending custom action attributes

Updated on January 22, 2021

To enable additional Action properties in Pega 1:1 Operations Manager, extend the underlying Pega 1:1 Operations Manager implementation application.

  1. Open the Decision Data rule that corresponds to the issue and group of the action, and then click Form fieldsAdd field.
  2. Define the property according to your requirements.
  3. Complete the change request.
  4. Log in to the Pega 1:1 Operations Manager application.
  5. Open the CustomAttributesPresent When rule and click Save as to save the rule into your Pega 1:1 Operations Manager implementation layer.
  6. Set the condition for the CustomAttributesPresent rule to true.
  7. If the custom SR property is at the top-level SR class level or at group level, save the property into the Pega 1:1 Operations Manager implementation layer and set the Applies-to class to Data-pxStrategyResult.
  8. Save the ActionCustomAttributes section into Pega 1:1 Operations Manager implementation layer and edit it to include additional custom attributes.
  9. Open the DefineOfferDetails flow action rule and save it into your Pega 1:1 Operations Manager implementation layer.
  10. Save the DefineOfferDetails section into your Pega 1:1 Operations Manager implementation layer with a new name.
  11. Edit the section that you created in step 6 and include additional custom properties either directly or by embedding a separate section.
  12. Update the DefineOfferDetails flow action to refer to the section that you created in step 6.
  • Previous topic Extending the change request approval process
  • Next topic Extending the treatment sections in Pega 1:1 Operations Manager

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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