6.3 Example of using Process Helper to request Business Portal user data
As anticipated in the introductory chapter, one of the most common uses of the process helper concerns the creation of customized forms that can be presented to Business Portal users in order to request and save information.
For details on the conditions and requirements to be able to activate the management of processes on the Customer Portal side, we recommend consulting chapter 18.3 of the general Vtenext manual.
The blocks and fields that make up these forms are called "dynamic forms".
In order to configure a process helper, you must first configure an Action Task (create a link with a dedicated section) following the dedicated procedure (Figure 1).
NOTE: it is advisable to use the User Task symbol, as we are indicating an activity that will be charged to the user.
Figure 1SuccessivamenteAfter allathe User Task, in questothis casospecific specificocase èit fondamentaleis creareessential unato create a Task all’internowithin dellawhich qualeto eseguireperform deichecks controllito perallow permetterethe alprocess processoto distop fermarsiand epresent presentarethe ladynamic form dinamica (FiguraFigure 2).
Figure 2
Once inside the User Task (in our example “Process Helper”) in configuration mode, we will find the section called “Process Helper” with all the related fields (see Figure 3)
Figure 3
Once the main fields have been configured (Assigned to, Linked to, Action requested) we will create the necessary blocks and fields in the dynamic form in order to save the information that will be entered by the user.
To better understand how it works, below is an example of a process helper aimed at requesting approval of a flow step by filling in a single field called “Action” (Figure 4).
Figure 4
This is a picklist type field with the following 3 static values: “empty”, “APPROVATE” and “DO NOT APPROVE” and with mandatory permissions as Default (Figure 5)
Figure 5
In the associated Control Task (called “Process Helper Control”) a condition is indicated that allows the process not to continue with its flow until a value other than blank has been entered (which instead represents the default value of the picklist) (Figure 6)
Figure 6
The two conditions inserted in separate groups allow the flow to be routed in two different paths based on the item selected by the user.
On the operational side, an email is sent to the address entered in the “Email” field of the Contact or Company entered in the “Assigned to” field of the Process helper that has a button called “CLICK HERE” (Figure 7)
FiguraFigure 7Al
Figure 8
The user will simply have to click on the “Fill” button (Figure 9), fill in the “Action” field and finally click on the “Save” button (Figure 10)
Figure 9









