On a task one can enable the option “Enable for empty subject” to have a task enabled even though there are no records available to use them on. Usually done for creating a new record.

The situation where one has the task on a detail screen, but the parent does not contain a record, such a task is not desirable to be enabled. If you would have a container with details tabs, navigating to them would be disabled, but the screen types are not always designed as such or only have 1 tab.

So, when a detail reference will be empty, a task should also be disabled despite the “Enable for empty subject” marking.

If there are use cases where this feature would not be desired, the implementation could also be done by having a model setting or an extended property to control this.

Reference to my question before making this idea: