Advanced Search
Search Results
113 total results found
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...
3.2 Update entity
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...
3.3 Delete entity
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...
3.4 Send Notification
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...
12.16 SDK Action: Update DynaForm table row
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 dinamica...
3.5 Send Email
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...
3.6 Send Newsletter
This action allows you to send a newsletter directly from process related to a static or dynamic campaign defined within the "Campaign" field. MAIN FIELDS - Campaign -> represents the field through which the campaign related to the newsletter that will be se...
3.7 Create PDF
This action allows you to create a PDF document using a template defined in the "PDFmaker" section. MAIN FIELDS - Entity PDF document -> allows to select an entity on which to generate the PDF.N.B: it is not possible to select an entity (instance of a module...
3.8 Reset Dynamic form
This action refers to the use of the Process Helper and allows you to clean the content of the fields present in the dynamic form from the values that have been entered during the compilation of the same.It is mainly used to allow the re-compilation of the dyn...
3.9 Cycle Rows
This action allows you to cycle and then dynamically manage the rows of a table field or a product block. NOTE: If there is no product block or table field in the main entity involved in the process and its related modules, the action will not be visible in t...
3.10 Reset Conditional Fields
This action refers to the use of process-side conditional fields. In fact, it is possible to set conditional fields on the selected entity (involved in the process) or based on the Dynamic Forms present in the process.In the case of conditional fields on the e...
3.11 Link Entities and Link Static Entities
LINK ENTITIES This action allows to relate between them 2 dynamic entities that present a relation N - N.The 2 entities do not present a field related to each other, but the relation to N. (Figure 1) Figure 1 LINK STATIC ENTITIES This action makes it pos...
3.12 Transfer Relations
This action allows to transfer/copy related entities from one entity to another in the process.In the case of relationship 1 - N records will be transferred, while in the case of relationship N - N records will be copied.This action is useful in entity convers...