Workflows can be linked with a generic process or with an app.

• To access Workflows, click on App Factory Icon > Process Automation > Process Designs. Open a record, and click on the tab Design.
• For Workflow applications, go to App Factory Icon > Application Builder> App Designer and then open a workflow-type app and go to step 2.

Code Components

Include Code Components in the Comidor Workflow Designer, and enhance your processes without using any coding. Users without development skills can add the following code components into the workflows to replace commands and queries:

• Set values
• Existence check
• SQL Creator
• String Utilities
• JSON Array to Excel
• Deserialize JSON

Set values

One of the available code components is the set values, where Comidor enables users to assign values to specific fields. For example, you can give to a date field the value of the current date (#DATE#), make a calculation, define a value (make a checkbox checked, or give an option in a key-value list type field), etc.

• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process as soon as this step is reached.
• In the Data map, define the fields of the workflow and the values you wish to assign to them.
  • Click on the + icon to map more fields
  • Click on the – icon to remove a row.

• In case you want to modify the Set values code component, you can click on the pencil icon and proceed accordingly.

• When you run the workflow, the Set values code component runs automatically when you reach this step. The fields defined in the map have the values you have set (eg the checkbox “Paid” will be checked, the “Travel date” will be today’s date and the “Total amount” will be calculated based on the formula and the values of the other 2 fields).

Existence check

With the existence check component, Comidor enables users to check if a record exists in a particular Comidor application. For example, you can check the existence of a contact or an account based on a defined condition (eg. email).

• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process as soon as this step is reached.
• Define in which Entity you want to search in if a record exists. Choose from the list of all Comidor applications.
• Write the Condition of your query (as if you would write it in a script)
• Choose a Response field to store the response of the check existence code component.
  • If you receive value 1, the system has found at least one query result
  • If you receive value 0, the system has not found any query result
  • You can use the response field in the workflow conditions to activate an alternative flow.

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

SQL Creator

Another code component is the SQL Creator component, which enables users to produce or execute database queries. For example, you can run an insert query in a specific table (e.g. Contacts). The SQL Creator component supports the statements: Select, Insert, Update, and Delete.

• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process as soon as this step is reached.
• Type: define the kind of operation/statement you want to perform. Choose between the Select, Insert, Update, and Delete options.
• Action: choose between:
  • Produce query – the component will form the statement, and write it on the Statement field so that the user can run it on a DB
  • Execute query – the query will be executed and the results (in case of selection) will be shown on the Results field
• Advanced Query: if checked, the advanced query text area will be displayed and the users write by themselves the query to be executed
  • Recommended for complex queries which cannot be specified otherwise
• Define in which Table, you want to search in if a record exists. Choose from the list of all Comidor applications.
• Choose fields: the field (select one field of the table) Value (select an app/process field)
  • in case of insert: the entity which will be inserted will have the value to the respective field
  • in case of update: similarly for the entity which will be updated
  • in case of select: the results of the select query for each field(1st column) will be stored in each Value(2nd column)
  • Click on the + icon to add more fields to your query.
  • Click on the – icon to remove a row.
• Write the Condition of your query (as if you would write it in a script)
• Order by: in the first row select the field which will sort the results, and in the second, specify if the sorting will be ascending or descending.
• Choose a Results field to store the response of the code component.

Examples are given below:

• You can insert a new contact with specific values in the Contacts table.
• You can update an existing contact, by providing a new email.
• You can delete all the existing contacts that have been created before a certain date.
• You can get Name, Country and Email from all the existing contacts. (select statement) In the results field, you see the JSON array of all the existing contacts in your database(the response of your query).

• You can get data such as Shipping Address, City, Vat Registration number, and other account fields from 1 existing account. (select statement) In the choose fields, you can map the account fields with process/app fields to assign values to (the response of your query). Do not forget to limit your query with a condition (e.g. where the id of the accounts table is equal to a record field where you chose 1 account “ID=”+#app.USR_SELECT_ACCOUNT#), or add ordering (eg Order by CREATE_DATETIME Descending, and it will fetch the last record added).
  

• In case you want to modify the SQL creator code component, you can click on the pencil icon and proceed accordingly.

String Utilities

Drag-n-drop the String Utilities code component into your workflow to perform common functions for a string variable (text field). Currently, the String Utilities code component supports the Index of and the Substring methods.
By using the Index of method, the user identifies the position of the first character of a string inside another. It is also a way to actually check if a character or a string exists in another.
The Substring method enables the user to get a part (substring) of a string(text) by defining the start and the end positions.

• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process as soon as this step is reached.
• Select a string field: the text or memo type field to run this code component.
• String function: choose between the options:
  • Index of
  • Substring
• Determine the Function Parameters:
  • Value to be found – for Index of: define the value of a field(runtime value) or a hardcoded value to be found in the string field selected above.
  • Start index – for Substring: add a value of the character position to start the substring
  • End index – for Substring: add a value of the character position to end the substring
• Choose the Result field to store the response of your function.

Examples:

• Search a text or memo field that includes the name of a file eg Report_January23.pdf to find the keyword “Report”.  In the String Utilities code component, choose the “Index of” function, define in the function parameter the value to be found “Report”, and choose in the result the field you wish to store the position character that the keyword was found. If the keyword is not found your number field will have the value of 0.
  • You can use this response field in your conditional paths.

• From a text field that includes the name of a file eg 1020104_January23.pdf, we want to store the unique code, which is the first 7 characters, in another field. In the String Utilities code component, choose the “Substring” function, define in the function parameters the values for start and end indexes (1 and 7 respectively), and choose in the result the field where you wish to store the unique code.

• In case you want to modify the String Utilities code component, you can click on the pencil icon and proceed accordingly.

JSON Array to Excel

One of the code components that allows you to get values from a JSON is the JSON Array to Excel. Add this code component into your workflow, get values from a JSON array and give its values to an excel type user field.

• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process as soon as this step is reached.
• Choose the memo/text field that contains the JSON array in the Input.
• Define from the list of user fields the excel type field to store the Output.
• Choose the Result text field to store the response of the code component.
  • The response will be “Error” or “Successful”.

Example: If you have received a JSON array as the response from a RESTFull web service or an SQL query, and stored it in a memo or text field, like this:

[{“ID”:”678782656625000″,”USR_STATUS”:”Reserved”},{“ID”:”678782656625800″,”USR_STATUS”:”Pending”}]

you can use this code component to show it to the end user in an excel type field, which is more user-friendly and readable than the JSON array.

Deserialize JSON

Drag-n-drop the deserialize JSON code component into your workflow, get values from a JSON object and give its values to certain fields. Comidor enables users to map the keys of a JSON object with application fields and assign its values to them.

• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process as soon as this step is reached.
• Choose the memo/text field that contains the JSON object you want to deserialize.
• Map the JSON keys with fields in which the values of the corresponding keys will be stored.
  • Click on the + icon to add more keys
  • Click on the – icon to remove keys.
• Choose the Result text field to store the response of the code component.
  • The response will be “Error” or “Successful”.

For example, if you have a response from a REST service or SQL query stored in a text/memo field in a JSON like this: [{“ID”:”678782656625000″,”USR_STATUS”:”Reserved”}]

you can use this component to get the values of each key and assign them to specific fields.

Find out more about the rest workflow components here and how to connect them with code components.

The post Code Components appeared first on Comidor Low-code Automation Platform.

The post Workflow Components appeared first on Comidor Low-code Automation Platform.

Comidor RPA components and elements allow you to automate and manage repetitive tasks. With the RPA Caller and RPA Receiver workflow components, you are enabled to retrieve or exchange data with other systems.

RPA can be integrated into:

• Process initiation
• Report generation
• File upload in Comidor Document Management System (DMS)

With Comidor RPA you can:

• Automate repetitive tasks
• Increase employee productivity
• Speed up time-consuming processes

Prior to involving RPA Scripts and Agents in a workflow design, the following actions need to take place:

1. Install an RPA agent to the PC (any unit) that you wish to perform RPA tasks
2. Save Agent’s properties (needed for RPA Agent set up in Comidor)
3. Install the RPA software (e.g. we used Sikulix for the following examples)
4. Create your RPA Script including all actions that you want the RPA bot to replicate
5. Save your RPA Script (Script name needed for RPA Script set up in Comidor)

RPA Agents

To access RPA Agents, go to App Factory Icon > RPA & AI/ML > RPA Agents.

1. Click on the “+” icon at the top of the screen to open the Creation Form.
2. Type an Agent Name.
3. The field Code refers to the agent code that you gave in application properties.
4. Provide other information such as the Operating System, Version, and Description of this Agent.
5. Select the desired Save option (refer to the Quick Reference Guide).

Edit RPA Agents

1. Go to App Factory Icon > RPA & AI/ML > RPA Agents.
2. Select the RPA Agent to edit.
3. Click on the Edit button to open the Edit Form.
4. Edit the information you want and click on the desired Save option (refer to Quick Reference Guide)
   

   

Delete RPA Agents

1. Go to App Factory Icon > RPA & AI/ML > RPA Agents.
2. Select one or more RPA Agents.
3. Click on Delete to delete one or multiple RPA Agents at the same time. A confirmation pop-up box appears.

RPA Scripts

To access RPA Scripts, go to App Factory Icon > RPA & AI/ML > RPA Scripts.

1. Click on the “+” icon at the top of the screen to open the Creation Form.
2. Type in the Script Name exactly as you saved the script file in the PC Agent.
3. Field Integrated Software refers to the software you have installed at the PC Agent.
4. Provide other information such as Built with and Description of this Script.
5. Select the desired Save option (refer to the Quick Reference Guide).

Edit RPA Scripts

1. Go to App Factory Icon > RPA & AI/ML > RPA Scripts.
2. Select the RPA Script to edit.
3. Click on the Edit button to open the Edit Form.
4. Edit the information you want and click on the desired Save option (refer to Quick Reference Guide).

Delete RPA Scripts

1. Go to App Factory Icon > RPA & AI/ML > RPA Scripts.
2. Select one or more RPA Scripts.
3. Click on Delete to delete one or multiple RPA Scripts at the same time. A confirmation pop-up box appears.

RPA Components in a Workflow Design

Comidor Workflow designer offers a variety of RPA components and elements, in order to eliminate manual repetitive tasks and allow employees to focus on more significant ones.

In particular, Comidor RPA components and elements are the following:

• RPA Caller/Receiver
• RPA Selenium
• RPA Document Creator
• RPA Excel Processor
• RPA Web Scraper

RPA Caller/ Receiver

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 receive data from other systems and perform actions in Comidor workflow fields.

To access Workflows go to App Factory Icon > Workflow Automation > Workflows

RPA Caller

• Drag-n-drop the RPA Caller element.
• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process once this step is reached.
• Select which Script you would like to run at this step, from the list of RPA Scripts that you have already created.
• Select which Agent you would like 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 Runtime Value of a custom field or predefined value.

RPA Receiver

• Drag-and-drop the RPA Receiver element.
• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process once this step is reached.
• Select a user field as RPA Response to store the result of the RPA Receiver once this runs.

RPA Selenium

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

• Drag-and-drop the RPA Selenium element in the workflow design.
• Give a Title to the component.
• In the Variables table, define all the actions that you wish the bot to execute step-by-step:
  • Go to URL: select this action to define the URL that the bot should browse.
  • Sleep: select 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: select this action when not certain of how many seconds the bot should wait for an element to be displayed.
  • Click: select this action to define where the bot should click on.
  • Input-Put: select this action when you wish to add a 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 as RPA Response to store the result of the RPA Selenium once this runs. If you used more than one “Input-Get” all the values will be stored in the response field, separated with commas.

Document Creator RPA Component

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.

• Set a Template File for your document either in a Form, 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 colour, size, alignment, number format, etc. and it will be captured in the produced document.

• • 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, in order 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. Excel fields and images stored in binary fields can be added too.
  • For excel fields specify the area to be replaced in the produced document. For example, r:1:2,c:0:4 will include from Rows 2-3 and columns A-D.
  • For images, correlate the binary field that is stored, and define the size in pixels in value. E.g. 200×200.
• Choose a field to be the name of the produced document from the list of text fields in File Name.
• 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. Leave it unchecked, and the produced document will be in the same format as the template.
• In Status you can add a text field, to see the response of this component.

Excel Processor

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

• Drag-and-drop the RPA Excel Processor component.
• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process once 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 – select this action to return values of cells or an entire area of the excel and store them in user fields.
  • Get No of Sheets – select this action to get the number of the sheets in the uploaded excel (useful for large excel files with multiple sheets)
  • Find in Sheet –  select this action to find a certain value in excel. Define the Search Index.
  • Find the row in Sheet – select this action to find a specific value in excel and get the entire row as a response.
    

    

• Select 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 to guide through.
• 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 user field as RPA Response to store the result of the RPA Excel Processor once this runs.

RPA Web Scraper

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

• Drag-and-drop the RPA Web Scraper element in the workflow design.
• Give a Title to the component.
• Set the Parent Stage which is the stage of the parent process once this step is reached.
• Choose whether you want a hardcoded or Dynamic source
  • In the dynamic source option, define fields as host and port; those fields should get value in a previous step
  • Alternatively, type a host and port to the respective fields.
• Define the URL that you wish to be scraped. Select a text field type.
• Choose the Search selector from the variety of options (xpaths, class, id, etc) based on the website you are scraping.
• Define the Selector (based on the Search option above). Select a text field type.
  • 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 as RPA Response to store the result of the RPA Web Scraper once this runs.

Find out more on how to create and manage workflows, including RPA components, and learn about all Comidor Workflow Elements.

The post Robotic Process Automation (RPA components) appeared first on Comidor Low-code Automation Platform.

Machine learning is an application of artificial intelligence (AI) that focuses on the development of computer programs that can access data and use it to learn for themselves. Comidor provides ML models such as Predictive ML Models and ML Text Classification Models in order to enhance Digital Process Automation. Use existing data to train your ML Models and get predictions on specified user fields. With Comidor ML Text classification model, assign tags or categories to text according to the field content.

With Comidor ML models you can:

• Enhance process automation
• Eliminate errors
• Save processing time

Comidor ML Text classification can be used for:

• Topic labeling
• Spam detection
• Intent detection

ML Predictive Models

To access ML Predictive Models, go to App Factory Icon > RPA & AI/ML > Predictive Models.

1. Click on the + Icon at the top of the screen to open the Create Form.
2. Type a Title for your ML Predictive Model.
3. Link the Model with a Connected Application or select the respective Entity.
4. Choose your preferred Classifier: 
   • Comidor offers a variety of algorithms that sort data into labelled classes or categories of information, such as J48, DecisionTable, DecisionStump, etc.
5. The Target field refers to the field you want to make the prediction for. Depending on the entity you have selected above, it will populate relevant fields to choose from.
6. Add 2 or more Training fields:
   • The values of these fields will be used by the classifier.
   • The user fields available here are linked to the entity you have chosen.
7. Limit training data with a condition to define specific values to be used by the classifier.
8. Select the desired Save option (refer to the Quick Reference Guide).

Edit ML Predictive Models

1. Go to App Factory Icon > RPA & AI/ML > Predictive Models.
2. Select the ML Predictive Model to edit.
3. Click on the Edit button to open the Edit Form.
4. Edit the information you want and click on the desired Save option (refer to Quick Reference Guide)
   

   

Train ML Predictive Models

After creating your ML Predictive Model, you have to train the Classifier based on the data entered in Comidor. The training process might take a while. The more data we have, the better the Accuracy we achieve.

1. Go to App Factory Icon > RPA & AI/ML > Predictive Models.
2. Select the ML Predictive Model to train.
3. Click on the Train button. Click on this option as many times as you wish, until you reach an acceptable Accuracy rate.
4. Click on the Save button that is appearing next to the Accuracy percentage. The ML Predictive Model is ready to be used in a workflow.

Delete ML Predictive Models

1. Go to App Factory Icon > RPA & AI/ML > Predictive Models.
2. Select one or more ML Predictive Models records.
3. Click on Delete to delete one or multiple ML Predictive Models at the same time. A confirmation pop-up box appears.

ML Text Classification

To access ML Text Classification, go to App Factory Icon > RPA & AI/ML > Text Classification.

1. Click on the + Icon at the top of the screen to open the Create Form.
2. Type a Title for your ML Text Classification.
3. Link the Classification with a Connected Application or select the respective Entity.
4. The Target field refers to the field you want to make the prediction for. Depending on the entity you have selected above, it will populate relevant text fields to choose from.
5. Add Training field:
   • The values of this text field will be used by the Text classifier.
   • The text user fields available here are linked to the entity you have chosen.
6. Limit training data with a condition to define specific values to be used by the Text Classifier.
7. Select the desired Save option (refer to the Quick Reference Guide).

Edit ML Text Classification

1. Go to App Factory Icon > RPA & AI/ML > Text Classification.
2. Select an ML Text Classification to edit.
3. Click on the Edit button to open the Edit Form.
4. Edit the information you want and click on the desired Save option (refer to Quick Reference Guide).

Train ML Text Classification Model

After creating your ML Text Classification model, you have to train the Classifier based on the data entered in Comidor. The training process might take a long time to fetch accurate results. The more data we have, the better Accuracy we achieve.

1. Go to App Factory Icon > RPA & AI/ML > Text Classification.
2. Select the ML Text Classification Model to train.
3. Click on the Train button. Once you click on this option, you can see the Accuracy rate of the Text Classifier. Click on this button as many times as you wish, until you reach an acceptable Accuracy rate.
4. Click on the Save button. The ML Text Classification Model is ready to be used in a workflow.

Delete ML Text Classification

1. Go to App Factory Icon > RPA & AI/ML > Text Classification.
2. Select one or more ML Text Classification records.
3. Click on Delete to delete one or multiple ML Text Classifications at the same time. A confirmation pop-up box appears.

Add a Predictive ML in the workflow design, to trigger an ML Predictive Model and get a prediction for the Target Field of a workflow, or a Text Classification to classify the selected Target field based on the Text Classification Model.

To access Workflows go to App Factory Icon > Workflow Automation > Workflows

Predictive ML

• Drag-and-drop the Predictive ML.
• 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.

Text Classification

• Drag-and-drop the Text Classification 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 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 field(s) that were selected in the ML Text Classification Model in view-only mode.

Find out more on how to create and manage workflows step by step and learn all about Comidor Workflow Elements.

The post ML Predictive Models & ML Text Classification appeared first on Comidor Low-code Automation Platform.

Most business processes include authorisation steps and document approvals.
With the Comidor Signature Models & Digital Signature component you can automatically include digital signatures to PDF documents.

Incorporate the Comidor digital signatures in your business processes with the following steps:

1. Draw or upload your personal signature
2. Create a signature model
3. Connect the digital signature component in your workflow

With Comidor Signature Models & Digital Signature component you can:

• Enhance process automation
• Eliminate errors
• Save processing time

1. Draw or upload your personal signature

Every user can specify their own digital signature, which can be used in PDF documents of a workflow.

• Go to the user icon on the top right of your screen > Settings.

• In the pop-up window, select the Signature tab.
• You can click on the “Design your signature” button.
  

  

  • In the pop-up window, you can draw your signature with your mouse.
  • Click on the “Clear” button to erase your drawing or on “Sav”e to store it.
• Alternatively, click on the “Upload your signature” button to upload an image file from your desktop.

• Click on “Save Changes” so as to store the signature settings.
  • A refresh of your browser is also required.

2. Create a signature model

In the second step, you should create one or more signature models, to provide PDF templates with the pages and exact parts of the document where you wish the signatures to be added.

To access Signature Models, go to App Factory Icon > RPA & AI/ML > Signature Models.

1. Click on the + Icon at the top of the screen to open the Creation Form.
2. Type a Title for your Signature Model.
3. Choose a Document in PDF format as your template.
4. Select the desired Save option (refer to the Quick Reference Guide).

After saving your Signature Model, you can get a preview of the document you uploaded.

1. The document you have uploaded in the creation form is displayed per page so you can select which page you would like to view.
2. Click on the “Add signature” icon, to add as many signatures needed to be included in your document.
   1. A signature box will be displayed in your page with an incremental number as title (Signature 1, Signature 2, etc).
   2. You can drag-and-drop the signature box and place it easily in the spot you wish to be displayed.
   3. The signature box can be also resized (from the bottom corner) or deleted.
   4. Any change you made in your model is automatically saved.

Edit Signature Models

1. Go to App Factory Icon > RPA & AI/ML Automation > Signature Models.
2. Select the Signature Model to edit.
3. Click on the Edit button to open the Edit Form.
4. Edit the information you want and click on the desired Save option (refer to Quick Reference Guide)
5. Any change you made in your model view form (signature spots, size, etc.) is automatically saved.
   

   

Delete Signature Models

1. Go to the App Factory Icon > RPA & AI/ML > Signature Models.
2. Select one or more Signature Models records.
3. Click on Delete to delete one or multiple Signature Models at the same time. A confirmation pop-up box appears.

3. Connect the digital signature component with your workflow

Add a Digital Signature component in the workflow design, to include digital signatures in PDF documents of your process after specific steps/approvals.

There are two options:

• Include a digital signature from a user  (as defined in their user settings); the workflow will add it automatically to the place of the document as per the signature model.
• Send an email to a recipient(workflow field), with a link. The email recipient by clicking on the link will be re-directed to another page with the full document. There, the recipient can read the whole document, switch from one page to another, draw his signature, place it in the document, resize it and finally submit it. The workflow will await until the signature is added.

To access Workflows, go to App Factory Icon > Workflow Automation > Workflows and choose the design tab.

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.).

• Check the option Send Email if you want the digital signature to be added by an external user.
  • Define the Email Recipient; choose from a list of text/email fields. This field should get value in a previous step of the workflow.
  • Type your Email body. With the rich text, you can add colours, styles, and font sizes and fully customize your email message.

Find out more on how to create and manage workflows step by step and learn all about Comidor Workflow Elements.

The post Digital Signature & Signature Models appeared first on Comidor Low-code Automation Platform.

Introducing Leia. Comidor’s new intelligent virtual assistant.

Every organisation deals with multistage internal processes, workflows, forms, rules, and regulations.

It’s vital for every employee to have access to essential information in order to perform their work efficiently and effectively.

Leia is an AI-enabled assistant that helps employees and teams work smarter, remotely, and more efficiently.

This chatbot can have quite an influence on how your employees experience their day-to-day duties. It can assist them in a more natural, more engaging, and ultimately, more human way. It is available at any time, and accessible at the right bottom of your screen.

To access the Leia chatbot, click on the chat icon at the right bottom of your screen, and a chat window will pop up.

• Simply ask a question and Leia answers the question with specific data or recommends a useful reading source.
• If the answer is large, you can see it in full view, as per Leia’s suggestion.

• Give your feedback on Leia’s answer to assist with the chatbot’s training. Simply click on Yes/No at “Was this answer helpful?”.

• Furthermore, the user can choose to send the question via email to a pre-defined email account, in case the question is not properly answered by the bot.
  • The administrator’s email should be defined by an application parameter.
• In case your question can be answered in multiple ways, the chatbot will suggest more than one answer. So, you can click on the one you wish to view in full view.

Other Actions

Leia’s capabilities have been enhanced, and apart from answering questions based on the Knowledgebase system, users can interact with Leia via slash commands:

• /add

Leia can understand the “/add” command and insert records (tasks, processes, and contacts) in Comidor.

For example, if you use the “/add” command to create a task, Leia asks proper questions to fill in mandatory fields.

After the creation, a link with the new record is displayed. Also, the new process can be created by choosing your desired process template.

• /quick

You can initiate an app with the “quick add” form via the chatbot.

When you write the “/quick” command, Leia populates a list of all “quick add” forms from the custom apps in your account. Once the desired app is chosen, Leia asks proper questions to fill in all fields from the selected form, in order to initiate a process.

• clear

This command deletes the chat history.

Don’t miss any of your important upcoming meetings or activities. Leia will alert you about your upcoming tasks.

• Leia frequently checks and alerts the user of the tasks that are scheduled for the next 30 minutes. The user receives a pop-up alert with the scheduled tasks in Leia’s chat.
• Leia’s reminder includes the title of the upcoming task and a link to open the task in full view.

Knowledge base

Through the Comidor Knowledge base unit, you can create the brain of your Leia bot.

Leia, the AI chatbot, retrieves data from a knowledge base and delivers information instantly to the end-users.

Comidor allows you to create your own knowledge base, the central repository for all the information your chatbot needs to support your employees and answer questions.

To access the Knowledge base go to Workplace > Knowledge base

Create an Answer

Click on the “+” icon to add a new record.

For every question you are able to add:

• A category, so you can group all your answers
• keywords separated in commas, that will be used as tags in the bot’s answers
• The relevant answer; type a paragraph with your answer here
• Any supportive links can be also included in your answer:
  • Add an explanatory URL link
  • Define the Quick Form JS Link Name and the Quick Form JS Link, so the user when clicking this link, a respective quick add form will appear.
  • Choose the Entity Link, from the list of all Comidor Entities (comidor units & custom apps). Then, choose the record that the user will open when clicking on this link.
• Click on save, save and new for multiple entries or cancel.

Edit an Answer

1. Go to Workplace > Knowledge base
2. Select one or more Sentiment Analysis records.
3. Click on the pencil icon, apply any change you wish and then save.

You can also apply multiple actions to one or more answers

1. Select one or more records.
2. Click on Delete to delete one or multiple records at the same time. A confirmation pop-up box appears.

Create your Model

After adding your questing and answers, you need to create your ai model.

• Go to Workplace > Knowledge base
• Click on the actions button>Create Model.

Now, Leia will be equipped with all those answers!

The post Leia Chatbot & Knowledge Base appeared first on Comidor Low-code Automation Platform.

The post Sentiment Analysis & Document Analyzer Models appeared first on Comidor Low-code Automation Platform.

To access Workflow Designer, click on the App Factory icon >  Process Automation >  Process Designs.

Learn how to create and manage workflows step by step.

Workflow Design

In the Design tab, you can start the Workflow creation.

Workflow Components

Basic Components: 

Comidor offers the following BPMN 2.0 basic workflow components:

• • Tasks and escalations
  • Subprocess
  • Email
  • SMS
  • Notification
  • Timer
  • AND/OR/XOR gateways
  • Annotation
  • End

Integration Components: 

Additionally, designers cover their integration needs with the following workflow components:

• • RESTful Web Service
  • OpenAI ChatGPT
  • Message Queue
  • Teams integration
  • Google Integration
  • Zoho projects API
  • Zoho leads API
  • Freshdesk API
  • Salesforce API

Data Components:

Designers use low-code data workflow components for data input and output.

• • Comidor DATA (insert/update/delete)
  • Shell Command
  • File Reader
  • Export Data
  • Convert Data
  • Digital Signature
  • Document Creator
  • QR Generator
  • Table Extractor
  • Excel Processor
  • Graph Creator
  • Blockchain

RPA Workflow Components:

Other workflow components can be added within the workflow design to enhance automation in business processes with RPA and ML/AI. Those components are:

• • RPA Caller/ Receiver
  • Sentiment Analysis
  • Document Analyzer
  • Text Classification
  • Predictive ML
  • Selenium RPA
  • Image Classification
  • Web Scraper

Code Components: 

Users without development skills can add the following workflow code components into the workflow designs to replace commands and queries:

• • Set values
  • Existence check
  • SQL Creator
  • String Utilities
  • JSON Array to Excel
  • Deserialize JSON

Basic Components

Flow Objects

In the Workflow Design panel, you may see flow objects like:

• Events
• Activities
• Gateways

Events

Having Standard Start Event and End Event already in the design area, you can add more flow objects with drag-and-drop 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 needed.

Other Intermediate Events exist:

• Email: The email element is a Throwing-Message Intermediate Event that can be used to create and send custom emails through your automated process.
• Timer: The 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 than within Activities.

Events affect the process flow and have a cause (trigger) and an effect (impact/result).

Activities

Activities refer to work performed by the 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 participant is involved and needs 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 into 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 email or type a specific email address. In order for your email to be sent, you have to set up first an email 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.

Gateways

A gateway is used to determine the branching, forking, merging, and joining of paths drawn 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.

Connectors

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 that exist in the same pool/lane.

Learn more about each Workflow Component in detail.

Swimlanes: Pool and Lanes

• Pool and Lane define the responsibility for activities (tasks/sub-processes)
• Lanes exist inside a Pool and pool boundaries represent the process that is automated with the workflow
• We may have a Pool with different Lanes (participants such as the user(s)/group(s) for process automation) or have different Pools with one Lane for different sub-processes of an automated mother process
• You can add Lanes in the Pool by clicking on the upper-left-side “+” button in the Designer. A Lane name is a free text – you may add a name of a person, department, or role
• 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 workflow management actions either referring to Design or Workflow ID:

• Choose how the conditional flow is depicted in Paths. Choose between Free, Classic, or Classic – Ignore Obstacles based on your preferences.
• Define the workflow validity period by clicking on the mini calendar icon.
• Add private or public tags to this workflow design for easier tracking and search capability.
• Leave a comment in Notes; people having access to the workflow will be notified accordingly.

Click here to view some Workflow Examples.

The post Workflow Designer appeared first on Comidor Low-code Automation Platform.