Workflows over HD Tables

No-Code Platform
1

When workflow is built over an HD table, the workflow seemingly only applies to the header table. Is there a difference between building workflow over a header table vs. an HD table?

2

I think that workflows are almost always built over just header and detail tables respectively. Are you trying to create a workflow where the wf status is in sync between the header and the details or something like that? I think that’s definitely possible.

3

There are 2 options for defining workflows with HD tables:

Separate Workflows for Header and Detail Tables

  • Independent Workflow States: Header and detail workflows are completely independent of one another and have different statuses.

  • Transition Control: Workflow transitions can be performed on the header and/or any number of details.

  • Workflow Security: You can apply workflow security to the header and details independently.

  • Orchestration: It is possible to set up complex workflow orchestration scenarios where the header’s workflow status drives the detail statuses, or vice versa.

  • Use Case: Best when you need all details to move freely within their own workflows, or need individual details to have different statuses than each other.

Workflow on the HD Table (Combined Workflow)

  • Shared Workflow State: Header and all associated details share a single workflow. When the header moves to a new workflow status, that status is immediately copied to all details.

  • Transition Control: Workflow transitions are only allowed from the header; details are read-only in terms of workflow.

  • Workflow Security: You can apply workflow security on the header record, but not on the detail records.

  • Orchestration: No complex orchestration support; the header and details move in lockstep with each other.

  • Use Case: Best when you want your entire object (header + details) to move together as a single unit in the same workflow state.

2 Likes