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.

Support Article

Property-Map-DecisionTable does not work for circumstanced rule



Unable to access circumstanced version of a decision table in an activity using the Property-Map-DecisionTable. That is, when the activity is executed, the base decision table is accessed though the circumstanced definition rule qualifies for execution.

Error Messages

Not Applicable

Steps to Reproduce

  1. Configure an activity.
  2. Use Property-Map-DecisionTable to invoke a decision table.
  3. Circumstance the decision table using the template and definition.
  4. Run the activity. The base version of the decision table is fetched each time though the circumstanced version qualifies for execution. 

Root Cause

The issue was with Property-Map-DecisionTable. It was unable to execute the circumstanced version of the rule. Else, the circumstanced rule was fetched correctly during runtime when this method was not used.


Perform the below local-change such that the Circumstance resolution uses the primary page:
  1. Break out the Property-Map-DecisionTable to another (new) activity.
  2. Invoke the new activity in the actual activity. The new activity's primary page is the page on which the circumstanced property value is set.

Published August 24, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us