Workflow Components featured | Comidor Platform

Workflow Components

Workflow Components 789 592 Comidor BPM Platform

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.

Workflow Components

Let’s zoom in on each workflow component.

Basic Components

In the Task component, you can add:

  • The title of the task is one of the required fields.
  • Parent Stage, which refers to the stage of the parent process as soon as this step is fulfilled.
  • Assigner’s name (Assigned From), selecting from a list which includes Process Creator, Admin, Assignee’s Manager, or other users.Workflow Task | Comidor Platform
  • Parent Completion Percent (%) is the completion percentage of the parent process once the current activity is completed.
  • Assignee’s name (Assigned To), selecting from a wide list of options (Abstract Options: Creator or Personnel of Process, Creator’s or Personnel Manager, Creator’s or Personnel Default group from Organizational Chart/Users’ Groups, Creator’s or Personnel Default group – Leader, Creator’s or Personnel Default group – Parent Group, Creator’s or Personnel Default group – Parent Group Leader, Role associated with a specific Functional Group/Division/Company, Account’s Responsible or Pre-defined options: User(s) name, Group Leader name(s), Group names).
  • Option to Filter group assignments according to main process assignees, meaning that a selection of “Assigned to” will be filtered according to what is added in the Main Process “Assigned to” field.
  • Form, where you can connect any User Form (that is already created).

Workflow Task | Comidor Platform

  • Show more options; by default, No is selected. If you change the option to Yes, more fields will be displayed:
    • Complete Start point, Endpoint, and Stage fields, and that information will be visible in the Business Process Guidelines of this task.
    • Define the RACI of the current task: Responsible user, Accountable user, Consulted user, and Informed user.
      • This information is visible in the RACI report as well.
    • Dynamic assignment, selecting the next assignee from a list of assignee user fields.
    • Link one or more KPIs with this task. Select from the list and click Add. In the Connected KPIs, you can see the linked KPIs and remove records if you wish.
    • Exception Assignees, which is a field where you define to whom the task will be assigned if other rules set above (group leader, role, etc) do not fetch any user.
    • Task type (work, appointment, meeting, event, etc.).
    • Define a user Activity related to this task.
    • File, where you can attach a draft of a File already uploaded in Comidor.
    • Approve/Reject Email Task in case you want this step to be completed via mail.
      • In this case, you should define the Email Task body and the recipient in Addresses either as a specific email address or in a text field of the workflow.
    • Do not display the default form option, where the basic information of the task is hidden and by selecting a custom user form above, you show the user only the important information based on your design.

Workflow Task | Comidor Platform

 

  • Change the Scheduling of this task, by defining date user fields of the workflow as Scheduled Start Date and Scheduled End Date.
    • Leave those fields empty if you wish the task to have a Scheduled Start Date the date of task creation.
  • Activity boundaries by setting the Maximum days or Maximum hours of this task duration.
    • Tip: In case you want to associate this task’s completion with the end of the whole workflow, you may put a negative numbering i.e. “-5” meaning 5 days before workflow completion.
  • Mandatory task duration field, where you ensure that the user will complete the actual duration before task completion.
  • Priority and Importance of this task.
  • Work Practice: describe the Activity that should be performed.  Add plain text or use HTML editor.
    • This information will be visible in the task’s description and the Business Process Guidelines.

Activity: SubProcess

In the SubProcess component, you can fill in most of the fields (as explained in Activity: Task), but also the following:

Connectors: Sequence/Conditional Flow

Through Conditional Flows, you can connect your workflow elements (activities, gateways, or events) and design any possible/desired alternative path. For example, once a Task is created you should connect it with the previous element with a Conditional Flow. In the conditional flow form:

  • Drag-and-drop a conditional flow from a Start Event to an Activity and select the Target State, which is the initial state of the target activity (state can be Scheduled or Running).  Type a brief description of the conditional flow that will help users in understanding this part of the workflow.Workflow conditions | Comidor Platform
  • Drag-and-drop a conditional flow from an Activity/Gateway and select the Source State and Target State, which are the trigger state (can be completed/failed/canceled) and impact state (can be scheduled/running/paused/completed/canceled/failed), respectively. Workflow conditions | Comidor Platform
  • Conditions can be added in both cases from the Advanced Conditions tab/Custom condition builder. Add further conditions through custom condition builder using either database system fields or any custom user fields you have created in User fields and have added in a User form.Workflow conditions | Comidor Platform
  • In more complicated workflows, there might be a need to combine and use more complex Advanced conditions. In these cases, the workflow will check more conditions as you can see below. Click on icons “<“,”>” to add parenthesis before or after the condition you want, and select AND, OR between the conditions in each case accordingly. With the “+” and “-” button you can add or delete a condition.

Workflow conditions | Comidor Platform

 

Once the above step(s) have been completed, a conditional flow with your brief description will be added to your workflow design between the standard start event and the task you have created or between activities/gates.

Diamonds in the conditional flow refer to Source state and arrows to Target State, blue: Running, green: Completed, black/white: Canceled, red: Failed, grey: Scheduled, orange: Paused.

Intermediate Events: Email

Email component is a Throw – Message Intermediate Event. By using it, you can send a custom email through each process that is related to the specific workflow. When adding an email element in workflows you can set:

  • The Title is one of the required fields.
  • The Parent Stage is the stage of the parent process as soon as this step is reached.
  • Variables that will appear inside the body of the e-mail. For example, set a variable Key for the Title field of the Process, or another database or custom field.
  • The Sender should be a predefined text and/or a custom text type field (probably already given in a custom form).
  • The Subject can be a predefined text and/or a custom text type field (probably already given in a custom form).
    Tip: in case of adding both predefined and custom text, the predefined text will appear first and then the custom one will follow.
  • The Email Body may be a predefined text and/or custom memo type field.
    Tip: in case of adding both predefined text and custom memo, the custom memo will appear first and then the predefined text will follow.

Workflow elements | Comidor Platform

  • For more advanced users: you can provide more details in your email body and create a paragraph, or just a sentence with data acquired during the process creation. In particular, you may use the variables you already set in a sentence with #key# as shown below. You can also apply HTML code for changing the size, font, and colors of your message.Workflow elements | Comidor Platform
  • The Recipients as:
    • Addresses that can be a predefined text with email addresses separated with a comma and/or one or more custom text type field(s) with email addresses.
    • Emails of process-related people and/or roles. These people can be users involved in the workflow, users with a specific role(s), any other users, leaders of groups, or all the members of groups.
  • Attachments as custom binary type fields.

Emails are connected with other events/gateways/activities using conditional flow.

Intermediate Events: Notifications

Set System Notifications in Workflows defining:

  • The Title is one of the required fields.
  • The Parent Stage is the stage of the parent process as soon as this step is reached.
  • The Subject can be a predefined text and/or a custom text type field.
  • The Recipients can be users involved in the workflow, users with a specific role(s), any other individual users, leaders of groups, or all the members of groups.Workflow elements | Comidor Platform

Notifications can be connected with other events/gateways/activities using conditional flow.

Intermediate Events: Timer

You can use a Timer to add a delay in your workflow by completing the below basic fields:

  • The Title is one of the required fields.
  • The Parent Stage is the stage of the parent process as soon as this step is reached.
  • Define the Region from the list of available Regional Settings, to exclude non-working days and public holidays from the delay.
  • The delay in days or hours, filling in the corresponding field.
  • Alternatively to the above, a specific date for the timer to wait or a Date field that is used within the workflow.

Workflow elements | Comidor Platform

The Timer can be connected with other events/gateways/activities using conditional flow.

 

Annotations

With the Comidor BPMN 2.0 workflow designer, you can add comments inside your design. This allows you to explain in detail what is the use of certain tasks or apply a description.

  • Drag-and-drop the Comment element.
  • In Your comments field, type your comment.

Workflow annotation | Comidor Platform

  • If you like, connect your comment with the component(s) that you wish.

Workflow annotation | Comidor Platform

  • In case you want to modify your comment, you can click on the pencil icon and proceed accordingly.

Data Components

Integration: REST

When adding a RESTful Web Service you can define:

  • The Title is one of the required fields.
  • The Parent Stage is the stage of the parent process as soon as this step is reached.
  • The URL of the resource.
  • The Method, selecting between GET, POST, or POST FORM.
  • The Request Header Parameters by giving the Parameter Name and its Value.
  • The Request Body by specifying the Key and its Value as the run-time value of a custom field or predefined value.
    Tip: By clicking on the “+” button you can add as many parameters or keys as required or needed.

    • Alternatively, you can add a JSON in the Free Text Request Body. 
  • The JSON response map by populating the Key and the respective custom Field.
    • Alternatively, click the option Show Response Code, and assign a numeric field to store the Response Code and a memo/text field to store the Response Body.

Workflow elements | Comidor Platform

 

Comidor Data (Insert/Update/Delete)

When adding a Comidor DATA object you can define:

  • The Title is one of the required fields.
  • The Parent Stage is the stage of the parent process as soon as this step is reached.
  • The Action, selecting between Insert, Update, Delete.
  • The ID Field (Runtime Value)/Value.
  • The Data Map parameters giving the Field, Field (Runtime Value), and its Value.
    Tip: By clicking on the “+” button, you can add as many parameters or keys as required or needed.
  • The Status and Message.

Workflow elements | Comidor Platform

Script Task: Shell Command

When adding a Shell Command you can define:

  • The Title is one of the required fields.
  • The Parent Stage is the stage of the parent process as soon as this step is reached.
  • The Shell Type, selecting between Unix (sh), Windows (cmd), Windows (Powershell), Platon script, Sikuli script.
  • The Shell Script Variables by giving the Key, the Field (Runtime value), and its Value.
    Tip: By clicking on the “+” button you can add as many keys as required or needed.
  • The Shell Script Body text.
  • The Shell Response.

Workflow elements | Comidor Platform

 

File Reader

With this component, Comidor enables users to check the existence of a file in a particular path and store it in a binary file.

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  •  In Layout, there are 4 options:
    • choose Read file.

Workflow elements | Comidor Platform

  • Type the exact File Name with its extension.
  • In Read From Path, select the path that the file is stored.
  • Click on the “Check Only File Existence”, if you do not need this file to be stored inside the workflow.
  • Alternatively, you can Save to File, to select a binary field from the list where the file will be stored within the workflow.
  • You can create a text field and set it as the Response field, to see the response of this component.

Workflow file reader | Comidor Platform

Secondly, users can import data from a file either from a specific path or from a binary field that is used within the workflow in a previous stage.

  • In Layout, choose Import Data.
  • Type the exact File Name with its extension.
  • In Read From Path, select the path that the file is stored.
  • Alternatively, in Read From File, select the name of the binary field that the file is stored.
  • In Entity, define in which table you wish the data of the file to be imported (Units, Apps).
  • In case you select Processes you should also define the Internal Type (General, Project, Issue, etc.).
  • Define the Start to read from row No.
  • Define if the CSV file Delimiter is semicolon or comma.
  • Set the Date, Time, and Number Format if you have those types of fields in the file.

Workflow file reader | Comidor Platform

  • In Before Save Script, you can type any additional scripts you wish to execute before the completion of the File Reader component.
  • Then, correlate the fields from the Table you have chosen with the respective columns of the CSV file.
  • You can create a text field and set it as the Response field, to see the response of this component.

Finally, there are 2 more options:

  • Read text from File – use this layout when you want to upload a binary field and store its content to a memo field.
    • Save text of File to: select a text/memo field to store the text of the binary file
    • Read text from File: select the binary field that you want to be read

Workflow components | Comidor Platform

  • Read text from URL– use this layout when you want to read a file from a URL and store its content in a memo field.
    • Save text of File to: select a text/memo field to store the text of the URL file
    • Read text from URL: select the text field that the URL will be typed so it can be read

Export Data

With this element, users can export any data from a workflow to a CSV file and make their own reporting.

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • In Entity, define the table of which you wish the file data to be exported (Units, Apps).
  • In case you select Processes you should also define the Internal Type (General, Project, Issue, etc).
  • Select the fields you wish to be exported and displayed in the CSV file as columns.
  • Type the conditions that you want to be met in your export in Where Condition.

Workflow export data | Comidor Platform

  • In Export Path, select the path that you wish the file to be stored in.
  • Alternatively, in Binary, select the name of the binary field that you wish the file to be stored in.
  • Give a File Name to the exported CSV.
  • You can create a text field and set it as the Response field, to see the response of this component.

Convert Data

With the Convert Data component, you can convert an excel file to CSV format and store it in a User field inside a workflow. Define the binary field, where you will upload the file, and a memo field where the content of the CSV file will be visible at.

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • In Converted Type select Excel to CSV.
  • In the field Convert From select the binary user field where you will upload the Excel file.
  • In the Convert To define the memo user field where the CSV will be displayed in.

Workflow components | Comidor Platform

Digital Signature

  • Drag-and-drop the Digital Signature in the workflow pool.
  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Signature Document: choose the binary field, where the user will upload the document in PDF format without signatures. After the digital signature component runs, the selected binary field will store the PDF document with the signature.
  • Select which Model you would like to run at this step, from the list of the Signature Models that you have already created.
  • User’s Signature: choose which user’s signature you want to add to your document.
  • Signature position at Document: refers to the number of the signature that you need to place in your document (Eg. 1, 2, etc.).

Digital Signature | Comidor Platform

 

Document Creator

Create invoices, reports, or other types of documents by combining a file template format and fields of the workflow.

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.

    Document creator | Comidor Platform

  • Set a Template File for your document either in a Form, or upload it in a step of the workflow in a Binary Field, or give the Template Name of a file stored in DMS.
    •  Form: Select the User Form in which you have uploaded the Template Tile. (fixed template scenario)
      • The Template file should be either .docx or .xlsx.
      • The produced file can be either .docx, .xlsx, or .pdf.
      • Apply format options in your template such as font color, size, alignment, number format, etc. and it will be captured in the produced document.

Document creator | Comidor Platform

    • Binary Field: Select the binary field in which the Template File will be uploaded during the workflow. (dynamic template scenario)
    • Template Name: Type the name of a file stored in DMS. Keep in mind that this file should be linked with the Account of the process to be used as a template file.
  • Define the Variables being used in the Template File by providing the Key and its Value as the run-time value of a custom field or predefined value.
  • Set the binary field in which you wish to save the Response document.
  • Check the option Return PDF, if you wish the produced document to be in PDF format.
  • In Status you can add a text field, to see the response of this component.

Excel Processor

Use the RPA Excel Processor element to parse a big excel file or part of it, and capture values of certain cells into user fields or a whole area and depict it in an excel type user field.

RPA Excel Processor | Comidor Platform

  • Drag-and-drop the RPA Excel Processor element.
  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Select a binary field in the Excel Document – the document that you will upload in a previous stage.
  • Define the Action you wish the Excel Processor to perform, from the following:
    • Parse Excel – use this action to return values of cells or an entire area of the excel and store it in user fields.
    • Get No of Sheets – this action is useful for large excel files with multiple sheets. The response will be the number of the sheets in the uploaded excel.
    • Find in Sheet –  use this action when you want to find a certain value in excel. Define the Search Index.
    • Find the row in Sheet – use this action when you wish to find a specific value in excel and get the entire row as a response.
  • Check the option Create Excel From Uploaded when you want to define an area of the excel to be saved in an excel type field. The fields Read uploaded from (row), Read uploaded to (row), Read uploaded from (column), Read uploaded to (column), and  Produced Excel Field will appear.
  • In Assign to user fields map the user fields with the cells. E.g. if you want to display B2, type in Index r1c1.
  • Select a memo user field to store the Response Field after the RPA Excel Processor runs.

Message Queue

Read an existing Message Queue and create a new one within your workflows with the Comidor Message Queue element.

Workflow components MQ | Comidor Platform

  • Drag-and-drop the Message Queue element in the workflow design.
  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • In MQ type select MQ Reader if you wish to read an existing MQ
  • Define the Host and Port where the MQ is stored, and the Routing Key is the title of the MQ
  •  Add your credentials (Username and Password fields)
  •  In Write to select a memo user field to store the Message Queue that will be read

Workflow components MQ | Comidor Platform

  • Alternatively, in MQ type select MQ Writer if you wish to create a new MQ
  • Define the Host and Port where the MQ will be stored, and the Routing Key is the title of the MQ
  • Add your credentials (Username and Password fields)
  • In Free Text Message Body type your Message that will be stored in the MQ that you defined in Routing Key above.
    • You can also include values of fields (e.g. #app.USR_NAME# for app fields and #this.USR_NAME# for database/process fields)
  • Alternatively, you can click the option Hardcoded Body. A new field will appear to select the user field where you have set the Value with script in a previous step.

RPA Components

RPA Caller/ Receiver

With the Comidor BPMN 2.0 workflow designer, users can involve RPA agents within their processes. Add an RPA Caller in various steps of the workflow design, to send data from the workflow and perform a series of repetitive actions in the 3rd party system, or an RPA Receiver to perform actions and receive data from other systems Comidor workflow fields.

RPA Caller

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Select which Script to run at this step, from the list of RPA Scripts that you have already created.
  • Select which Agent to run at this step, from the list of RPA Agents that you have already created.
  • Define the Request Body by specifying the Key and its Value as the run-time value of a custom field or predefined value.

RPA Caller | Comidor Platform

RPA Receiver

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Select a user field to store the RPA Response after the RPA runs.

RPA Receiver | Comidor Platform

 

 

Sentiment Analysis

Use the Sentiment Analysis element in a workflow to identify and categorize opinions expressed in a text field of a workflow, and determine whether the writer’s attitude is positive, negative, or neutral.Sentiment Analysis | Comidor Platform

 

  • Give a Title to the element.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Select which Model you would like to run at this step, from the list of the Sentiment Analysis Models that you have already created.
  • Define the field in which the Sentiment analysis should be performed (Sentiment Analysis Field).

Supportive ML

Add a Supportive ML in the workflow design, to trigger an ML Predictive Model and get a prediction for the Target Field of a workflow.

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Select which Model you would like to run at this step, from the list of the ML Predictive Models that you have already created.

ML Predictive models | Comidor Platform

Document Analyser

With Comidor Document Analyser Models, enterprises can scan documents, e.g. invoices, and create digital copies. The text that is extracted from the document is saved in a text field and can be used within any workflow.

Document analyser | Comidor Platform

 

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Select which Model you would like to run at this step, from the list of the Document Analyser Models that you have already created.
  • Document Analyzer Field: the binary field for the file you wish to analyze.
  • You can create a text field and set it as the Response Field, to see the response of this component.

Text Classification

Add a Text Classification to classify the selected Target field based on the ML Text Classification Model.

  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Select which Model you would like to run at this step, from the list of the ML Text Classification Models that you have already created.
  • You will also see the Target field and the Training fields that were selected in the ML Text Classification Model in view-only mode.

Text Classification | Comidor Platform

RPA Selenium

Use an RPA Selenium in your workflow to replicate repetitive manual steps. Use unique CSS Selectors for specifying each element.

RPA Selenium | Comidor Platform

  • Drag-and-drop the RPA Selenium element in the workflow design.
  • Give a Title to the component.
  • In the Variable table, define all the actions that you wish the bot to execute step-by-step:
    • Go to URL: use this action to define the URL that the bot should browse.
    • Sleep: use this action to determine how many seconds should the bot wait until the next action. This depends on the loading time of each website.
    • Wait for element: use this action when you are not certain of how many seconds the bot should wait for an element to be displayed.
    • Click: use this action to define where the bot should click.
    • Input-Put: select this action when you wish to add value to a specific element. Specify the unique id of the element in “Value 1” and the value of the field in “Field(Runtime Value)”
    • Input-Get: select this action when you wish to get the value of a specific element. Specify the unique id of the element in “Value 1”.
  • Select a user field to store the Response Code after the RPA runs. If you have used more than one “Input-Get” all the values will be stored in the response field, separated with commas.

 

Image Classification

Use one or more Image Classification components in your workflow to specify images to be found within documents.

  • Drag-and-drop the Image Classification component in the workflow design.
  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Define the binary field that you wish to be scanned in the Template File.
  • Upload the Wanted Image in png that you want to be found in the template file.
  • Specify the Response field to store the outcome of the image classification.
    • In case the wanted image is found in the Template file, the response field will get the Actual value
    • In case the wanted image is not found in the Template file, the response field will show -1.

Image Classification | Comidor Platform

Web Scraper

Use an RPA Web Scraper in your workflow to find information in a selected area of a website and store it inside user fields.

RPA Web scraper | Comidor Platform

  • Drag-and-drop the RPA Web Scraper element in the workflow design.
  • Give a Title to the component.
  • Give the Parent Stage which is the stage of the parent process as soon as this step is reached.
  • Define the URL that you wish to be scrapped. Select a text field.
  • Choose the Search selector from the variety of options (xpaths, class, id, etc) based on the website you are scrapping.
  • Define the Selector (based on the Search option above) Select a text field.
    • You can have a script in a previous step and give a specific value to this field. (eg. #this.USR_SELECTOR# = “//*[@class=’v2-responsive-table__content v2-pav10′]//tbody/tr/td”)
  • Select a memo user field to store the Response Field after the RPA runs.

Find out more on how to create and manage workflows step by step.

WPversion5.6.2