Validations
- The workflow data object attributes specified in the input mappings must be valid. The criteria that defines a valid workflow data object attribute may be seen in Validations
- The type of the formal parameter being mapped to and the type of the workflow data object attribute being used in that input mapping must be compatible. For example, if the input mapping being created is a struct field that has a type of STRING, then the workflow data object attribute being used for that mapping must also be of type STRING.
- The Context_Task workflow data object cannot be used in an input mapping if the associated activity is not a manual or decision activity.
- The Context_Loop workflow data object cannot be used in an input mapping if the associated activity is not contained within a loop.
- A validation warning will be displayed if all struct parameters defined in the business process object method do not contain an associated input mapping.
- All primitive base type formal parameters defined in the business process object method which must contain an associated input mapping.
- If the formal parameter field being mapped is a base type parameter, then an attribute from a list workflow data object cannot be used.
- If the formal parameter field being mapped is from a list structure, then it must be mapped to an attribute from a list workflow data object.
- If the indexed item from a list workflow data object (i.e. ClaimantDependent[Context_Loop.loopCount]) is being used in an input mapping, then the associated workflow data object must be a list workflow data object and the activity containing the input mappings must be contained within a loop.