New Worklist features on 12.1.3
- by Vijay Shanmugam
Following new Worklist features are available on E-Business Suite 12.1.3 via Patch 13646173.
Ability to view comments on top of a notification
If an action is performed on a notification such as Reassign, Request for Information or Provide Information, the recipient of the notification will see who performed the last action and the associated comment on top of the notification.
Reassigning a request for information notification
If an approver requests more information on a notification from it's submitter, the submitter now has two options
Answer Request for More Information
Transfer Request for More Information
If the submitter thinks the requested information can be provided by another user, he/she can transfer the request to the other user. Please note that only Transfer is supported for Request for More Information. Once transferred, the submitter cannot access the notification and provide the requested information.
Use actual sent date when reassigning a notification
The Sent field in notification header always showed the date on which the notification was first created. If the notification was later reassigned, the Sent date was not updated to show the last action date. This caused problems in following scenario
Approval notification was sent to JACK on 01-JAN-2012
JACK waited for 10 days before reassigning to JILL on 10-JAN-2012
JILL does not see the notification as sent on 10-JAN-2012, instead sees it as sent on 01-JAN-2012
Although the notification was originally created on 01-JAN-2012, it was sent to JILL only on 10-JAN-2012
The enhancement now shows the correct sent date in Worklist and Notification Details page.
Figure 1 - Depicts all the above 3 features
Related Action History for response required notification
So far it was possible to embed Action History of an response-required notification into another FYI notification using #RELATED_HISTORY attribute (Please refer to Workflow Developer Guide for details about this attribute). The enhancement now enables developers to embed Action History of one response-required notification into another response-required notification.
To embed Action History of one response-required notification into another, create message attribute #RELATED_HISTORY. To this attribute set a value during run-time in the following format.
{TITLE}[ITEM_TYPE:ITEM_KEY]PROCESS_NAME:ACTIVITY_LABEL_NAMEThe TITLE, ITEM_TYPE and ITEM_KEY are optional values.
TITLE is used as Related Action History header title. If TITLE is not present, then a default title "Related Action History" is shown.
If ITEM_TYPE is present and ITEM_KEY is not, For Example: {TITLE}[ITEM_TYPE]PROCESS_NAME:ACTIVITY_LABEL_NAME , the Related Action History is populated from parent item type of the current item.
If both ITEM_TYPE and ITEM_KEY is present, For Example: {TITLE}[ITEM_TYPE:ITEM_KEY]PROCESS_NAME:ACTIVITY_LABEL_NAME , the Related Action History is populated from that specific instance activity.
Figure 2 - Depicts Related Action History feature
