As a power user, I want to add attachments to my notification template

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Objects
• Labels:
  • bravo-retro-done
  • bravo_q2
  • fc_22_07
  • good-to-go
  • low-code-milestone
  • qa_test_mapped
  • team-bravo
• Epic Link: Custom notifications for Liferay Objects

 Context:

Allow users to have a unified way of creating and managing their object notifications template to be used in their Objects. Will be possible through this feature to create an e-mail notification and add an attachment from an object entry.

Mockups:

Mockup

Acceptance Criteria

1 - Given a power user,
when managing a notification template,
then I must be able to select attachments to the notification

• The file will be available to be sent through the notification
• The attachment does not have restrictions on size or file type. Will follow the attachment field definition.

2 - Given a power user,
when managing attachments on the notification template,
then I must be able to select just the data type "attachment" fields of an object

• All custom objects existing in the instance will be shown in the list (draft and published).

3 - Given a power user,
when managing attachments on the notification template,
then I must be able to delete an object attachment

4 - Given a power user,
when sending the notification,
then the system must be able to add the file as an attachment to the notification

• To be shown, the object and field from the attachment data source need to be related to the entry on the action (trigger entry)

 Out of Scope:

• We won't work on the notification details page;
• This feature is not able to validate if the objects of attachment and actions have a relationship.
• This feature is not able to validate if the SMTP is able to send the attachment, because of the file size or file type.
• This feature is not able to work with system objects

Definition of Done (DoD):

• All Acceptance Criteria were passed;
• Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
• Validated by QA and Product Manager;
• No critical bug related to Story scope (FP5);
• Make sure that all system documentation were updated (if necessary)

 

References:

*