feat: Enhancement in notifications

[deepeshgarg007]

Ability to send notifications to assignees

Added a check to send emails to all assignees

Send notification based on child table field

Now child table fields also show up in the receiver_by_document_field in the recipients child table

[prssanna]

@deepeshgarg007 should we add assigned users to the Receiver by Document Field options instead of using a new field to send to all Assignees?

[rmehta]

what is this additional thing?

[deepeshgarg007]

This adds fields with options as "User" and "Email" from child tables in the select dropdown in the recipients table same way we do for fields on parent level

[rmehta]

ok can you add comments, because it is hard to read the logic.

also add comments in other places where you think it will be helpful in review ;-)

[deepeshgarg007]

@deepeshgarg007 should we add assigned users to the Receiver by Document Field options instead of using a new field to send to all Assignees?

Technically it(Assignees) is not a doc field so thought to keep it outside as a separate field and not under the Receiver By Document field. Is there any docfield from where I can get all the assignees. If yes then let me know as I am not aware of it.

We also have conditions at the parent level as well so there was no incentive to put it in the child table. Here a separate field makes it clear to the user what checking the field will do, in child table it might be a bit unclear. If moving the option in child table gives user more control and I have missed anything let me know, will move it to the child table then

[prssanna]

@deepeshgarg007 we have doc._assign. I just thought that grouping all the recipient options together would make more sense UX-wise, but yeah this is a more clear implementation. Also the condition in the child table gives the user the power to set specific conditions for different sets of recipients (but I'm not sure how much that is actually used).