A WebSphere® MQ Workflow container must contain the item data
that is needed to make the business process decision.
Purpose
It must also contain certain internal attributes
from the Retail_Item business object so they can be returned to succeeding
collaboration objects that require them. The following list includes those
attributes that must be mapped into the WebSphere MQ Workflow container:
- internals.item_status
- This attribute holds the item status value when there are no cascaded
GLNs in the internals.cascadedGlns child business object.
The approver(s) responsible for approving items must set the value of this
attribute to Approved, Rejected, Accepted,
or Review through a customized user interface with WebSphere MQ Workflow,
so that the succeeding collaboration objects can determine the processing
path for the item. If the status remains Review, the item
is routed back to the ItemValidation collaboration object and then back into
business review/approval processing.
- internals.cascadedGlns
- This attribute is an N-cardinality child business object that holds the
cascaded GLNs and the status for each GLN. When cascaded GLNs are present
in the internals.Glns child business object, the approvers
responsible for approving items must set the value of the internals.cascadedGlns.item_status attribute
for each cascaded GLN to Approved, Rejected , Accepted,
or Review through a customized user interface with WebSphere MQ Workflow,
so that the succeeding collaboration objects can determine the processing
path for the item. If the status remains Review, the item
is routed back to the ItemValidation collaboration object and eventually back
into business review/approval processing.
Note: If you are using DTD XML definitions,
all GLNs, whether cascaded or not, are carried to the WebSphere MQ Workflow
in this attribute.
- internals.item_command
- This attribute holds the item command value.
- internals.correlationID
- This attribute holds the identifying key used to retrieve the item from
the local item store. Even if a local item store is not used, the value for
this attribute must be returned since it is used by the UCCnetMessageReceive
and UCCnetMessageSend collaboration objects.
- internals.fromGln
- This attribute holds the GLN of the supplier publishing the Retail_Item.
- internals.toGln
- This attribute holds the top-level retailer GLN to which the item is being
published.
Other useful data to map
Other useful data to map into
the WebSphere MQ
Workflow container includes the following attributes:
- internals.date_processed
- This attribute holds the date that the item is processed by the approvers.
- internals.time_processed
- This attribute holds the time that the item is processed by the approvers.
- internals.responder_name
- This attribute holds the name of the approver or a list of approvers.
If the WebSphere MQ Workflow business process needs
additional data from the Retail_Item business object that is not mapped into
the container, a customized program that reads the local item store must be
developed. For example, a collaboration template could be developed that invokes
an ItemStore collaboration object to read the store. The custom collaboration
object could pass the Retail_Item business object
internals.correlationID attribute
to the ItemStore collaboration object as the key to the item in the store.
See
Persisting, retrieving, updating, or deleting an item to or from a local item store.