Proposition changes are not propogated to other PR nodes
A R-A-P file containing the Data instances such as the below Proposition data instance classes is imported.
Steps to Reproduce
Import a zip file with the Data instances (DSM) in Pega 7.1.7.
When PRPC is running on multiple system nodes connected to the same database, Decision Management uses the SystemPulse to ensure the consistency of Propositions across all nodes. Proposition cache is invalidated when a Proposition is saved (triggered by adding or changing a Proposition) or deleted. Adding records that result in the Proposition cache to become invalid is performed through two Declare Trigger Rules that run the pyRefreshPropositions activity (pyPropositionSaved and pyPropositionRemoved in Data-pxStrategyResult.)
For Pega 7.1.7 (with DSM Services enabled) having multiple nodes connecting to the same database, user needs to configure PegaDM:Administrators Access Group under Agent Schedule for Pega-RULES: Core Engine Processing Agent to ensure the consistency of Propositions across all nodes. Below are the steps:
1. In the Records Explorer, navigate to SysAdmin > Agent Schedule.
2. Open the Pega-RULES: Core Engine Processing Agent data instances for every active node and add the PegaDM:Administrators Access Group.
3. Restart PRPC or use SMA to restart the Agents.
0% found this useful