Main Module


Start Task


The start task is the only one that differs depending on the type of process. The other tasks may or may not be present, but they are exactly the same, maintaining the same properties.


Start Task: In Main Processes


Each process can have only one start task. The process is inherently associated with a record type, allowing it to take all active records of that type. Using the 'filters' property, it is possible to narrow down this set of files by applying filters in ANSI SQL. The properties of this task are: name, description, and filter.




Manual Tray Task


This is the only manual task, and it is only found in the main process type. It causes the flow to pause until the user assigned to that task takes action. Its properties are: name, description, and duration (the number of hours available to resolve the task; if it is not resolved within this time, an alert will be sent to the involved users).



Settings:

  • Actors: Lists all Netcontent users and selects who will take action in this task.
  • Index Fields: Lists the fields of the selected record type and configures which will be visible and editable for the user.
  • Actions: Lists all the actions that the user can perform according to the record type.


Conditional Task


The conditional task evaluates a condition and, based on the response, takes one path or another. The properties of this task are: Name, Description, Field, Condition, and Value.




Field: Lists the possible existing fields of the process {cp_<field_name>} and the index fields of the record {ci_<field_name>}.


Condition: A list is presented with the following options: '=', '<', '>', '<=', '>=', '!='.


Value: The value can be entered by the user; a process field or an index field of the record can also be used. If a process field or index field is entered, the proper nomenclature must be respected.


One of the particularities of this task is that each outgoing flow must specify the condition it corresponds to, as there will be two possible outcomes: one for true and another for false. To cover more conditions, the user can create multiple nested tasks.


Field Setting Task


This task allows the creation or initialization of process fields.


It is in this task where the user can create process variables and assign them initial values. Additionally, database or C# scripts can be executed to handle a very complex task. The possible properties for this task are:




Field: You can type the desired field name, and the list will autocomplete with the fields of the existing process. If the field to be used is found, you can select it; otherwise, it will be created.


Expression: You can assign a fixed value, another process field, an existing index field, or a scripting operation to the selected field.

To do this, you must follow the established nomenclature, indicating the field within braces. If it is a process field, it will be {cp_<field_name>}, and for an index field, {ci_<field_name>}.


For a mathematical operation, the possible operators can be any recognized by C# or ANSI SQL.


An example would be performing mathematical operations like the following: ({ci_<field_name>} + 2) / 2, or taking the current date using "Now".


You can also perform complex operations, such as calculating the number of days that have passed since a given date.


For example, using an index field:



You can also add an ANSI SQL expression, such as taking a string representing a period, converting it to the YYYYMM format, taking the current date, and converting it to the same format to compare them. It will then return a 1 if the current period is greater than that of the record. Since it is SQL, it must start with BEGIN and end with END.





Database Field Update Task


This task allows you to update a field in the database.


The possible properties for this task are: name, description, field, and value.



Field: The field to update is selected from a list of index fields of the record and process fields.


Value: The value can be a user-entered value or a process field or an index field. If a process field or index field is entered, the established nomenclature must be followed.


Export Record Task:This task allows exporting a record to a physical location or a database using the preloaded connections.



The possible properties for this task include: name, description, export type (such as CSV file, JSON file, or existing connections), destination path, include details, and attach to existing content, among others, depending on the chosen export type.



Wait Time Task


This task pauses the process for a specified duration.


The properties for this task are: name, description, and duration.


Time: The amount of time to wait, in minutes. For example, if the wait time should be one day, you would enter 1440.


Database Search Task


This task allows you to search for values in a SQL Server, Oracle, or MySQL database and pass the result to process fields. It will only take the first row of the query results, so it is most commonly used when aggregation functions (COUNT, SUM, MAX, MIN, etc.) are applied.



The possible properties for this task are: name, description, connection, SQL query, and field mapping.


Connection String: The OLDB representation of the connection. The connections used here are those preloaded in the Netcontent database, specifically in the NC_Connections table.


SQL Query: An SQL query that will return results in multiple columns.


Field Mapping: Each field from the query will be loaded into the field defined here, following the order of appearance.



Email Task


This task allows you to send an email.


The possible properties for this task are: name, description, recipients, subject, and message.



Recipients: Specify one or more recipients, separated by ','.

Subject: Provide a brief text.

Message: Enter a message.


Consume SOAP Service Task


This task allows you to consume information from a SOAP service.



The possible properties for this task are: name, description, data mapping, request (WSDL and method), request headers (field and value), request message, and script.


Descriptions of some of these properties:

  • Field Mapping: The result of the service execution will be loaded into a process field. Here, you need to define the name of the process field and the internal variable used for the service execution.
  • WSDL: The endpoint of the service to be consumed.
  • Request Header: Allows you to define the headers for the service.



Request Message: The XML containing the parameters to be sent. Script: The result of the execution can be used as-is, or a parsing script can be defined. Here, you can add logic to process the result using C# or SQL scripting.




Consume REST Service Task


This task allows you to consume information from a REST service.




This task includes several properties: name, description, data mapping, request (URL and method: POST, PUT, GET, PATCH, DELETE, COPY, HEAD, OPTIONS, LINK, UNLINK, and PURGE), request headers (field and value), request message, and script.


Descriptions of some of these properties:


  • Field Mapping: The result of the service execution will be stored in a process field. Here, you need to define the name of the process field and the internal variable used for the service execution.
  • URL: The HTTP/HTTPS address of the service to consume.
  • Method: GET, POST, PUT, etc. If it is GET, the parameters can be defined directly in the URL. In the case of POST or PUT, you can use the Request Message to define the JSON to be sent.
  • Request Header: You can define the headers for the service.
  • Script: The result of the execution can be used as-is, or you can define a parsing script. Here, you can add logic to process the result using C# or SQL scripting.


End Task


Each process can have only one end task. It indicates the completion of the process.




The possible properties for this task are: name, description, and linked process.


Linked Process: The completion of one process can trigger the start of another. This will create a record of the selected process's record type.


FTP Service Task

This task allows you to exchange data with another server.



The properties for this task are: name, description, path, and the option to delete the file after sending.


Digital Signature Task


This task allows you to perform a digital signature, either via an external signature service or internally.



The possible properties for this task are: name, description, type (Viafirma or internal), status, control email, files to sign, template id, status. Some properties may change depending on the type of signature that is chosen.

Created with the Personal Edition of HelpNDoc: Easily share your documentation with the world through a beautiful website