WHAT IS WORKFLOW STUDIO?
...
A workflow is a series of activities that model the steps involved in a business process. It is a logical, sequential representation of the actual activities performed by the people or systems that interface with a business model. In EmpowerID, the workflow is the primary means by which users interact with IT resources to accomplish specific organizational tasks. All workflows have at least two layers, :
- a process
...
- layer that represents the workflow and how it functions in a business environment
- and a data layer that represents the information being captured by the workflow.
Workflows using these layers are generally automated and initiated by pre-determined processes and can be used to capture data for reporting, compliance, and other needs. Other workflows are user-centric. They do not occur in response to automated system events, but require human interaction, whether that involves simply clicking a button to initiate a workflow or entering and manipulating data at various points of the workflow's lifecycle. Like automated workflows, user-centric workflows comprise process and data layers, but they contain an additional layer as well — the presentation layer. The presentation layer is that part of the workflow that presents itself to the end-user. Known as the form or lookup, the presentation layer gives users functional access to a workflow by providing the interface that allows them to work with business objects and data.
| Info |
|---|
In the EmpowerID model, users never directly interact with a workflow; rather, they interact with what is known as a request workflow. A request workflow is one of the resource types registered in the EmpowerID Identity Warehouse that is related to resource acquisition and management. A specific request workflow is an Identity Warehouse resource record corresponding to an EmpowerID workflow that is used to control who may interact with the workflow. |
A typical EmpowerID workflow is comprised of a number of components. Depending on the purpose of the workflow, not all of these need to be present.
FORMS
Forms provide components that allow users to enter information into a workflow, which can then be captured and used throughout the workflow. Form data is incorporated into a workflow in this way through a compilation and publication process by which Workflow Studio creates a special type of activity, known as a "Form activity." Once published, Form activities can be added to workflows, where the drag-and-drop property binding capabilities of Workflow Studio can be used to send form data to and from other workflow objects at runtime.
Form Components
Form components used in Workflow Studio comprise two category types: Primitives and RBAC Components. Primitives allow you to place simple objects such as drop-downs, calendar controls, and fields on a form, while RBAC Components allow you to place the properties of objects bound to EmpowerID-protected resources on a form. Each of these RBAC components can be used to return the properties of these protected resources for use in a workflow. For example, if you want to capture data specific to a workflow initiator with an EmpowerID identity, you can add an RBAC Component for a Person object to a form, incorporating into your form design only those properties (person attributes) relevant to your data needs.
...
For both activity lines, the same Business Rule is applied. It is only the evaluation of the rule's logic that differs. For this example, the logic of the Business Rule could look like the following code:
return CurrentWorkflow.OperationActivity.OperationExecuted...