The CreatorCon Call for Content is officially open! Get started here.

Default SLA workflow email

jammer
Tera Expert

I've been creating Incidents that are using the Default SLA Workflow.   Looking at that workflow, I expected to get email notifications at 50%, 75%, and 100% with respect to the breach time.

I'm getting the emails at both the 50% and 75% intervals, but I don't get an email when the 100% mark is reached.

Here's a specific example:

We have a SLA definition (which uses Default SLA Workflow) with a duration of 9 hours.   It has a schedule associated with it defining a business day as Monday thru Friday from 8 am to 5 pm.

I created an Incident which uses that SLA definition at 9 am on Wednesday 02/08.   Taken into consideration the duration and the schedule, the incident was set to breach on Thursday (02/09) at 9 am.   I believe this is correct.

However, I only received emails at the 50 and 75% intervals.   I got an email at 1:30 pm on Wednesday (02/08) and another at 3:45 pm on Wednesday (02/08).   This is correct.

The Incident breached/expired at 9 am on Thursday (02/09), which is correct, but I did NOT receive an email at this 100% mark.

Is my understanding of the email functionality associated with the Default SLA Workflow incorrect?   Why do I not get an email once 100% has elapsed/expired?

1 ACCEPTED SOLUTION

So, I noticed that your workflow isn't quite what comes out of the box. Last thing I can think of to try before sending to HI support. Update the workflow so it looks like out of the box.



Screen Shot 2017-02-10 at 3.26.46 PM.png


The notify assignee:


Screen Shot 2017-02-10 at 3.28.36 PM.png


The notify assignee manager:


Screen Shot 2017-02-10 at 3.29.18 PM.png


View solution in original post

31 REPLIES 31

I was told that our default sla workflow hadn't been altered from delivered version.   I think i was given incorrect information.   Clearly it has been changed.



I will rebuild the default sla workflow accordingly on Monday.   I have a good feeling this will fix my email problem.


Thanks the help guys.   As it turned out, our default sla workflow had been changed without my knowledge.   Once I changed it back to match OOB, the email functionality worked as expected.