I have run SD45ViewRules.cmd against our test/development environment and we seem to have alot of issues, rules cannot be deserialised, can you tell me exactly what this means and what the impact these rules could have on our environment?
that is interesting. I have run this in the past and found rules like Jay. However the rules appeared to work ok when tested so we left them as they were but noted that if a rule didn't work in the future to take this into consideration.
I wonder of the deserialisation tool reports with 100% accuracy.
I have taken your case with the following description: I have run sd45viewrules.cmd and the log file shows a number of ours rules could not be deserialised, does this mean that the rule is not used? are these rules corrupt?
I logged a few questions last year about this tool and got the same "definitive" reply - ie if the tool says a rule can't be deserialised, then that rule is useless and won't/can't ever execute. HP said there is no way to get any info about what the rule was, and that it should be deleted. Of course it's worrying because you don't know which rules you've lost....unless you have a detailed design to compare back to.