Possible cache issue when updating peoplecode?
edited Feb 22, 2013 12:52PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 12 commentsAnswered ✓
I updated the peoplecode for FUNCLIB_HR.National_ID. We had issues with HR keying in employees with duplicate SSN, I was asked to set the warning that appears to an error.
The only change I made was on line 137, I simply changed Warning to Error. Unfortunately this impacted the template based hire and caused the save and submit button to become non responsive.
I changed the Error back to a warning... Most users are fine now, but it seems that randomly a user will get the old peoplecode and the save and submit will become non responsive again.
I've tried clearing the local cache in my web browser and the app server cache. Where else should I look to clear this issue?
0