CREATING SUB-PROCESSES SKILLS PRACTICE SOLUTIONS

In this exercise, you will create a basic sub-process for a supervisor to review the new
vehicle that will be added and approve, deny, or request more info about it.

1. Add a new process model to the VFM Application called VFM Review Vehicle. Give
the process model a description and save it in the VFM Process Model folder.
Configure security for the model, and add a swimlane for the Supervisor.
2. Create parameterized process variables for the data that will be received from the
main model:
a. vehicle (VFM_vehicle)
b. requestor (user)
3. Create non-parameterized process variables for data that will be collected in this
process:
a. approvalDecision (text)
b. supervisorComment (text)
4. Add a user input task to the canvas, rename it, and give it a description and a
dynamic display name. Assign it to the supervisor of the registrar.

(NOTE: The process initiator must have a supervisor assigned in his/her user profile,
or you must configure the expression to handle null values by assigning the task to
VFM Supervisors if the user does not have a supervisor).
5. Add node inputs to the user input task for the data being collected on the form:
a. approvalDecision (text)
b. supervisorComment (text)
6. Add a new interface to the VFM Application. The interface should be a form with two
sections: the first to display the vehicle details for the supervisor’s review. These
fields should all be text, and read-only. The second section should be for the
supervisor’s decision and comments. These fields should both be editable. Make
sure the decision gives the supervisor three options: Approve, Reject, or Request
More information.
7. Call the interface rule from the user input task and pass in the appropriate value for
each parameter in the rule.
8. In the main process model, add the sub-process node in the Supervisor swimlane
and connect it between the “Enter Vehicle Information” node and the end event.
9. Rename the node and give it a description. In the Setup tab of the node map the
sub-process parameters to the main model data. Use the expression editor to find
the process property pp!initiator for the requestor.
10. In the setup tab of the sub-proccess, create an output for each the approval details
captured in the subprocess and map the appropriate process variables to one
another.
11. Debug the Add Vehicle process model. When you get to the sub-process node,
right-click on it and click “View Sub-Process” to open the process instance in another
tab and continue to debug. (See “Actions and Debugging” lesson for how-to debug)
APPROVAL FORM: 
Your form should look something like this:

CREATING THE SUB-PROCESS: 

Under process properties, you should have the following variables. Requestor and vehicle
are parameters because we are expecting these values from the parent process model.
We will collect supervisorComment and approvalDecision from the supervisor from this
process model so these variables should not be parameters.
Your process should look like this once you’ve added the user input task for the supervisor.
CREATING DYNAMIC TASK DISPLAY NAMES: 
In your user input task, the task should be dynamically named similar to the one below:
TASK ASSIGNMENT: 
Your user input task should be assigned to the supervisor of the requestor (however, if the
requestor does not have a supervisor, you should add an expression to account for null).
MAPPING THE FORM IN THE SUB-PROCESS: 
Your form in the user input task should be mapped similar to the one below. Read only
fields map to pv! whereas editable fields should map to ac!
ADDING THE SUB-PROCESS: 
Once you have saved and published your sub-process model, you should hook it up to the
parent model using a “Sub-process” node.
CONFIGURING THE SUB-PROCESS NODE: 
Your sub-process node should be configured similar to the one below: