The following table describes the keywords that reference datasets in various contexts:
|
Dataset |
Dataset Context |
Description |
|---|---|---|
|
Datasets |
Named Dataset |
Uses the following format to access a named dataset in a CA Process Automation Library: Datasets[dataset_path].field_name dataset_path A CA Process Automation expression that evaluates to the full path for a named dataset in the current Library. For example, the following path references a dataset named CxLinuxDev located in the Data subfolder of the Demo folder in the Library: Datasets["/Demo/Data/] |
|
Process |
Dataset of a Process |
Accesses a process dataset in the following format: Process.field_name or Process[expression] Process.field_name or Process[expression] field_name The dataset variable. expression A variable or other expression that returns the name of a field. For example: Process.x = 5; Process.fn = "x"; Process.y = Process[Process.fn]; A process dataset is defined in a process. Each time a process starts, it creates a copy of itself (called an instance of the process), including its process dataset. The original process object determines the initial values for the dataset. Changes to a dataset in a process instance do not affect the original. |
|
Caller |
Process Dataset for a parent process when it is starting a child process |
Passes values between processes in a call hierarchy when one process uses the Start Process operator (in attached, detached, or inline mode). The process dataset initialization code option of the Start Process operator specifies these assignments. For example, when ProcessA calling ProcessB needs to initialize fields in the ProcessB dataset, ProcessA specifies ProcessB in the process dataset initialization code. In this context, Caller refers to the dataset of the parent (ProcessA), and Process refers to the dataset of the child (ProcessB). In the context of the process dataset initiation code, the Process keyword is always required to reference a variable in the child process dataset. If you omit both the Process and Caller keywords on a variable name in the process dataset initiation script, CA Process Automation only looks for a calculation-scope variable. The product does not check for a similarly-named variable in either the parent or child dataset. For example, the following code fails if no calculation-scope X was previously created in the calculation context: Process.X = Caller.X; Process.Y = X + 100; |
|
none |
The current calculation and, in some cases, the process dataset |
If you omit the Process keyword on the left side of an assignment statement, CA Process Automation always creates or assigns a value in the scope of the current calculation (a calculation variable). A calculation variable exists as long as CA Process Automation is processing a calculation field. For example, the following code creates a calculation variable equal to the value 5: a = 5 If you omit the Process keyword in other contexts (such as on the right side of an assignment statement), CA Process Automation looks first for a calculation scope variable or a Process variable with the same name. For example: Process.a = 1 Process.b = 2 a = 5 x = a y = b CA Process Automation creates two variables in the process dataset (a=1 and b=2), and two calculation variables (x=5, y=2). |
|
Process.operator_name or Process[expression] |
Operator dataset in a process |
Enables access to an operator dataset, where operator_name is a string that specifies the name of an operator in a process. For example: Process.y = Process.emailOp.subject Expression returns the name of an operator in a process, for example: Process.opName = “emailOp” Process.y = Process[Process.opName].subject Notes: - For information about specifying operator dataset fields and for a list of system generated fields in operator datasets, see Specify Operator Dataset Variables. - For more information about specifying operator variables in operator properties settings, see Dataset Variables in Parameters. |
|
System |
System Dataset |
Enables access to the system dataset. Fields in the system dataset represent CA Process Automation system information, such as the host name, date, and time. The system dataset is read-only. Note: For more information about fields in the system dataset, specifying system variables, and a list of system variables, see Specify System Dataset Variables. |
|
Root |
Parent Dataset |
Enables an inline child process to access the process dataset of a parent instance. You can use the keyword Root to access the Process dataset of the root instance. Examples: - ProcessA starts an inline process ProcessB. ProcessB starts another inline process ProcessC. ProcessC uses the keyword Root to access the dataset of ProcessA. - ProcessA starts ProcessB in non-inline mode and ProcessB starts ProcessC in inline mode. ProcessC only has access to the dataset of ProcessB (and not ProcessA) using the keyword Root. |
|
Copyright © 2013 CA.
All rights reserved.
|
|