Here comes our eighth wish, because som workflow experiences show that there are further attributs missing in the BPMN 2.0 specification. Here is the general use case:
After Task A has been finished the fowolling Task B should be finished itself after a defined period of time otherwise the flow should go to Task C.
This feature is trivial and may fit in many cases, but it is not flexible enough especially in Case Management situation. Let´s have a look to the special use cases.
1. use case – user defines on the fly
Here the user must be able to define the period of time on the fly when he finishes Task A. On the workflow user interface a dialog should pop up showing the proposed date calculated on the defined period of time for the next Task B. The user sets the individual time corresponding to the konwledge he has discovered working on the case.
Request: The should be offered an attribute TimeSettingType as string for the corresponding attached interrupting timer event of Task B which can be used to flag the needed user interaction. An additional attribut TimeSettingDialog as string may cover a text which should be presented in the dialog requesting the escalation date.
2. use case – rule based escalation date
At the time Task B is reached a rule service should calculate the escalation date corresponding to the current meta data of the case.
Request: There should be offered an attribite TimeSettingRule which should hold a string for the rule service for calculating the corresponding escalation date