We use several scripts that we run manually on the SF database. One example is a script that suppresses all validation messages for a branch. We run this immediately after creating a feature branch, so that open validation messages carried over from the development branch don't obscure new messages originating from the feature branch itself.
We have included this script in our model as a dynamic procedure, which means it falls directly under model maintenance. The procedure has been marked as inactive, because it should not run during every deploy — we only want to execute it manually.
However, for inactive procedures the execute button is also disabled. This means we have to activate the procedure first, run it, and then deactivate it again. A bit cumbersome.
Idea: allow the execute button to remain available for inactive dynamic procedures, so they can be run manually regardless of their active/inactive status.
