Warning messages

Navigation:  Testing and releasing the repository > Validating the repository > Validation messages >

Warning messages

Previous pageReturn to chapter overviewNext page

Table 7-4 details all of the warning error validation messages that may occur during the validation process and provides a brief description of their meaning:

Warning Validation Message

Description

Following decisions do not have corresponding formulas.

Decisions are attached to a set of formulas through 'Formula References'. When a decision is run, the appropriate formula is chosen out of the set of referenced formulas, and is used to determine the result of that decision. In order to achieve a result, a decision should be attached to at least one formula, otherwise the decision will do nothing. This validation returns a warning if a decision does not refer to any formulas.

 

These Operations delete their caller decision group's contexts.

 

Decision groups are associated with paths to nodes on a Customized Schema, and these decision groups are used to determine how their descendent decisions are executed. Decisions can be grouped under multiple levels of decision groups, all of which influence how that decision is to be run. Decisions can execute formulas, which can remove nodes in a Customized Schema. In some situations, a decision (grouped under at least one decision group) could remove a node on the Customized Schema which is used in one (or more) of the paths of that decision's ancestor decision groups. This means that the information that is used to determine how a decision is to be executed is being removed. This validation returns a warning when this scenario occurs. Note that this validation only gives a warning, as under some circumstances, there are legitimate uses for this scenario.

 

 

Following formulas have no child formula versions.

 

Formulas contain one or more Formula Versions which comprise the execution logic for the formula. If a formula contains no Formula Versions, it cannot be executed. This validation returns a warning when a formula contains no Formula Versions.

 

Following Formula Versions are referenced but incomplete.

 

Usually, formulas are executed by a decision (through a Formula Reference) or by another formula or a UDO (through an 'ExecuteFormula' operation). When a formula is incomplete, it cannot be executed properly and will be treated as though it did not exist. A formula is considered to be incomplete when on of the Formula Versions has not be completed. While it is possible to run the decision Server with references to incomplete formulas, there is no logical reason to do so. This validation will return a warning when an incomplete Formula Version is found within a formula that is referenced.

 

Following items have more than one element that are effective dated in the future.

 

In a repository, certain items, including Table Contents, Formula Versions, and Formula References, are stored in groups. These items have an effective date and an end date, which together describe the interval during which the item is valid. Given an item, at any time earlier than the effective date, or later than the end date, the item will be considered invalid. If any group has an item effective dated in the future, then, at that date, this item will become the current item and the behaviour of the Rules engine will be adjusted accordingly. If any group has more than one item effective dated in the future, then there will be multiple dates in the future where the behaviour of the Rules Engine will be adjusted. This does not cause any problems, but the Rules Expert should be made aware of this situation. This validation returns an warning when there is more than one item in a group that has an effective date set sometime after the release date.

 

Following Formula Versions/UDOs have node enumeration related Operations that are pointing to an incorrect enumeration value.

Formula Versions and UDOs can contain NodeEnum operations, which relate to enumerations on a Customized Schema. A NodeEnum operation contains a location of a node on a Customized Schema, such as '/Report/DayOfWeek', and a query value, such as 'Saturday'. The NodeEnum operation will return true if the value at that node on the input document is equal to the query value, or false otherwise. The query value of a NodeEnum operation must be one of the legitimate values specified in the enumeration, as defined on the Customized Schema. If a NodeEnum operation has a value that is not specified in that enumeration, then that operation will not be processed correctly. This validation returns a warning if a formula or UDO has a NodeEnum operation with a value that does not belong to the associated enumeration.

 

Following Formula Versions/UDOs have Summation operations that will never execute.

 

Formula Versions and UDOs are composed of operations. Operations can be grouped into categories by the name of the Operator that they use. The 'Summation' operator is used to calculate the sum of a sequence of terms. A 'Summation' operation should define a parameter, for example 'var', and some beginning value and end value for that parameter. If the end value is less than the start value, then the Summation operation will always return zero. This validation will return a warning if a summation operator is defined that has an end value less than the start value.

 

Following Tables do not have implementing TableContents.

 

Tables define a number of columns, along with their associated names and data types. Table Contents belong to a Table and can have any number of Table Rows. Tables and Table Contents are used together to support Formula Versions and UDOs; for example, a Formula Version might use a 'TableLookup' operation to find the value of a certain field on a row inside a set of Table Contents. Any Tables that have no associated Table Contents cannot provide any meaningful information to either Formula Versions or to UDOs. This validation returns a warning if a Table has no associated Table Contents.

 

Following UDOs have Parameters that are never used.

 

UDOs accept a number of parameters and return a result. These parameters have names and associated data types; for example, a name such as 'Surname' and a data type such as 'string'. Usually, parameters used inside the UDO affect the result of that UDO in some way. Parameters that are not used inside a UDO do not contribute in any meaningful way to the behaviour of that UDO. Such parameters are unnecessary and should be deleted. This validation returns a warning if a UDO has one or more parameters that are not used.

 

Table 7-4: Validation Messages - Warning Messages