You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

HR Helpdesk 20C - Inability to have Primary Point of Contact and Affected Party the same

edited Sep 3, 2020 1:52PM in Work Life Solutions 1 comment

Summary

Causing problems locating cases

Content

Issue description:

Service Request 1: A case is raised by the user it is regarding so we put their user name in the primary point of contact field.

Service request 2: A case is raised by a manager on an employee's behalf, so we put the employee name in the affected party field and the manager name in the primary point of contact field.

This means that there is not a consistant way to search for cases raised about a certain user. As one case might have the user in the PPOC field and one case might have the user in the Affected Party field. Meaning if a caller rang the phone line and the agent were to check for any cases raised against them they would have to do one search with the user ID using the PPOC field and one using the Affected Party field. Given the affected party field is already long winded to search using, this is creating a lot

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!