Apps To Fusion

It is a very common business need to send email notifications from Oracle Workflows.
By default the sender in these Workflow Notification emails is always picked from Workflow Global Configurations.

However in many cases, the clients demand that these workflow notification emails are sent from specific email addresses.
Effectively the sender of these notification emails must not be picked up from global workflow configurations.

For example, the sender of workflow email notifications from Learning Management Module could be This e-mail address is being protected from spambots. You need JavaScript enabled to view it
On similar lines, the "Sender and Reply to Address" for the email notifications sent from iRecruitment workflows could be This e-mail address is being protected from spambots. You need JavaScript enabled to view it
This feature is specially useful when you want the recepient of Email notifications to be able to reply to that notification email itself.


Therefore there is often a need to send notification emails in such a way that Sender/From Email address is specific to that workflow notification.

In this step by step demo, you will see a simple workflow that sends notification from a specific email account named "Anil Passi Testing".
The idea is to use the special Workflow attributes that can be attached to the Notification message.

If you do not implement this approach, then sender of the notification will be picked from the Workflow Global Preferences.


Steps for imlpementing this solution are
Step 1. Create a role for the Sender of Workflow Email Notification
This can be created dynamically if one does not exist, using an API named wf_directory.createadhocrole

Step 2. In your workflow, define 3 Attributes
Their names are
#FROM_ROLE
#WFM_FROM
#WFM_REPLYTO
See the sample workflow for how these attributes appear in WF Builder

Step 3. Open the workflow builder and attach these attributes to Workflow Notification Message, by dragging these attributes to the workflow message in workflow builder

Step 4. Set these WF Attributes programmatically in PL/SQL
      wf_engine.setitemattrtext(itemtype => itemtype
                               ,itemkey  => itemkey
                               ,aname    => '#FROM_ROLE'
                               ,avalue   => 'Enter Name of the Sender Here');
      wf_engine.setitemattrtext(itemtype => itemtype
                               ,itemkey  => itemkey
                               ,aname    => '#WFM_FROM'
                               ,avalue   => 'Enter Name of the Sender Here');
 
      wf_engine.setitemattrtext(itemtype => itemtype
                               ,itemkey  => itemkey
                               ,aname    => '#WFM_REPLYTO'
                               ,avalue   => 'Enter the Senders Email Address Here');

In reality, you can set these WF Attributes to the desired values as per your logic


In this example, the email from workflow notification will look as shown below.
Notice that sender is specific to our business requirement.

To replicate this test case on your eBusiness Suite environment is two step process.

Step 1. Right click to Save this workflow on your file system. Then open this wft file in WF Builder and save to Database.
http://www.apps2fusion.com/training_demo/anilpassi/wf_override_sender/XXTEST.wft
Note- this workflow will send notification to SYSADMIN from desired email address.

Step 2. Run the below SQL to kick off this workflow and set the special attributes.
Within 3 minutes the email should be sent out by notification mailer.

DECLARE
  l_itemkey    VARCHAR2(100);
  v_role_name  VARCHAR2(100) := 'Anil Passi Testing';
  v_role_email VARCHAR2(100) := ' This e-mail address is being protected from spambots. You need JavaScript enabled to view it ';
  n_count_role INTEGER := 0;
BEGIN
  SELECT COUNT(*)
  INTO n_count_role
  FROM wf_local_roles
  WHERE NAME = v_role_name;
  IF n_count_role = 0
  THEN
    --If the sender does not exist in WF Local Roles, then create one on the fly
    wf_directory.createadhocrole(role_name       => v_role_name
                                ,role_display_name        => v_role_name
                                ,role_description           => v_role_name
                                ,notification_preference => 'MAILHTML'
                                ,email_address             => v_role_email
                                ,status                       => 'ACTIVE'
                                ,expiration_date           => NULL);
    dbms_output.put_line('Ad Hoc Role Created');
  ELSE
    dbms_output.put_line('Ad Hoc Role Already Exists');
  END IF;

  SELECT oe_order_headers_s.NEXTVAL
  INTO l_itemkey
  FROM dual;
  wf_engine.createprocess('XXTEST'
                         ,l_itemkey
                         ,'XXTEST');
  wf_engine.setitemuserkey(itemtype => 'XXTEST'
                          ,itemkey  => l_itemkey
                          ,userkey  => l_itemkey);
  wf_engine.setitemowner(itemtype => 'XXTEST'
                        ,itemkey  => l_itemkey
                        ,owner    => 'SYSADMIN');

--The three API calls in bold is what you need.
  wf_engine.setitemattrtext(itemtype => 'XXTEST'
                           ,itemkey  => l_itemkey
                           ,aname    => '#FROM_ROLE'
                           ,avalue   => v_role_name);
  wf_engine.setitemattrtext(itemtype => 'XXTEST'
                           ,itemkey  => l_itemkey
                           ,aname    => '#WFM_FROM'
                           ,avalue   => v_role_name);
  wf_engine.setitemattrtext(itemtype => 'XXTEST'
                           ,itemkey  => l_itemkey
                           ,aname    => '#WFM_REPLYTO'
                           ,avalue   => v_role_email);
  wf_engine.startprocess('XXTEST'
                        ,l_itemkey);
  COMMIT;
END;
/



To test your notifications, run this SQL
SELECT *
FROM wf_notifications
WHERE message_name = 'XX_TEST' AND message_type = 'XXTEST' ;


IMPORTANT- Given that our workflow in this demo will send notifications to SYSADMIN, ensure that SYSADMIN does have an email address associated.
This can be checked by running SQL as below
SELECT email_address FROM WF_LOCAL_ROLES WHERE NAME like 'SYSADMIN%';


The Workflow process used for this demo is a very simple workflow, as shown below

The attributes at workflow level are as shown below

 

 

 

 

< Prev		Next >