We are looking for a way to prevent our ServiceMax App/Ipad Users to log more than 12 hours per Work Order.
Based on our first approach using Validation Rules, it seems that they are only getting the Validation Rule Error when the sync is happening, we actually would like this validation rule to be triggered and displays the error message even when there is no network and that their Ipad is basically offline.
What approaches have you used or would you recommend?
I'm blessed with a very knowledgeable colleague that found a solution for that: the first time the start time is synced, use a formula field that adds 12 hours to the start time and sync that back to the device. Then have a validation against that field. That works as long as there is a sync sometime while working on the Work Order. Of course, when only working offline this will still not work. We have multiple fields added to the Work Order etc just for these offline validations. If you want more info, contact Adam Cooper from CCEP...
Hello Sylvaine Boyer. For a completely offline solution, you can use an SFM Formula to sum up the total labor hours on a Work Order onto the header. Then you can use an SFM Validation rule to throw an error upon trying to save a work order with hours greater than 12 hours. The SFM Formula function that you would need to use is found on page 138 of the "SFM TRANSACTIONS DESIGNER GUIDE". This would be worth testing to ensure that the formula calculates before the validation rule fires.
Just verified the order of execution for these offline SFM processes and the solution should work per a diagram that Engineering sent me recently. Formulas execute first and then validation rules fire.
Thank you so much Michael, would this approach trigger an error message on the ipad even if the ipad is offline when the FSR is entering his time?
Hello Rob van Waveren. I checked the ServiceMax "Apps Comparison Matrix" in the Userdocs and found this table which shows that the iPhone app does support SFM Data Validation Rules, and also SFM Formulas, so according to SMax Product team, this should work.