At this moment it is possible to deactivate a control procedure which gives the possibility to deactivate them first see if they are really not needed and delete them later or to save them as a reference as they are not used at the moment but might be in the future.
I think that the person who created this has a great and brilliant insight but …
If something is possible for one thing … why wouldn’t it generally be possible for everything?
My idea is that someone should take a big spin through the application and generalize this.
The reason that I come up with this is that a consultant put work in setting up the flows for microsoft graph integration. I decided that we should not use it for the functionality we are building now, but I don’t want to throw away the code workflows and tables, etc.
Add deactivate option to everything
- Sidekick
+10Hi
Deactivating components can indeed be a useful feature, but we want to specifically apply this to elements related to the processes within the platform, rather than parts of the application itself.
For example, a control procedure may generate code that supports a process, yet it doesn't form part of the core application. Similarly, unit tests (which you can also deactivate) creates test results, but is not a part of the actual application either.
In line with this, we are also thinking about enabling you to make inactivate validation within your work model, even when they are generated from a base model.
To preserve other parts of the application, such as code, workflows, or tables that are not currently needed, we decided not to implement your idea. Instead, we recommend creating a separate branch for this. This allows you the option to later merge these components back if desired.
+10Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.