Triggers when suing automated scripts.
What I'm looking to do is setup some sort of variable that tells a script whether it should deploy or not while in the middle of another script that say assigns records to invoices or creates new records.
I've never had to use this type of thing in the past and now that last two processes I've tried to create have cause issues in a bunch of scripts because they involve activating when switching to and from certain modes etc.
I've seen this method gets used in the past but I don't have any databases to refer to so I'm wondering if someone could give me pointers on this. Is it as simple as turning a global variable from on to off. When a script that I want to run uninterrupted starts it marks the variable as off, performs it's script and then turns it on at the end. All scripts that I want to have affected by this would always start by checking if the script switch is on or off ... seems like that would do the trick but wanted to see what others thought.