Configure the REST message to save the returned response body as an encrypted
When you use this function with a REST message that is sent
through a MID server, the MID server user must have any roles required to read and write
attachment records, as well as any roles required to read and write records on the table
specified in the tableName parameter.
The response body does not need to be a binary file to be saved as an
attachment. Response bodies using text formats, such as JSON or XML can also be saved. If
the instance fails to save the attachment, call getErrorMessage() on the
related RESTResponseV2 object for error details.
Table 1. Parameters
||Specify the table that contains the record you want to attach the saved file
||Specify the sys_id of the record you want to attach the saved file to.
||Specify the file name to give to the saved file.
||Specify the sys_id of an encryption context. The saved file is encrypted using
Table 2. Returns