There are some scenarios where, I need to use javascript in the source 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 channel 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 'source queue' if an exception is raised in the source transform or filter, which would then use similar queue settings as exist in the destination connector.
There are some scenarios where, I need to use javascript in the source 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 channel 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 'source queue' if an exception is raised in the source transform or filter, which would then use similar queue settings as exist in the destination connector.
Imported Issue. Original Details: Jira Issue Key: MIRTH-4308 Reporter: jerchap Created: 2018-07-20T16:19:50.000-0700