Skip to main content

Define steps

Basic structure of the steps

In the template there is the section Steps. A step contains, among others:

  • Step Code
  • Step Name
  • Order
  • Step Type (Normal / Error / Final)
  • Allow Record Editing
  • Assignment logic
  • Approvals / Related Approvals: optionally enable line approvals (Enable Related Approval) and set the Approval Mode .

image-1766415665254.png

Create the first "Normal" step

  1. In the section → Steps → New.
  2. Step Type = Normal.
  3. Step Code and Step Name assign.
  4. In the card, set the Assignee Type and set the Assignee .

Important system behavior:

  • When the first normal step is created, the app automatically generates:
    • an Errorstep (code e.g. ERROR)
    • an Finalstep (code e.g. FINAL)

Configure assignment

On the AWF Stepcard you maintain:

  • Assignee Type
  • Assignee
  • Approver Limit Type

Notes:

  • With Salesperson/Purchaser the assignee is derived automatically from the record (salesperson/purchaser).
  • With Workflow User Group a workflow user group must exist and have members.

If a step cannot resolve a valid assignee, the workflow is typically moved to the error step at runtime.

image-1766415688087.png

Due Date Formula (Due Date)

On the AWF Stepcard a Due Date Formula can be configured:

  • Field: Due Date Formula (e.g. <+3D>, <+1W>, <+2W>)
  • When set, approval entries created in this step automatically receive a due date.
  • The due date is relevant for:
    • The display in "Requests to Approve"
    • The Escalation Engine (escalation steps are based on the due date)
    • Standard BC due-date notifications



No comments to display

Back to top