Business Process Automation

Subject Property Key

This page is accessed via Business Process Automation > Power Data > Event Management > Stylesheet Profiles. Then select the Subject Property Key field.

The subject that is part of the agent action NOTIFY CONTACT will only be used in addition to the corresponding notification's default subject if there is a notification associated with that event.

For example, event is "ORDER RELEASE LINE - CREATED" and the stylesheet that is associated with this event is "ORDER_RELEASE_LINE_EVENT_BY_EMAIL". The default subject for this stylesheet is "subjectPropKey.Order_Release_Line_{0}_{1}" for which the translation in English (select * from translation_d where translation_gid like 'subjectPropKey.Order_Release_Line%' and lang='en') will be "Order Release Line {0} {1}", so the output you would see (Order Release Line LINETEST-001) is the same where {0} is replaced by the object ID.

If you want to see a user-defined subject in the notification email, for example, HAVE A NICE DAY!, then the subject needs to be changed to the following: "Order Release Line {0} {1} {2}" (added {2}) because {2} gets replaced with the user-defined subject. This is true for all notifications.

If you want to see only the user-defined subject, then your default subject (of stylesheet ORDER_RELEASE_LINE_EVENT_BY_EMAIL) should just have {2} in it. Only in that case will it use the user-defined subject alone. If you want the same text to be displayed for all notifications corresponding to this event, you could change the default value to a static text as well.

To Define the Above:

  1. Go to Business Process Automation > Power Data > Event Management > Stylesheet Profiles.
  2. Enter ORDER_RELEASE_LINE_EVENT_BY_EMAIL for Stylesheet Profile ID.
  3. If internationalization is not a factor, the Subject Property Key for this record should be changed from "subjectPropKey.Order_Release_Line_{0}_{1}" to "Order Release Line {0} {1} {2}"
    OR
    If (internationalization) is a factor, then a translation entry needs to be created for which the key will be subjectPropKey.Order_Release_Line_{0}_{1}_{2} and the text in English could be Order Release Line {0} {1} {2}

Additionally, you can create a client-specific stylesheet, update the subject and use that stylesheet instead for this event.

{0} is replaced by the object ID.

{1} is used for documents. If the event is on an object that has a document associated in the context of notification, then {1} will be replaced with the document type (XID of document_def table).

{2} gets replaced with the user-defined subject.

Support for XML Parsing

Support for XML parsing in the NOTIFY CONTACT, NOTIFY INVOLVED PARTY and NOTIFY SERVICE PROVIDER agent action Subject fields. By default, these fields represent a sub-header of the report (e.g. READY, AVAILABLE) and can be localized via translation entries (e.g. notifySubFunction.READY). If, however, the Subject field begins with an asterisk (*), the entire subject is based on the text following the asterisk. This text can include XML macros. So in a NOTIFY CONTACT action, a header with only the COLLECTION ADVICE REFERENCE would be:

*Collection Advice Reference: <notify/Report/P/COLLECTION ADVICE REFERENCE>

Related Topics