Hi everyone, please check out our new discussion forum located in our GitHub site: https://github.com/nextgenhealthcare/connect/discussions. Let us know your feedback as we try out this new part of GitHub! Don't worry, the content in these forums won't be going away and will at a minimum be preserved for historical reference.
The on-update checkbox is set to "No". The update sentence is at the source transformer, and is only executed when the condition is true. You can use this code both at the source or the transformer.
Of course, this way is less efficient than using the on-update sentence.
I've one question regarding this topic: what happens if the message gets undelivered by any reason? For instance: an expection in the transformer, the recipient host is offline, there is a network problem ...
The On-Update statement gets executed regardless of the result of the success of the message?
In my environment, I would need the statement only to be executed when everything works out fine. What would be the best way to do this? Maybe by adding a Database Destination?
Is it possible to set a destination so it gets executed only in case the result from the previous destination was SUCCESS? I cannot figure out how to do that ...
dgilperez: Synchronize option (AFAIK) is used to force Mirth to execute each destination in order. Without "synchronize" option enabled, you cannot use postprocessor (because this script is executed when all the destinations are done), and cannot use the code posted below (because you don't know if a destination is yet executed when evaluating the current destination)
I was wondering if the destinations are executed in order, just by putting the DBWriter the last one it was done, because if the previous failed the DBWriter was not going to execute ....
... but anyway we can be double sure with your suggestion, activating Syncro and using and adaptation of the code you posted. It's working for me now.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment