Search Results

START EVENT It represents the unique point from which each individual process begins. This means that only one can be present in each process, as the flow starts from a single point.Note: It must always be followed by a control task, as this represents the ta...

END EVENT It represents the endpoint of a process.Unlike the Start Event, it can be used more than once within a single process, since the flow may end at multiple points.

INTERMEDIATE/BOUNDARY EVENT TIMER It represents an element widely used for managing the timing of task and process execution. It can be quickly selected from the menu on the left while in diagram editing mode. There are two groups of timers, which diffe...

Exclusive Gateway Allows the process flow to split into multiple different branches.It must be preceded by a control task in which the parameters are defined to determine which branch of the Gateway will be followed. To use it, in diagram editing mode, you...

Questa funzione SDK permette di eseguire un aggiornamento delle righe esistenti di un campo tabella presente su un determinato modulo. Come primo parametro va passato l'ID della riga, ossia il parametro chiave che permette di identificare in maniera univoca un...

CONDITIONAL TASK Represents the element used to perform creation and control actions within the flow of a process. ACTION TASK To define the type of task, Vtenext provides symbols that can be used to indicate the action performed by each task. These symb...

CONNECTORS (CONNECTIONG OBJECT) If the flow elements (events, activities or branches) in a process are “what actually happens,” they must be logically connected to each other. This is what connectors are for. Connectors must always have flow direction.

1 - Upon process creation, the system automatically inserts a Start Event (see Chapter 2.1 for details), which is the element that represents the unique point from which each individual process begins. There can only be one in each individual process, since, t...

The system provides several comparison operators that can be used within Conditional Tasks, which are the types of tasks that allow you to perform checks on the fields of the dynamic forms/forms involved within the process. WARNING! -> the system is “Case Sens...

Some comparison operators should be used carefully within the “Initial Condition” Tasks, i.e., those Conditional Tasks directly associated with the Start Event within which conditions are defined that allow the process to be triggered or not. (Figures 1 and 2)...

Within the “Initial Condition” Tasks, i.e., those Conditional Tasks directly associated with the Start Event within which the conditions that allow the process to be triggered or not are defined, the “When to Run Control” section is presented with the followin...

Within classic Conditional Tasks, i.e., those Tasks used to perform checks within the process, the “When to check” section is presented with the following values: - “upon change” -> the process will wait for a change in the record (instance of a form) invol...

This action allows you to create records for entities within the system (standard or custom modules). For each individual field, you can set a static or dynamic value (i.e., one derived from the entities involved in the process itself) (Figure 1). Figure 1 To ...

This action allows updating an entity (instance of a module) directly involved in the process or otherwise an entity related to them. Static or dynamic values (thus taken from the entities involved in the process itself) can be reported for each individual fi...

This action allows you to delete an entity (module instance) involved within the process. PLEASE NOTE: The record deleted by this action is not completely deleted from the Data Base but is placed in the “Trash” section. To prevent the user from encounter...

This action allows internal notifications to be sent to system users viewable in the “Notifications” section marked by an icon depicting a bell in the top right menu. Figure 1 MAIN FIELDS - Description -> represents the body of the notification; specifi...

Questa funzione SDK permette di eseguire un aggiornamento delle righe esistenti di un campo tabella presente su una form dinamica di un process helper. Come primo parametro va passato il metaid, ossia l'ID che identifica univocamente una specifica form dinamic...

This action allows you to send automatic emails with the possibility of attaching documents and linking the mail to an entity (standard or custom) in such a way that it remains historicized. In the body of the email, it is possible to report on the classic st...