Design Approach for a Workflow Business Process

Many forms use workflows; a good design approach is to outline the workflow first to understand what kind of forms you will need at each step. Once you have a good understanding of the workflow and what forms will be necessary, you can create the forms and then assign them to the appropriate steps as you create the workflow.

View vs. Action Forms in a Workflow

Part of understanding the workflow is considering each phase of a step. For most steps, there will be a "viewing" phase and an "action" phase. As a business process arrives at each step in a workflow, Primavera Unifier notifies the appropriate users if they are involved in the step. When they open the notification, Primavera Unifier displays a view-only form of the step’s task. Each user can choose to accept or decline the task implicit in this form. If the user declines the task, the step ignores the user. If the user accepts the task, the form becomes an action form where the user can enter or edit information and attach comments, line items, or documents, and forward the form on to the next step in the workflow.

You will be designing the "view" and "action" forms for each step in a workflow.

What Users Can Do

On a view form

On an action form

  • Accept the task
  • Decline the task
  • Print the form
  • Terminate the record
  • Send email
  • Transfer ownership of the record
  • Add an assignee to the current step
  • Copy users to the current step
  • Audit the progress of the record
  • Undo the task acceptance (decline the task)
  • Select the step’s next action
  • Add or edit form content
  • Save a draft of the record
  • Terminate the record
  • Transfer ownership of the record
  • Display the view form of the BP
  • Audit the progress of the record
  • Spell check the record content
  • Add attachments, line items, etc.
  • Send the form to the next step



Legal Notices | Your Privacy Rights
Copyright © 1998, 2020

Last Published Friday, April 9, 2021