There are some scenarios where, I need to use javascript in the filter or transform to make a database call for the purpose of filtering or augmenting the message. In these cases, if an exception occurs I would like the destination to queue and retry similar to how Mirth would do when sending the message to the downstream system through the destination connector.
I propose adding an option to turn on a 'destination queue' if an exception is raised in the destination transform or filter, which would then use the same queue settings that already exist.
There are some scenarios where, I need to use javascript in the filter or transform to make a database call for the purpose of filtering or augmenting the message. In these cases, if an exception occurs I would like the destination to queue and retry similar to how Mirth would do when sending the message to the downstream system through the destination connector.
I propose adding an option to turn on a 'destination queue' if an exception is raised in the destination transform or filter, which would then use the same queue settings that already exist.
Imported Issue. Original Details: Jira Issue Key: MIRTH-4307 Reporter: jerchap Created: 2018-07-20T16:18:31.000-0700