Register today for Oracle CloudWorld. October 17th - 20th, Las Vegas

Register now

Hillel Cooperman, Senior VP of User Experience Design, has a message for you on Oracle CloudWorld

Watch now
What are the risks of personalizing the meaning of values from a system lookup? — Cloud Customer Connect
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

What are the risks of personalizing the meaning of values from a system lookup?

Received Response
1
Views
2
Comments

Summary:

Hi there,

We are implementing Talent Review at a client. They have a request to personalize the names/ labels for meeting Participants like this : Reviewer into Line Manager and Participant into Observer.

Tried to replace text with UIT however it did not worked as expected (Tool has some errors and at least for Reviewer did not identified all needed fields). Investigating with Page Composer the component I realized the drop down for Participant uses a lookup. I went further in setup and maintenance in Talent Review tasks and identified HRR_PARTICIPANT_TYPE a system lookup.

Now I know that the documentation is saying system lookups cannot be modified, but when I tried to update the meaning of lookup values REVIEWER and PARTICIPANT into Line Manager and respectively Observer it worked. Values were updated in Talent review pages, including in the notifications that these participants get, Updating this meaning will meet my client requirement and I don't have to waist time with UIT and OWCs. However since this is a more unorthodox personalization I was wondering if anyone has done this before and would you estimate are the consequences of updating a system lookup value

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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