Strangely, when I am adding Steps to the stages in the Payroll setup case, it tries to search for existing flows and when a step which does not correspond to an existing flow it does not allow me to save the stage. Never saw this before. And I always thought that it does not enforce such mandates on stage designer. Error thrown is shown in 2nd screenshot. Anyone faced this before, hw did it get solved ?
Running in tracer, the error messages are raised really early on (immediately after the Save button is pressed). The problem is somewhere in this bit of Java code. I'll try to debug it further. I am thinking here that I have a patch missing!
Posted: 7 years ago
Posted: 7 May 2015 5:57 EDT
Tom Holt (Tom_Holt)
Lead System Architect
OK, found the problem. I had the pyDefault Case Type rules checked out. This causes a conflict since the Case Designer 'Save' button checks out the Case Type rule, amends it (with your changes) then checks it back in. It can't do that if you already have the file checked out, so throws the suitably cryptic error.
Note to self: Don't check out pyDefault Case Type rules!