SLA with circumstance

I've created one circumstance in a new version. The base rule is in the old version. When I try to use the SLA, it is taking the value of the old version only. If I save as the old base rule in the new version and change the urgency level then also it is taking the urgency from the old one. can anybody help?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

December 9, 2010 - 1:50pm

You need to check-in the Rule after the changes to use the new values.

December 9, 2010 - 2:06pm

I already checked in and then tried.

December 9, 2010 - 2:15pm

You might want to look at the logic to determine the circumstance and if your test data is has the new circumstance value to pickup the new values.

December 9, 2010 - 2:23pm

Now I change the value of the base one, but it's giving me some error, like 1. The ruleset of the service level is not present in the Pega-ProCom Data-Agent-Queue's access group.
In that case, either add the ruleset to the Agent's access group, or specify a different one for it.
2. The service level does not exist. Carefully check the class and spelling.
3. A database error occurred.

December 9, 2010 - 2:31pm

You shouldn't be changing the base rule. Contact your App Server administrator and get the Explicit temp directory contents / Marker file deleted and re-cycle your App Server and try it should work.

December 9, 2010 - 2:35pm

Ok, Thanks

January 6, 2011 - 12:11pm

which version are you working?

till 5.4 as per my knowledge SLA has some issue with circumstance ,it always picks up base rule.

In 5.5 there might be some fix with release notes.

January 7, 2011 - 12:38am

For the time being ,change the availability of base rule to "No" and check whether the circumstance version is fired.Once this is done you will be able to figure out where the issue is ..