Hi Dan and Bozhidar,
I'm glad you're revisiting this topic. The good news is that there is a method that you might find helpful to do this. The script that follows is a fairly elementary one that decrypts a particular attachment for an incident record. I think this could a building block as part of your next steps to decrypt particular attachments of interest. After successfully running the script, the padlock icon will be removed from the encrypted attachment when viewing the incident record and in the sys_attachment table, the attachment entry's encryption context will be "empty".
Decryption();
function Decryption() {
gs.log("*********** DECRYPTION RUN BY " + gs.getUserName());
decryptAttachments("incident");
gs.log("*********** DECRYPTION COMPLETED");
}
// Note that whomever runs this script must have access to use the specified encryption context or nothing will happen
function decryptAttachments(table) {
gs.log("*********** BEGIN DECRYPTING ATTACHMENTS FOR " + table + " TABLE");
var attachmentGR = new GlideRecord("sys_attachment");
attachmentGR.addQuery("sys_id", "2c181788dbdf2f0035ccd8c75e96198b"); // only attachment sys_id for the specified glide record
attachmentGR.query();
var count = 0;
while (attachmentGR.next()) {
var sysAttachment = new GlideSysAttachment();
sysAttachment.changeEncryptionContext(attachmentGR.getValue("table_name"), attachmentGR.getValue("table_sys_id"),
attachmentGR.sys_id, null);
gs.log("*********** DECRYPTED [" + attachmentGR.sys_id + "] " + attachmentGR.getValue("file_name"));
count++;
}
gs.log("*********** DECRYPTED " + count + " ATTACHMENTS FOR " + table + " TABLE");
return count;
}Output from the above script shows a successful completion:
Could you please kindly indicate if my response was helpful and/or correct in your reply and for the benefit of the community?
Thanks,
Mike
