Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-155663

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

    Details

      Description

       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:

      *

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              daniel.angotti Daniel Angotti (Inactive)
              Reporter:
              luiz.jardim Luiz Jardim
              Engineering Assignee:
              Daniel Angotti (Inactive)
              Recent user:
              Rodrigo Paulino
              Participants of an Issue:
              Product Designer(s) Assigned:
              Victor Santos
              Backend Developer(s) Assigned:
              Carolina Barbosa, Rodrigo Paulino
              Frontend Developer(s) Assigned:
              Aline Cantarelli, Rebeca Pimentel (Inactive)
              QA Engineer(s) Assigned:
              Diogo Santos
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master