Skip to main content
Skip table of contents

Step 3: Assign Forms to Process Steps

Follow Our Example User Story

David has now designed the forms that need to be filled during the process as well as the process model. Now he can assign the forms to the corresponding user tasks so that user can fill in the required data in the desired process step.

In the first step of the process, order data is entered into a web form. This is depicted in the process by a User Task cm_user_task.png .
User task Enter Web Order should show the form to enter the order data (Form_EnterWebOrder) and provide the order data to the process. Click on the user task Enter Web Order on the BPMN canvas:

Switch to the Attributes panel and select Form_EnterWebOrder from the list of available forms provided in attribute Form:

form_enter_web_order_assigned.png

Next, you need to assign a button that triggers the form to continue the process. This is done by adding a trigger event.

Good to Know: What is a trigger event?

A form can contain several buttons. In case a button is clicked, something should happen. The developer needs to define, what should happen when a button is clicked. Therefore, he has to assign attribute Trigger Events in the attributes panel: It defines which button of a form associated to the element triggers the default process flow of a BPMN process.

Refer to Form - Process Interaction in the Designer Guide for details.

To do this, click the attribute Trigger Events and select buttonOK.click:

assign_trigger_event_enter_web_order.png

All necessary attributes are now set for user task Enter Web Order, so you can continue to assign your other three forms to the corresponding user tasks:

assigned_form_attributes.png

User Task

Attributes

Check order

  • Form: Form_CheckOrder

  • Trigger Events: buttonReject.click

Show approval message

  • Form: Form_EndApproved

  • Trigger Events: buttonApprovedOK.click

Show rejection message

  • Form: Form_EndApproved

  • Trigger Events: buttonApprovedOK.click

If an order should be approved manually, you want to trigger the approval branch by clicking the Approve button in Form_CheckOrder. To define that process, click the Plain Event element and switch to the attributes panel. Select the trigger event buttonApprove.click:

Since you already set the event buttonReject.click for the Form_CheckOrder, this event is not available any more (it is greyed out).

Your process is now ready for a first test.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.