Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-16031

Fix conflict between mail subject parameter and subject form field

    XMLWordPrintable

    Details

    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      The variable exposed is now "mailSubject"

      <notification name="Email document" channel="email" enabled="true" availableIn="all"
      autoSubscribed="true" template="emailDocument" subject="${mailSubject}"
      label="label.nuxeo.notifications.email.document">
      <event name="emailDocumentSend"/>
      </notification>

      Show
      The variable exposed is now "mailSubject" <notification name="Email document" channel="email" enabled="true" availableIn="all" autoSubscribed="true" template="emailDocument" subject="${mailSubject}" label="label.nuxeo.notifications.email.document"> <event name="emailDocumentSend"/> </notification>

      Description

      A conflict is present when using the document notification form :

      • the action behind the form builds an event where one of the its context options is named "subject"
      • any notification has also a "subject" attribute

      Both values are used to build the email, but the value from the form overrides the notification attribute.

      Therefore, the email subject does never contain the email prefix, and never computes the subject attribute defined in the notification.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.