About the ginseng, argument, related data
First, FormalParameter
For the definition of WorkflowProcess and Application, once WorkflowProcess and Application define a certain number of ginseng, then:
Quote This WorkflowProcess is defined in the definition of subflow's Activity. You must define the same number of arguments; When and Application, the engine is responsible for using the correct value of the correct arguments.
Second, ActualParameter
Communication in the activity definition of the Activity and Tool types of the subflow type
The number must be in accordance with the referenced WorkflowProcess or Application defined in the argument; the sources of data can be the relevant data of this process and the formation of the process is responsible for the designation tool; When the engine is responsible for using the correct value of the correct related data and the value of the reference in the first process of the engine initializes its value.
Third, related data (Datafield)
Related Data Used in WorkflowProcess definitions
When instantiation, the engine is responsible for initializing it to one of the initial values declared in the definition as a source of data from the argument, and the engine is responsible for associating it to the correct argument.
Four, in, Out, inout
Three types, in, OUT, INOUT
IN: When the correspondence is true, the engine is responsible for the initial value, and after the Activity is executed, the engine is responsible for ignoring any changes to the real gate value, keeping the original value OUT: The engine does not have to be Before the active execution, the Activity must be assigned to the reference. After the Activity is executed, the engine must retain its value inout: correspond to the actual parameters, the engine is responsible for the initial value, Activity is completed It can be assigned to the real reference, or it may not be assigned, the Activity is executed, the engine must retain its value.
V. INDEX
Shape participating in the transmission order problem, defined in the index attribute, the engine is responsible for the correct parametric parametric; for example:
<
FormalParameters
>
-
<
FormalParameter ID
= "
Subflow.Wor2.for1
"
Index
= "
3
"
Mode
= "
In
">
-
<
DataType
>
<
BasicType
Type
= "
String
"/>
DataType
>
<
Description
>
Name
Description
>
FormalParameter
>
-
<
FormalParameter ID
= "
Subflow.Wor2.for2
"
Index
= "
1
"
Mode
= "
OUT
">
-
<
DataType
>
<
BasicTyPetyPE
= "
Integer
"/>
DataType
>
<
Description
>
Quantity
Description
>
FormalParameter
>
-
<
FormalParameter ID
= "
Subflow.Wor2.for3
"
Index
= "
2
"
Mode
= "
Inout
">
-
<
DataType
>
<
BasicType
Type
= "
Boolean
"/>
DataType
>
<
Description
>
agree or not
Description
>
FormalParameter
>
FormalParameters
>
Suppose it is placed in object [] actparams, then the value of subflow.wor2.FOR1 should be actparams [2], subsflow.wor2.for2 is actparams [0], subsflow.wor2.for3 is actparams [1] --- -------------------------------------------------- WFMC original ------------------------------------------------------------------------------------------------------------------------------------------ -----------
7.1.2
.1. Parameter transfer semantics
The parameter delivery semantics is defined as follows:
i. In the call, the read-only form parameter (IN) is initialized by the value of the actual parameters corresponding to it. This is the value of the value
Righteousness.
II. Readable / Write Form Parameters (inout) initializes the value of the actual parameters, but the actual parameter must be work
The identifier of the flow correlation data entity. When the process is completed, the value of the output form parameter is replenished to the actual participation of its initialization.
number. This is the copy of the copy.
Iii. Only written form parameters (OUT) are initialized to 0 (the String type is set to empty). After the process is completed, the value of the output form parameter must be replenished to the original actual parameter (the actual parameter must be the identifier of the workflow related data entity). This is
0- Return semantics.
7.1.2
.2. Summary
The copy and storage of the parameters are automatically completed, thereby avoiding access conflicts in concurrent workflow related data operations, and these operations are serialized. in
7.1.2
In (c), when the call is returned, the copy and the memory between the copies are unlocked by default, and the return parameter value will overwrite the local value.
7.1.2
.3. Form - actual parameter mapping
The parameter mapping table defines the mapping of the actual parameter to the form parameters during the call. The actual parameters are mapped to the form parameters in order 1: 1, such as the first actual parameter mapped to the first form parameter, and the second actual parameter is mapped to the second form parameter. Require type compatibility when process definition, or to force type conversion when the workflow system is running.
In the case where the actual parameter is an expression, the workflow calculates and buffers the expression, while the content of the buffer is used to perform a form - actual parameter mapping. How to run beyond the scope of this specification.
