Workflow Model Flashcards
Three primary layers in a workflow
Process Layer, Data Layer and presentation layer
Process Layer
This layer represents the logical flow of the activities within a workflow. It defines the sequence and conditions of tasks, decision points, branching, and parallel execution paths.
Data Layer
The data layer captures and manages the information processed throughout the workflow. It includes input and output data, intermediate variables, and any data transformations or manipulations required by the workflow activities.
Presentation Layer
This layer is specific to user-centric workflows that require human interaction. It provides the user interface (UI) through which end-users interact with the workflow, input data, or make decisions.
Lookup Control
A component used for displaying data in a tabular format and comes with various configurations for data manipulation and presentation. It is used for displaying and searching for EmpowerID objects. All text/labels in a ____ can be localized.
Business Rules
Logical expressions, based on Boolean values, which are applied to the connections between workflow activities where the process flow may branch off in different directions due to varying conditions.
Orange Lines
Attached business rule evaluates to false
Blue lines
Indicate that the attached business rule evaluates to true
Black Lines
Indicate that there is no business rule applied
Bindings
Used to pass data from one activity to another or even to flow data from the workflow itself to any of the activities.
Event Handler
A method or a function that can handle user actions. Associated with a particular action so that you can write code that gets triggered when an action happens.
SetDataCode
Event runs before your activity executes and is useful to initialize/set your activity properties
GetDataCode
Event runs after your activity executes and is useful to output your activities values or set other workflow properties.
Forms
Offer components that enable users to input information into a workflow, which can subsequently be collected and utilized throughout the workflow.
Operation Based Activities
Protected blocks of code based on the EmpowerID workflow authorization framework used to determine if the current user in a given workflow process can execute the code contained in that activity against the workflow’s target object.
