Description
This page allows you to edit an allocation function input mapping. There are three types of allocation strategies currently supported by Cúram workflow: function, rule and target. Selecting a function allocation strategy results in the invocation of the specified allocation function when the associated activity is executed by the workflow engine. The workflow engine processes the input mappings defined for the associated allocation function and invokes it to retrieve the list of allocation targets.
Page Preview
Page Flow Diagram
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions. Fullscreen
Fields
LabelTypeDescriptionMandatory
Data Object AttributePDT_WDO_ATTRIBUTE_IDWorkflow data object mapping for the allocation function. 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.No
Links and Actions
Page Level Actions
LabelDescription
CancelThe Cancel action dismisses the page.
SaveThe Save action updates the record using the information entered on the page.
Messages
When page is loaded
MessageMessage CatalogConfigurableConfigurable Validation Reference ID
An error occurred loading the process definition XML document.LinkNo
An Exception occurred as the timeout has been reached and the transaction has been rolled back.LinkNo
At least one of the mappings specified for the input formal parameters of the business process object method is invalid. The mappings should be refreshed.LinkNo
A workflow data object defined by the workflow engine.LinkNo
Cannot find the default locale for this localized text.LinkNo
Enacting UserLinkNo
Enactment TimeLinkNo
Process Instance IDLinkNo
Runtime InformationLinkNo
The business process object with the fully qualified name of %1s cannot be found on the classpath.LinkNo
The field %1s already exists on the formal parameter.LinkNo
The login ID %1s does not map to a user name.LinkNo
The released workflow process definition %1s with identifier %2n and version %3n is invalid. The validation error is %4sLinkNo
The workflow process definition %1s cannot be found.LinkNo
The workflow process definition %1s version %2s cannot be changed as it has already been released.LinkNo
The workflow process definition is invalid against the schema. The schema error is %1sLinkNo
The XML Binding API cannot be invoked as the classesToBeBound parameter is empty.LinkNo
Unable to unmarshal the data for the class '%1s'. The error message is '%2s'.LinkNo
When page is submitted
MessageMessage CatalogConfigurableConfigurable Validation Reference ID
An error occurred converting the process definition to XML.LinkNo
An error occurred loading the process definition XML document.LinkNo
An error occurred updating the workflow process definition: %1s.LinkNo
An Exception occurred as the timeout has been reached and the transaction has been rolled back.LinkNo
A workflow data object attribute must be specified for mappings to primitive types.LinkNo
A workflow data object defined by the workflow engine.LinkNo
Cannot find the default locale for this localized text.LinkNo
Enacting UserLinkNo
Enactment TimeLinkNo
Process Instance IDLinkNo
Runtime InformationLinkNo
The indexed list workflow data object attribute %1s cannot be mapped to this parameter as this activity is not in a loop.LinkNo
The login ID %1s does not map to a user name.LinkNo
The released workflow process definition %1s with identifier %2n and version %3n is invalid. The validation error is %4sLinkNo
The type of the workflow data object attribute %1s does not match the type of the business process object method field %2s.LinkNo
The type of the workflow data object attribute %1s does not match the type of this parameter.LinkNo
The workflow process definition %1s cannot be found.LinkNo
The workflow process definition %1s version %2s cannot be changed as it has already been released.LinkNo
The workflow process definition is invalid against the schema. The schema error is %1sLinkNo
The XML Binding API cannot be invoked as the classesToBeBound parameter is empty.LinkNo
Unable to marshal the data for the class '%1s'. The error message is '%2s'LinkNo
Unable to unmarshal the data for the class '%1s'. The error message is '%2s'.LinkNo
Related Entities
When page is loaded
ProcessDefinition
When page is submitted
ProcessDefinition
Technical Information