Notifications can be configured in the FAB Process Designer. Templates define the structure and content of the Notification.
...
Notifications / Emails
From FAB V3.2.0 onwards it is possible to design and configure Notifications from within the Process Designer. FAB V3.2.0 supports Email Notifications only.
...
Press the 'Notifications' tab of the Process Designer.
...
Templates
Templates define the structure and content of the Notification. Each Template consists of 'Sections', and Sections can consist of 'Subsections'. Sections and Subsections consist of 'Content' (usually HTML).
To create a new Template, press the Add Button and give the Template a meaningful Id. To demonstrate, we will create a Notification Template that will be used to send an email to the Initiator stating that the request has been submitted for approval.
...
...
Id
The Id is a unique identifier for the Notification. It is used elsewhere when configuring which Notification to generate at what point in time. The Id can also be used in various FAB user-exits to identify the Notification being processed at run-time
...
Shown below is the Template definition so far. In this example we are not using a Master Template.
...
Sections
Now we will begin to define the content of our Notification in Sections.
Right-click the Notification in the 'Template Structure' tree-view and choose 'Add Section'.
...
Id
Template Sections also have an Id to identify the section during editing. It is recommended to use something meaningful so that the Template structure is easily understood.
...
<p>Your request has been submitted.</p>
...
Preview
Notice that once the Content is updated, the 'Preview' section shows the resulting formatted HTML. This preview can be used to check for errors in the HTML, for example, if incorrectly formed HTML is used, the Preview will not generate as expected.
...
Initial Testing
Before proceeding with a more complex Notification, we will see how to configure the Notification so that it sends when the Request is submitted.
...
Note that successful emailing depends on the correct configuration of the SAP emailing system, such as SCOT and SOST, and the recipient users must have valid email addresses configured on their user-ids or 105 Infotype of their HR Personnel Master record (PA30)
...
The initial testing has proven that the Notifications and Emailing system are generally functioning correctly. We will now look further at developing more complex Notifications.
More Complex Templates
Add Instance Data to Notification
...
<p>Your request for {RequestAmount} has been submitted.</p>
...
Using Real Data in Preview
...
There are a few options for improving this. One option is to create another Data Model variable 'RequestAmountFormatted' (with Character based SAP Type) and use ABAP code in one of the user-exits like PERFORM_ACTIONS_FOR_STATUS_CHG to set this value.
...
...
Then change the HTML Content to use {RequestAmountFormatted} instead.
...
Another option is to implement similar logic in user-exit CHECK_AND_SEND_NOTIFICATION before calling the SUPER implementation.
...
...