In our application we have different regions, where the operator context time zones are been updated on fly based on the region specific, Parallel.
Here the constraint is initially when ever user login the pydefaulttimezone value on pxrequestor page is getting formed with the previous setted value. The details which are been updated on operator is not getting reflected on pxrequestor page. But the same user logoff and login the second time, the details are been updated properly on pxrequestor page.
The logic is implemented in such way, the operator has been updated based on region. But pxRequestor is not in sync with operator context. Need any suggestion on this.
If the user doesn't log-off properly like if he closes the Browser session and reopens it after some time if the requester with old session still persist in the data base then there might be chances of having stale data.But once the user log-off and login properly pxRequestor page along with the operator page will be updated as it will treat it as fresh login and new requester session will be formed, due to which the updates that are performed are reflected properly.