Dear @Mark_Plaggenborg,
“ In this situation I want to disable that task as well, so now I am creating context procedures to handle this.”
Is there any reason why the option "Enable for empty subject ” cannot be disabled for that situation?
I can think of another situation, where the user want to be able to run the task that create also a record for the parent, not only for the detail reference.
" Would it make sense to have the GUI default the behaviour to disable all tasks in that case even though “enable for empty subject” is enabled? ”
I think it might confuse the user, if the default behavior is to disable all task even though the option “enable for empty subject” is enabled.
Kind regards,
Dani
@Dani Thank you for your input.
The option “Enable for empty subject” is valid when the parent is available and child is still an empty subject, as it will be the first record to be added. If you disable the option, you can never use it unless at least 1 record visibly exists.
I am talking about this situation. Customer (parent) available, so an Address (child) should be possible to be created.:
Parent exists, so child task needs to be available for first address
Against this situation. Customer (parent) unavailable, so an Address (child) does not make sense as you have no customer to add it to.:
Parent does not exists, but child task is still available.
If I were do disable the option on the “Add” task for Address, it would behave the same as you see now for “Edit” and “Delete” and I could never create the address even in situation 1.
Hey @Mark_Plaggenborg ,
I see your point now, it is for the default task like add/edit/delete.
I think you can create a community idea for it, disable default task action for the detail on empty parent by default.
Kind regards,
Dani
