thanks for the code. But by this the value of the property will be removed as well. I am not that create java expert but is it also possible the error message itself and keep the not correct value of the property. When the property is resaved then the error should be removed and that works fine. So when to do Property-Set to replace the property with itself then the edit validation will disappear. Not sure if the will happen also when done by Java instead of the Property-Set methode.
The other workobject will contain the data of the corrupt workobject (as a seperate page). By this at a later stage we can investigate what was the root case of the error. The error might not related to the validation error but to another cause.
E.g. in this particular example I am working on at the moment, we have cases of which for some reason the assignments disappear while the cases are not being resolved yet. We have placed tooling to recreate the assignments, so correct the problem, but when doing this all the situation of the corrupt case will disappear.
Disappear from the Worklist/Workbasket and from the database as well? Did you double check on the database side? Any relevant information from case history to understand who/what has process/delete this assignment ?
The Page-Clear-Message method is used to delete all messages placed by the Page-Set-Messages method on the step page. Messages placed by constraints rules, edit validate rules, and property type validation are not cleared - they are cleared and the restrictions are detested only when the property value changes.