Netsuite workflow's SET FIELD VALUE action in RECORD AFTER SUBMIT does not trigger UE

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** Based on the conversations, it appears that the "Set Field Value" action in a NetSuite workflow, when placed in an "After Record Submit" context, does not trigger a User Event (UE) script, despite what the NetSuite documentation might suggest. This behavior seems to be consistent regardless of the trigger used in the workflow. One user suggested that this might be due to the fact that a User Event cannot trigger another User Event. The "Set Field Value" action might be considered a User Event, and therefore it cannot trigger the second firing of the User Event script. Another user suggested replacing the "Set Field Value" action with a custom workflow action that performs a setValue and a save operation. This workaround seemed to work and did trigger the User Event script. It's worth noting that this behavior might be considered a bug or at least a discrepancy between the actual behavior and the official NetSuite documentation. One user mentioned the intention to open a ticket with NetSuite about this issue. Please note that this information is based on user experiences and might not be entirely accurate or up-to-date. Always refer to the official NetSuite documentation and support for definitive information.