The GLN Cascade Grouping File is a user-created text file, which provides information the ItemDispatcher collaboration object needs to determine how to group the GLNs for a given item in messages sent to WebSphere® MQ Workflow for approval.
Each FILTER subsection must be followed by a GLN_GROUPS subsection. A GLN_GROUPS subsection must contain at least one comma-delimited list of cascaded GLN values grouped together on a single line. Additional groups of cascaded GLNs can be defined simply by adding more lines of comma-delimited GLN lists to this subsection. A GLN_GROUPS subsection can be followed by a FILTER subsection, another GLN_GROUPS subsection without a filter, or an optional END separator at the end of the file.
The ItemDispatcher collaboration object reads through the GLN Cascade Grouping File specified in the GLN_CASCADE_GROUPING_FILE configuration property until it finds a FILTER subsection that is satisfied by the attribute values contained in the Retail_Item being processed. The collaboration object then groups the GLNs according to the GLN_GROUPS subsection associated with the satisfied FILTER subsection. If an item satisfies the conditions of multiple filters, only the first filter in the file is ever considered.
FILTER internals.fromGln 0001000000001,0001000000002 AND item.catalogueItem.tradeItem.tradeItemInformation.classificationCategoryCode. \ additionalClassification[].additionalClassificationCategoryCode 0001.001.001,0001.001.002,0001.001.003 GLN_GROUPS 0005000000001,0005000000002,0005000000003 0005000000004,0005000000005,0005000000006 FILTER internals.fromGln 0001000000005 GLN_GROUPS 0005000000001,0005000000002 0005000000003,0005000000004 0005000000005,0005000000006 GLN_GROUPS 0005000000001 0005000000002 0005000000003 0005000000004 0005000000005 0005000000006
Any GLNs that are not in the GLN_GROUPS subsection are disregarded. Each group of GLNs is sent separately to WebSphere MQ Workflow for approval, so a maximum of two messages are sent.
If none of the preceding filters has been satisfied, the filterless GLN_GROUPS subsection is assumed to apply. Each of the six listed GLNs will be sent to WebSphere MQ Workflow in its own message. Unlisted GLNs are disregarded, so a maximum of six messages are sent.
If no FILTER subsection is satisfied and there is no filterless GLN_GROUPS subsection, then the behavior is determined by the value of the GLN_CASCADE_GROUPING_DEFAULT property.
Parent topic: Processing business objects with cascaded GLNs