Thursday Oct 09, 2014

Global Worklist Header - New Feature on 12.2.3

About

Global worklist header is a new feature available from Oracle E-Business Suite Release 12.2.3 in Skyros look and feel.

  • Worklist header icon is the bell icon which is displayed by default in all HTML based pages in the global header, the worklist header icon is an alternative to including a worklist region in the Oracle E-Business Suite home page. Users can select the icon to view a summarized list of recent notifications, and then click to view and respond to each notification in the notification details page.
  • With this feature, users can view the recent notifications from any HTML page by default instead of navigating back to homepage and checking the homepage worklist for any recent notifications.
  • The open notification count is displayed next to worklist header icon in the global header and the count gets updated on page reload or refresh.
  • On click of the worklist header icon, the worklist menu opens up, which displays the recent 10 notifications. Each notification section shows from user, notification subject link,  sent date and due date of the notification.
  • Users can navigate to notification details page on click of the notification subject link and can review and respond to the notification. The subject text is displayed up to 45 characters and on hover of the subject link, the full subject text is shown.
  • The worklist menu also displays the ‘Go to Full Worklist’ link at the bottom and on click of link, user is taken to the advanced worklist page.
  • The worklist menu can be closed by clicking anywhere outside the menu.
  • If the open notification count for the user is zero, then on click of the worklist header icon, the worklist menu still opens up and displays the message ‘No open notifications found for the user’ along with the ‘Go to Full Worklist’ link at the bottom.

Configuration

Though worklist header icon is rendered by default, the icon rendering in the global header can be controlled at user, responsibility, application, site levels using profile ‘WF_ENABLE_WORKLIST_HEADER’. By setting the profile value, the worklist header icon can be rendered on/off at various levels.

Availability 

  • The worklist header feature is available across all OAF and JTT pages by default from Oracle E-Business Suite Release 12.2.3
  • It is i18n enabled and also supports accessibility features. The opening and closing of the worklist menu and the navigation to each notification component, full worklist link, navigation to notification details page, advanced worklist page from the worklist menu links can be fully controlled by keyboard. The navigation with the keyboard is the same as in any HTML page. In addition, user can navigate through the notifications using key up and key down as well.
  • The global worklist header feature is available in all supported browsers of Oracle E-Business Suite Release 12.2.3

Screenshot

Additional Resources

Release 12.2.3 is currently available on My Oracle Support as Patch 17020683. This patch needs to be applied on top of Oracle E-Business Suite Release 12.2.2. Instructions for downloading and applying the patch are in the Oracle E-Business Suite Release 12.2.3 Readme, Note 1586214.1

'The signing operation has failed' - common error with Password Based Signatures in Workflow Notifications

Introduction

Oracle Workflow Notifications can be digitally signed in two ways.

  1. Password Based Signature
  2. X.509 Certificate Based Signature.

Following are the authentication mechanisms categorized based on whether or not a user subscribes to Single Sign-On (SSO).

 

  1. Pure E-Business Suite User (Otherwise called FND User)
  2. Pure SSO user
  3. Hybrid Mechanism (Both E-Business Suite and SSO)

Issues and Reasons

Time and again we have encountered a problem with Password Based signatures failing with the error: 'The signing operation has failed'. This happens when the notification is signed using SSO credentials i.e., the logged in user is an SSO user. The profile option APPS_SSO_LOCAL_LOGIN, controls the type of authentication mechanism to be used for a user at the time of user-creation. More information about SSO can be found here

The possible values of this profile option are:

  • LOCAL - Login is only allowed via Oracle E-Business Suite local login.
  • SSO - Login is only allowed through Single Sign-On. The password is set to ‘EXTERNAL’ after a single sign-on account and an application account are linked.
  • BOTH - Login can be through both Single Sign-On and Oracle E-Business Suite. (Please note this is only a separate authentication mechanism but not a different class of users created for it)

Now based on the type of login/authentication mechanism, the signing differs.

 

  • For a FND User, the validation utility validates the credentials by fetching password from FND_USER table from ENCRYPTED_USER_PASSWORD column.
  • For a pure SSO user, the ENCRYPTED_USER_PASSWORD column is set to 'EXTERNAL' in FND_USER table and the Validation utility fetches the password from OID to validate it.
  • For a user using both types of authentication mechanisms, the Validation utility validates it as it does in the case of a FND User i.e., comparing the ENCRYPTED_USER_PASSWORD from FND_USER table. This implies that when the user uses authentication mechanism for both FND User and SSO user then the password for FND User is used for validation.

Also, it is to be noted that the password for SSO user is case sensitive and the password for FND user depends upon a profile option SIGNON_PASSWORD_CASE. In short:

 

  • An SSO user password is case-sensitive.
  • An FND User password is by default case insensitive. It depends upon the value of profile option 'SIGNON_PASSWORD_CASE' to have it case sensitive or case insensitive.
  • For a user which uses both authentication mechanisms, the password for FND user is used for signing. It would be good if these passwords are maintained in sync.
Hence, when one encounters the error mentioned here, the starting point to investigate is to see what type of user it is. Mostly it would be user using authentication mechanism for both FND User and SSO User. In that case the FND User password should be used and not the SSO password. Also the case of the password should be heeded to as that can well be the cause of the issue. 

 

 

Wednesday Aug 06, 2014

Now Available: Oracle Mobile Approvals for iOS

About

Oracle Mobile Approvals for Oracle E-Business Suite lets you respond on-the-go to your pending approval requests. From your phone, anywhere and anytime, take quick action on approval requests for expenses, requisitions, purchase orders, recruitment vacancies and offers, and more.

- Quickly filter approval requests by sender or subject
- Review at a glance header and line item details, action history, and comments
- Approve or reject with or without comments, or request more information

Oracle Mobile Approvals for Oracle E-Business Suite is compatible with Oracle E-Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must be a user of Oracle E-Business Suite, with mobile services configured on the server side by your administrator.

Availability

Client

Oracle Mobile Approvals for Oracle E-Business Suite 1.0.0 is available on Apple's iTunes Store  for download.

This app works against Oracle E-Business Suite Release 12.1.3 and above and 12.2.3 and above.

Server

Oracle Mobile Approvals requires set up on Oracle E-Business Suite instance to support connections from the mobile app. Following patches are required to be applied.

Screens


Additional Resources


Friday Nov 16, 2012

New Worklist features on 12.1.3

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

  1. Answer Request for More Information
  2. 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

  1. Approval notification was sent to JACK on 01-JAN-2012
  2. JACK waited for 10 days before reassigning to JILL on 10-JAN-2012
  3. JILL does not see the notification as sent on 10-JAN-2012, instead sees it as sent on 01-JAN-2012
  4. 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_NAME

The TITLE, ITEM_TYPE and ITEM_KEY are optional values.

  1. TITLE is used as Related Action History header title. If TITLE is not present, then a default title "Related Action History" is shown.
  2. 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.
  3. 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

About

This blog is dedicated to bring latest information on Oracle Workflow new features, best practices, troubleshooting techniques and important fixes directly from it's Development Team.

Search

Archives
« August 2015
SunMonTueWedThuFriSat
      
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
     
Today