As a power user, I want to use relevant user information on notification template settings

• Type: Story
• Status: Closed
• Priority: Critical
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Objects
• Labels:
  • 23M1|DEV#3|Feb06-Feb17
  • 23M1|DEV#4|Feb20-Mar03
  • 23M1|DEV#5|Mar06-Mar17
  • bpm
  • bpm_q1_23
  • non-initiative-related
  • squad-zulu

Context

Currently, in Email notification templates, Creator term is supported, but only retrieving its name.

For real scenarios, email notifications are sent dynamically to users related to the object entry, as creator, the current user updating, or even from a relationship with user (as assingee).

For this story, the goal is to allow users to use the variables of Creator and Current User in notification templates (email and user notifications).

Use Cases

• In a ticketing object, send a confirmation that the ticket was opened for the ticket creator email.
• Create a template where the message displays only the first name of the current user.
• Create a template where the message displays the full name (first name + last name) of the current user.

Design Deliverables

Mockup link

Acceptance Criteria

1. Allow users to add the following terms on To, CC, BCC, From, Subject, and Template fields in email notification settings
   1. [%CURRENT_USER_ID%]
   2. [%CURRENT_USER_FIRST_NAME%]
   3. [%CURRENT_USER_LAST_NAME%]
   4. [%CURRENT_USER_EMAIL_ADDRESS%] 
   5. [%OBJECT_AUTHOR_ID%]
   6. [%OBJECT_AUTHOR_FIRST_NAME%]
   7. [%OBJECT_AUTHOR_LAST_NAME%]
   8. [%OBJECT_AUTHOR_EMAIL_ADDRESS%]
2. Allow users to add the following terms on Recipients > Definition of Terms > To and Subject fields in user notification settings
   1. [%CURRENT_USER_ID%]
   2. [%CURRENT_USER_FIRST_NAME%]
   3. [%CURRENT_USER_LAST_NAME%]
   4. [%CURRENT_USER_EMAIL_ADDRESS%] 
   5. [%OBJECT_AUTHOR_ID%]
   6. [%OBJECT_AUTHOR_FIRST_NAME%]
   7. [%OBJECT_AUTHOR_LAST_NAME%]
   8. [%OBJECT_AUTHOR_EMAIL_ADDRESS%]

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 blockers related to Story scope (FP5);
• Make sure that all system documentation tickets are created;

Ticket Updates:

1. Provide the following terms as well because they're already supported, see:

1. 1. [%CURRENT_USER_MIDDLE_NAME%]
   2. [%CURRENT_USER_PREFIX%]
   3. [%CURRENT_USER_SUFFIX%]
   4. [%OBJECT_AUTHOR_MIDDLE_NAME%]
   5. [%OBJECT_AUTHOR_PREFIX%]
   6. [%OBJECT_AUTHOR_SUFFIX%]