Hi Bradley,
Thanks for the response. I understand that the logout and login will refresh the data. But user wants to avoid typing in16 digit password.
To solve this I am assuming there should be some method in framework which product team might be using.
I did some digging and thought method ModelService.allWithOslcWhereAndLocalQuery is something useful and added it in completionHandler to see what it does.
ModelService.allWithOslcWhereAndLocalQuery('activeCrew',null,null,'getUserCrew', 100, false).then(function (activeCrewSet) {
console.log('testing');
}).otherwise(function(error) {
console.log('error');
});
When I see contents of activeCrew, that is coming out of this call, its not changed.
------------------------------
Prasad Pandari
------------------------------
Original Message:
Sent: Fri March 25, 2022 06:50 PM
From: Bradley Downing
Subject: Forcing the system data resource refresh
Prasad,
The design intent of System Data was that this is pretty static in nature and would rarely change. As such the perceived need (on the designers' part) to refresh it is pretty infrequent. An occasional log-out and log-in (say once a day for example) is thought to be sufficient to enable a system refresh on a frequency such that users should have pretty timely data refresh on system level data. Examples of System Level Resources are MyLabor, Domains (Synonym, ALN, Numeric), the WOSTATUS object, WPEDIT Settings, and the CrewLabor Object. These typically are fairly static, and again if there is a need to change, a simple log-out and log-in and end of shift or beginning of shift should be a very light requirement for a user to accept. Hope this helps.
------------------------------
Bradley K. Downing , MBA
Solutions Engineer
IBM
Bakersfield CA
------------------------------