Menu. Workflows

 WORKFLOWS

From this section of the menu, users can view a table listing all the workflows that have been generated. The user will be able to define workflows on the documents uploaded to the application. The document management system flow or document workflow consists of a process automation where the pre-established hierarchy intervenes, but applied to the existing documents. This means that activities are carried out with the least possible effort on the part of the personnel, i.e., through software. Thanks to workflow automation, the company will be able to significantly reduce the time invested in each process.

Through"Add", the application displays a new window to register a new workflow, where it is necessary to establish a Name and a Description identifying the flows that have been established, and then Save or Cancel.

Once we have created or generated the corresponding workflow, we can either Edit the flow by clicking on the pencil iconor Delete the flow by pressing the garbage can If you do not need to keep it, launching a popup window to confirm the elimination elimination.

In the lower right part of the table, the total number of workflows obtained as a result is shown, either without applying any type of search or filtering or applying any of the possible options. The system shows by default 10 lines per table and screen, allowing to show 15 lines or 25 lines per table and screen. It also allows forward or backward navigation in the displayed lists, depending on the pagination set.

In case you have chosen the Edit option, the system will display in the same browser window in which you are working, a main board with grids for the workflow design or task flow called"Workflow Editor". This editor offers flexibility in workflow configuration and execution. Whether you are looking for a fast console-based workflow or a full ASP.NET Core workflow server.

Designer workflows

For visual representation and management of your workflows, the workflws editor offers an easy-to-use interface to design, monitor and manage your workflows. When using the editor, you define workflows by dragging and dropping activities onto the canvas and connecting them. The underlying data model is the same as the one used for programmatic workflows and uses the Flowchart activity. In other words, when you create workflows using the editor, you are creating workflows whose Root (ownership) is established in a Flowchart (activity).

When you create workflows with the designer, input values are defined using script expressions instead of C# lambda statements. Although you can use C# script expressions in the designer, the difference is that C# script expressions are evaluated at runtime, while lambda expressions in programmatic workflows are compiled at compile time.

Workflows editing window working areas

1. Activities of available workflows:
   1. Administration.
      1. Find group: allows you to find a group of users based on the group name.
      2. Find user: allows you to find a user based on email or user name.
   2. Branching.
      1. Decision: enter a condition that has "True" or "False" outputs.
      2. Join: activity of joining several flow lines. Allows waiting for any or all of the preceding activities.
      3. Switch (flow): allows inserting as many outputs as necessary by configuring the conditions to be fulfilled in each one of them.
   3. Document explorer (Document explorer):
      1. Create smartinbox document: creation of a document based on a template.
      2. Digital signature flow: creation of a remote signature flow.
      3. Receive document: document entry activity in Waidok. Currently, this activity is the start of any document-related flow.
      4. Search document: retrieves one or more documents based on text or metadata associated with the documents in the selected collection.
      5. Update document metadata: allows you to update the metadata of a document based on the document ID or the metadata associated with the document in the selected collection.
   4. Flow:
      1. End: Indicates the end of the workflow.
   5. Forms:
      1. Receive form request response: activity that begins when the response to a form request is completed or rejected.
      2. Send custom form: sends a preconfigured form to a user or a group.
   6. HTTP:
      1. HTTP request: sending requests to data published in an HTTP.
      2. HTTP request (flow): activity that determines an action in the workflow when a given response is received from an HTTP URL (200, failed to connect, Timeout, etc.).
   7. Looping:
      1. Break: breaks the loop and exits the loop.
      2. For: executes an instruction or a block of instructions while a Boolean expression evaluates to "True".
      3. For each: executes an instruction or a block of instructions for each element of an instance of the defined type.
      4. While: executes an instruction or a block of instructions while a Boolean expression evaluates to "True". Since that expression evaluates before each loop execution, a While loop executes zero or multiple times. This type of loop differs from the Do loop because it is executed once or multiple times.
   8. Notification:
      1. Notify by email: sends an email to a user or a group of users.
   9. Primitives:
      1. Set variable: assigns values to a predefined variable.
   10. Records:
       1. Create record: creates a record of a certain type with some metadata values.
       2. Receive record: activity of entering a record in Waidok. Currently, this activity is the start of any flow related to records.
       3. Search records: retrieves one or more records based on text or metadata associated with a record type.
       4. Update record metadata: allows you to update the metadata of a record based on the record ID or the metadata associated with the record of the selected type.
   11. Scheduling:
       1. Cron: scheduling of an activity through a cron expression.
       2. Delay: delay in the execution of an activity based on a time interval.
   12. Tasks:
       1. Create approval task: generation of an approval task for a user or group of users that allows exits to approval, rejection and other.
       2. Create decision task: generation of preconfigured decision tasks with the intervention of a user or group of users that allows exits to rejection and other.
       3. Create task: generation of a simple task to be performed manually by a user or group of users.
       4. Create upload document task: generation of a document metadata update task for a user or group of users that allows outputs to update, reject and other.
2. Workflow name and save area. By default the saving is automatic, but it is necessary to publish it in order to make it operational in production. .
3. Workflow design area. Activities are dragged and merged in this work area.
4. Input and output data and information of the workflow activities. It is also possible to change the name under which we see the activities in the workflow design area.
5. Workflow configuration area. Here you can edit the workflow properties, as well as the variables, workflow input and output and view the history.
   

Example of workflow designed in Waydok

In this example/model, the design grid of the selected workflow, whose name is shown in the upper part, in this case "Sales quote", is differentiated in the central part . Below the name of the workflow, there is a toolbar that will act on the workflow tasks already defined. On the left side are shown the library of activities that are contemplated in different categories, each of them containing more options that will be able to be selected once each of them is displayed. On the right side there is a series of values and information corresponding to each of the workflows and their variables.

Let's see an example using a JavaScript expression.

The following workflow has been created using the designer:

Description of the activities in the example workflow

1. We start the flow with the entry in the system of a document from the Sales quote collection.
2. It is checked if the total budget is greater than or equal to €2,500.
   1. If the amount is equal to or greater than €2,500, it is sent for approval to a user.
      1. If approved, a task is generated for the Sales team to send to the customer.
      2. If rejected, a correction task is generated for the Sales team.
   2. If the amount is less than €2,500, a task is generated for the Sales team to send to the customer.