The Mykosmos/BOS has all the necessary equipment to do Business Process Management (BPM). However, in reality, the general idea in kosmos/BOS is that :
“Every record‘s insertion, modification or deletion must be an activity that is part of a business procedure.“
This way, we can show the database an “instance of the world“ and the exact path we have taken to achieve this “instance of the world.“ To clarify how we implemented the BPM in our suite, let‘s put some FAQs on it.
How do we describe the business procedure we want to implement?
We do it by building (programming) a coordinator agent for each business procedure. If some procedure breaks in sub-procedures, then we program the analogous coordinator agents for the sub-procedures.
How do we assign activities to users?
The coordinator agents assign activities to users. By using in AutoScript ‘‘bpm_assign_job‘‘ we have the opportunity to assign (programmatically) activities to users and wait (or not) the activities to finish for the procedure to forward to the next step (or steps)
How are we implementing the organization (i.e., Organogram) of a company?
Every user can have one or more roles (on the company‘s Organogram). The coordinator agents assign activities to users not only by their names (John, Clark, etc.) but also (and mainly) by the user‘s role (accountant, general director, salesman, etc.). Thus in a company fully automated, by Mykosmos/BOS coordinator agents, the flow of activities follows precisely the organization of the company (as described in the procedures of the ISO manuals)
How is OR-Split supported?
Sometimes we have to split a business procedure into parallel execution lines. In case is known in advance the number of splits we (as programmers) use in AutoScript the block of commands: