Attachments added to a Variable the type of HTML or Attachment on a Record Producer are not copied to the generated record (Requested Item, etc)Issue When using a Record Producer that has a Variable the type of 'HTML' or 'Attachment', any attachment added to the Variable is not copied to the generated record such as a Requested Item, etc When checking the attachment record in the [sys_attachment] table, you can observe that it is still linked to the Record Producer > Table name = 'ZZ_YYsc_cat_item' and Table Sys ID = 'Sys ID of the [sc_cat_item] record'. The attachment record should have been updated to get linked to the generated record. For example > Table name = 'ZZ_YYsc_req_item' and Table Sys ID = 'Sys ID of the [sc_req_item] record. This issue does not cause any functional issues. The target records such as Requested Items can be processed as usual and users can access the attachments because the Variables contains the Sys ID of the attachment record. To know to which target record an attachment should be linked, the following URL can be used:https://<instance_name>.service-now.com/sc_item_option_mtom_list.do?sysparm_query=sc_item_option.value%3D<sys_id_of_the_attachment_record>&sysparm_view= However, this can cause a data loss situation when you commit an Update Set with a new version of the Catalog Item. When you capture a change of that Catalog Item into an Update Set on a development instance, the payload of that object in the Update Set does not include all the attachments linked to the Catalog Item which are present on the target instance where the Update Set will be committed. So, at commit time on the target instance, all the attachments linked to the Catalog Item are being deleted. CauseThe issue occurs when for example a custom SC Catalog Item Widget is being used instead of the OOB Widget. The custom Widget will likely not contain the client controller code which copied the [sys_attachment] record from the [sc_cat_item] record to the generated record.ResolutionTo resolve this, using the OOB Widget is recommended. If needed, a clone of the OOB Widget can be made and updated to fit the use case that the previous custom Widget intended to fill.