In attempting to reduce DB bloat and UI snappiness, it would be great if using the Attachment Handler in Response Transformers, both could replace the stored Response in the Destination, and could then also be reattached to the Source Response in the Source settings.
Describe your use case
We receive large strings (Base64 Decoded Clinical Documents) in a response from a Destination and would like to limit the amount of duplication we do with a returned response and make the overall storage footprint smaller.
Describe the solution you'd like
Support Destination Response Attachment Handling, when receiving a Response, not just Reattachment in the Destination going outbound. Similar options to the Summary options:
In attempting to reduce DB bloat and UI snappiness, it would be great if using the Attachment Handler in Response Transformers, both could replace the stored Response in the Destination, and could then also be reattached to the Source Response in the Source settings.
Describe your use case We receive large strings (Base64 Decoded Clinical Documents) in a response from a Destination and would like to limit the amount of duplication we do with a returned response and make the overall storage footprint smaller.
Describe the solution you'd like
Support Destination Response Attachment Handling, when receiving a Response, not just Reattachment in the Destination going outbound. Similar options to the Summary options:![image](https://github.com/nextgenhealthcare/connect/assets/4349174/554cc9b5-3e34-4141-9865-b9d4a5bafe26)
Support Source Response Reattachment![image](https://github.com/nextgenhealthcare/connect/assets/4349174/3b0e193b-5138-4aef-9054-fadadfad0709)