Troubleshooting

This error occurs when the name of the rule is not unique to the rule type. For example, two decision table rules cannot be named "Student Grades". You can resolve this issue by changing the name of the repeated decision table rule to something unique, either by appending a character or number or by renaming the rule altogether.

This error occurs when you attempt to create or save a rule without a name. Although you can create a rule without a description, you cannot create one without a name. You can resolve this issue by adding a name that starts with a letter or number and contains only letters, numbers, spaces, and/or the following characters: "-", "_", "(", ")", "[", and "]".

This error occurs when you attempt to create or save a rule with a name that starts with a character other than a letter or number. For example, you cannot name a rule "<Business Process Decision>". You can resolve this issue by removing the leading bracket.

Message: The resource name cannot contain the character '!'

This error occurs when you attempt to create or save a rule with a name that contains unsupported characters such as "!". For example, you cannot name a rule "Business Process Decision!". You can resolve this issue by removing the leading character that is not supported. The following characters are supported: hyphen "-", underscore "_", open parenthesis "(", close parenthesis ")", open bracket "[", and close bracket "]".

This error occurs when you attempt to import a file into Rules that is not a .bri file. You can resolve this issue by checking the file type of the rule that you want to import.

Data queries in process automation run by converting the SQL-like expressions in the builder into SQL statements. This error appears when the resulting SQL statement contains a syntax error. You can resolve this issue by ensuring each section of the editor is defined.

For example, you might receive the error message, "The query contains a syntax error: "SELECT ALL Name FROM Country WHERE Surface_Area >"" when you do not specify the value that the surface area is greater than. You might receive the error message, "The query contains a syntax error: "SELECT ALL"" when you do not select a table in the FROM section.

This error occurs when no tables are selected in the FROM area's available tables.

To resolve, click an available table in the FROM area and click the Add > button to move it to the Selected Tables field.

This error occurs when a Column chosen in the SELECT or WHERE areas doesn't match the lookup table column data within the selected tables in the FROM area.

To resolve, click within a column field and choose a Column from the available options. You can adjust these options using the Lookup Table Editor.

This error occurs when the SELECT area's Output parameter field is set to blank, or when the WHERE area's Input value is set to blank.

To resolve, type a name in these fields that uses alphanumeric characters and underscores only. Additionally, the WHERE area's Input value must start with a letter.

This error occurs when an Output parameter or Input value field is named with a character that is not alphabetic, numerical, or an underscore.

For example, names that contain spaces, question marks, hyphens, or exclamation points would return this error.

To resolve, type a name in these fields that uses alphanumeric characters and underscores only.

This error occurs when the data source connection has not yet been verified in a Data Query.

To resolve, click the Test hyperlink under the Data Source Connection field in the right pane.

This error occurs when using a name that starts with a non-letter character in the Input field of the WHERE area.

For example, using the name "20" in the field does not start with a letter and will return this error.

To resolve, begin the name of the WHERE input field with a letter.

This error appears upon hovering over the red exclamation point when two input or output fields have identical names. The following sample decision table returns this error:

You can resolve this issue by changing one of the two overlapping names.

This error appears when an interval of numbers does not contain a value. The following sample decision table includes a few empty intervals:

You can resolve this issue by ensuring that the interval is not empty. The value on the top must be less than the value on the bottom, so these can be improved by changing the interval to (3, 4) for example.

This error appears when a character in a cell does not match the field type. The following sample table has a text value in a cell, where the field uses the Number data type.

You can resolve this issue by changing the cell value to “15” for example or the field data type to Text.

This error appears when someone can enter a combination of inputs that do not match any of the inputs on the decision table. The following decision table produces an error, because the inputs "false" and "true", as well as "true" and "true", do not match any of the input values.

You can resolve this issue by adding more combination of input values.

This error appears when a decision table is set to use a Unique hit policy and two or more input values in a field overlap. The following sample decision table receives an error upon validation, because the two cells in the Pass input field overlap.

You can resolve this issue by changing one of the values to “false”. You may also receive this error when one cell in the input field is >50 and another is <60. For values 51 to 59, there is an overlap. Learn more about the unique hit policy

This error appears in a decision table with an Any hit policy when two or more input values in one field match and the outputs are different.

You can resolve this issue by changing one of the values to match the other value. For example, the second output value can be changed to “Move on” or the second input value can be changed to “false”. Learn more about the any hit policy

The error appears when the decision table uses a no order hit policy with a numerical operation applied to the output values. The output values must all be numerical output values for the operation to work. For example, the decision table applies a sum operator to the outputs of the decision table, the outputs must be numerical for the operation to work.

You can resolve this issue by ensuring that the output values are numerical. Learn more about the single result hit policy

This error appears when your decision table contains multiple output components, but the selected rule type can only contain one component. The following sample table returns this error, because the decision table has multiple output components while the hit policy is set to Sum.

You can resolve this issue by changing the hit policy from a single result hit policy or removing the additional output components. Learn more about the single result hit policy

This error appears when the inputs do not cover all the possible inputs that may be entered into the decision table. The following sample table returns this error, because the decision table does not account for values over 10.

You can resolve this issue by accounting for all possible user inputs. For example, you can add another input value for values greater than 10.

This error occurs when you attempt to upload a file that is not in the .doc format. You can resolve this issue by ensuring that the file you want to upload is a Word document.

This general error appears when a function produces some type of error.

You can resolve these types of issues by referencing the helper text in the Functions section for a detailed explanation of how to use the function. Also, ensure that you are using the correct data type for the function. Learn more about data types

This error appears when a function is not recognized by the formula editor. The formula "NW()" for example misspells the "NOW", so the formula cannot be properly performed. You can resolve this issue by ensuring that you have spelled the formula correctly and are using one of the formulas in the Functions box.

This error appears when a part of a formula cannot be understood by the formula editor. The part that cannot be understood is identified in the error message. The formula "SECOND(2017-01-13 4:30:01 PM)" for example returns this error because the proper syntax for the SECOND function is to have quotes around the datetime object. You can resolve these issues by referencing the helper text in the Functions section for a detailed explanation of how to use the function.