Configuring SLA Due Date

[Ben Gundry]

Can anyone tell me what the format options for configuring the SLA Due Date in cases/processes/tasks?

Neither the docs not Maciej Swiderski's blog's on the subject describe the format options.  There is a video where the value "1m" is entered, which indicates that is expecting a duration (though not quite in the java format).  Are there any other format options?

Also, can the SLA be set dynamically?  I tried setting a variable #{caseFile_sla}, and passing in a value when I started the case, but this came back with an error ("Unexpected error during processing request "Error parsing time string: [ #{caseFile_sla} ]"").  This is possibly a bug, because it seems to work for a standard process, but not for a case.

For cases, It would be really good to be able to set an absolute "due date", rather than an "SLA duration".  Eg. this case must be completed by June 5th.  Also, often the SLA needs to be calculated, eg. 5 business days.  So, only being able to hard-code an SLA is rather restrictive.

[Maciej Swiderski]

Wiadomość napisana przez Ben Gundry <bgu...@gmail.com> w dniu 01.06.2018, o godz. 05:12:

Can anyone tell me what the format options for configuring the SLA Due Date in cases/processes/tasks?

Is is a duration expression like:

1ms - one millisecond

1s- one second 

1m - one minute

1h - one hour

1d - one day

Neither the docs not Maciej Swiderski's blog's on the subject describe the format options.  There is a video where the value "1m" is entered, which indicates that is expecting a duration (though not quite in the java format).  Are there any other format options?

Not at the moment, duration is the most flexible option to represent time within process definition 

Also, can the SLA be set dynamically?  I tried setting a variable #{caseFile_sla}, and passing in a value when I started the case, but this came back with an error ("Unexpected error during processing request "Error parsing time string: [ #{caseFile_sla} ]"").  This is possibly a bug, because it seems to work for a standard process, but not for a case.

Yes you can do so but I believe it was added after 7.7 was released so it will be available in 7.8

For cases, It would be really good to be able to set an absolute "due date", rather than an "SLA duration".  Eg. this case must be completed by June 5th.  Also, often the SLA needs to be calculated, eg. 5 business days.  So, only being able to hard-code an SLA is rather restrictive.

That’s already there (7.8) and should cover most of the needs

Maciej 

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/06955704-fca9-488c-937d-6f16377b4c2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ben Gundry]

Thanks Maciej.  It looks like 7.8 is going to be a significant release.

[prathibha madishetty]

Hi Maciej,

We are using RHPAM 7.3. In this we have SLA Due Date field on user task level but when i gave 1m or 2d it is not giving any compilation or build issues but it is not also reflected. When i create process instance SLA complience is coming as N/A. Also the expirationTimestamp value in TASK table is not updated. It is not even getting expired after SLA.

Could you please guide me how to add SLA or how to expire my user tasks in RHPAM 7.3 using process modeler? After expiry if i want to trigger an event then what modifications do i need to do? Or do we need to write custom code? if so what class we need extend or implement?

Also i could not see any field to set process level SLA. 

Please help me.

On Saturday, 2 June 2018 14:11:41 UTC+5:30, Maciej Swiderski wrote:

Wiadomość napisana przez Ben Gundry <bgu...@gmail.com> w dniu 01.06.2018, o godz. 05:12:

Can anyone tell me what the format options for configuring the SLA Due Date in cases/processes/tasks?

Is is a duration expression like:

1ms - one millisecond

1s- one second 

1m - one minute

1h - one hour

1d - one day

Neither the docs not Maciej Swiderski's blog's on the subject describe the format options.  There is a video where the value "1m" is entered, which indicates that is expecting a duration (though not quite in the java format).  Are there any other format options?

Not at the moment, duration is the most flexible option to represent time within process definition 

Also, can the SLA be set dynamically?  I tried setting a variable #{caseFile_sla}, and passing in a value when I started the case, but this came back with an error ("Unexpected error during processing request "Error parsing time string: [ #{caseFile_sla} ]"").  This is possibly a bug, because it seems to work for a standard process, but not for a case.

Yes you can do so but I believe it was added after 7.7 was released so it will be available in 7.8

For cases, It would be really good to be able to set an absolute "due date", rather than an "SLA duration".  Eg. this case must be completed by June 5th.  Also, often the SLA needs to be calculated, eg. 5 business days.  So, only being able to hard-code an SLA is rather restrictive.

That’s already there (7.8) and should cover most of the needs

Maciej 

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-...@googlegroups.com.

[Arif Mohammed]

regarding your first question... SLA is set at node level. You will not see the SLA due date/time in Task table, look for it in NodeInstanceLog

[Yuriy Petrov]

Quite old topic, but seems it's still actual

On Saturday, June 2, 2018 at 2:41:41 AM UTC-6, Maciej Swiderski wrote:

Wiadomość napisana przez Ben Gundry <bgu...@gmail.com> w dniu 01.06.2018, o godz. 05:12:

...

For cases, It would be really good to be able to set an absolute "due date", rather than an "SLA duration".  Eg. this case must be completed by June 5th.  Also, often the SLA needs to be calculated, eg. 5 business days.  So, only being able to hard-code an SLA is rather restrictive.

That’s already there (7.8) and should cover most of the needs

Maciej 

The question - does anybody know how to set _absolute_ due date, not a duration?

And is it possible at all? I've looked at org.drools.core.time.TimeUtils (the code that parses sla strings) in drools-core - the ISO-8601 pattern is commented out. But I may miss something and absolute sla dates still may be available.

Thanks,

Yuriy