When a workflow executes, the Workflow Engine determines the type of the form associated with the provisioning request definition. Based on whether it is a legacy form or the form is created in the new Form Builder, it takes appropriate action.
The Workflow Engine continues to support the workflow processes built in the earlier versions that include the request and approval forms created in the Forms tab of Designer. When a workflow executes, the Workflow Engine determines that a legacy form is associated with the provisioning request definition and then generates an HTML and passes it on to the client based on the data item mapped for rendering the form.
The new Form Builder is embedded within Designer and can be launched from Designer. The forms that are created in the new Form Builder are stored in the JSON format. When a workflow executes, the Workflow Engine determines that a new form is associated with the provisioning request definition and reads the form from the Workflow Forms container in the Identity Vault. For example, system\driverset1\UserApplicationDriver\workflow forms>. Based on the data item mapping, the data is populated in the form and the form is sent to the client in the JSON format. At the client side, the Form Renderer renders the form.
When a user submits the form, the Workflow Engine reads the data from the JSON format. The data is persisted in the workflow database similar to the previous versions.