I recently upgraded to IDM453 Engine and Remote Loader. In one of my
custom HL7 drivers (from EST Group, LLC) there was code in the Sub Event
Transform to "Set-Operational-Association", this would let the
transaction flow to the Output Transformation to be processed, with out
becoming a synthetic add. Prior to IDM 453, this would also add that
association to the object. With 453 installed, it does still by pass
the synthetic add, but does not add the association, which caused issues
in my custom driver on the second transaction from that object. I have
fixed by using the Add-association and set-operational-association in a
"if" policy. This was just the quick fix that I used, I am now going to
reexamine the whole driver, but it is working again.

Just an observation that I wanted to share :-)


rjreisbi's Profile: https://forums.netiq.com/member.php?userid=2906
View this thread: https://forums.netiq.com/showthread.php?t=55512