Forms - Best Practices

Last Updated: Mar 8, 2023


  1. Always define forms for the table presentations you have created for all the roles that will access them.
    • If no form is defined, the Default form is applied, provided default form exists, and all users, regardless of their roles will have view and edit access to all the data columns in the table.
    • Ensure that forms are designed for all the combinations of roles and status that are needed in the automation flow.
  2. Always order the forms. Whenever multiple forms meet the Role & Execution state criterion, the first form in the ordered list that meets the criterion gets applied.
    • Order the forms as per the priority in the automation flow.
  3. Always select the correct datatype for the columns in the table as they are rendered in the form as per the datatype.
  4. In Button setting, select the State you want the execution State of the record to be updated to after the particular action.

    After Approval, the State should get updated from For Approval to Approved.

  5. The design of the task that is being triggered should ensure that.
    • Parameters are set in the Start Node for UUID. The UUID will be the link between the record of the form and the task.
    • The record is locked at the start of task execution and lock is released before the end of task execution. This ensures that no other task accesses the record while it is being processed during the task execution.

See Also

Did you find what you were looking for?