Data Flow in Process Models

joel.larin — Wed, 14 Feb 2024 18:57:04 GMT

Current Revision posted to Guide by joel.larin on 2/14/2024 6:57:04 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Within the process model designer you will encounter additional domain prefixes that are unique to process models. These additional prefixes grant you access to data used throughout the process model, including process model properties, individual task/node properties, individual instance properties, and node functional data.

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

When we connect different nodes together in a process model, we assemble different features together in a specific order. In the above example, the process execution engine executes the start form first, then the script task, and so forth, all the way to the end node.

Node Data Flow

Every node in a process model performs a specific function, based on the inputs and outputs it is provided. For example, the Write Records node writes a set of Record information to the database. The Write Records node can’t just write any record, however, it writes a set of record information that the process model specifies. If the node is not given an input, the write records node doesn’t know what to do and will error out.

Every type of node (Script Task, Write Records, etc.) has different inputs and outputs. These inputs and outputs are referred to as Activity Class Parameters. Activity Class Parameters are effectively local variables for their associated node and their data does not persist in memory unless explicitly saved to a process variable. These parameters are managed in the Data tab of a node which is split into two corresponding Node Inputs and Node Outputs sections. Node Inputs define the data being passed into the node, and Node Outputs define the data available to be passed out of the node.

Some nodes have Activity Class Parameters that are required for the node to function (like the Node Input “Records” in a Write Records node). Some nodes have specific outputs defined as a result of the node’s function. For example, the Write Records node has three defined results:

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

Interfaces can’t directly use process variables, so in order for the Supervisor Review interface to receive and manipulate the data from the process variable, the data must first be mapped to the Node Inputs which directly correspond to the rule inputs of the form. Once mapped the data can flow from process variable to node input to rule input to node output finally back to process variable.

User Input Task Configuration

Understanding that the data needs to be passed from process variable to activity class parameter to rule input and back again, consider the configuration required to make this work. After adding the form to the Form tab of the User Input Task and allowing the process modeler to automatically create Activity Class Parameters for the associated rule inputs, the node inputs must be configured.

Here, the value parameter for the node input vehicle is pv!vehicle. The value parameter tells the process to take pv!vehicle and pass it into ri!vehicle of the form. If the value parameter is left blank, then the form will launch with a null value for ri!vehicle.

Next consider how the data returns from the rule input of the form back into the process variable. This is addressed by the save into parameter for the node input vehicle. The process assigns the “Review New Vehicle” task to a supervisor, who then opens the form, changes some vehicle information, and hits submit. Since the supervisor is working within the interface, all of those changes are stored in ri!vehicle of the interface, not in pv!vehicle of the process model.

The save into parameter for the vehicle node input allows the changed information in ri!vehicle on the form to be passed back into the process as pv!vehicle. Until the supervisor hits submit, pv!vehicle is the older, outdated version of the vehicle information. Thus, if the save into parameter is left blank, the process variables will not receive any changes from the user input task and the process will continue as if the user input task had no impact to the data at all.

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 16:31:32 GMT

Revision 31 posted to Guide by joel.larin on 1/10/2024 4:31:32 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 16:26:46 GMT

Revision 30 posted to Guide by joel.larin on 1/10/2024 4:26:46 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 16:26:09 GMT

Revision 29 posted to Guide by joel.larin on 1/10/2024 4:26:09 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 16:25:50 GMT

Revision 28 posted to Guide by joel.larin on 1/10/2024 4:25:50 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 16:25:27 GMT

Revision 27 posted to Guide by joel.larin on 1/10/2024 4:25:27 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 16:24:52 GMT

Revision 26 posted to Guide by joel.larin on 1/10/2024 4:24:52 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 16:23:14 GMT

Revision 25 posted to Guide by joel.larin on 1/10/2024 4:23:14 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 16:21:48 GMT

Revision 24 posted to Guide by joel.larin on 1/10/2024 4:21:48 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 15:50:01 GMT

Revision 23 posted to Guide by joel.larin on 1/10/2024 3:50:01 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:41:56 GMT

Revision 22 posted to Guide by joel.larin on 1/10/2024 2:41:56 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:31:19 GMT

Revision 21 posted to Guide by joel.larin on 1/10/2024 2:31:19 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:26:04 GMT

Revision 20 posted to Guide by joel.larin on 1/10/2024 2:26:04 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:19:30 GMT

Revision 19 posted to Guide by joel.larin on 1/10/2024 2:19:30 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:17:22 GMT

Revision 18 posted to Guide by joel.larin on 1/10/2024 2:17:22 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:15:33 GMT

Revision 17 posted to Guide by joel.larin on 1/10/2024 2:15:33 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Process Model Data Flow

Examine how data flows in the life cycle of a process instance. In the following example, we have initiated a record action as a registrar to add a new vehicle to a vehicle database.

After initiating the action, the registrar is taken to the start form for the process model. This start form contains rule inputs for managing the data associated with the form that are accessed with the ri! domain prefix.
Once the registrar has input the new vehicle data into the rule input ri!vehicle and clicks submit, the data in ri!vehicle is then transferred to the process variable pv!vehicle.
For the subsequent nodes, process variable data is passed to the activity class parameters for the node, the node manipulates the data, then the data stored in the activity class parameters is sent back to the process variables.

Node Data Flow

Records Updated: a list containing the primary keys of records and related records updated
Error Occurred: a boolean that returns true if any record writes fail
Error: the error that occurred when writing the records

Other nodes, however, do not have defined results and require different configurations. Two primary examples of nodes without results are Script Tasks and User Input Tasks.

Take a closer look at the data flow through a User Input Task where the data for the process variable, pv!vehicle, is modified via user interaction on an interface.

User Input Task Configuration

Tags: process models, Data Management

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:03:41 GMT

Revision 16 posted to Guide by joel.larin on 1/10/2024 2:03:41 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv! (record variable)
	Process Model	pv! (process variable)
	Interface	ri! (rule input)
	Expression Rule	ri! (rule input)
	Integration	ri! (rule input)

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:02:18 GMT

Revision 15 posted to Guide by joel.larin on 1/10/2024 2:02:18 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv!(record variable)
	Process Model	pv!(process variable)
	Interface	ri!(rule input)
	Expression Rule	ri!(rule input)
	Integration	ri!(rule input)

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:02:01 GMT

Revision 14 posted to Guide by joel.larin on 1/10/2024 2:02:01 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv!(record variable)
	Process Model	pv!(process variable)
	Interface	ri!(rule input)
	Expression Rule	ri!(rule input)
	Integration	ri!(rule input)

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:01:40 GMT

Revision 13 posted to Guide by joel.larin on 1/10/2024 2:01:40 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv!(record variable)
	Process Model	pv!(process variable)
	Interface	ri!(rule input)
	Expression Rule	ri!(rule input)
	Integration	ri!(rule input)

Data Flow in Process Models

joel.larin — Wed, 10 Jan 2024 14:00:37 GMT

Revision 12 posted to Guide by joel.larin on 1/10/2024 2:00:37 PM

Skills Covered

In this guide you'll learn how to pass data through Appian Process Models.

Skills Checklist

Recall applicable domain prefixes to handle variables in process models
Explain how data flows through a process model
Describe how data flows through a process model node
Configure the node inputs of a user input task

Domain Prefixes

Each design object has a specific domain prefix that is used to reference their associated variables.

	Design Object Type	Domain Prefixes
	Record Type	rv!(record variable)
	Process Model	pv!(process variable)
	Interface	ri!(rule input)
	Expression Rule	ri!(rule input)
	Integration	ri!(rule input)