you'll need to treat it as two separate executions...
# suitescript
k
you'll need to treat it as two separate executions of the script for beforesubmit and aftersubmit that finishes/returns once that specific entry point is done - nothing is going to be sustained in memory
s
Interesting, given all the scripts I've done surely I've shared state between a
beforeSubmit
and
afterSubmit
. Those two events are synchronous. I guess my gut reaction is I don't buy the argument that they have to be separate. I'll have to test it I guess.