8 essential building blocks to create your workflow.
One of the basic elements of Dynamic Case Management is process. Process connects people, data and documents. In Rulecube we build this workflow from eight separate building blocks. With these 8 building blocks you take control of your case management:
We explain these building blocks with an example:
Suppose you are a housing association. You want to build a mid-office system that helps house applicants quickly and easily.
Action. An action or action is the execution of a business rule. That Rule can be complex or simple. An action is only executed at the specifically scheduled moment in the workflow. And it has only one outcome.
For example: A house applicant responds to a property. An Action can be: retrieving and adding the current waiting points, search points, situation points and starting points to the total number of points.
Wait. Sometimes you need to wait a while for a manual or automatic step from outside your system to be performed.
For example, when a house applicant has a week to think about whether he wants to rent the property. During that week, he can indicate in the customer portal that he accepts or rejects the property. In that case, the system waits for an incentive from the customer portal
Switch. A switch is similar to a switch in a railroad track. Like the action, you execute a business rule, but based on the outcome of that business rule, you can have different follow-up steps. A switch is appropriate for an either/or situation.
For example: If the house applicant responds by the deadline or who wants the house, the response is processed. If the house applicant does not respond by the deadline, an email is sent that the deadline has passed and the house applicant loses their rights to the property. With the switch, you control that either one or the other process is started.
Fork. A fork is a split, where several processes run in parallel. So a fork involves and/and, not either/or.
For example: A house applicant rejects a house. Then a confirmation process is started and the next step is taken for the next interested party. In addition, a process is set in motion whereby the house applicant is deducted one search point or even loses all points. This all happens simultaneously with the help of a fork.
Join. Join reduces all parallel processes started from a Fork to a single step. When all previous steps are finished, you move on.
For example: After accepting a home, the house applicant must be sent a contract and sign it and provide a copy of identification, a paycheck, and a bank statement. Those documents must be checked. Only when everything is submitted and approved, with all items of the join function completed, is the next step taken.
Delay. Some processes run better when you do nothing for a while. Delay, then, is simply waiting. It prevents you from continually making calls to third-party systems when there’s no realistic chance of getting anything yet. Or sending reminders that come across as pushy.
For example: If a house applicant has been sent a rental contract, it makes sense to wait a few days to check that it has been returned signed before sending a reminder.
Upload. This building block is specifically for submitting documents. You wait for a document to arrive.
For example, the already mentioned signed rental contract.
End. With this building block you stop the workflow. This completes the process.
For example: after the inspection has taken place and the house applicant has received the key to the new house, the process is completed.
Do you want to know more about how to combine these building blocks to create your ideal dynamic workflow? Contact us today for a personal demo using the button below.
