Add XML Policy support to IIB's mapper

Idea / RFE Review. Apologies for the length of time this request has been held in the status of Uncommitted Candidate / Future Consideration. Unfortunately this particular enhancement request has not received much traction from the community despite the time period it has been open, but we are still sympathetic to the essence of the suggestion as GDM behaviour can be confusing for users in situations where they might expect certain default actions to be executed by an empty map (such as assigning defaults in to the logical tree for example). The original development update from 2016 still holds here ... whilst unlikely to replicate the UI approach of the core XSLT mapper, in concept we like the idea of what is being requested ... In summary we still hold long term sympathy for the request although this is likely a long term area as changes of this nature are not likely to become a high business priority, especially with the lack of clear support amongst existing users. Status is maintained as Future Consideration.

Thank you for raising this RFE. The principle of allowing the IIB user greater control over how the Graphical Data Map node interacts with the in-memory IIB logical tree structure which is passed into and out of the Map node, is a very good sound enhancement. It is likely that any such future enhancement would include facilities like being able to specify values should be assigned as NULL or given a default value as defined by a property of the map. For these reasons, we are moving the status to Uncommitted Candidate, with the comment that the UI/runtime meaning of the XML Policy tabs referred to in the original RFE may not be "lifted and shifted". Although the GDM runtime executes XQuery, we strive to make the UI relevant for users of other wire formats (eg DFDL, JSON) and as such we might well implement the spirit of the RFE without replicating the UI approach. For other readers of this RFE, any suggestions for how to externalise such a future feature would be very much appreciated.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB