New Responsibility Is Not Getting Changed Untill Server Is Bounced As the Personalization Profile Is Not Updated (Doc ID 2221441.1)

Last updated on JANUARY 09, 2017

Applies to:

Siebel CRM - Version 15.4 [IP2015] to 16.7 [IP2016] [Release V15 to V16]
Information in this document applies to any platform.

Symptoms

On : 15.4 [IP2015] version, Loyalty

ACTUAL BEHAVIOR
---------------
New Responsibility is Not getting Changed until Server is bounced.

Once the User has Changed the New Responsibility and log out from the Application and Log in back again, still the Old Responsibility is shown. Only once the Server is Bounced the New Responsibility is changed.

For Testing the change of Responsibility , Created a Calculated field and accessed the vanilla Profile Attribute GetProfileAttr("Primary Responsability Name") and found that it is still getting the Old Responsibility Field, by this we got to know that the Responsibility is not getting changed once it is Set and Clear Cache as well.

EXPECTED BEHAVIOR
-----------------------
It is expected that the New Responsibility associated to the Employee is taken without bouncing the Server and only by clearing the cache.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Associate a New Resp to the Employee
2. clear Cache
3. Logout and logon again
4. Old Resp is still in place.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot have the New Resp available so that the new set of View are displayed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms