I use XSLT extensively throught my app.
I almost always map from the root, so I have access to the whole SMO.
I read the following from the InfoCenter:
If you select /, /headers or /context as the root, you need to explicitly map all the SMO sections, using the XML mapping editor. *****
Can someone please tell me what headers (such as SMOHeader, properties) , and what fields from context that I DEFINITELY need to transfer?
I have received errors such as Message-ID not found (thrown from a Trace primitive) when I haven't transferred these fields.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2013-03-25T20:28:22Z by spriet
Pinned topic Required fields for XSLT Transformation with SMO root /
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-25T20:28:22Z at 2013-03-25T20:28:22Z by spriet
mmalc 10000036A9216 PostsACCEPTED ANSWER
Re: Required fields for XSLT Transformation with SMO root /2011-01-20T21:42:49Z in response to geejayIf I map from the root, I generally right click on the left hand object in the xslt primitive and select "match mapping" This creates all the necessary transformations that I will need and map them if they are present. Then I don't need to worry.
Note why do you always map from the root. If you are doing gateway stuff then I can perhaps understand, but you lose a lot of the performance benefits of the xslt primitive by doing that.
spriet 100000KQWB58 PostsACCEPTED ANSWER
Re: Required fields for XSLT Transformation with SMO root /2013-03-25T20:28:22Z in response to geejayThe recommendation would be to only map at the / (root) level if you are doing mappings that are outside the /body. If you are only mapping data in /body then it would be better performance and easier to manage by just mapping /body.
BPM Architect, BPM SWAT