Validations

An allocation strategy must be defined for a manual task.
If the allocation strategy is of type function, the function specified must be a valid and must exist on the Cúram application classpath.
If the allocation strategy is of type function, the return type of the function must be curam.util.workflow.struct.AllocationTargetList.
If the allocation strategy is of type function, any of the input parameters of the specified function that are mapped must be to valid workflow data object attributes and the type of the workflow data object attribute must match the type of the input parameter field.
If the allocation strategy is of type function and an indexed item from a list workflow data object is used in an input mapping, then the workflow data object must be a list workflow data object and the activity containing the mapping must be contained within a loop.
If the allocation strategy is of type classic or CER rule, the specified ruleset must be valid.
If the allocation strategy is of type CER rule, a primary CER rule class name must be specified.
If the allocation strategy is of type CER rule, the specified primary CER rule class must exist in the specified CER ruleset.
If the allocation strategy is of type CER rule, the specified primary CER rule class must extend the required abstract Workflow Allocation CER rule class.
If the allocation strategy is of type CER rule, the specified primary CER rule class must contains an attribute named targets.
If the allocation strategy is of type CER rule, if CER rule classes other than the primary CER rule classes have been specified in the input mappings, then the CER primary class must contain attributes that refer to those class, one for each class.
If the allocation strategy is of type CER rule, all of the source attributes specified in the mappings must be valid workflow data object attributes in the context of the containing workflow process definition. All of the target attributes must be valid CER class attributes in the context of the specified ruleset. The type of the workflow data object attribute specified as the source attribute must match the type of the CER class attribute specified as the target attribute in the mapping.
If the allocation strategy is of type CER rule, no duplicate target attribute mappings are allowed. In other words, a CER rule class attribute can only be specified once in any list of CER class mappings.
If the allocation strategy is of type CER rule, all of the attributes that have been marked as specified for all of the CER rules classes used for the allocation strategy must contain an input mapping. CER class attributes that have not been marked as specified must not contain an input mapping.
If the allocation strategy is of type classic rule, all of the source attributes specified in the mappings must be valid workflow data object attributes in the context of the containing workflow process definition. All of the target attributes must be valid rules data object attributes in the context of the specified ruleset. The type of the workflow data object attribute specified as the source attribute must match the type of the rules data object attribute specified as the target attribute in the mapping.
If the allocation strategy is of type classic rule, no duplicate target attribute mappings are allowed. In other words, a rules data object attribute can only be specified once in any list of ruleset mappings.
If an indexed item from a list workflow data object (i.e. PersonDetailsList[Context_Loop.loopCount]) is used in the function, classic rule or CER rule allocation strategy mappings, then the workflow data object must be a list workflow data object and the activity containing the mapping must be contained within a loop.
If the Context_Parallel workflow data object is used in the function, classic or CER rule allocation strategy mappings, then the activity containing the mapping must be a Parallel activity.
If an indexed item from the Parallel List Workflow Data Object is used in the function, classic or CER rule allocation strategy mappings, then the activity containing the mapping must be a Parallel Activity (i.e. ParallelListWDO[Context_Parallel.occurrenceCount]). The workflow data object being indexed by the Context_Parallel Workflow Data Object must be the Parallel Activity List Workflow Data Object.