Start new SLA on change of an assignment group

[sourabhdhaygude]

HI Community members,

I have an SLA which runs asynchronous. I need to cancel this SLA and start a new one based on the change of an assignment group. But as I am running these SLA's async, the system does not recognize "on change" event. Hence it does not cancel the current SLA and start a new one.

Has anyone encountered this kind of problem?

Kind regards,

Sourabh Dhaygude

[SanjivMeher]

Hi Sourabh,

Do you have your SLA configured in SLA definition table.

You can define start and stop condition there to cancel existing SLA and run a new SLA.

For ex, In our projects, when priority changes, the existing SLA gets cancelled and a new SLA gets associated.

Also can you tell me how did you configure Async SLA? Because if you are running an async business rule to trigger your SLA, async can't recognize onChange events. It is best practice to use SLA defintion instead of manually triggering SLA using scripts

[sourabhdhaygude]

Hi Sanjiv,

With the property "com.snc.sla.engine.async" you can change the SLA's to run async.

I am not at all able to see the "changes" condition in my Helsinki instance as well as personal instance. Please find below the options.

Is something wrong with my instances? Are you able to see the "changes" option?

Kind regards,

Sourabh D

[Subhajit1]

Hi Sourabh,

The Current SLA will cancel if you specify in the Reset condition to Reset the SLA when the current Assignment group changes. IMO, all SLAs are async in nature, so that should not be the problem.

Thanks,

Subhajit

[sourabhdhaygude]

Hi Subhajit,

Are you able to see the option for "changes"? I am not able to see that option in my Helsinki instance.

Also there   is an option in SLA properties to run the SLA's sync or async.

I have selected to run these SLA's async. Hence i came across this problem.

Kind regards,

Sourabh D