Everything in the [Document Template] scope is captured in the Update Set as 'Global' - Known Error

Everything in the [Document Template] scope is captured in the Update Set as 'Global' Description After creating an update set in the "Document Templates" scope and performing the update work, the contents of the update set shows that the "Application" of the record stored in the related list "Customer Updates" as "Global" instead of "Document Templates".

Steps to Reproduce

1. After logging in, go to the settings on the right side of the header and set "Show application picker in header" to True to show the application picker. 2. Switch the application to "Document Templates". 3. Create a new update set making sure that the application is "Document Templates". 4. Go to System Notifications > Email > Notifications and search for "Notify review doc task rejected[Mobile]" in the Name column. The application for this email notification "Notify review doc task rejected [Mobile]" is "Document Templates". 5. Open the record, change Active to False, and update it. 6. Open the update set that you had configured and look at the "Application" of the customer update record that was added, you will see that it is "Global".

Workaround After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience.

Changing the sys_id of the application is not possible by fix scripts as the access to this field is denied by the GlideRecord function. Also changing the sys_id at the plugin.xml record would cause double entries in the sys_metadata table.

As a workaround, before exporting or using the update set of the document templates, run the following fix script:

var gr = new GlideRecord('sys_update_xml'); gr.addActiveQuery(); gr.addQuery('update_set.application', '6a9ea833b763330088d9bc78ee11a88q'); gr.query(); while(gr.next()){ gr.setValue('application', '6a9ea833b763330088d9bc78ee11a88q'); gr.update();

}

This will set the application of the sys_update_xml records appropriately to our application.