Disable subjects logical concept when last template is disconnected

We’ve looked into this idea, and while it could work in cases with only static control procedures, it becomes more challenging for program objects that also contain control procedures that rely on SQL-assignment.

In those cases, the last static assignment records could be removed but some templates are still assigned dynamically via SQL assignments.

Some examples where program objects are temporarily unavailable:

• During definition generation (when objects have been removed but not yet recreated)
• When an error occurs during generation
• Just after creating a new branch, before any definitions have been generated (we currently do not yet copy the program objects when creating a branch)

In such cases, automatically unchecking the checkbox based on missing assignments is undesirable, since the situation is only temporary. The tricky part is that there is currently no reliable way to tell whether it’s a temporary situation or if someone has intentionally removed the last assignment. 

An enrichment might also play a role in the implementation here, as it can be executed at a chosen time.

These are considerations we need to keep in mind when picking up this idea, but this is not something we plan to do in the foreseeable future.

Last note: for static control procedures, you can already easily disable the program object in the tab ‘Assigning’, which clears the checkbox in the subject's settings.