WebSphere Process Server messages     Operating Systems: All supported
CWLBT4000E: The brgFile attribute in the business rule component file {0} is missing and is required.
Explanation: The required attribute "brgFile" is not defined in the business rule component file. This attribute defines the name of the business rule file that has a file extension of ".brg".
User Action: In the business rule group component file, define the brgFile attribute.

 

CWLBT4001E: The {1} value of the brgFile attribute in the {0} business rule component file must refer to an existing business rule implementation file.
Explanation: The value of the brgFile attribute refers to a business rule component file that does not exist. The brgFile attribute must define the name of an existing business rule file, which has the file extension .brg.
User Action: Change the value of the brgFile attribute to the name of a business rule component file that exists.

 

CWLBT4002E: The {0} business rule component contains the {1} interface, which the business rule implementation does not support.
Explanation: The business rule implementation must support all the interfaces defined in the business rule component file.
User Action: Change the unsupported interface to an interface that the business rule implementation supports.

 

CWLBT4003E: The {0} business rule component file specifies an interface that is not a WSDLPortType interface.
Explanation: Business rule components support WSDLPortType interfaces only.
User Action: In the business rule component file, change the interfaces that are not WSDLPortType interfaces to interfaces that are WSDLPortType interfaces.

 

CWLBT5000E: The {0} file cannot be loaded or read.
Explanation: Either the file does not exist in the location you specified or it has errors.
User Action: Make sure the file exists and fix any errors.

 

CWLBT5001E: The targetNameSpace attribute for the artifact is missing.
Explanation: The targetNameSpace attribute is required for each artifact.
User Action: In the business rule group component file or the business rule group selection table file, specify the missing targetNameSpace.

 

CWLBT5002E: The name attribute for the artifact or operation is missing.
Explanation: The name attribute is required for each artifact.
User Action: In the business rule group component file or operation in the business rule group selection table file, add the name attribute to the artifact.

 

CWLBT5003E: An operation for the business rule group component is missing.
Explanation: At least one operation must be defined for the business rule group component.
User Action: In the business rule group component, specify at least one operation name.

 

CWLBT5004E: The selector element is missing.
Explanation: Because the selector element defines the selection algorithm that the operation uses, it is required. The system-provided default algorithm is named com.ibm.wbiservers.common.selection.GenericSelector.
User Action: In the business rule group selection table specify a selector element. The name of the selector element must be the fully qualified class name of the implementation class.

 

CWLBT5005E: The name of the {0} operation is not a valid Java identifier.
Explanation: The characters in the name of the specified operation must form a valid Java identifier.
User Action: When defining the operation name, use only valid characters for a Java identifier.

 

CWLBT5006E: The {0} operation is a duplicate of another operation.
Explanation: Each operation can be defined only once for a business rule component.
User Action: Remove the duplicate operation from the business rule component.

 

CWLBT5007E: The {0} operation is missing from the business rule group selection table.
Explanation: The operations defined by the business rule group component must also be defined in the business rule group selection table. The selection table defines the target business rules for each operation.
User Action: In the business rule group selection table, which is in the business rule component, define the operation.

 

CWLBT5008E: The specified portType elements include operations that are not defined in the business rule group component.
Explanation: All of the operations that are specified by the portType elements must be defined in the business rule group component. The business rule group component artifact defines the operations that are supported by the generated implementation for the component. A missing operation would result in the request ending with a runtime exception since the component would be unable to process the request.
User Action: In the business rule group component, define the operations that the portType elements specify.

 

CWLBT5009E: The business rule group selection table contains operations that are not defined on the business rule group component.
Explanation: The business rule group component must include all of the operations that are specified in the business rule group selection table. Operations defined in the selection table and not on the component will be unusable.
User Action: In the business rule group component, define the missing operations.

 

CWLBT5010E: The business rule group component is missing the interface definition.
Explanation: The interface element is required for the interface definition. The business rule group component implementation cannot be generated without the interface definition.
User Action: In the business rule group component, define the missing interface.

 

CWLBT5011E: The business rule group component interface is missing an interface element.
Explanation: The interface must contain at least one valid interface element, such as a port type with an operation.
User Action: Add at least one interface element to the interface, such as a port type with an operation.

 

CWLBT5012E: The portType attribute is missing.
Explanation: The portType attribute is required for WSDLPortType interfaces.
User Action: Define the missing portType attribute for the interface.

 

CWLBT5013E: The portType attribute of the interface is not valid.
Explanation: For the value of the portType attribute of the interface to be resolved to a portType object, the portType attribute must be defined by the interface.
User Action: Correct the value of the portType attribute for the interface.

 

CWLBT5014E: The definition for the selection data parameter is missing.
Explanation: The selection data must be defined as a parameter, and it must contain a valid value.
User Action: In the business rule group component, define the selection data parameter as either stand-alone or with an XPath.

 

CWLBT5015E: The JavaCode element is required.
Explanation: The selection data was defined as a code snippet, but the JavaCode element for the code snippet is missing.
User Action: In the business rule group component, define the JavaCode element.

 

CWLBT5016E: The value for the import that was specified in the code snippet is missing.
Explanation: An import that is specified in the code snippet must specify either a fully qualified class name or a package name that has a wildcard specified for the class name.
User Action: In the business rule group component, define the import value in the code snippet.

 

CWLBT5017E: The business rule group selection table is empty.
Explanation: The business rule group selection table must define at least one operation.
User Action: In the business rule group selection table, define at least one operation.

 

CWLBT5018E: An operation with the name {0} already exists in the business rule group selection table.
Explanation: Each operation can be defined only once in a business rule group selection table.
User Action: Remove the duplicate operation from the business rule group selection table.

 

CWLBT5019E: The name of the {0} operation is not a valid Java identifier.
Explanation: The characters in the name of the operation must form a valid Java identifier.
User Action: Edit the name of this operation so that it has only characters that are permitted for a Java identifier.

 

CWLBT5020E: The definition of the {0} operation is missing the rule destination.
Explanation: The operation requires at least one rule destination that is a date-based or time-based destination, or a default destination.
User Action: In the business rule group selection table, specify a date-based or time-based destination, or a default destination.

 

CWLBT5021E: The {0} destination for the {1} operation is missing a SelectionKey element.
Explanation: The destination defined for the operation must have a SelectionKey element.
User Action: In the business rule group selection table, specify a SelectionKey element.

 

CWLBT5022E: The {0} destination for the {1} operation is missing.
Explanation: The destination defined for the operation must have a SelectionData element.
User Action: In the business rule group selection table, specify a SelectionData element.

 

CWLBT5023E: The {0} starting value of this range cannot be greater than the ending value {1}.
Explanation: The starting value must be less than or equal to the ending value, or the range will not be valid.
User Action: In the business rule group selection table, set the starting value of the range to be less than or equal to the ending value, or set the ending value of the range to be greater than or equal to the starting value.

 

CWLBT5024E: The starting value of this range {0} is greater than or equal to the ending value {1}.
Explanation: The starting value of the range must be less than the ending value, or the range will not be valid.
User Action: In the business rule group selection table, set the starting value of the range to be less than the ending value, or set the ending value of the range to be greater than the starting value.

 

CWLBT5025E: {0} is not a valid date and time value.
Explanation: The date and time value must be in the format yyyy-mm-ddThh:mm:ss.
User Action: In the business rule group selection table, specify a date and time with the correct format.

 

CWLBT5026E: {0} is not a valid date value.
Explanation: The date value must be in the format yyyy-mm-dd.
User Action: In the business rule group selection table, specify a date with the correct format.

 

CWLBT5027E: {0} is not a valid integer value.
Explanation: The integer value must be in decimal digit format.
User Action: In the business rule group selection table, specify an integer value in decimal digit format. To indicate a negative value, the first character can be a minus sign.

 

CWLBT5028E: {0} is not a valid long value.
Explanation: The long value must be in decimal digit format.
User Action: In the business rule group selection table, specify a long value in decimal digit format. To indicate a negative value, the first character can be a minus sign.

 

CWLBT5029E: {0} is not a valid float value.
Explanation: The float value must specify the floating-point literal specifier "f" (for example, "1.0f").
User Action: In the business rule group selection table, specify the floating-point literal specifier "f" for the float value.

 

CWLBT5030E: {0} is not a valid double value.
Explanation: The double value must specify the floating-point literal specifier "d" (for example, "1.0d").
User Action: In the business rule group selection table, specify the floating-point literal specifier "d" for the double value.

 

CWLBT5031E: In the {0} operation, the time period for the {1} destination overlaps with the {2} destination.
Explanation: Overlapping destinations put more than one business rule into effect for a particular period of time. However, an operation can have only one matching business rule destination in effect during a particular period.
User Action: In the business rule group selection table, remove the overlapping destination from the operation.

 

CWLBT5032E: null is not a valid value for a SelectionSingletonKey element.
Explanation: The SelectionSingletonKey element must have a valid value specified.
User Action: In the business rule group selection table, specify a valid value for the SelectionSingletonKey element.

 

CWLBT5033I: Because the operation has no defined selection parameters, the default input parameter will be used.
Explanation: By default, the operation uses the input parameter.
User Action: If you do not want the operation to use the default input parameter, specify a selection parameter in the business rule group component.

 

CWLBT5034I: The default destination cannot be used because an inclusive key range is defined.
Explanation: A destination with an inclusive key range takes precedence over a default destination.
User Action: If you want to use the default destination, remove the inclusive key range from the business rule group selection table.

 

CWLBT5035W: More than one interface in the interface set contains the {0} operation.
Explanation: Although the operation is defined more than once in the set of interfaces, the operation will be defined only once on the business rule group component.
User Action: If necessary, rename the duplicate operation on the interface.

 

CWLBT5036W: The {0} operation is not defined by an interface that the business rule group component supports.
Explanation: Operations that are not defined by an interface that the business rule group component supports cannot be called.
User Action: Remove the operation from the business rule group component or define it on one of the interfaces.

 

CWLBT5037E: The {0} operation does not have a parameter named {1}.
Explanation: The XPath that is defined for the selection data points to a parameter that does not exist in this workspace.
User Action: In the business rule group component, change the XPath value so that it points to a valid parameter that exists in this workspace.

 

CWLBT5038E: The {0} property type is not valid.
Explanation: The value for the property type must be either SystemDefined or UserDefined.
User Action: In the business rule group component, change the value of the property type to either SystemDefined or UserDefined.

 

CWLBT5039E: The property name must contain at least one non-blank character.
Explanation: The property name cannot be null, the zero-length string, or a string containing only blanks. It must contain at least one non-blank character.
User Action: In the business rule group component, specify a property name that contains at least one non-blank character.

 

CWLBT5040E: The property value cannot be null.
Explanation: The value for the property cannot be set to null.
User Action: In the business rule group component, specify a valid value for the property or remove the property from the property list.

 

CWLBT5041E: The targetNameSpace attribute for the artifact is invalid.
Explanation: The targetNameSpace attribute must satisfy certain requirements, such as beginning with a letter.
User Action: In the business rule group component file and the business rule group selection table file, enter a valid targetNameSpace.

 

CWLBT5042E: The property name {0} is already in use for another property.
Explanation: The property name is being used by another property on this rule group.
User Action: Change the name of the property so that it is different from all other properties on this rule group.

 

CWLBT5043E: The display name "{0}" for the rule group {1} is too long.
Explanation: Display names for rule groups must be shorter than 250 characters.
User Action: Change the display name to one shorter than 250 characters.

 

CWLBT5044E: The property name is too long. It must be less than 250 characters.
Explanation: The name of the property attribute must be less than 250 characters long.
User Action: Change the name of the property attribute to one shorter than 250 characters.

 

CWLBT5045E: The property value is too long. It must be less than 250 characters.
Explanation: The value of the property must be less than 250 characters long.
User Action: Change the value of the property to one shorter than 250 characters.

 

CWLBT6000E: The SelectionData element is missing from the list of AvailableTargets.
Explanation: The SelectionData element must be in the list of AvailableTargets. The AvailableTargets list contains the SelectionData elements that are supported for an operation. A SelectionData element is a business rule set and decision table.
User Action: In the business rule group selection table, add the SelectionData element to the list of AvailableTargets.

 

CWLBT6001E: For each selection table entry for the operation, a rule logic destination must be specified.
Explanation: All selection table entries for an operation must have a rule logic destination specified with a valid name value.
User Action: In the business rule group selection table, specify a rule logic destination.

 

CWLBT6002E: The business rule is not found in this workspace.
Explanation: The value of businessRuleName attribute cannot be resolved to a valid business rule.
User Action: In the business rule group selection table, change the name of the business rule to one that exists in this workspace.

 

CWLBT6003E: The BusinessRuleGroupTable is missing.
Explanation: The BusinessRuleGroup element must contain a valid BusinessRuleGroupTable element.
User Action: In the business rule group component, specify the name of the BusinessRuleGroupTable.

 

CWLBT6004E: The BusinessRuleGroupTable element value is not valid.
Explanation: The value of the BusinessRuleGroupTable element cannot be resolved to a valid business rule group selection table.
User Action: In the business rule group component, change the name of the BusinessRuleGroupTable to one that exists in this workspace.

 

CWLBT6006E: The {0} Reference element already exists.
Explanation: A Reference element can be defined only once for a business rule group component.
User Action: Remove the duplicate reference from the business rule group component.

 

CWLBT6007E: The interface element for the {0} Reference element is missing.
Explanation: Each Reference element requires an interface element.
User Action: In the business rule group component, specify an interface for the specified Reference element.

 

CWLBT6008E: The SelectionKey elements used for business rules may have only one SelectionKeyElement of the Date and Time range type.
Explanation: Business rule operation definitions are restricted to only one SelectionKeyElement of the Date and Time range type.
User Action: In the business rule group selection table, remove the extra SelectionKeyElement entries from the definition.

 

CWLBT6009E: The rule logic {0} is incorrectly specified as either the scheduled rule logic or available rule logic as it does not belong to this business rule group and does not have a matching interface.
Explanation: The operation name of the business rule target destination must match the operation name of the business rule group. An incorrect operation name will result in a runtime exception and the invocation of the business rule target destination will fail. This problem typically happens when a rule set or decision table that is created with one business rule group and interface is attempted to be used in another business rule group which is using the same interface or when a rule set or decision table from one business rule group is incorrectly specified for a different business rule group.
User Action: Remove the business rule from the list of available rule logics and also remove it from an scheduled rule logic entries.

 

CWLBT6010W: The reference name, {0}, does not correspond to a reference defined on the component for this business rule group.
Explanation: The reference name specified in the business rule group file does not correspond to a reference defined on the component for the business rule group. The reference name must match the name of some reference defined on the component for this business rule group in order for the reference to be found at runtime. If WebSphere Integration Developer is being used to develop this module, then the references defined on the component can be seen in the assembly diagram for the module.
User Action: Change the reference name to match the name of some reference defined on the component for this business rule group.

 

CWLBT7000E: The name has not been specified.
Explanation: The business rule artifact does not have a name attribute. A business rule artifact must have a valid name attribute specified.
User Action: Provide a valid name attribute for the business rule artifact.

 

CWLBT7001E: The specified name is not valid.
Explanation: The business rule artifact has a name attribute specified that contains incorrect characters (such as spaces or sympols) that do not conform to standard XML requirements.
User Action: Provide a valid name attribute for the business rule artifact.

 

CWLBT7003E: The TargetNamespace has not been specified.
Explanation: The business rule artifact does not have a targetnamespace attribute. A business rule artifact must have a valid targetnamespace attribute specified.
User Action: Provide a valid targetnamespace attriubte for the business rule artifact.

 

CWLBT7004E: The interface has not been specified.
Explanation: The business rule artifact does not have an interface element. A business rule artifact must have at least one interface element specified.
User Action: Provide a valid interface element for the business rule artifact.

 

CWLBT7005E: The rulegroup has not been specified.
Explanation: The business rule set artifact does not have a ruleblock element specified. A business rule set artifact must specify one rulegroup element as each business rule artifact is associated with a single business rule group.
User Action: Provide a valid rulegroup element for the business rule artifact.

 

CWLBT7006E: The rule set "{0}" does not have a ruleblock. .
Explanation: The business rule set artifact does not have a ruleblock element. The ruleblock element contains the rulelogic for the rule set. Business rule set artifacts must have a ruleblock element specified.
User Action: Provide a valid ruleblock element for the business rule set artifact.

 

CWLBT7007E: The porttype has not been specified.
Explanation: The interface element in a business rule artifact must have at least one porttype element specified.
User Action: Provide a valid porttype element for the business rule artifact.

 

CWLBT7008E: The porttype "{0}" is not valid.
Explanation: The porttype element has a value specified that contains incorrect characters (such as spaces or sympols) that do not conform to standard XML requirements.
User Action: Provide a valid porttype element for the business rule artifact.

 

CWLBT7009E: The portType "{0}" cannot be found.
Explanation: The business rule artifact must specify at least one interface element that has at least one porttype element. During deployment of the business rule artifact, the porttype definition of the interface is used to locate the operation that is validated that the correct message parts are available to the rule logic of the business rule. In order to perform this validation, the interface is checked for the existance of the porttype.
User Action: Provide a valid porttype element for the business rule artifact or check the interface for the declaration of a porttype by the referenced name.

 

CWLBT7010E: The operation has not been specified.
Explanation: The business rule artifact must specify an operation attribute for the interface element. The operation is used to validate the correct message parts available to the rule logic of the business rule. In order to perform the validation, the operation must be specified.
User Action: Provide a valid operation attribute for the interface element in the business rule artifact.

 

CWLBT7011E: The portType "{0}" does not contain an operation to match "{1}".
Explanation: The business rule artifact must specify at least one interface element that has at least one porttype element. The interface element must contain an operation attribute that is specified on the actual porttype. During deployment of the business rule artifact, the porttype definition is checked for the operation in order to validate the correct message parts are available to the rule logic of the business rule.
User Action: Provide a valid operation attribute for the interface element in the business rule artifact or check the interface for the declaration of an operation by the referenced name.

 

CWLBT7012E: The rule group "{0}" is not valid.
Explanation: The business rule artifact is validated to insure that a rule group is specifed as each business rule artifact must be associate with one business rule group. The business rule artifact must have a rulegroup element specified that has a valid rule group specified. The specified rule group must be a valid separate artifact and attributes such as the name or namespace can not contain characters (such as spaces or sympols) that do not conform to standard XML requirements.
User Action: Verify the rule group artifact referenced by the business rule group is valid and has valid attributes for the name and namespace.

 

CWLBT7013E: The rule group "{0}" cannot be found.
Explanation: The business rule artifact is validated to insure that a rule group is specifed as each business rule artifact must be associate with one business rule group. The business rule artifact must have a rulegroup element specified that has a valid rule group specified. The specified rule group must be a valid separate artifact. The specified rule group artifact must reachable by name and namepace during validation.
User Action: Verify the name and namespace values for the rule group specified in the business rule artifact are correct for the rule group and verify the rule group artifact is packaged in the same module or JAR as the business rule artifact.

 

CWLBT7014E: The rule group does not contain a porttype to match "{0}".
Explanation: The business rule artifact is validated to insure that a rule group is specifed as each business rule artifact must be associate with one business rule group. The business rule artifact must have a rulegroup element specified that has a valid rule group specified. The specified rule group must be a valid separate artifact. The specified rule group artifact must have a porttype that matches the porttype element specified in the business rule artifact to verify the operation specified for the business rule group is avaiable.
User Action: Verify the rule group and the business rule artifacts have the porttype definitions which match.

 

CWLBT7015E: The template ID has not been specified.
Explanation: Business rule sets and decision tables may use templates to define rule defintion and expressions. The template must have a name attribute and an ID element. The ID element is used to associate a template instance with the correct template definition and must be specified.
User Action: Provide a valid ID element for the template definition in the business rule artifact.

 

CWLBT7016E: The template name has not been specified.
Explanation: Business rule sets and decision tables may use templates to define rule defintion and expressions. The template must have a name attribute and an ID element.
User Action: Provide a valid name attribute for the template definition in the business rule artifact.

 

CWLBT7017E: The template Web presentation has not been specified.
Explanation: Business rule sets and decision tables may use templates to define rule defintion and expressions. The template must have a webPresentation element.
User Action: Provide a valid webPresentation element for the template definition in the business rule artifact.

 

CWLBT7018E: The number of web presentation parameter values does not match the number of template parameters.
Explanation: Business rule sets and decision tables may use templates to define rule defintion and expressions. As part of the template definition, a Web presentation must be specified. For the Web presentation, parameters from the rule logic or expression can be substituted into the Web presentation value. The parameters which are used in the Web presentation must be defined in template.
User Action: Correct the parameter value which is specified in the Web presenation or add the appropriate parameter value.

 

CWLBT7019E: The template rule has not been specified.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template that is specified for a rule is not found in the business rule artifact.
User Action: Specify the correct template name for the rule or remove the rule and create a rule based upon a template.

 

CWLBT7020E: The constraint expression "{0}" is not valid.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters which can be contrained by a range or enumeration expression. The constraint expression must be a valid exprmatch either one of these formats.
User Action: Correct the expression for the parameter to be range or enumeration in the template definition.

 

CWLBT7021E: This constraint must be a range expression.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. If a constraint is chosen, the range or enumeration expression must be specified.
User Action: Specify the constraint expression for the range or specify no constraint for the parameter.

 

CWLBT7022E: This constraint must be either an enumeration or an expression.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. No other types of constraints can be specified.
User Action: Specify range, enumeration or no constraint on the parameter.

 

CWLBT7023E: The enumeration item has not been specified.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. For enumerations, an expression must be specified.
User Action: Specify the enumeration expression on the parameter.

 

CWLBT7024E: The enumeration item "{0}" is duplicated in the enumeration set.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. For enumerations, the list of values must not have duplicate items.
User Action: Specify a valid type for the parameter.

 

CWLBT7025E: The variable data type is unknown.
Explanation: Business rule sets may have local variables defined that can be used to hold temporal data during the executing instance of the rule set.

 

CWLBT7026E: The enumeration item data type is unknown.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. All parameter values are treated as string values and then at runtime converted to the correct type in order for the values to be used in expressions. The parameter type must be of type string, int, double, boolean, float, long, short, or byte. If an enumeration is specified for the parameter, the enumeration items must be of a type which is also of type string, int, double, boolean, float, long, short, or byte.
User Action: Check the enumeration value to be a type which matches the parameter type.

 

CWLBT7027E: The enumeration item value "{0}" is not compatible with parameter of type {1}.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. All parameter values are treated as string values and then at runtime converted to the correct type in order for the values to be used in expressions. The parameter type must be of type string, int, double, boolean, float, long, short, or byte. If an enumeration is specified for the parameter, the enumeration items must be of a type which is also of type string, int, double, boolean, float, long, short, or byte.
User Action: Check the enumeration value to be a type which matches the parameter type.

 

CWLBT7028E: The rule set must have at least one rule.
Explanation: The business rule set artifact must have a ruleblock element with at least one rule element.
User Action: Add a rule element to the ruleblock of the business rule set artifact.

 

CWLBT7029E: The rule label "{0}" is not unique within the rule set
Explanation: The business rule set artifact must have a ruleblock element with at least one rule element. Each rule in the ruleblock must have a unique name attribute.
User Action: Specify a unique value for the name attribute of the rule.

 

CWLBT7030E: The rule type "{0}" is not allowed. Please choose another type.
Explanation: The business rule set artifact must have a ruleblock element with at least one rule element. Each rule must have a type attribute that has a value of IfThenRule, AssertionRule or TemplateInstanceRule.
User Action: Specify a type attribute of IfThenRule, AssertionRule or TemplateInstanceRule.

 

CWLBT7031E: The rule template "{0}" does not exist.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. For template instances, a reference to the template is specified in a templateRef element.
User Action: Specify the correct value for an existing template for the templateRef element.

 

CWLBT7032E: The parameter value "{0}" is not defined as a parameter in the rule template
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters. Any parameters that are specified in the Web presentation for a template or used in an expression must be defined in the template.
User Action: Specify a parameter value which has been defined in the template or define the parameter in the template.

 

CWLBT7033E: The parameter value data type is unknown.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters which have a specific type. All parameter values are treated as string values and then at runtime converted to the correct type in order for the values to be used in expressions. The parameter type must be of type string, int, double, boolean, float, long, short, or byte.
User Action: Specify a valid type for the parameter.

 

CWLBT7034E: The parameter value type {0} does not match the template parameter type {1}.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with a specific type. All parameter values are treated as string values and then at runtime converted to the correct type in order for the values to be used in expressions. The parameter type must be of type string, int, double, boolean, float, long, short, or byte.
User Action: Check the parameter type value to be a type which matches the parameter type.

 

CWLBT7035E: The parameter value "{0}" does not exist in the enumeration constraint.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with a range or enumeration constraint. The parameter value must be in the range or listed in the enumeration constraint.
User Action: Specify a parameter value that is in the range or listed in the enumeration constraint.

 

CWLBT7036E: The parameter value does not exist for the template parameter "{0}".
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters. All parameters must have a value assigned.
User Action: Specify a value for the mentioned parameter.

 

CWLBT7037E: The action or invocation has not been specified.
Explanation: Business rule sets can have if-then or action rules. For if-then rules, there must be either an action or invocation element. For action rules there must be an action element.
User Action: Specify an action or invocation element for the rule in the rule set.

 

CWLBT7038E: Only action or invocation may be set.
Explanation: Business rule sets can have if-then or action rules. For if-then rules, there must be either an action or invocation element. For action rules there must be an action element. For if-then rules, only an action or an invocation element can be specifed rather than both.
User Action: Specify either an action or invocation element for the rule in the rule set.

 

CWLBT7039E: The partner link has not been specified.
Explanation: To specify an invoke, the specific partner link must be specified in the action.
User Action: Specify the name of a partner link that has been defined on the business rule group.

 

CWLBT7040E: The rule group does not contain a reference to match "{0}".
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group.
User Action: Specify a partner link that matches a partner link found on the business rule group.

 

CWLBT7041E: The rule group reference does not contain a porttype.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The partner link has an interface specified. The interface must be well-formed and contain a port type definition as an operation on the port type is also specified as part of the invoke action.
User Action: Check the interface specified for the partner link and insure that it has a port type with an operation that matches the operation specified for the invoke action.

 

CWLBT7042E: The expression data type is unknown.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input. These items or message parts are verified that they match the type of the message parts declared for the operation. The type for the input message parts specified could not be determined.
User Action: Check that each message part is of the correct type for the message parts on the operation.

 

CWLBT7043E: The invocation input data type is unknown.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the type of the message parts declared for the operation. The type for the input message parts specified in the operation definition could not be determined.
User Action: Check the operation definition in the interface that each message part is of the correct type for the message parts on the operation.

 

CWLBT7044E: The invocation input type {0} is not compatible with the referenced operation input type {1}.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the type of the message parts declared for the operation. The type for the input message part specified does not match the type of a message part of the operation.
User Action: Check that each message part is of the correct type for the message parts on the operation.

 

CWLBT7045E: The invocation Input "{0}" does not exist on the referenced operation.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the message parts declared for the operation. The input message part specified is not part of the message parts of the operation.
User Action: Verify the message part name specified for the invoke action matches a message part specified for the operation.

 

CWLBT7046E: The operation input "{0}" does not exist as an invocation input.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the message parts declared for the operation. For the input message parts of the operation, the specified part was not found to be specified in the invoke action.
User Action: Add the input message part for the invoke action or remove the message part from the operation in the interface definition.

 

CWLBT7047E: The type for variable "{0}" has not been specified.
Explanation: Business rule sets may have local variables declared to be used in the the if-then and action rules. The type for each variable must be specified.
User Action: Specify a valid type for the variable.

 

CWLBT7048E: The invocation output data type is unknown.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the type of the message parts declared for the operation. The type for the output message parts specified could not be determined.
User Action: Check the operation definition in the interface that each message part is of the correct type for the message parts on the operation.

 

CWLBT7049E: The invocation output type {0} is not compatible with referenced operation output type {1}.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the type of the message parts declared for the operation. The type for the output message part specified does not match the type of a message part of the operation.
User Action: Check that each message part is of the correct type for the message parts on the operation.

 

CWLBT7050E: The type for the rule set output "{0}" is unknown.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the type of the message parts declared for the operation. The type for the output message parts specified in the operation definition could not be determined.
User Action: Check the operation definition in the interface that each message part is of the correct type for the message parts on the operation.

 

CWLBT7051E: The invocation output is not set to a valid rule set output or local variable.
Explanation: If-then or action rules that invoke a service in a business rule set must specify an output that is either a local variable defined in the business rule set or an output message part listed for the business rule set. The ouput that is specified for the invoke action is not a local variable or an output part for the business rule set.
User Action: Specify either a local variable or a message part from the business rule set output.

 

CWLBT7052E: The invocation output is not set to a valid decision table output.
Explanation: Action expressions in a decision table that invoke a service must specify an output that is an output message part listed for the business rule set. The output that is specified for the invoke action is not an output part for the decision table.
User Action: Specify a message part from the decision table output as the output for the invoke action.

 

CWLBT7053E: The invocation output "{0}" does not exist on the referenced operation.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the message parts declared for the operation. For the output message part specified, it is not part of the message parts of the operation.
User Action: Verify the message part name specified for the invoke action matches a message part specified for the operation.

 

CWLBT7054E: The operation output "{0}" does not exist as an invocation output.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input and output. These items or message parts are verified that they match the message parts declared for the operation. For the output message parts of the operation, the specified part was not found to be specified in the invoke action.
User Action: Add the output message part for the invoke action or remove the message part from the operation in the interface definition.

 

CWLBT7057E: The name must begin with a letter.
Explanation: Within a rule set, if-then and action rules can be defined. These rules must begin with a Java permissible character as the names are used in generating the Java code that is used for executing the rule set at runtime. Java permissible characters for the beginning of the rule include letters, currancy symbol, and the underscore ("_") character.
User Action: Insure the rule name is using a Java permissible character.

 

CWLBT7058E: The name "{0}" has an invalid character "{1}".
Explanation: Within a rule set, if-then and action rules can be defined. These rules must contain Java permissible character as the names are used in generating the Java code that is used for executing the rule set at runtime. Java permissible characters include letters, numbers, currancy symbol, the underscore ("_") character, and non-space characters.
User Action: Insure the rule name is using a Java permissible character.

 

CWLBT7059E: The variable name "{0}" conflicts with variable type name "{1}".
Explanation: Business rule sets may have local variables defined that can be used to hold temporal data during the executing instance of the rule set. The name of the variable can not be the same as the type name.
User Action: Change the variable name to a value which is not the same as a type name.

 

CWLBT7060E: The type "{0}" does not exist.
Explanation: Business rule sets may have local variables defined that can be used to hold temporal data during the executing instance of the rule set. The type of the variable must be a defined type of either string, int, double, boolean, float, long, short, or byte or it must be defined with a XML schema such as a business object.
User Action: Check the variable type to be a primitive type or a defined type.

 

CWLBT7061E: The variable name "{0}" is already in use.
Explanation: Business rule sets may have local variables defined that can be used to hold temporal data during the executing instance of the rule set. Each variable must have a unique name from other defined variables.
User Action: Change the variable name to be a unique name.

 

CWLBT7063E: The template Parameter "{0}" is used multiple times in the web presentation; each parameter may only be used once.
Explanation: Business rule sets and decision tables may use templates to define rule defintion and expressions. As part of the template definition, a Web presentation must be specified. For the Web presentation, parameters from the rule logic or expression can be substituted into the Web presentation value. The parameters which are used in the Web presentation must be defined in template. Each parameter may only be used in the Web presentation.
User Action: Change the Web presentation to only use each parameter once.

 

CWLBT7064E: The template Parameter "{0}" is not used in the web presentation; each parameter must be used once.
Explanation: Business rule sets and decision tables may use templates to define rule defintion and expressions. As part of the template definition, a Web presentation must be specified. For the Web presentation, parameters from the rule logic or expression can be substituted into the Web presentation value. The parameters which are used in the Web presentation must be defined in template. Each parameter must be used in the Web presentation once.
User Action: Change the Web presentation to use each parameter once.

 

CWLBT7065W: Quotation marks are not necessary around Template value {0} of type string; if not removed, they will be considered part of the string value.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters which can be of type string. If the type is string, quotation marks are not needed. If they are specified, they will be considered as part of the parameter value.
User Action: Check that the parameter value has been specified and verify that the quotation marks which have been specified are intended.

 

CWLBT7066W: Quotation marks are not necessary around Enumeration Item value {0} of type string; if not removed, they will be considered part of the string value.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. If the type is string, quotation marks are not needed. If they are specified, they will be considered as part of the parameter value.
User Action: Check that the parameter value has been specified and verify that the quotation marks which have been specified are intended.

 

CWLBT7067E: The invocation input has not been specified.
Explanation: Business rule sets and decision tables may have actions which invoke services specifed through a partner link that is declared on the business rule group. The invoke action must have items specified for input.
User Action: Check that all input parts for the invoke have been specified.

 

CWLBT7068E: The file cannot be loaded and may be corrupt: {0}
Explanation: When a business rule set or decision table is prepared for the runtime and deployed, the rule artifact is loaded for validation. If the artifact is not proper XML or corrupted it can not be loaded for validation or code generation.
User Action: Check the file to be a readable document that is well-formed XML.

 

CWLBT7070W: A type definition and element declaration exist with the same QName "{0}"; the type definition will take precedence.
Explanation: During validation of business rule sets and decision tables, the type definitions are validated. If it is found that the definition of the type and the element surrounding the type definition have the same QName, then the type definition with the QName will be used.
User Action: No action is required.

 

CWLBT7501E: The tree node is missing.
Explanation: Decision tables must have a tree node element ("treeNode") that contains the decision table conditions and actions.
User Action: Specify a "treeNode" element in the decision table.

 

CWLBT7502E: The tree action term is missing.
Explanation: Decision tables must have an action term ("treeAction") that contains the declaration of what action should be taken for a specific condition or set of conditions.
User Action: Specify a "treeAction" in the decision table.

 

CWLBT7503E: The tree condition is missing.
Explanation: Decision tables are defined with a number of different conditions in a tabular format. All conditions in the table must be specified.
User Action: Check that all condition definitions are specified.

 

CWLBT7504E: The "{0}" attribute is set to TRUE which is not supported.
Explanation: Certain attributes of the rule artifact are defined by the rule set or decision table schema, however are not supported in the current release.
User Action: It is not supported and it should be unset or not defined and set to TRUE.

 

CWLBT7505E: The partial expression and invocation are both specified.
Explanation: For tree actions in decision tables, the action must be either an expression or an invocation. Both expressions and an invocation can not be specified.
User Action: Specify either an expression or invocation for the tree action.

 

CWLBT7506E: The template and invocation are both specified in this decision table.
Explanation: In a decision table, you cannot define an action rule as a template and then also specify the rule to invoke a service call in a tree action.
User Action: Specify either a template or an invocation for the tree action.

 

CWLBT7507E: The expression and template are both specified in this decision table.
Explanation: In a decision table, action rules defined as templates cannot also have expressions.
User Action: Specify either an expression or a template for the tree action.

 

CWLBT7508E: The expression, template, and invocation are all specified.
Explanation: In a decision table, action rules defined as templates cannot also have expressions or invoke a service call.
User Action: Specify either an expression, template, or invocation for the tree action.

 

CWLBT7509E: The expression, template, or invocation is missing.
Explanation: Decision table action rules must be defined with an expression, template or service invocation.
User Action: Specify only an expression, template, or invocation.

 

CWLBT7510E: The template is missing.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template for the definition or expression can not be located.
User Action: Insure the correct template name is specified for the rule definition or expression or define the named template.

 

CWLBT7511E: The next action or condition is missing.
Explanation: The definition of a decision table is made of a balanced tree structure where each condition has a child condition or child action.
User Action: Specify a condition or action for the current condition.

 

CWLBT7512E: The tree condition value is missing.
Explanation: The definition of a decision table is made of a balanced tree structure where each condition has a child condition or child action. If a child condition is specified, a condition value must be specified for the condition.
User Action: Specify a condition value for the tree condition.

 

CWLBT7513E: The case edge is missing.
Explanation: The definition of a decision table is made of a balanced tree structure where each condition has a child condition or child action. The different child elements are defined in a case edge element.
User Action: Specify a case edge for a condition node.

 

CWLBT7514E: The tree action(s) is missing.
Explanation: The action node of a decision table must have a tree action ("treeAction") defined that contains the tree actions for the node.
User Action: Specify treeAction for the action node.

 

CWLBT7516E: The orientation is wrong. The number of columns must match the number of rows in this decision table.
Explanation: Decision tables can have an orientation of either column or row. Any other value is not allowed.
User Action: Specify either row or column for the orinetation for the decision table.

 

CWLBT7517E: The tree condition term is missing
Explanation: Decision tables have condition nodes which are made up a term and different condition values that are compared to the term.
User Action: Specify a condition term for the condition node.

 

CWLBT7518E: The condition value and template cannot both be specified.
Explanation: In decision tables, the condition node will have a condition term and different condition values. The condition values can be specified explicitly or through a template definition. Only one is accepted.
User Action: Specify either a value or template for the condition node.

 

CWLBT7519E: The partial expression template is missing.
Explanation: In decision tables, the condition values may be defined with a template which is referenced by a specific ID.
User Action: Specify a template for the condition value that is defined or define a template by the appropriate ID.

 

CWLBT7520E: The term template is not supported.
Explanation: In decision tables, the condition term must be specified with an expression. A template can not be used to define a condition term value.
User Action: Specify an expression for the condition term.

 

CWLBT7521E: The partial expression must be specified.
Explanation: In decision tables, the condition term may be defined with an expression.
User Action: Specify a condition term with an expression.

 

CWLBT7522E: Only the partial expression can be specified.
Explanation: In decision tables, the condition term may be defined with a template or an expression, however for the current release only an expression is supported.
User Action: Specify a condition term with an expression.

 

CWLBT7523E: Template instance expressions are not supported.
Explanation: In decision tables, the condition term may be defined with a template or an expression, however for the current release only an expression is supported.
User Action: Specify a condition term with an expression.

 

CWLBT7525E: The tree action term''s partial expression templates are missing
Explanation: In decision tables, the action node will have at least one action term and different action values. The list of templates for the expressions can be empty, but it must exist.
User Action: Specify an expression template or define an empty list.

 

CWLBT7526E: The tree action term''s partial expression is missing
Explanation: In decision tables, the action node will have at least one action term and different action values. The action term must be specified with an expression.
User Action: Specify an expression for the action term.

 

CWLBT7527E: The constraint can only be a range.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. If a range constraint is specified, it must be a range expression.
User Action: Check the constraint on the parameter to insure it is a properly specified range expression.

 

CWLBT7528E: The value is not in the constraint list.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. If an enumeration is specified, the value for the parameter must be in the enumeration.
User Action: Specify a parameter value which is in the enumeration.

 

CWLBT7529E: The constraint list has an invalid element.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. If an enumeration is specified, a value must be specified. The value may be an empty string, but it can not be null.
User Action: Check the values specifed for the enumeration of the parameters.

 

CWLBT7530E: The constraint list has a duplicate element.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. If an enumeration is specified, values can not be duplicated.
User Action: Check the values specifed for the enumeration of the parameters and insure there are no duplicates.

 

CWLBT7531E: The parameter value''s type does not match the parameter type.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. The parameter type must be of type string, int, double, boolean, float, long, short, or byte. If an enumeration is specified for the parameter, the enumeration items must be of a type which is also of type string, int, double, boolean, float, long, short, or byte. The value for the parameter must be convertable to the type specified for the parameter.
User Action: Check the parameter value and insure that it can be converted to the parameter type.

 

CWLBT7532E: The parameter value does not match a parameter.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters with range or enumeration constraints. For parameters with an enumeration constraint, the parameter value must be defined in the enumeration.
User Action: Check the parameter value to insure it is correct for the enumeration constraint.

 

CWLBT7533E: The number of template parameter values is incorrect for the template definition.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters. The number of parameter values does not match the number of defined parameters.
User Action: Check the number of parameter values and make sure it matches the number of the parameters defined in the template.

 

CWLBT7534E: The template expression values are missing.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters. Values must be specified for each paramter.
User Action: Check the number of parameter values and make sure it matches the number of the parameters defined in the template.

 

CWLBT7535E: The template parameters are missing.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters. The parameters for the template instance must be specified.
User Action: Check that the parameters for the template instance are specified with values.

 

CWLBT7536E: The action term cannot have a partial expression specified.
Explanation: In decision tables, the action node will have at least one action term and different action values. The action term must be specified with an expression or an invoke action. If an action term is indicated to be specified, it must have expression.
User Action: Specify an expression for the action term.

 

CWLBT7537E: The termNotApplicable attribute is set to "{0}" so the "{1}" cannot be specified.
Explanation: =In decision tables, the action node will have at least one action term and different action values. For the action value, the value can either be an expression or an invoke action. The termNotApplicable attribute indicates if an expression or an invoke action can be performed. Only an expression or invoke is allowed and is defined by the attribute termNotApplicable. If termNotApplicable is set to TRUE, the expression can not be set to invoke. If termNotApplicable is set to FALSE, the expression can not be set to partial_expression.
User Action: Specify the correct value for termNotApplicable if an invoke action is specified or if an expression is specified.

 

CWLBT7538E: The termNotApplicable attribute is set to "{0}" so the "{1}" must be specified.
Explanation: In decision tables, the action node will have at least one action term and different action values. For the action value, the value can either be an expression or an invoke action. The termNotApplicable attribute indicates if an expression or an invoke action can be performed. Only an expression or invoke is allowed and is defined by the attribute termNotApplicable. If termNotApplicable is set to TRUE, the expression can not be set to invoke. If termNotApplicable is set to FALSE, the expression can not be set to partial_expression.
User Action: Specify the correct value for termNotApplicable if an invoke action is specified or if an expression is specified.

 

CWLBT7539W: Actions or conditions following an unconditional return expression will never be run.
Explanation: In the rules for a rule set, a return statment can be specified. If the return statment is in an unconditional expression and there are any action or conditions after the return, these statements will not be executed at runtime.
User Action: Change the rule logic in the rule set to either remove the return statment or to change the order of the rules.

 

CWLBT7540E: Name, "{0}", is not valid: It is the same as another rule set or decision table.
Explanation: A rule set or decision table which is validated must be unique from other rule sets or decision tables which are defined in the module. Each rule set or decision table must have a unique file name.
User Action: Specify a different file name for the rule set or decision table.

 

CWLBT7541E: Property type, {0}, is not allowed. Property type must be either SystemDefined or UserDefined.
Explanation: Properties can be specified for business rule groups. The properties can be of type SystemDefined or UserDefined
User Action: Check the type of the property to be SystemDefined or UserDefined.

 

CWLBT7542E: Property name is not specified or is the zero-length string.
Explanation: Properties can be specified for business rule groups. The business rule properties are specified with a name and value. The property name must be specified and can not be of zero-length.
User Action: Check the name of the property.

 

CWLBT7543E: Property value is not specified.
Explanation: Properties can be specified for business rule groups. The business rule properties are specified with a name and value.
User Action: Check the properties on the business rule group for values.

 

CWLBT7544E: The template parameter value {0} is not less than {1}.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters that can have constraints placed on the allowed values. A value is being specified for a template parameter that is not within the allowed range specified by the constraint on the parameter.
User Action: Specify a value that is within the allowed range for the template parameter.

 

CWLBT7545E: The template parameter value {0} is not less than or equal to {1}.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters that can have constraints placed on the allowed values. A value is being specified for a template parameter that is not within the allowed range specified by the constraint on the parameter.
User Action: Specify a value that is within the allowed range for the template parameter.

 

CWLBT7546E: The template parameter value {0} is not greater than {1}.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters that can have constraints placed on the allowed values. A value is being specified for a template parameter that is not within the allowed range specified by the constraint on the parameter.
User Action: Specify a value that is within the allowed range for the template parameter.

 

CWLBT7547E: The template parameter value {0} is not greater than or equal to {1}.
Explanation: Business rule sets and decision tables may use templates to define rule definition and expressions. The template can be defined with parameters that can have constraints placed on the allowed values. A value is being specified for a template parameter that is not within the allowed range specified by the constraint on the parameter.
User Action: Specify a value that is within the allowed range for the template parameter.

 

CWLBT7548E: The namespace {0} is not a valid Uniform Resource Identifier.
Explanation: The business rule artifact has a namespace value that is not a valid Uniform Resource Identifier. The namespace value must be a valid Uniform Resource Identifier. Refer to the XML schema documentation for more information about namespaces.
User Action: Specify a valid Uniform Resource Identifier for the namespace of this artifact.

 

CWLBT7549E: Property name, "{0}", is too long.
Explanation: Property names cannot be longer than 250 characters.
User Action: Shorten the name of the property.

 

CWLBT7550E: Property value, "{0}", is too long.
Explanation: Property values cannot be longer than 250 characters.
User Action: Shorten the value of the property.

 

CWLBT7551E: Interface file, {0}, has errors in it.
Explanation: Rule logic files cannot be processed if the corresponding interface file has an error in it.
User Action: Correct the interface.

 

CWLBT7552E: The type "{0}" is not supported for template parameters.
Explanation: Business rule sets may have parameters defined. This particular type is not supported for parameters.
User Action: Change the parameter type to a supported type.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009