Is it somehow possible to do a set on a parameter of an element in an automation script, without checking the value of the read?
I know it’s possible to disable this on script level, but in this case it’s only needed for one specific set. All other sets in the script can still be checked.
Tom Waterbley [SLC] [DevOps Catalyst] Selected answer as best 9th May 2022
Starting from 10.1/10.0.8, the flag can be toggled at runtime by calling engine.SetFlag(RunTimeFlag.NoCheckingSets) or engine.UnSetFlag(RunTimeFlag.NoCheckingSets). (see Help)
You could unset the flag, then do the parameter set and then set the flag again afterwards.
Tom Waterbley [SLC] [DevOps Catalyst] Selected answer as best 9th May 2022
Unfortunately, as far as I see, requesting the current state of a flag is not currently available as a public method.
Is it then possible to also get the current flag state? Suppose that somebody starts the automation script without the check sets active. In the script it’s been defined to disable the check set for one item, and after that set, the check set flag is activated again (because we were assuming that the script started with that flag activated). Won’t we then by mistake activate the flag for further sets if we’re not aware with what settings the script started?