Currently if a control procedure is in development the severity given to it in validation is Error. In the current version this will stop the execute complete creation if you have abort on error selected. In reality I want to abort the creation on errors like database errors or major model errors, not on a procedure that is not yet set to "waiting for review status". So I propose to change the severity for control procedures in development to warning instead.
Closed
Change control procedure is in development from Error to Warning
+23Hi Erwin,
Having a Control procedure in Development is comparable with having a car without quality check or APK-check. There could possibly be mistakes in it causing an accident or undesired result. We do think calling this a warning does not reflect the importance of having code reviewed by others. It is completely possible that your code is flawless, but we do incentivize reviewing written code; certainly when deploying your database.
But we are interested how others look at this validation, so we'll open the idea and watch the votes and comments.
+23Updated idea statusNew→Open
+10Unfortunately, this idea has not received enough votes. Because we want to keep the focus on ideas that are in high demand in our Thinkwise Community, we are closing this idea.
+10Open→Closed
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.