The process logic includes validation and filtering.
The following flow shows the process logic for this collaboration template's Create verb:
Message type | Usage |
---|---|
Create | An item is to be treated as a new submission from the source channel. |
Update | An existing item is being updated to reflect changes in data previously submitted. |
Delete | An item is no longer available and is to be processed for removal. |
Load | The initial loading of items. |
The ItemValidation collaboration template supports the application of business policy logic to any or all Retail_Item business object commands or message types. If you implement this template, you must set specific configuration properties within the collaboration object and add the customized code containing the business policy rules to the collaboration template. See Validating an object against customized business policy rules.
If the Retail_Item business object status is not set to Rejected by the business policy logic, the ItemValidation collaboration object continues to process it. If the Retail_Item business object status is set to Rejected by the business policy logic, the collaboration object aborts any further processing and returns the business object to the caller through its From port. The collaboration object can initiate notification of the rejection. See Notifying of item rejection or processing error conditions.
This missing data check logic is configured to execute for any or all Retail_Item business object commands or message types through specific configuration properties, which must be set by the user. You can also add customized data check logic to the collaboration template. See Validating an object by requiring data for specific attributes.
If error conditions are encountered during any stage of processing, the ItemValidation collaboration object sets the Retail_Item business object's attribute value named in the configuration property ITEM_STATUS_ATTRIBUTE to Error, logs the error, and returns the object to the calling collaboration object through its From port.
The ItemValidation collaboration object can log the Retail_Item business object in the configured IBM® WebSphere® InterChange Server (ICS) log destination based on the value of the attribute named in the configuration property ITEM_STATUS_ATTRIBUTE. Logging is controlled through the configuration properties LOG_ERROR_ITEM, LOG_REVIEW_ITEM, and LOG_REJECTED_ITEM.
The collaboration object can also initiate notification of item rejection after business policy analysis or if any error conditions are detected during processing. See Notifying of item rejection or processing error conditions.
Validating an object against customized business policy rules
To accept or reject an item based on existing business policies, insert customized code into the ItemValidation collaboration template's Business Policy Processing subdiagram.Validating an object by requiring data for specific attributes
You can require that data exist for specific attributes.Adding customized code to the collaboration template
The ItemValidation collaboration template contains a subdiagram called Message Type Processing that can be customized to contain any desired logic.Persisting an object to a local item store
The ItemValidation collaboration template can persist the Retail_Item business object to a local store. .Notifying of item rejection or processing error conditions
The ItemValidation collaboration template can enable notification if an item is rejected by business policy rules or if errors are detected during processing.
Parent topic: Collaboration template processes