Repositiory Validation

Navigation:  Reference chapter > Version 4.2 release notes >

Repositiory Validation

Previous pageReturn to chapter overviewNext page

•The validation message for validating that node list operations (e.g. PositionToNode) have a repeating element context has been updated to correct spelling errors ("arises" -> "arises", "over looked" -> "overlooked").

•The validation that warns users of tables without implementing table sets no longer gets raised for tables that are auto-linked.

•Literal operation literal values are now validated against its data type to prevent issues with code generation compilation. This validation is not something that can be violated by normal use of the decision manager, but is possible when using repositories from older versions of the decision manager/server.

•Incomplete formulas are now raised as a validation error if they are used downstream from any decision/decision group that has an action type that isn't set to "None".

•Fixed an issue that was causing ExternalContext operations to not be validated if was being used in a formula that was referenced from a decision group only.

•Fixed an issue with validation that was not reporting decision group referenced formulas/UDOs that were accessing nodes belonging to schemas not referenced by the decision model.

•Fixed an issue in the schema renderer where declaring multiple elements of the same name on the same level would cause that element to switch to unbounded - this didn't really make sense as there is no guarantee/check to see whether the elements even had the same structure. This was also causing re-used complex type elements to show up as unbounded because of the way complex types are currently processed.