Support Article
Rule resolution uses wrong class after check out then check in
SA-1027
Summary
There is an issue with rule check-in where it creates the pyWorkPage with the obj-class Work-ProjectManagement-CheckIn, but it does not delete pyWorkPage when the check-in is complete.
Error Messages
Failed to find instance Work-ProjectManagement-CheckIn.ValidSearchCriteria for non personal RSLH cde91c70b771df695c3b22fe79bac01b Top App Hash ProducersSelfService!en_US_!PSS:Administrators!02.20$159ec3605bc287a9ee7552996b76cd2d of type Rule-Obj-When.
Steps to Reproduce
This error happens everytime you check out or in a rule, and just try to run the application without logging out and back in.
Root Cause
Despite best attempts by development to address all the avenues and paths by which a pyWorkPage may be created and/or referenced by the engine (thus creating a blank page on the clipboard) there are still additional paths that can create a pyWorkPage. It is not feasible or appropriate to attempt to eliminate or cancel out all of these permutations, and that rather this problem *must* be addressed by protective code that checks the class of the pyWorkPage and/or for the existence of expected properties.
Resolution
This issue is resolved through the following local change: added protective code that checks the class of pyWorkPage or for the existence of expected properties.
Published June 12, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.