About Approval Workflows
App Portal 2020 R1
Approval workflows can be dynamic or static, and can have conditions applied to them.
| • | Dynamic vs. Static Workflow Steps |
| • | Using Conditions |
Dynamic vs. Static Workflow Steps
Each workflow step (also referred to as a level) can be either dynamic or static:
| • | Dynamic steps are evaluated based on user and computer conditions. For example, if the workflow step is defined as Manager, the end user’s manager will be required to approve the request. |
| • | Static steps are the same regardless of who requests it or where it goes. For example, if the workflow step is assigned to a specific user, that same user will be required to approve all requests for this catalog item, no matter which end user requests it. |
Workflows are defined and listed on the Workflows View, which is opened by selecting Workflows under Site Management on the Admin tab.
Workflows and workflow steps can have conditions applied to them. Conditions determine whether the workflow and / or workflow step should be applied to the given situation.
| • | Single workflow applied to catalog item—When you assign a single workflow to a catalog item, the conditions of the workflow are not evaluated; only the workflow step conditions are evaluated. |
| • | Multiple workflows applied to catalog item—When you apply more than one workflow to a catalog item, the conditions of the workflow as well as the steps within that workflow are evaluated. |
Conditions can be based on user attributes including group and OU membership, AD property value, deployment system collection membership for both users and computers, and catalog item properties such as cost and inventory availability. Conditions can also be based upon the answer that a user gives to a question (from the catalog item’s associated Question Template) when requesting a catalog item.
See Also
App Portal / App Broker 2020 R1 Administration GuideAugust 2020 |