0% found this document useful (0 votes)
170 views12 pages

Workflow With Approval Notification-1

This document describes a workflow that sends an email notification with approval options. It involves: 1. Creating an item attribute to store the recipient 2. Designing an email message with a dynamic attribute field 3. Configuring a notification activity to send the message when the workflow reaches that step 4. Linking the notification to the approval function and endpoints based on the response

Uploaded by

satish1981
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
170 views12 pages

Workflow With Approval Notification-1

This document describes a workflow that sends an email notification with approval options. It involves: 1. Creating an item attribute to store the recipient 2. Designing an email message with a dynamic attribute field 3. Configuring a notification activity to send the message when the workflow reaches that step 4. Linking the notification to the approval function and endpoints based on the response

Uploaded by

satish1981
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Workflow with Approval Notification

Sample workflow with Approval notification

Save the file on the desktop:


Once the workflow file is saved on the desktop, Now we will be modifying that wft.

The target is to send an email notification to one person using Oracle workflow.

For this as step one we are creating an Item Attribute which is similar to a Global Variable in a
PLSQL Package. There are different types of item attributes like Text, number, date, lookup, form,
url, document, role, attribute and event. Here we are selecting a text. We can even go for a Role
type but then we need to create a role and assign it then to the attribute.

Set the item attribute properties:

Once the attribute is created then create a new message which needs to be send in the notification.
Set the properties of the new message:

In the body the actual email notification Body and in the subject the email notification subject goes
in. We can also modify using html body if we need to enter the data in tables with different color
coding, .etc. Here in the message body we have appended the Item attribute just for reference on
how to add item attributes which change dynamically in the workflow.
As we are using standard Approve/Reject notification we are selecting an existing lookup. Else if we
want to create a new, we can always create a new lookup with its values and use it here.
Add the display name and description which are mandatory.
Create a new notification by using right click on the notifications menu in
Custom workflow:

Set the Notification properties:


Select the Message which we have created.

Drag the item attribute to the message as we are using the item attribute in the message:

Now edit the Main Process so to add the new Notification: -


Delete the link between existing Function and End to add the Notification in between:

Form a link between Function and notification:


Now when creating the link between Notification and end, The workflow asks for the result type
based upon the Result selected in the workflow notification. If the result of the notification is custom
lookup it prompts for the custom lookup values in the lookup

Edit the properties of the Notification to add the performer:


In the node change the Performer type to Item attribute as we intent to set the attribute value from
function. We can also load the roles from database and add it here. The timeout is also important in
a notification as if the user does not respond in a particular time period we can control the workflow
path. The Time out can also be an item attribute

Drag another end so that when in the notification when user selects another result which is Reject, it
should also flow till the end. Use can also use default as when there are multiple results, then other
than the result mentioned in the flow rest all comes under this flow. Any can also be chosen if the
workflow should also follow this path in either case. –
Validate and save the workflow in the database or on the desktop and upload it using WFLOAD.
Once the Workflow is saved in the database then validates using following scripts: -

SELECT *
FROM wf_item_activities_history_v
WHERE item_type = 'XAOATEST';

SELECT *
FROM wf_item_types
WHERE name = 'XAOATEST';

SELECT *
FROM WF_PROCESS_ACTIVITIES
WHERE process_item_type = 'XAOATEST';

SELECT *
FROM wf_item_types_tl

WHERE name = 'XAOATEST';

You might also like