With Comidor BPMN 2.0 designer, you can map and optimize any process that takes place in your company.
To access Workflows, click on App Factory icon > Process Automation > Workflows.
Learn how to create and manage workflows step by step.
In the Design tab, you can start the Workflow creation.
In the Workflow Design panel, you may see flow objects like:
Having Standard Start Event and End Event already in the design area, you can add with drag-and-drop more flow objects in your Workflow. The Start Event Notation can be only one; a workflow may start when:
- a Process (of any type: Generic Process, Project, Opportunity, Event, Training, Issue, Ticket, Topic, Job Posting, Campaign) connected with this Workflow is set as “Running”
- a Process Template is initiated with the initial state “Running”
- a Process Schedule is triggered
Still, you may have as many End events as you wish.
Other Intermediate Events exist:
- Email: Email element is a Throwing – Message Intermediate Event that can be used to create and send custom emails through your automated process.
- Timer: Timer element is a Catching – Timer Intermediate Event that adds a timer counting delays in hours or days in your workflow.
- System Notification: Sends pre-defined or custom system messages to specific Comidor users.
Timer boundary Events and Conditional Events are depicted in Comidor differently from Activities’ inside.
Events affect the process flow and have a cause (trigger) and an effect (impact/result).
Activities refer to work performed by user(s)/group(s) (atomic or non-atomic) which can be a Task or Sub-Process (sub-process may be of any type: Generic Process, Project, Opportunity, Event, Training, Issue, Ticket, Topic, Job Posting, Campaign).
- Tasks (atomic or choreography): a task is used when the work is not broken into a finer level, while the choreography task is used when more than one participants are involved, who need to exchange messages. This piece of work is depicted in Comidor with a Workflow Task that can be assigned to one or more Personnel/Group leader(s) of a team/whole team and can be broken down manually to sub-tasks later, while the process is on the go.
- Sub-process: a process that can be broken down in a set of smaller activities (other workflows with tasks and sub-processes or call-activities) and can involve one or more participants.
- Escalation is also available. The user can set specific conditions that will trigger actions or notifications as per the user’s needs and requirements. In the task you wish to apply the escalation to, click on the upwards arrow button. A new window opens, where you can create and manage the escalations for this particular task.
Click on the “+” button to create a new escalation. In the “Basic” tab, fill in the Description, Priority and Repetition Days fields. Workflow and Stage fields are automatically set and cannot be edited.
In the “Conditions” tab, choose the conditions based on which an action or notification should be triggered. For example, in case the completion of the task is delayed by a specific amount of hours or more, a predefined action could be triggered or notifications/emails could be sent to specified users/groups.
In the “Actions” tab, you have the option to perform an action in a field related to the mother process or to a global field. In this example, when the task’s finish is delayed over 3 hours, the mother process state will be paused. The “+” and “-” buttons allow you to add or delete actions.
In the “Notifications” tab, you can select the users/groups that should receive the notification. In addition, you can add related comments in the “Content” field. The users will receive the notification in the System Notifications button of the main Notification bar.
Similarly, in the “E-mails” tab, you can either select the users/groups that should receive a predefined e-mail or type a specific e-mail address. In order for your e-mail to be sent, you have to set up first an e-mail account.
Once all the above have been completed, click on “Save” or “Save and New” if you wish to create more escalations for this task. Otherwise, click on”Cancel” if you do not want to save your entry.
A gateway is used to determine branching, forking, merging and joining of paths drew by sequence flow. In Comidor we have Exclusive, Inclusive and Parallel gateways.
- Inclusive (OR) Gateway: Inclusive Gateway refers to activating one or more flows when dividing. For incoming, all paths may be taken/fulfilled, from one to all.
- Parallel (AND) Gateway (Fork/Join): Parallel Gateway refers to dividing into two or more flows (fork). For incoming flows, the parallel gateway will wait for all incoming flows before continues (join).
- Exclusive (XOR) Gateway: Exclusive Gateway refers to choosing “either/or” and will limit the outcome to exactly one single flow of the output branches.
We use sequence flow connecting objects in Comidor.
Conditional Flow shows the order of activities; it may hold a condition (conditional flow) or stand as default flow. It connects activities/events/gateways with each other, being in the same pool/lane.
Data and Artifacts
In Comidor we store data inside the activities or inside the whole process. Data Input and Output are achieved via user forms with database or custom user fields. Still, there is an option to insert/update/delete fields in Comidor Tables (such as Personnel/Contact/Account/Project Requirement).
- Comidor Data (Insert/Update/Delete) : Ability to insert/update/delete Personnel/Contact/Account/Project Requirement fields.
- RESTful Web Service: Communicate with 3rd party systems via RESTful Web Service.
- SOAP: Comidor can connect with external applications or systems using SOAP-based Web Service in order to exchange information.
Other workflow elements can be added within the workflow design to enhance automation in business processes with RPA and ML/AI. Those elements are:
- File Reader
- Export Data
- Convert Data
- RPA Caller/ Receiver
- Document Creator
- Sentiment Analysis
- Document Analyzer
- Text Classification
- Supportive ML
Learn more about each Workflow Element in detail.
Swimlanes: Pool and Lanes
- Pool and Lane define the responsibility for activities (tasks/subprocesses)
- Lanes exist inside a Pool and pool boundaries represent the process which is automated with the workflow
- We may have a pool with different Lanes (participants such as user(s)/group(s) for process automation or have different pools with 1 lane for different subprocesses of an automated mother process)
- You can add Lanes in the Pool by clicking on the small “add” button. A Lane name is a free text – you may add a name of a person or a department name of a role name
- You can click on the pencil button to edit the name of a Swim Lane, and change its position with the arrows.
Manage Workflows Design
In general, there are some workflows management actions either refer to Design or to Workflow id:
- Firstly, in Design the Paths – how conditional flow is depicted. Choose between free, classic, or classic-by ignoring obstacles based on your preferences.
- Define the version you wish to be active, by clicking on the mini calendar icon.
- Add private or public tags to this workflow design, for easier search capability.
- You can also leave a comment in Notes. People having access in the workflow will be notified
Click here to view some Workflow Examples.