ER-Setting up concurrent functionality in the application is very cumbersome
(Doc ID 1964994.1)
Last updated on MAY 31, 2018
Applies to:Oracle Fusion Performance Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Setting up concurrent functionality in the application is very cumbersome.
Behind the scenes, to set up the performance management process flow, we checked the box for allowing concurrent functionality.
We then created our templates (exactly as before) but referenced this flow that had the concurrent functionality box checked.
In the application (Fusion Performance Management):
The manager has to log-in, bypass the task, and then return to worker in order for both employee and manager to have ability to work on a performance document at the same time.
When the manager bypasses the task, the employee is locked out of the performance document. Only when the manager clicks the return to worker button does the employee resume ability to edit the performance document.
Is this how the concurrent functionality is intended to work? Are there updates coming to make this process smoother and less clicks?
The feedback provided from our audience was that this was too confusing on the manager's side to have to click so many buttons just to have the ability to work on a performance document at the same time as an employee.
Would this functionality are coming in future releases?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!