Page History

...

The process above shows another set of dynamic case management concepts.

Hybrid process

...

: Automated tasks, Manual tasks, Ad-hoc tasks

...

In the process diagram of the first phase (Apply), we see a hybrid process, containing automated tasks () as well as manual tasks (no Image Removed) . Furthermore, we see flow-oriented orchestration of these tasks by means of arrows and ad-hoc () orchestration by means of preconditions (). This is a very strong feature of this process design; with Blueriq it is possible to design processes that contain the best of both worlds. The automated task ReadDataFromCivilRegister must always be performed first, this is why the task is connected to the start event of this phase by means of a flow-arrow.

...

In this phase, there is one mandatory () task, RequestProduct. A precondition will determine whether the task may be performed or not, but the phase Apply will not end unless the task is performed.

Preconditions

All other tasks can be performed in the phase as well, but the order is not set in stone, neither is the applicability of these tasks. Preconditions tell us when the tasks may be performed and (as mentioned in How to use Decision Requirements Graphs to visualize ad-hoc tasks in business process modeling here) a Decision Requirements Graph will tell what the precondition is, as shown below for the task RequestProduct.

Milestones

(Diagram will be replaced with English version)

Milestones

Milestones (in the process diagram depicted by a diamond Image Added) are used as goal for each phase. A milestone is merely a decision and is based on data and artifacts. The milestone for the phase Apply for instance is only true (and therefor reached) when the application is complete, meaning all mandatory data is provided and necessary documents are uploaded. Milestones are used to steer the phases at a high level. In theory each phase has one milestone that ends the phase and each phase (except the first one) will only be opened when the milestone of the previous phase is reached. It is very uncommon and nt advisable to design a process that can be in two phases at once or no phase at all.

Process changes

 Bla

Maintainability

In a previous article (How to use Decision Requirements Graphs to visualize ad-hoc tasks in business process modeling), we discussed how Decision Requirements Graphs help visualize ad-hoc tasks.
This article was written as a response to often heard comments on ad-hoc task modeling regarding insight and overview when modeling business processes with ad-hoc tasks rather than (work)flow oriented tasks. Using the strategy described in this article, combined with the design as outlined here, will result in dynamic processes which are not only really flexible, but also maintainable.