I have a requirement to trigger specific logic when print files are printed. I have developed a trigger called ‘PostPrint’ which is working great. However, I am having to implement all my code in the one trigger ‘PostPrint’, see below.
In the past, I tried creating multiple triggers under the CREXTPRT for each print file, e.g. one for MWS435, one for MWS485 etc. However, when I tested it I noticed that only 1 was executed – I was expecting all of them to execute in parallel.
I have also recently noticed that if an XtendM3 trigger/transaction throws unhandled exceptions multiple times within a timeframe, it is deactivated. This means that all my print file extensions will deactivate if one faces a problem.
Has anyone else had this problem and if so, how have they resolved it?
Thanks, Callum
