“Automation of Business Process” is a hot topic.
There seems to be a lot of excitement with words of RPA (Robotic Process Automation) come out.
Well, I am going to mention about “automation”, but it is especially a tiny one.
Questetra has a function to “set to sleep automatically for a certain period during flow of a Process“.
Sleeping in the Middle
By placing [Timer Intermediate Event] in the middle of the flow diagram, you can put the issue to sleep until restart time that has been set. It will refer to the Datetime data items that have been input at the upstream Step for the restart time. For example, in “Reservation Acceptance flow”, you can build a mechanism to transmit reminding email automatically at the downstream Step (the day before the reservation date).
Its advantage is,
* When the wake-date comes, the Process surely proceed to the next Step (as a matter of course…)
However, I have heard customer voices of Questetra users that “Want use the Sleep function with a little bit more devising“, so I am writing this to respond these voices.
Use Cases and Its Background for Using Sleep Function
In the first place, what concrete use cases there are, for example, the following cases.
Episode 482: Making A Notification at Later Date Independent as “Reminder Mechanism”?
When I design, for example, a Contract Process, I would want an Email alert (Email reminder). That is, I want to arrange an Event to transmit an email at the most downstream of the business flow…(omission)…The following Workflow is a Business Process of Email reminder part that is independent. (It is too simple to refer to as a Business Process, though.) In short, it is a mechanism that just to accept “messages” from various Business Processes, and to transmit them at “Reminding date and time”…
There, it comes to the point where”Want use the Sleep function with a little bit more devising“.
According with the use case I mentioned before, it could be considered such as
For a sales representative, it is natural for him / her to say “We welcome if you would like to renew the maintenance contract soonerly! Of course, I will manage it anyhow.”
So, this is how to realize “To bring forward the reminder notification time“.
You probably think that “Going to make it possible to change the reminder date and time during the time of sleep!」”
Even if you changed the reminder date and time during sleep, it is not reflected in the “reminder time” of Timer Intermediate Event. (It sleeps until the date and time initially set)
Well, what shall we do?
Solved with Timer Boundary Event
It can be solved by using the Timer Boundary Event(*) as above figure.
* Deadline in Each Step
The deadline for each step is set in the properties screen of the step on the flow chart. Various setting such as, ‘Finish within 12 hours after the Requested.’ or ‘Finish until desired time for the answer.’ are available. The deadlines are indicated on the list of [My Tasks], so it will help to give priorities to handle.
* When “Send time” comes, “X. Change remind date-time” ends and goes to the next step
This will be the realization of “adjustment of sleep period”.
(Though I know it’s unfair to mention in Afterword) I apologize that you may have many objections to this article.
The advantage which I mentioned that “You can ignore the matter until the wake-up date” will be lost.
That’s right. The number of matters will line up in My Task as many as the number of contract renewals.
I should have said that it was rather a workaround to complement the specification of Timer Intermediate Event.
You would better to determine whether
* The person with control privilege terminates the Issue and restart it
according to how many demands for “changing sleep period during sleeping” are there.
If you have any questions, please feel free to contact us.
Original in Japanese has written 2017-07-25
|Prev article - 50. Questetra Tips||Can Backlog and Cloud BPM Cooperate?|
|Next article - 50. Questetra Tips||How to Cooperate between Office 365 and Cloud Based Workflow|
|Another article - Masato Furukubo||Measures for “Cannot Delete Issues!”|