Detect New Information
When an SA2 message comes in, a workflow is triggered in TIBCO MDM to translate the message and process further. The translation activity works on an XSL file. These XSL files are used to find unmapped incoming information.
In the XSL files, a variable eanuccAttributes has a string value, this string is a comma separated list of all mapped attributes. An XSL template DetectUnmappedAttributes parses these attributes and elements in an incoming message, and verifies if they are mapped by checking if it exists in eanuccAttribute. If a node is found to be new, it is added to a collection maintained in the java extension handler using the XSL template AddUnmappedAttribute.
The XSLs which have this logic incorporated are –
$MQ_COMMON_DIR/standard/maps/mpfromagentrics50wlto26v1.xsl
The following is an example of a return node from GetUnmappedAttributes.
(This example is GDSN specific)
<UnmappedAttributes count="2">
<UnmappedAttribute>
<AttributeName>NewAttribute</AttributeName>
<AttributeValue>New Attribute Found</AttributeValue>
</UnmappedAttribute>
<UnmappedElement>
<ElementName>NewInformation</ElementName>
<ElementValue>Here we found new information</ElementValue>
</UnmappedElement>
</UnmappedAttributes>
After the mapping, an XSL template GetUnmappedAttributes is called to get all the unmapped attributes in the collection as an XML node.
This node is added to the MLXML document which is the output of the Translate activity. Notice an attribute count set to root element UnmappedAttributes. This attribute gives additional information about the number of unmapped nodes found. This XML document can be viewed in the event details.
The next activity in the workflow - Translate - checks whether there any unmapped attributes in the translated XML document. If so, it creates a work item to the designated user’s inbox. The workflows which are used are:
$MQ_COMMON_DIR/standard/maps/mpfromagentrics50rfcinwlto26v1.xsl