I’m trying to understand the new validation checks in program rules for v40. Our previous instance (on 2.37.9.1) gives a valid checkmark, however the same program rule notes both “Expression is not valid” and also “0 error(s), 6 warnings”. To be clear, the program rule is functional on both instances (including v40 where it is saying it is not valid).
Questions:
Is there a way to get more information about the “warnings” being noted? Looking around in the console, can’t see anything useful here.
Should I expect that warnings are recommendations vs. errors which note actual lack of program Rule functionality?
Anyone have any guesses as to what the 6 warnings relate to for the example below? Screenshots from 2.37 and v40 instances below
This is pure hypothesis and I’m also interested in having an “official” explanation, but:
2/ I’d assume that the nomenclature is the same as for program rules action
3/ There are 6 iterations of {SOP code} > xyz so those could be your 6 warnings and I could see that there might be something around value type (inability to assess?) issuing a warning.
Agreed on both points—I’m thinking its likely the combination of > and the ProgramRuleVariable, as the 7th iteration of the PRV can be in ‘’ or #{} and still no additional warning appears.
@jason Actually I think you’re right—this is an option set DE which defaults to text in the format. That said, it does actually respect the rule because, I suppose, it finds numbers when it searches for the values. Point more generally is 2.37 says is valid (and it works), V40 says it is not valid (still works) but perhaps correctly is noting some best practices being ignored. Makes me wonder if 2.37’s “validity” note + V40’s “Warnings” are the best combination here
@Matthew_Boddie, could you share a screenshot of the dev console? Also, if possible, check the Catalina logs to see if there’s any useful information there
