Ever had to guarantee to Audit that every stage executed is logged so anyone could trace what the robot executed in case of incidents? We know that developers can edit code to not log stages and execute it on debug mode without saving and nothing will be registered, neither the changes in the code, nor the stages executed in debug mode... So... how to justify this? We wouldn't need if we had a configuration for that!
It would be great to be able to overwrite any configuration of Stage Logging (code or resource) on an Environment/Instance level. This shouldn't be difficult to implement either.
The benefit would be to guarantee stage logging in sensitive environments where every execution of stages needs to be registered for Audit and regulative institutes purposes.