If you are modeling a process that should run automatically later, data must be transferred. To do so, create a data flow for each function. In this video tutorial we will show, how a data flow is modeled based on the example of the human task 'Evaluate change request'. The human task can be found in the Governance Automation Models' reference database. The data flow is created and opens.
The "Evaluate change request" function, the executing person and the e-mail are already placed and connected with the relevant fields. Various operators, including:
- boolean operators,
- operators for collections,
- and comparison operators are available to you.
- Operators for data elements
- Operators for documents
- Numerical operators
- And other operators.
If you require additional model objects in the data flow, you can simply pull them inside.
Use constants for the values that do not change during the execution of the automated process. You can use existing constants or create new ones. The new constant is used directly.
If the value of a collection should be used, you must define it.
Use variables for values that change during the execution of the automated process - such as, for example calculation results. To model variables, you must first select a variable catalog. You can use existing variables or create new ones.
The new variable is used directly. You can hide fields that you do not require. The completed data flow could look like this. Close the data flow. It is automatically assigned to the function.
You just saw how a data flow is modeled. Data can be transferred while the automated process is running. For human tasks, dialogs that can be filled out by an executor are required. To find out how to model a dialog, please take a look at the video "Creating a dialog".
