What I did may be helpful for you, I created a UI Action and selected client callable, then configured the script to do the following ( I hope this pseudocode exercise is helpful) put the server steps in a script include:
- create an array variable to contain the interesting field names of the existing record,
- create an array variable to collect the values of these interesting fields,
- perform a GlideRecord query to find the interesting record then collect the values,
- perform a .initialize and .insert GlideRecord to create a new record in your interesting table,
- perform a value assignment using the two array variables in a while or foreach logic,
- use a GlideRecord to query the sys_attachment table for interesting attachments,
- add the new record to the attachment record (or create a new sys_attachment record for your new record using .initialize and .insert GlideRecord activities),
- set the interesting record as your new redirect url value so that it is open and visible,
For us, the attachment encryption algorithms sometimes prevents the attachment copies as the security logic is complex and fragile so handling attachments in your instance may also require more research and testing.
If this is helpful, please mark it helpful.
Kind Regards,
Woody
