We have discovered that when an exception is thrown, for example we put disable the queue specified on the MQOutput node, that the Environment tree is not propagated down the Catch terminal of the MQInput node. If we rewire the flow and bypass the plugin node the Environment tree is propagated as expected.
One of two things is happening here. Either the plugin is lacking some code that ensures the Environment is preserved when an exception is thrown or there is a product defect.
Before I open a PMR I'd like to know if anyone else has encountered this and if so if they could kindly point out what is amiss.
Thought I'd post the resolution to this. Turns out that the GlobalEnvironment is the only message in the message assembly that is mutable. As a result there is no need to copy it to a new assembly if you want to change it.
If you do copy it then when an exception is thrown the changes made to it will be lost and not available to nodes upstream from the plugin. If you change the GlobalEnvironment directly then the changes will be available upstream when an exception is thrown.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum