Question
Virtusa
IN
Last activity: 21 Jan 2025 15:34 EST
SLA is not picking highest versioned rule
Hi,
I have latest code in DT which will get triggered if SLA reaches Deadline. For testing i have checked out SLA rule with 2 min on SLA expiry my highest versioned code is not picked. When i save as the SLA in delegate version/ Branch my latest code got picked.
What could be the reason. Can anyone pls let me know.
Thanks in advance.
Maantic Inc
IN
SLA is run on the backend by an agent called ServiceLevelEvents. Agents run on the application context which does not include private checked out rules. That's why after check-in the SLA is able to recognize your changes.
virtusa
IN
Hi Soham,
Thanks for the explanation.
Even though the agent context is a higher version and the modified DT is also available in the lower version, we are still encountering the same issue.
Could there be another factor causing this?
Thanks again
Maantic Inc
IN
You're saying the DT is checked in already? I the DT in a branch? If not, is the ruleset in which its present, is added in the application context?
virtusa
IN
Yes, the DT is checked in already. It is not in a branch. The ruleset in which it's present is added in the application context.
Despite this setup, we are still facing the issue. Could there be any other factors at play?
Pegasystems Inc.
CA
Please remove the SLA rule from your branch and the delegation rule if you want to pick the rule from your highest rule version. As part of the rule resolution, it picks the rule from the branches or delegated rules over the ruleset version if there is anything available in your branch/delegated ruleset.