Skip to main content

Hi,

 

 

I don’t understand why the schedule value drops to zero when the first SLA expires. Could someone explain what is the logic behind it?

 

I have an Activity with two SLA (Primary and Secondary) and the schedule value is correct within the first SLA, but after expiring the first one it drops to zero.

 

For example one Activity with both SLA active in PSO appears:

 

Nevertheless the same Activity with the first SLA already expired appears:

 

 

At FSM all time commits are with the expected status:

 

Best regards,

Hi Joao,

Have the start and end proportions for SLA Type Secondary set up correctly?

Hi,

 

I implemented a workaround...instead of creating  two TC at the same time, I only create the second one when the first expires (BR which deletes the first one and creates the second).

 

Best regards,

Terms & ConditionsCookie settings