- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2024 07:40 AM
HI All,
We encountered an issue where the response SLA is not triggering for few of the cases, even the cases are satisfying the conditions of the response SLA.
Can someone provide your inputs here on what could be the reason for not triggering the SLA?
Thanks in Advance!!!
Manisha
Solved! Go to Solution.
- Labels:
-
Human Resources Service Delivery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2024 04:58 AM
Hi @Manisha30,
Can you update the Stop condition specifically around the state values to and 'AND' and not an 'OR'...
State is not Draft AND is not Ready (Rather than the currently configured 'or')
To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.
Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2024 04:58 AM
Hi @Manisha30,
Can you update the Stop condition specifically around the state values to and 'AND' and not an 'OR'...
State is not Draft AND is not Ready (Rather than the currently configured 'or')
To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.
Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2024 05:45 AM
Your stop condition only looks at the assigned to and because that is not empty, your SLA condition does not get attached.
The reason it is not looking at your state-field, is the 'OR' condition. An 'OR' on 'IS NOT' will always return true:
- state = draft --> true, because it is not ready
- state = ready --> true, because it is not draft
- state = new --> true, because it is not ready (or draft)
Adjust your condition to ' state is not draft AND state is not ready' or use state IS conditions.
If you change it to that, you will get a 'new' record to attach the SLA even if 'assigned to' is not empty.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2024 01:13 AM
Hi @Manisha30,
Can you confirm which table the SLA's are against. You mention 'Cases'. Using CSM (Customer Service Management) cases as an example, if a cases has an 'Assigned to' is the state set to Open rather than 'New'? Do you have any Business Rules or Logic setting the state based on Assigned to, thus changing the variables in play on the SLA Definition?
To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.
Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2024 10:22 PM
Hi @Manisha30 ,
Can you please share a snip of your SLA configuration? Then it will be much easier to help you. Also, as @Robbie have already asked. The HR case that should trigger the SLA condition, have you verified that this is on the same table?
If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
Best regards
Anders
If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.
Best regards
Anders
Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2024 11:56 PM