Advanced Search
Search Results
1657 total results found
WASB Conversations Module
The WASB Conversations module is: Integratable into VTENEXT workflows. Relatable to any native or custom module in VTENEXT. Synchronizable with the WASB address book via processes and SDK functions.
Available SDK Functions
The package automatically installs four Field Actions (identified by the WASB prefix): Send Template: Allows sending a message via the WASB Conversations module using a WASB Template (approved by Meta). Send Contact Record: Enables the creation of a cont...
vtenext Processes
Three complete VTENEXT processes are available on www.bpmconsulting.it, associated with the following modules: Ticket Management Process – TICKET MODULEAutomatically sends a comment through the WASB channel.Checks if an active conversation is linked to the ...
1.2 Process Manager Section: General Description and List of Features
GENERAL DESCRIPTION This section allows you to modify, create, import, and export BPMN processes.It is composed of the following columns: Name → represents the name of the process Description → represents the description of the process Sub-proc...
1.6 Process Helper Section: Introduction and Usage Guide
INTRODUCTION The Process Helper, as the name suggests, is a tool designed to assist those configuring processes by allowing them to create “structures” for requesting and storing data, known as “Dynamic Forms.” It consists of two main sections: HEADER FIELD...
2.1 Start Event e Timer Start Event
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...
2.2 End Event
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.
2.3 Intermediate / Boundary Event Timer
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...
2.4 Exclusive e Parallel Gateway
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...
12.15 SDK Action: Update ModLight row
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 una...
2.5 Conditional Task and Action Task
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...
2.6 CONNECTORS (CONNECTIONG OBJECT)
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.
2.7 Basic rules
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, ...
2.8 Comparison Operators: Description and Use in Conditional Tasks.
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 S...
2.9 Comparison operators: Rules of use in initial condition tasks
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)...
2.10 Configuration Section “When to run the check” in the Initial Condition Task.
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...
2.11 Configuration Section “When to run the check” in Conditional Tasks
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...
3.1 Create entity
This action allows you to create entity records present within the system (basic or custom modules). For each individual field, a static or dynamic value (thus taken from the entities involved in the process itself) can be set (Figure 1) Figure 1 To sel...