Previous step

Make sure that you have first completed the previous tutorial - Designing a Userview

Introducing the new Process Builder

  1. In the Design App page, click on the Processes menu on the left, and then on the Design Processes button along the top.

  2. This is the Process Builder.There are 3 main areas in the Process Builder. On the top (red), the Navigator panel contains a list of processes together with the action buttons on the right. On the left (blue), this is where the element palette is placed by default. One can move it around to suit one's style. The main panel in the middle is the Graph area (green) that contains the actual process diagram.

  3. Click on the edit icon under the process name in the Navigator. This brings up the properties dialog where you can edit the process details. Take note on the default workflow variable called status.

  4. Add Participants into the process by clicking on the green add button under current Participant. Participants represent users or roles that perform a certain task. Click on the edit button while hovering over the participant name to set its properties.

  5. Add Activities, Tools and Routes into the process diagram. Activities represent forms which require human interaction. Tools represent system or automated tasks, and routes are decision points. Use Transitions to link them all together in a flow. You may either expand your design by connecting from existing nodes or by dragging the required nodes from the element palette into the process diagram.  

  6. Ensure that the process has a proper Start and End. Click on Deploy at the top right to deploy the process to the server.

Mapping Participants to Users

  1. Once a process has been successfully deployed, return to the previous tab/window. The new process diagram will be generated after you click on OK. Joget will interpret the process diagram and load the process details.


  2. Click on Configure Mapping button along the top.


  3. The Process Mapper is one of the main highlights Joget DX.


  4. Click on the Participant to open up the Map Participants to Users.

  5. Participants defined in the process are listed in the Map Participants to Users, and you can map each participant to specific people. Click on Add/Edit Mapping to map to specific groups, users, organization chart, etc. If no mapping is done for a participant, any tasks are automatically defaulted to the current user instead.


Mapping Activities to Forms

  1. In the Process Mapper, click on an Activity to open up the Map Activities to Forms.

  2. In the Map Activities to Forms, all process activities are listed.

  3. For each activity, click on Add/Edit Form to select from a list of current forms in the app.


  4. As an example to handle an approval process, click on Create New Form to create a new Travel Approval Form. In this new form, add a Subform that displays the original submitted form, and radio buttons to capture the approval status.


  5. Configure this Subform to select the original request form.


  6. Configure the status radio button to have Approved and Rejected options.


  7. For routing purposes, an important setting in the radio button is the mapping to a workflow variable under Advanced Options. In this case, setting the mapping to status means that the value will be stored in the status workflow variable.



  8. After all the configuration, the new approval form should look similar to the following screenshot:


  9. Ensure the Activities are mapped accordingly.


Mapping Tools to Plugins

  1. By clicking on a Tool in the Process Mapper, it will open up the Map Tools to Plugins


  2. In the Map Tools to Plugins, you can map tools defined in the process to plugins. For each tool, select a Plugin and perform the necessary configuration.


Mapping Routes to Plugins

  1. To handle routing (for example approval conditions), use Routes in combination with workflow variables. To create a workflow variable, click on Design Process to access the Process Builder. Double click on the process name in the Navigator to bring up the process dialog. Click on the first small icon under the Workflow variable heading, and key in the ID of the variable e.g. status.


    Learn more about  Process Routes .

  2. Once a workflow variable has been defined, get back to the Process Mapper. By clicking on a Route it will open up the Map Routes to Plugins.


  3. In Map Routes to Plugins, you can map routes defined in the process to plugins. Select the Simple Rules Decision plugin. 

  4. In the plugin configuration,click on Add Rule and then click Add Condition. Set the Variable field to status and set the Value field to Approved. The variable status is referring to the workflow variable

  5. In the THEN rule, click on Add Action and set Type to Transition  and set Transition to transition3 (Send Approved Email). This means that this transition will occur if the value of status is "Approved".


  6. In the ELSE THEN rule, Set the Type to Transition and set Transition to transition4 (Send Rejected Email) to indicate that it is the default path to take when other conditions are not met. An example of a simple routing process is as shown below:

Test Driving the Process

  1. To perform a test run on a process, click on the Run Process button along the top of the App design process page.

Incorporating the Process into the Userview

  1. In the Design App page, click on the name of an existing userview to launch the Userview Builder.


  2. Drag a Run Process element into a menu category. This menu element allows the user to start a process from the userview.


  3. Click on Properties of the Run Process element and select the process to run.


  4. Drag an Inbox element into a menu category. This menu element provides the user with an inbox to manage their assigned workflow tasks.


  5. Save the userview, and you will be able to run and perform assigned tasks in the published userview.

Related Tutorials

  • No labels