Before I turn this into an idea, I would like to know what the vision is about the “enable for empty subject” option of a task in combination when applicable on an empty detail reference.
I am encountering that I have Create tasks on several entities and those need to support being enabled when the subject is empty as they could be the first record to be created. The consequence is that when I have this in a detail and the parent has no records, the task is available, but would not work as there is an empty reference and no parent_id would be available.
In this situation I want to disable that task as well, so now I am creating context procedures to handle this.
This is also only an issue when the detail screen is directly available, as detail tabs become disabled when the reference is empty, though you can still stay inside one if you already navigated to it and can change the filter on a parent for example.
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? In my case it would never pose an issue in any of the functionalities we currently have, but perhaps there are plenty of use cases which do no desire this behaviour.
Dear
“ 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
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.:
Against this situation. Customer (parent) unavailable, so an Address (child) does not make sense as you have no customer to add it to.:
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
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
Idea created:
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.