Skip to main content


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

Troubleshooting Decision Data rules

Updated on September 15, 2022

Use the following troubleshooting tips to help solve issues related to Decision Data rule configuration.

Pega Customer Decision Hub

Issue: Guardrail warning appears when updating Decision Data rules or Proposition Hierarchy groups

When you update a Decision Data rule or Proposition Hierarchy group, you may receive a guardrail warning. The specific troubleshooting steps differ depending on the type of object that you are editing, and whether or not the Pega 1:1 Operations Manager is present in your application stack.

Pega 1:1 Operations Manager used?Type of rule editedTroubleshooting steps
✓Proposition Hierarchy groupThe warning cannot be removed directly from the Pega 1:1 Operations Manager portal.
✓Treatment Decision Data rule
  1. Add the required Treatment Decision Data rule to the Pega 1:1 Operations Manager overlay application.
  2. Create a standard or fast-track Revision Management change request for the rule.
  3. Open and save the Decision Data rule from the change request.
  4. Resolve the change request and Revision.
NoProposition Hierarchy group
  1. In Dev Studio,open the class that corresponds to the Proposition Hierarchy group.
  2. Click Save.
NoDecision Data rule, unlocked ruleset
  1. In Dev Studio, check out the Decision Data rule.
  2. Click Save.
  3. Check in the Decision Data rule.
NoDecision Data rule, locked rulesetSave the rule to an unlocked ruleset version.

Tags

Pega Customer Decision Hub 8.7 Decision Management

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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