-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IDEA] Add attachment functionality to destination response #5351
Comments
The response needs to be collected of course with or without a button. It's an interesting idea of course just suggesting another workaround not mentioned your initial feature request. On a side note, we always set response transformer data types to raw so the response transformer always fires such that we can fully inspect the result (e.g. the response code, the data, handle sendAttempts, possibly set a message to sent even if errored, add some part of the response JSON as an attachment and so on). |
I should have added this before but you can workaround this by using the org.apache.http libraries and calling the endpoint in javascript to get the response back without logging it.
Need to code something for Web Service Sender payload now. |
Is your feature request related to a problem? Please describe.
We are hitting a lot of REST endpoints that return a PDF and it would be helpful to have the ability to process that response as an attachment the same way an attachment is processed before the source.
Describe your use case
Store a PDF within a response as an attachment to reduce on logging and processing within Mirth connect.
Describe the solution you'd like
An optional attachment button within an HTTP Sender to capture an attachment the same way one is captured via the source
Describe alternatives you've considered
Currently, as a workaround, we are initiating the requests via a JavaScript Writer using the HttpGet and then adding it as an attachment.
The text was updated successfully, but these errors were encountered: