
Name | Description | Context | ID | Synonym, Notes |
Task | The description and context of what needs to be performed in a workflow step. | Both | Step type, activity | |
Work item | The instance of a task. | Both | Task | |
Agent-determination | The algorithm to determine which users are assigned to a task and receive it in My Inbox. | Both | Recipient assignment | |
My Inbox | Users receive their tasks in this app in the Fiori Launchpad | Both | Fiori App ID: F0862 | |
My Outbox | Users can revisit their completed tasks in this app | Both | Fiori App ID: F0862 | A parameterized version of My Inbox |
Classic Workflows | These are the classical workflows, built using the workflow builder and delivered by SAP. They are usually referred to as simply workflows, but sometimes referred to as workflow templates. | Classic Workflow | Transaction SWDD | Customers of S/4HANA On-premise can still build classic workflow templates using the workflow builder. |
Workflow Scenario | The set of building blocks used to configure a flexible workflow. This set includes the tasks, recipient assignment rules and conditions. Workflows themselves are configured by the customer, although one default workflow (pre-delivered content) may be delivered by SAP as part of the workflow scenario. The resulting workflows can be configured by the process expert using Fiori Manage Workflow app. | Flexible Workflow | Transaction SWDD_SCENARIO | These are created in the backend by SAP development, or in On-Premise also by the customer. |
Conditional Workflows | This is a type of flexible workflow, whose triggering depends on a condition being met. This simplifies workflow configuration, enabling many small workflows to take the place of one very large and complex workflow. The conditions, and the flow of the process is determined by the Manage Workflow App. | Flexible Workflow | ||
Ad Hoc Workflows | A UI component that is embedded in business objects to allow a user to define a one-off workflow. | Flexible Workflow | An example of this in S/4HANA is the Engineering Record in PLM | |
Manage Workflows App | The Fiori App that is used to define the flexible workflows. Applications will deliver their own individual apps, which appear identical, but each configures the workflow scenarios relevant to the one particular line of business. | Flexible Workflow | Fiori App ID: F2190 | Most S/4HANA applications also use their own configuration of this tile preset for the application. |
Flexible Workflow Templates | Reusable workflow segments, that can be strung together in different sequences or used to populate ad hoc workflows. | Flexible Workflow | Fiori App ID: F2787 | |
Administration Tiles | Different tiles to support administration duties, such as identifying work items which have not been assigned to a user. | Both | ||
Workflow Instance Component | A UI component that renders the simulation of a workflow and displays its subsequent execution within the business document | Flexible Workflow | For example, in S/4HANA purchase requisitions the progress of the workflow can be followed within the purchase requisition document. | |
Teams & Responsibility Management | Management of users in teams and hierarchies of teams assigned to business context. This is one of the algorithms that can be used for agent-determination. | Flexible Workflow | Fiori App ID: F2412 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
26 | |
23 | |
23 | |
22 | |
20 | |
17 | |
14 | |
11 | |
8 | |
8 |