Oracle Policy Modeling Error Codes
If any errors are detected in your project, including errors with rules, the data model or the interview, an error pane will be displayed below the command bar in Policy Modeling. The following table lists the error codes, the error messages and the topics to refer to to help you understand and resolve the issues.
Tip: You can click on the error text in Policy Modeling to go to the source of error.
Error code | Message | Further information |
---|---|---|
OPA-E00023 | Relationship '{0}' is a multiply proven relationship. | Fix a Multiply Proven Attributes Error |
OPA-E00024 | Attribute '{0}' is a multiply proven attribute. | |
OPA-E00046 | Attribute '{0}' has a broken parse. Please verify there are no missing custom verbs. | Change the Sentence Forms for an Attribute |
OPA-E00074 | Raise event function must be in conclusion style. | Write an Error Event Rule |
OPA-E00075 | Text in configuration style must match one of the supported configuration functions. The function '{0}' is no longer supported. | Function Reference |
OPA-E00085 | Compiler failed to write which should have implied errors. | Please contact support for this issue. |
OPA-E00089 | An explicit intermediate premise must have subordinate premises. | BOTH, ALL, EITHER and ANY Grouping Operators |
OPA-E00090 | The premise looks like an intermediate premise but doesn't have any subordinate premises. | |
OPA-E00091 | Explicit conjunctions should not have any premises underneath them. | AND and OR Connectors |
OPA-E00092 | '{0}' and '{1}' should not be used in an intermediate premise. | |
OPA-E00093 | The last premise should not have a conjunction. | |
OPA-E00094 | Inconsistent conjunction used. | |
OPA-E00096 | Condition text cannot be empty. | Define Decision Tables In Excel Workbooks |
OPA-E00118 | A closing quotation mark is missing in the message text. | Validate User Input |
OPA-E00119 | Message text must be contained within quotation marks. | |
OPA-E00130 | Duplicate definition of attribute text: {0}. | Specify Data Types for Attributes In Excel |
OPA-E00139 | Apply-sheet rules cannot have further conclusions. | Split Rule Tables According to the Date They Apply From |
OPA-E00141 | Apply-sheet rules cannot be used with negative attribute conclusions. | |
OPA-E00142 | The worksheet '{0}' is used by multiple apply-sheet rules. | |
OPA-E00168 | Sheet not found: {0}. | |
OPA-E00174 | Missing '{0}' or '{1}' between conditions. | Walkthrough of Creating a Word Rule |
OPA-E00207 | Missing a conclusion line. | |
OPA-E00209 | '{0}' is not available here. You may need to use an entity function to refer to '{1}'. | This error often occurs when improperly referring to an entity or relationship. If you are not intending to infer from one entity to another, consider rewording your attributes (see Choose Attribute Text and Attribute Names). If you are intending to infer from one entity to another, see Use an Entity Or Relationship In a Rule. |
OPA-E00226 | The inferred relationship '{0}' must be proved in the primary direction. | Write Rules That Infer Relationships and Entities |
OPA-E00229 | Invalid legend key '{0}'. | Specify Data Types for Attributes In Excel |
OPA-E00232 | Missing definition of attribute text. | |
OPA-E00234 | Unsupported attribute type: {0}. | |
OPA-E00246 | Text in configuration style must match one of the supported configuration functions. Check the text is in the correct style or refer to the OPM Function Reference for supported configuration functions. | Function Reference |
OPA-E00300 | Relationship '{0}' is used to infer entity instances, but '{1}' is not related to the direct parent entity of '{2}'. | Write Inferred Entity Rules In Excel |
OPA-E00302 | Missing definition of attribute type. | Define Decision Tables In Excel Workbooks |
OPA-E00305 | Duplicate definition of legend key: {0}. | |
OPA-E00317 | The form file name contains invalid characters. It must not contain any of the following characters: {0}. | Invalid Characters for File and Folder Names |
The form control file name contains invalid characters. It must not contain any of the following characters: {0}. | ||
The new file name contains invalid characters. It must not contain any of the following characters: {0}. | ||
The new folder name contains invalid characters. It must not contain any of the following characters: {0}. | ||
The project file name contains invalid characters. It must not contain any of the following characters: {0}. | ||
The file name {0} contains invalid characters. It must not contain any of the following characters: {1}. | ||
OPA-E00341 | Internal error: unknown compiled entity '{0}'. | Please contact support for this issue. |
OPA-E00345 | Inferred entity '{0}' does not have an identifying attribute. | Write Rules That Infer Relationships and Entities
|
{0} must have an identifying attribute because it is a mapped child of an entity dynamically loaded by a query | Identifying Attributes for Entities | |
OPA-E00348 | Argument {0} for {1} is {2} but is required to be {3}. | Function Reference |
OPA-E00350 | Cannot determine an automatic type for attribute '{0}'. Please choose one manually. | Attribute Types |
OPA-E00352 | Error saving Interview: {0}. | Check the file save location. If the error persists, contact support. |
OPA-E00355 | Error occurred starting debugger: {0}. | Try closing and re-opening Policy Modeling, restarting your computer if necessary. Alternatively there may be a problem with your installation. See Install Policy Modeling. If the error persists, contact support. |
OPA-E00393 | The input control '{0}' ({1}) has no associated attribute. | The input control is either invalid or it may have referred to an attribute that has been removed from the data model. Delete the input and (if required) re-add an input for the correct attribute. See Add Questions to Screens. |
OPA-E00394 | The input attribute '{0}' does not belong to the entity '{1}'. | The entity level of a screen control may have changed, making the screen definition invalid. Delete the input and re-add to a valid screen. See Add Questions Or Information From Different Entity-Levels to the Same Screen. |
The input attribute '{0}' does not belong to the entity '{1}' or one of its ancestors. | ||
OPA-E00395 | The input style '{0}' is not valid. | A screen control is no longer valid. Delete and re-add this control. See Create a Screen. |
OPA-E00396 | The static default value '{0}' is not valid for an input attribute of type '{1}'. | Specify the Values for an Input |
OPA-E00397 | No list options have been provided for the list input control. | |
OPA-E00398 | Duplicate list entries for value '{0}' detected. Each value must be unique for a given list. | |
OPA-E00399 | The list value '{0}' is not valid for an input attribute of type '{1}'. | |
The list value '{0}' does not meet the input restrictions for attribute '{1}'. | ||
OPA-E00400 | The static default value '{0}' is not a valid list option. | |
OPA-E00401 | The entity '{0}' is not parented by '{1}'. | Add Questions Or Information From Different Entity-Levels to the Same Screen |
The entity '{0}' is not parented by '{1}' or one of its ancestors. | ||
OPA-E00403 | The {0} '{1}' contains an unrecognized substitution attribute '{2}'. | The % character should only be used as an attribute substitution character. If it needs to occur within a URL (that is for HTML encoding of spaces), it is required to be escaped with another % so that you have two % characters together. |
OPA-E00404 | The {0} '{1}' contains invalid substitution parameter(s): '{2}'. | Personalize Attribute Text |
OPA-E00405 | The specified default value attribute '{0}' is not of type {1}. | Specify the Values for an Input |
OPA-E00406 | The specified default value attribute '{0}' does not belong screen's entity context '{1}' or one of its ancestors. | Specify the Values for an Input
Collect Entity Data |
OPA-E00407 | Alias '{0}' is not available here because of an intermediate rule. | Use an Entity Or Relationship In a Rule |
OPA-E00409 | An alias cannot be defined when testing membership of a relationship. | |
OPA-E00411 | This text already has a translation (see cell {0}). | Translate Policy Models Into Other Languages |
OPA-E00413 | Tab characters are not permitted in rules. | Walkthrough of Creating a Word Rule and Overview of Reference Tags |
OPA-E00414 | Missing condition. | Walkthrough of Creating a Word Rule |
OPA-E00415 | Inferred relationship must not reference an alias. | Write Rules That Infer Relationships and Entities |
OPA-E00416 | Inferred relationship target entity must not reference an alias. | |
OPA-E00417 | Inferred relationship '{0}' does not refer to instances of '{1}'. | |
OPA-E00419 | Cannot infer membership of the containment relationship '{0}'. Did you intend to write an inferred entity rule? | This error often occurs when improperly using the membership function. If you are intending to infer membership, see Use an Entity Or Relationship In a Rule. If you are not intending to use this function, see Choose Attribute Text and Attribute Names. |
OPA-E00420 | Ambiguous alias references: Both '{0}' and '{1}' were used. | Use an Entity Or Relationship In a Rule |
OPA-E00424 | The conclusion attribute '{0}' is of type '{1}' and cannot be assigned from a value of type '{2}'. | Function Reference |
OPA-E00425 | Condition is not a Boolean expression. | Walkthrough of Creating a Word Rule |
OPA-E00426 | Custom function '{0}' is no longer available. | Upgrade a Project |
OPA-E00429 | The entity '{0}' cannot be bound to '{1}'. | Overview of Data Mapping |
OPA-E00430 | The entity '{0}' cannot be bound to '{1}'. Inferred entities can only be bound if the top-level output mapping is update/create. | |
OPA-E00431 | The attribute '{0}' is mapped in or mapped out but entity '{1}' is not bound. | |
OPA-E00432 | The attribute '{0}' has an invalid mapped in '{1}'. | |
OPA-E00433 | The attribute '{0}' has an invalid mapped out '{1}'. | |
OPA-E00434 | The type of attribute '{0}' ({1}) is not compatible with the type of mapped in '{2}' ({3}). | |
OPA-E00435 | The type of attribute '{0}' ({1}) is not compatible with the type of mapped out '{2}' ({3}). | |
OPA-E00436 | The user profile in mapping settings is invalid. The table '{0}' does not exist. | |
OPA-E00437 | The mapping input in mapping settings is invalid. The table '{0}' does not exist. | |
OPA-E00438 | The mapping output in mapping settings is invalid. The table '{0}' does not exist. | |
OPA-E00440 | The mapping '{0}' of entity '{1}' is invalid. | |
OPA-E00441 | The mapping '{0}' of entity '{1}' is incompatible with the containment relationship. | |
OPA-E00442 | Substitution attribute '{0}' has incorrect case (should be '{1}'). | Personalize Attribute Text |
OPA-E00443 | Substitution attribute '{0}' not recognized. | |
OPA-E00444 | The project '{0}' could not be
opened. Reason: {1}
Project language {0} is either an invalid culture identifier or not supported by the operating system. Project region {0} is either an invalid culture identifier or not supported by the operating system. |
Try opening the project again,
check the project exists, restarting your machine if necessary. If the error persists, contact support.
If the project language or region appears invalid, you may be trying to open a project created with a locale only available on later operating systems. For example, "es-419" is a generic locale for Latin America that was introduced in Windows 8. |
OPA-E00445 | A project with the same name already exists. Please choose another name or folder. | Create a new project |
OPA-E00446 | The project cannot be uploaded. Its zipped size ({0}) exceeds the size limit of {1}. | The default size limit is 64 MB. Consider reducing the size of interview images and Form templates in your project. See Add Images to Screens and Design an RTF Template for a Form. If the error persists, contact support. |
OPA-E00447 | Cannot undo because the {0} '{1}' no longer exists. | The previous action cannot be undone. |
OPA-E00448 | Cannot redo because the {0} '{1}' no longer exists. | The previous action cannot be redone. |
OPA-E00449 | Failed to delete: {0}. | Try deleting again, restarting your machine if necessary. If the error persists, contact support. |
OPA-E00450 | Unable to undo: {0}. | The previous action cannot be undone. |
OPA-E00451 | The entity '{0}' is inferred and cannot be collected on a screen. | Collect Entity Instances |
OPA-E00452 | Invalid conclusion. A rule must conclude one of the following: Boolean attribute, direct attribute assignment, relationship membership, entity instance existence, or an event. Refer to the Oracle Policy Modeling documentation for more information. | Walkthrough of Creating a Word Rule |
OPA-E00453 | Scoping functions must have at least one subordinate premise. | This error often occurs when improperly referring to an entity or relationship. If you are not intending to infer from one entity to another, consider rewording your attributes (see Choose Attribute Text and Attribute Names). If you are intending to infer from one entity to another, see Use an Entity Or Relationship In a Rule. |
OPA-E00454 | '{0}' cannot be used as an alias because it is already the name of an entity. | Use an Entity Or Relationship In a Rule |
OPA-E00455 | Can not save project file: {0}. | Try saving again, restarting your machine if necessary. If the error persists, contact support. |
OPA-E00456 | Rules folder '{0}' does not exist. | Check the folder exists on your machine. If the error persists, contact support. |
OPA-E00457 | Can not save file '{0}': {1}. | Try saving again, checking the file location and restarting your machine if necessary. If the error persists, contact support. |
OPA-E00459 | The project '{0}' could not be opened because the project directory (or one of the files in it) is read-only. | Check your policy modeling files are writeable using Windows Explorer. If the error persists, contact support. |
OPA-E00462 | The substitution attribute '{0}' in {1} '{2}' does not belong to the entity '{3}'. | Collect Entity Data |
Personalize Attribute Text | ||
OPA-E00463 | The substitution attribute '{0}' in {1} '{2}' does not belong to the entity '{3}' (or one of its ancestors). | Collect Entity Data |
Personalize Attribute Text | ||
OPA-E00465 | Negative sentences are not allowed in a generic conclusion column. If necessary, rewrite this conclusion with its own conclusion column. | Define Decision Tables In Excel Workbooks |
OPA-E00467 | Failed to launch interview: The Embedded Tomcat location could not be found. | Try closing and re-opening Policy Modeling, restarting your computer if necessary. Alternatively there may be a problem with your installation. See Install Policy Modeling. If the error persists, contact support. |
OPA-E00468 | Failed to launch interview: The interview template can not be found. | |
OPA-E00470 | Failed to launch interview: Could not unpack web application. | |
OPA-E00471 | Failed to launch interview: No available TCP ports. If you have multiple instances of Oracle Policy Modeling open, close them and try again. | |
OPA-E00474 | It appears that Java is not installed. | There may be a problem with your installation. See Java Requirements. If the error persists, contact support. |
OPA-E00475 | The Java installation directory {0} is invalid. | |
OPA-E00476 | Java {0} or later is required to run the embedded web server. Java {1} ({2}) was found. | Try setting the JAVA_HOME environment variable in your Windows settings to the Java path specified in the Diagnostics window in Policy Modeling. If the error persists, there may be another problem with your installation. See Java Requirements or contact support. |
OPA-E00477 | Invalid character {0} detected at the end of the header text. | See HTML Validation for Interviews for a list of valid characters. |
Invalid character {0} detected at the end of the left footer text. | ||
Invalid character {0} detected at the end of the right footer text. | ||
Invalid character {0} detected at the end of the add button caption. | ||
Invalid character {0} detected at the end of the button caption. | ||
Invalid character {0} detected at the end of the day input hint text. | ||
Invalid character {0} detected at the end of the hint text. | ||
Invalid character {0} detected at the end of the list display text. | ||
Invalid character {0} detected at the end of the month input hint text. | ||
Invalid character {0} detected at the end of the remove button caption. | ||
Invalid character {0} detected at the end of the screen title. | ||
Invalid character {0} detected at the end of the stage title. | ||
Invalid character {0} detected at the end of the year input hint text. | ||
Invalid character {0} detected at the end of the relationship control's target caption. | ||
Invalid character {0} detected at the end of the message. | ||
Invalid character {0} detected at the end of the caption. | ||
OPA-E00478 | Invalid character {0} at position {1} in the add button caption. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | See HTML Validation for Interviews for a list of valid characters. |
Invalid character {0} at position {1} in the button caption. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the day input hint text. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the description. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the hint text. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the image link address. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the list display text. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the month input hint text. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the remove button caption. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the screen title. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the stage title. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the header text. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the left footer text. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the right footer text. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the year input hint text. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the relationship control's target caption. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the message. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
Invalid character {0} at position {1} in the caption. If this was meant to be a tag then it is malformed, otherwise it should be encoded as {2}. | ||
OPA-E00479 | Unterminated HTML tag '{0}' in the header caption. | HTML Validation for Interviews |
Unterminated HTML tag '{0}' in the left footer caption. | ||
Unterminated HTML tag '{0}' in the right footer caption. | ||
Unterminated HTML tag '{0}' in the add button caption. | ||
Unterminated HTML tag '{0}' in the button caption. | ||
Unterminated HTML tag '{0}' in the day input hint text. | ||
Unterminated HTML tag '{0}' in the description. | ||
Unterminated HTML tag '{0}' in the hint text. | ||
Unterminated HTML tag '{0}' in the image link address. | ||
Unterminated HTML tag '{0}' in the list display text. | ||
Unterminated HTML tag '{0}' in the month input hint text. | ||
Unterminated HTML tag '{0}' in the remove button caption. | ||
Unterminated HTML tag '{0}' in the screen title. | ||
Unterminated HTML tag '{0}' in the stage title. | ||
Unterminated HTML tag '{0}' in the year input hint text. | ||
Unterminated HTML tag '{0}' in the relationship control's target caption. | ||
Unterminated HTML tag '{0}' in the message. | ||
Unterminated HTML tag '{0}' in the caption. | ||
OPA-E00480 | Invalid closing tag in {0} at position {1}. HTML {2} elements can not have closing tags. | HTML Validation for Interviews |
OPA-E00481 | Unexpected end tag in {0} at position {1}. The element {2} does not appear to have been opened. | |
OPA-E00482 | Unexpected end tag in {0} at position {1}. Expecting closing element for {2}. | |
OPA-E00483 | {0} is not an allowable HTML element in a {1} at position {2}. | |
OPA-E00484 | Invalid root tag in {0} at position {1}. {2} must have a parent element. | |
OPA-E00485 | Pseudo-classes are not allowed in style attributes for a {0}. (See element {1} at position {2}). | |
OPA-E00486 | At-rules are not allowed in style attributes for a {0}. (See element {1} at position {2}). | |
OPA-E00487 | Invalid style rule found in {0}. Styles should be of the form "identifier: value; identifier: value". (See element {1} at position {2}) | |
OPA-E00488 | {0} is not an allowable style attribute rule in {1}. (See element {2} at position {3}) | |
OPA-E00489 | Invalid HTML attribute value in {0}. The use of JavaScript in the {1} attribute is not allowed (See element {2} at position {3}) | |
OPA-E00490 | Invalid HTML attribute specification in {0}. Element contains multiple definitions of attribute '{1}' (See element '{2}' at position {3}) | |
OPA-E00491 | Invalid HTML attribute value in {0}. The use of VBScript in the {1} attribute is not allowed (See element {2} at position {3}). | |
OPA-E00492 | Invalid HTML attribute value in {0}. The use of LiveScript in the {1} attribute is not allowed (See element {2} at position {3}). | |
OPA-E00495 | Invalid HTML attribute specification in {0}. The use of the "{1}" attribute is not allowed (See element "{2}" at position {3}) | |
OPA-E00496 | Invalid tag in {0}. No element name specified at position {1} | |
OPA-E00497 | Unterminated HTML element "{0}" in {1} at position {2}. | |
OPA-E00498 | The custom goal set must have at least one goal. | Set the Goals for an Interview |
OPA-E00499 | The explanation attribute '{0}' does not belong to the entity '{1}'. | Add an Explanation Control |
OPA-E00500 | Invalid attribute text '{0}'. Attributes must contain at least one letter. | Choose Attribute Text |
OPA-E00501 | The left side of '=' in a conclusion must be an attribute. | Walkthrough of Creating a Word Rule |
OPA-E00502 | Invalid table conclusion: {0}. | Prove Conditional Calculations In a Rule Table |
OPA-E00503 | Attribute '{0}' has an invalid minimum value '{1}' for type '{2}'. | Specify Minimum and Maximum Values |
OPA-E00504 | Attribute '{0}' has an invalid maximum value '{1}' for type '{2}'. | |
OPA-E00505 | The mapping input in mappings settings is invalid. The relationship '{0}' does not exist. | Overview of Data Mapping |
OPA-E00506 | The mapping output in mappings settings is invalid. The relationship '{0}' does not exist. | |
OPA-E00507 | An error occurred while running the tests. Reason: An unexpected error has occurred while running remote session. | Check your test cases are properly constructed, or if a test case is triggering an error rule. To resolve, change your test case data (see Create, Edit Or Delete a Test Case) or remove the error rule (see Write an Error Event Rule). Try closing and re-opening Policy Modeling, restarting your computer if necessary. If the error persists, contact support. |
OPA-E00508 | Example project '{0}' was not found. | Try closing and re-opening Policy Modeling, restarting your computer if necessary. Alternatively there may be a problem with your installation. See Install Policy Modeling. If the error persists, contact support. |
OPA-E00509 | The required field '{0}' with type '{1}' of table '{2}' is not mapped out from any attribute in the '{3}' entity. | Overview of Data Mapping |
OPA-E00510 | The minimum validation value '{0}' is not a valid value for type '{1}'. | Specify Minimum and Maximum Values |
OPA-E00511 | The maximum validation value '{0}' is not a valid value for type '{1}'. | |
OPA-E00512 | Unable to create folder: {0}. | Try closing and re-opening Policy Modeling, restarting your computer if necessary. If the error persists, contact support. |
OPA-E00513 | Invalid closing tag. {0} is not an allowable HTML element in a {1} at position {2}. | HTML Validation for Interviews |
OPA-E00514 | Style attributes must have a value for a {0}. (See element {1} at position {2}). | |
OPA-E00515 | Unexpected character in HTML attribute "{0}" in {1}. Expected either a '=' or a ' ' (See element "{2}" at position {3}). | |
OPA-E00516 | HTML attribute "{0}" in {1} is missing a value. (See element "{2}" at position {3}). | |
OPA-E00517 | Invalid HTML attribute "{0}" in {1}. Attribute values must be quoted (See element "{2}" at position {3}). | |
OPA-E00518 | Invalid HTML attribute "{0}" in {1}. Unterminated quote detected (See element "{2}" at position {3}). | |
OPA-E00519 | The field '{0}' of table '{1}' is required to be mapped out by an attribute in the '{2}' entity when '{3}' is selected in Mapping Settings. | Overview of Data Mapping |
OPA-E00520 | The attribute '{0}' has an invalid mapped in '{1}' for load stage 'Load at start'. | |
OPA-E00521 | The attribute '{0}' has an invalid mapped in '{1}' for load stage 'Load after submit'. | |
OPA-E00522 | At least one of the fields of object '{0}' of table '{1}' is required to be mapped out to an attribute in the '{2}' entity. | |
OPA-E00523 | Unable to create file: {0}. | Try closing and re-opening Policy Modeling, restarting your computer if necessary. If the error persists, contact support. |
OPA-E00524 | The project you are trying to open was created with a later version of the product | Update your version of policy modeling to open this project. See Install Policy Modeling. |
OPA-E00525 | Entity instance existence cannot be used as a condition | Infer Membership of a Relationship |
OPA-E00526 | Invalid value for default entity instances - '{0}'. Please input a value from 0 to 99. | Specify the Default Number of Blank Entity Instances |
OPA-E00527 | Default entity instances for one-to-one relationships cannot be greater than 1. | Types of Relationship |
Specify the Default Number of Blank Entity Instances | ||
OPA-E00529 | Unhandled errors when running tests using remote calls either in OPM, in Excel or via command line. | Check your test cases are properly constructed, or if a test case is triggering an error rule. To resolve, change your test case data (see Create, Edit Or Delete a Test Case) or remove the error rule (see Write an Error Event Rule). Try closing and re-opening Policy Modeling, restarting your computer if necessary. If the error persists, contact support. |
OPA-E00530 | An inferred relationship cannot be set by a user. | Add Values for Attributes and Relationships |
OPA-E00531 | Cell formatting does not match the Intelligent Advisor style used. Re-apply {0} style or change the formatting of this cell. | Define Decision Tables In Excel Workbooks |
OPA-E00532 | Cell has the same formatting as an Intelligent Advisor table cell but does not use an Intelligent Advisor style. Re-apply Intelligent Advisor style or change the formatting of this cell. | |
OPA-E00533 | The attribute '{0}' cannot be its own condition attribute. | Walkthrough of Creating a Word Rule |
OPA-E00534 | An internal error occurred while compiling the document | Try closing and re-opening Policy Modeling, Word and Excel, restarting your computer if necessary. If the error persists, contact support. |
OPA-E00535 | The text '{0}' could not be parsed correctly. Consider rephrasing the attribute text and contact support if necessary. | There may be a problem with your language parser. Please rephrase your attribute text or report this issue to support. If the error persists, contact support. |
OPA-E00537 | The screen name '{0}' is already in use. | Enter a screen name that has not previously been used in the project. See Create a Screen. |
OPA-E00538 | Remove the upload control, or correct the mapping settings. | This error occurs where an Upload Control has been added to a screen in a project where the mapping settings do not support uploads. See Attach Documents to Interviews. |
OPA-E00539 | '{0}' is not a valid screen name. {1}. | Create a Screen |
OPA-E00540 | No image selected. | A screen image control has encountered an error. Delete and re-add this control. See Add Images to Screens. |
OPA-E00541 | The upload control '{0}'
does not belong to the entity '{1}'. The upload control '{0}' does not belong to the entity '{1}' or one of its ancestors. The input relationship '{0}' does not belong to the entity '{1}'. The input relationship '{0}' does not belong to the entity '{1}' or one of its ancestors. |
Collect Members of a Relationship |
OPA-E00542 | The static default value {0} does not exist in the value list {1} used by the attribute {2}. | Set Up a Value List In a Project |
OPA-E00545 | Duplicate custom property '{0}' detected. Custom properties must be unique for a given screen. | Define Custom Properties for Screens and Controls |
OPA-E00546 | Duplicate custom property '{0}' detected. Custom properties must be unique for a given control. | |
OPA-E00547 | The value '{0}' is not valid for the type '{1}'. | Overview of Value Lists |
OPA-E00548 | The value '{0}' is a duplicate. | |
OPA-E00550 | Failed to create {0} web site. | Try closing and re-opening Policy Modeling, restarting your computer if necessary. Alternatively there may be a problem with your installation. See Install Policy Modeling. If the error persists, contact support. |
OPA-E00551 | An error occurred while debugging the test case. Reason: {0}. | |
OPA-E00552 | Failed to run {0}. | |
OPA-E00553 | The forms attached to submission of screen '{0}' are not valid. | Save a copy of a form or signature to a connected application |
OPA-E00554 | The interview has no Submit button. Mapped out data requires a Submit button on at least one screen. | Control Screen Behavior Using Buttons |
OPA-E00555 | Formatting settings have errors. | Change the Formatting of Attribute Values In an Interview |
OPA-E00556 | Unable to revert changes: {0}. | Policy modeling is unable to revert the selected change. See also Understand Conflicts and Resolve Conflicts. |
OPA-E00557 | Duplicate entity '{0}'. | Ensure each entity in the policy modeling project has a unique name. See Define an entity. |
OPA-E00558 | Duplicate relationship '{0}'. | Ensure each relationship in the policy modeling project has a unique name. See Define a relationship. |
OPA-E00561 | The relationship '{0}' can not be used as its own filter. | Collect Members of a Relationship |
OPA-E00562 | The specified relationship '{0}' does not target the entity '{1}'. | |
OPA-E00563 | The specified relationship '{0}' does not belong to the entity '{1}' or one of its ancestors. | |
OPA-E00564 | The specified attribute '{0}' does not belong to the entity context '{1}' or one of its ancestors. | Add Questions Or Information From Different Entity-Levels to the Same Screen |
OPA-E00565 | The specified attribute '{0}' is not valid. Attributes must be of type Boolean or a value list. | Configure a Control to Display Conditionally |
OPA-E00566 | The expression can not have multiple values if using a '{0}' operator. | Function Reference |
OPA-E00567 | Entity container controls can not be nested inside an entity collect control. | Add Questions Or Information From Different Entity-Levels to the Same Screen |
OPA-E00568 | Entity container controls can not be nested inside another entity container control whose layout style is tabular. | |
OPA-E00570 | The goals explanation control does not belong to the entity '{0}'. | |
OPA-E00571 | Entity collect controls can not be nested inside another entity collect control. |
Add Questions Or Information From Different Entity-Levels to the Same Screen |
Entity collect controls can not be nested inside another entity container control. | ||
OPA-E00572 | The default blank instance attribute '{0}' does not belong to the entity context '{1}' or one of its ancestors. | Specify the Default Number of Blank Entity Instances |
OPA-E00573 | The default blank instance attribute '{0}' is neither a number nor a currency attribute. | |
OPA-E00574 | Invalid expression operator defined using Boolean attribute '{0}' Valid operators are '{1}', '{2}', '{3}','{4}' and '{5}'. | Function Reference |
OPA-E00575 | The expression has no comparison value(s). | |
OPA-E00577 | The value '{0}' is not valid for the attribute '{1}' in the expression. Only values in the list '{2}' can be used. | |
OPA-E00578 | Attribute with text '{0}' cannot be created because one of the text forms has the same text as attribute '{1}'. Please find and remove any ambiguous attributes or overrides with similar statement text. | Choose attribute text |
OPA-E00579 | Gender attribute '{0}' must be of data type 'text'. | Collect the Gender of a Person |
OPA-E00580 | Gender attribute '{0}' specified by attribute '{1}' does not belong to the same entity. | |
OPA-E00581 | The relationship '{0}' cannot be bound because entity '{1}' is not bound. | Overview of Data Mapping |
OPA-E00582 | The cardinality of the link '{0}' is not compatible with the relationship '{1}'. | |
OPA-E00583 | The link '{0}' cannot be bound to relationship '{1}' because it is already bound to '{2}'. | |
OPA-E00584 | Invalid audit mapping settings for attribute '{0}'. Current data mapping settings do not support saving audit reports. | |
OPA-E00585 | The project {0} can not be opened because the project file was not found or could not be accessed. | Open an Existing Project |
The project {0} can not be opened because it has an invalid Oracle Policy Modeling product version. | ||
OPA-E00586 | The project {0} can not be opened because no suitable version of Oracle Policy Modeling can be found. | You may be opening a project that has been created with a different version of policy modeling than the version installed on your machine. Open the .xprj in a text editor to view version information and install the correct or later version. Alternatively there may be a problem with your installation. See Install Policy Modeling. |
OPA-E00587 | The project folder already contains a project. Please choose another folder or change the project name. | Choose a project name that does not match a folder name in your selected project location. See Upgrade a Project. |
OPA-E00588 | OPM Launcher has been passed invalid command line arguments. | Try closing and re-opening Policy Modeling, restarting your computer if necessary. Alternatively there may be a problem with your installation. See Install Policy Modeling. If the error persists, contact support. |
OPA-E00589 | There was an error accessing this file: {0}. | |
OPA-E00590 | The specified file could not be found: {0}. | There may be a problem with the project you are trying to open. Try closing and re-opening Policy Modeling, restarting your computer if necessary. Alternatively there may be a problem with your installation. See Install Policy Modeling. If the error persists, contact support. |
OPA-E00591 | There was an unexpected problem reading from '{0}', the system reports: {1}. | Try closing and re-opening Policy Modeling, restarting your computer if necessary. Alternatively there may be a problem with your installation. See Install Policy Modeling. If the error persists, contact support. |
OPA-E00592 | The Oracle Policy Modeling product version information in this file was in a non-standard format and can not be read. | There may be a problem with the project you are trying to open. Try closing and re-opening Policy Modeling, restarting your computer if necessary. If the error persists, contact support. |
OPA-E00593 | No installation data was found for Oracle Policy Modeling. Please contact your system administrator. | There may be a problem with your installation. See Install Policy Modeling. If the error persists, contact support. |
OPA-E00594 | There are no valid references to Oracle Policy Modeling installation files which can be found. Please contact your system administrator. | |
OPA-E00595 | Oracle Policy Modeling version information could not be found in this file, are you sure this is an OPM Project file? | There may be a problem with the project you are trying to open. Try closing and re-opening Policy Modeling, restarting your computer if necessary. If the error persists, contact support. |
OPA-E00596 | This project can not be opened. No version of Oracle Policy Modeling could be found matching the project file version {0}. | You may be opening a project that has been created with a different version of policy modeling than the version installed on your machine. Open the .xprj in a text editor to view version information and install the correct or later version. Alternatively there may be a problem with your installation. See Install Policy Modeling. |
OPA-E00597 | The goal attribute {0} does not exist in the policy model. | An attribute previously referred to in the policy model can no longer be found based on the attribute text. Open the control causing the error and select a valid policy model attribute. See also Upgrade a Project. If the error persists, contact support. |
The goal control attribute {0} does not exist in the policy model. | ||
The input control default attribute {0} does not exist in the policy model. | ||
The mandatory attribute {0} does not exist in the policy model. | ||
The read-only attribute {0} does not exist in the policy model. | ||
The reference relationship control display attribute {0} does not exist in the policy model. | ||
The reference relationship control filter attribute {0} does not exist in the policy model. | ||
The visibility attribute {0} does not exist in the policy model. | ||
The input control attribute {0} does not exist in the policy model. | ||
OPA-E00598 | Document decision report attribute with id {0} does not exist in the policy model. | An attribute previously referred to in the policy model can no longer be found. See also Upgrade a Project. If the error persists, contact support. |
OPA-E00599 | Reference relationship control relationship {0} does not exist in the policy model. | A relationship previously referred to in the policy model can no longer be found. Open the screen control causing the error and select a valid policy model relationship. See also Upgrade a Project. If the error persists, contact support. |
Reference relationship control filter relationship {0} does not exist in the policy model. | ||
Folder relationship {0} does not exist in the policy model. | ||
OPA-E00600 | Document {0} does not exist in the policy model. | A document previously referred to in the policy model can no longer be found. Delete the document or re-add it to the project. See also Upgrade a Project. If the error persists, contact support. |
OPA-E00601 | Entity collect control has no entity. | An entity collect control is no longer associated with an entity. Delete the entity collect from the screen and re-add it if necessary. SeeCollect Entity Instances and Upgrade a Project |
OPA-E00602 | Entity collect control entity {0} does not exist in the policy model. | An entity previously referred to in the policy model can no longer be found. Open the control causing the error and select a valid policy model entity. See Collect Entity Instances and Upgrade a Project |
OPA-E00603 | Input control has no attribute defined. | An attribute previously collected as an input on a screen can no longer be found. Delete the input from the screen and re-add it if necessary. See also Add Questions to Screens and Upgrade a Project |
OPA-E00604 | Reference relationship control has no relationship defined. | Collect Members of a Relationship and Upgrade a Project |
OPA-E00605 | Goal control has no attribute defined. | Set the Goals for an Interview
Upgrade a Project |
OPA-E00606 | Container controls can not be nested inside an entity collect control whose layout style is tabular. | Collect Entity Instances |
OPA-E00607 | Container controls can not be nested inside an entity group control whose layout style is tabular. | |
OPA-E00608 | The attribute '{0}' is collected multiple times on the screen '{1}'. | Add Questions to Screens |
OPA-E00609 | The entity '{0}' is collected multiple times on the screen '{1}'. | Collect Entity Instances |
OPA-E00610 | The relationship '{0}' is collected multiple times on the screen '{1}'. | Collect Members of a Relationship |
OPA-E00611 | Some custom language strings appear to be untranslated. | Translate Policy Models Into Other Languages |
OPA-E00612 | Unable to display upgrade issues due to the following error: {0}. | There may be a problem with your installation or upgrade. See Install Policy Modeling and Upgrade a Project. If the error persists, contact support. |
OPA-E00614 | Entity Container controls for inferred entities cannot contain Input, Upload or Signature controls. | Collect Entity Instances |
OPA-E00615 | The relationship '{0}' is inferred and cannot be collected on a screen. | Collect Members of a Relationship |
OPA-E00617 | The {0} symbol can not be used in a translation unless it is used in a translation parameter, such as {1}. | Translate Policy Models Into Other Languages |
OPA-E00618 | The translation parameter {0} could not be recognized. | |
OPA-E00619 | The '%' symbol can not be used in a translation. | |
OPA-E00632 | A reference tag is not supported in this location. | Overview of Reference Tags |
OPA-E00633 | Unable to compile as there are serious data model errors. | Try closing and re-opening Policy Modeling. If the error persists, contact support. |
OPA-E00634 | A reference tag is used in a cell that has no text. | Overview of Reference Tags |
OPA-E00636 | More than one signature control for '{0}' can not exist on the same screen. | Add a Signature Control |
OPA-E00637 | Form template for '{0}' ({1}) is larger than the maximum size of 25MB. Check for large images in the template and try using the 'Compress Pictures' feature in Microsoft Word to reduce their size. | Design an RTF Template for a Form |
OPA-E00638 | Attribute '{0}' has a duplicate mapping to '{1}'. | Overview of Data Mapping |
OPA-E00639 | Failed to locate reference tag. Please recompile the project by pressing 'Debug'. | Overview of Reference Tags |
OPA-E00640 | This attribute already exists and its data type or existing mapping is incompatible with this field. | Overview of Data Mapping |
OPA-E00641 | Unable to create more than one instance of '{0}' because its containment relationship is one-to-one. | Specify the Default Number of Blank Entity Instances
Define a relationship |
OPA-E00642 | The expression {0} will always be false because {1} does not exist in the value list {2}. | Use a value list |
OPA-E00643 | The expression {0} will always be true because {1} does not exist in the value list {2}. | |
OPA-E00644 | Attribute {0} can not be inferred to the value {1} because it does not exist in the value list {2}. | |
OPA-E00645 | Field '{0}' is mapped in to multiple attributes. See '{1}'. | Overview of Data Mapping |
OPA-E00646 | Screen '{0}' has a submit button but there is no output mapping. | |
OPA-E00647 | The value list type for attribute '{0}' does not exist. | Overview of Value Lists |
OPA-E00648 | Attribute '{0}' can not have a filter defined for it because its value list '{1}' does not have any parents. | |
OPA-E00649 | The filter '{0}' is not valid for attribute '{1}' because it does not have a valid value list. | |
OPA-E00650 | The filter '{0}' is not valid for attribute '{1}' because its value list '{2}' does not parent the attribute's enumeration '{3}'. | |
OPA-E00651 | Attribute '{0}' cannot be a URL parameter as the entity '{1}' is inferred. | Allow Interview Data to Be Seeded From a URL |
Attribute '{0}' must have a name for a URL parameter. | ||
Relationship '{0}' must have a name for the URL parameter attribute '{1}'. | ||
OPA-E00652 | Error saving value lists: {0}. | Overview of Value Lists |
OPA-E00653 | There are multiple value lists with the name "{0}". | |
OPA-E00654 | Value list "{0}" contains an entry with no value. | |
OPA-E00655 | Current data connection does not support interview session checkpoints. | Overview of Data Mappingand Overview of Checkpoints |
OPA-E00656 | Identifying attributes can not be of type Boolean (Entity '{0}'). | Identifying attributes |
OPA-E00657 | The table '{0}' cannot be used for both Load and Create new operations. | Overview of Data Mapping |
OPA-E00658 | This string is reserved for the uncertain value. | Overview of Value Lists |
OPA-E00659 | '{0}' has been included in the test case multiple times: | Delete the repeated test case data or create multiple test cases. See Create, Edit Or Delete a Test Case. |
OPA-E00660 | The signature attachment for entity '{0}' is not valid for submission of screen '{1}'. | Save a copy of a form or signature to a connected application |
OPA-E00661 | To enable interview session checkpoints, Contact must be logged in. | Overview of Data Mapping and Overview of Checkpoints |
OPA-E00662 | Remove the attachment '{0}' from the 'Submit' button. | Save a copy of a form or signature to a connected application |
OPA-E00663 | The mappings settings are invalid. A new '{0}' can not be created via the relationship '{1}', so loading data can not be optional. | Overview of Data Mapping |
OPA-E00664 | The mapping output in mappings settings is invalid. The relationship '{0}' can not be output. | |
OPA-E00666 | The following error has occurred and the project will now close: {0}. | Try closing and re-opening Policy Modeling. If the error persists, contact support. |
OPA-E00667 | To enable interview session checkpoints, a user must be logged in. | Overview of Data Mapping and Overview of Checkpoints |
OPA-E00668 | Agent checkpoints are not enabled for this connection. | |
OPA-E00669 | Agents can save checkpoints only when additional data is loaded. | |
OPA-E00670 | Worksheet '{0}' has multiple conclusions for attribute '{1}' | Define Decision Tables In Excel Workbooks |
OPA-E00671 | This conclusion has the same conditions as a previous conclusion and will never apply. | Prove the Same Set of Conclusions Using Multiple Conditions |
OPA-E00672 | See previous conclusion. | |
OPA-E00673 | Attribute '{0}' is in the negative form which cannot be used here. | Prove Multiple Boolean Attributes In a Single Conclusion Column |
OPA-E00674 | Generic conclusion column can only contain Boolean attributes. | |
OPA-E00675 | An 'else' row contains conditions that are not 'else' conditions. | Styles Used for Excel Rule Tables |
OPA-E00676 | Rule content found after the 'else' row. 'Else' must be the last row in a rule. | |
OPA-E00677 | A relationship cannot be used as a condition. | |
OPA-E00678 | Inferred relationship must be a relationship from '{0}'. | Write Rules That Infer Relationships and Entities |
OPA-E00679 | '{0}' cannot be used as an alias because it is already used above. | Use an Entity Or Relationship In a Rule |
OPA-E00680 | The column attribute '{0}' cannot be compared using '{1}'. | Write Rules Using Comparisons |
OPA-E00681 | A value of type '{0}' cannot be compared using '{1}'. | |
OPA-E00682 | The column attribute '{0}' cannot be compared to a value of type '{1}'. | |
OPA-E00683 | The following error occurred trying to edit this attribute: {0}. | Create, Edit Or Delete an Attribute |
OPA-E00684 | The font family "{0}" has already been added. | Insert Standard Text Into an RTF Form Template |
OPA-E00685 | Can not add a non-system font family. | |
OPA-E00686 | Can not remove a system font family. | |
OPA-E00687 | The font family {0} does not exist in this project. | |
OPA-E00688 | The font family {0} is being used by another process. | |
OPA-E00689 | Custom control URL missing for label control. | Define a Custom Control |
OPA-E00690 | Custom control URL missing for input control. | |
OPA-E00691 | Input controls of type '{0}' are not supported in August 2016 compatible interviews. | Switch a Project to Use Latest Version Interviews |
OPA-E00692 | Calendar input controls are not supported for date time attributes in August 2016 compatible interviews. Vertical radio buttons are not supported for Boolean attributes in August 2016 compatible interviews. Horizontal radio buttons are only supported for Boolean attributes in August 2016 compatible interviews. |
Calendar controls |
OPA-E00693 | Custom HTML controls are only supported for input controls in August 2016 compatible interviews. | Custom controls |
OPA-E00694 | Unchecked image required for '{0}' input control. | Image button controls and Image toggle controls |
OPA-E00695 | An input mask must be specified for masked input controls. | Choose How Data Is Collected |
OPA-E00696 | No start year specified. | Date and Time Types |
OPA-E00697 | The start year '{0}' is not a number. | |
OPA-E00698 | No end year specified. | |
OPA-E00699 | The end year '{0}' is not a number. | |
OPA-E00700 | The static default value '{0}' does not meet the input restrictions. | Specify a Default for an Input |
OPA-E00701 | The static default value '{0}' can not be displayed due to the currently configured input options. | |
OPA-E00702 | Captcha controls can not be inside entity collects or entity containers. | Prevent Web Bots From Submitting Interviews |
OPA-E00703 | Button group controls with images must use value lists. | Image Buttons |
OPA-E00704 | The value list "{0}" is missing images. | |
OPA-E00705 | Custom file '{0}' not supported for current interview mode. | Test Customizations In Existing Deployments |
OPA-E00706 | The display text {0} in value list {1} contains an unrecognized substitution attribute {2}. The display text {0} in value list {1} contains a circular reference for value list {2}. |
Personalize Attribute Text |
OPA-E00707 | Invalid substitution text {0} in value list {1}: {2}. | |
OPA-E00708 | The minimum validation value '{0}' is not an integer. | Specify Minimum and Maximum Values |
OPA-E00709 | The maximum validation value '{0}' is not an integer. | |
OPA-E00710 | The minimum validation value '{0}' must be less than the maximum validation value '{1}'. | |
OPA-E00711 | Capturing user location is not supported in August 2016 compatible interviews. | Capture the User's Location |
The collected latitude attribute on screen {0} must be of type number. | ||
The collected longitude attribute on screen {0} must be of type number. | ||
OPA-E00712 | Failed to generate loop report: {0}. | Investigate a Rule Loop Warning |
OPA-E00713 | The image link address must be an absolute URL. | Add Images to Screens |
OPA-E00714 | The specified attribute '{0}' is not valid. A value list must be of type text or number in August 2016 compatible interviews. | Overview of Value Lists |
OPA-E00715 | The attributes "{0}" and "{1}" can not be collected on the same screen in August 2016 compatible interviews. Value lists can only be dynamically filtered by parent value lists of type text or number. | Associate a Value List with an Attribute Collected On a Screen |
OPA-E00716 | Multiple values cannot be set for a relationship with a single target. | Add Values for Attributes and Relationships |
OPA-E00717 | Failed to export the data model: {0} | Export the Data Model |
OPA-E00718 | The static default value '{0}' does not meet the input mask. | Specify a Default for an Input |
OPA-E00719 | Form template {0} must be saved as a RTF file. | Design an RTF Template for a Form |
OPA-E00720 | Form template file {0} does not exist. | Edit a Form |
OPA-E00721 | The project can not be migrated because the path to one of the project files is too long. Please shorten the path of the project directory and try again. | Migrate a Version 10.4 Project |
OPA-E00722 | Oracle Policy Modeling requires Microsoft Internet Explorer 11 or later to correctly display interactive interview authoring. | Policy Modeling System Requirements |
Oracle Policy Modeling requires Microsoft Internet Explorer 11 or later to correctly display interview debugging. | ||
Oracle Policy Modeling requires Microsoft Internet Explorer 11 or later to correctly display project styling. | ||
OPA-E00723 | The default visibility expression is not supported in August 2016 compatible interviews. Visibility expressions for individual options are not supported in August 2016 compatible interviews. |
Switch a Project to Use Latest Version Interviews |
OPA-E00724 | Setting the file name of the form control is not supported in August 2016 compatible interviews. | |
OPA-E00725 | Form controls of file type 'HTML' only support 'New window' in August 2016 compatible interviews. | |
OPA-E00726 | Form controls of file type '{0}' only support 'Download' in August 2016 compatible interviews. | |
OPA-E00727 | The file type '{0}' of the form control is invalid. | |
OPA-E00729 | The relevant operator is not available for legacy interviews. | |
OPA-E00730 | Displaying errors immediately is not supported in August 2016 compatible interviews. | Choose when error and warning events are shown |
OPA-E00731 | {0} is not a valid color for the {1} style. | Design Accessible Interviews |
OPA-E00732 | The contrast ratio {0} is too low for the {1} style. WCAG 2.1 AAA requires a contrast ratio of at least 7:1 or {2} for text greater than 18 point or 14 point bold. | |
OPA-E00733 | The contrast ratio {0} for the {1} style is only WCAG 2.1 AAA conformant for large text. If your text size is less than 18 point or 14 point bold, the contrast is required to be at least 7:1. | |
OPA-E00734 | The contrast ratio {0} is too low for the {1} style. WCAG 2.1 AA requires a contrast ratio of at least {2} or 3:1 for text greater than 18 point or 14 point bold. | |
OPA-E00735 | The contrast ratio {0} for the {1} style does not meet WCAG 2.1 AA requirements. Contrast ratio must be at least {2} if your text size is less than 18 point or 14 point bold. | |
OPA-E00736 | The header image does not have an alternate text description. This may be required for WCAG 2.1 accessibility conformance. | |
The image does not have an alternate text description. This may be required for WCAG 2.1 accessibility conformance. | ||
OPA-E00737 | For WCAG 2.1 accessibility conformance you must provide an alternative method to sign such as a checkbox or text input. | Add a Signature Control |
OPA-E00738 | The clear button text can not be edited on a per control basis in August 2016 compatible interviews. | Configure the Signature Clear Button |
OPA-E00739 | Submit and redirect is not supported on the final screen in August 2016 compatible interviews. | Redirect the User to an External URL |
OPA-E00740 | The selected condition '{0}' to attach '{1}' does not belong to the target entity or one of its parents. | Hide and Show Screen Controls |
OPA-E00742 | Setting the number of rows on a per control basis is not supported in August 2016 compatible interviews. | Switch a Project to Use Latest Version Interviews |
OPA-E00743 | The number of rows in multi-line input must be an integer value greater than 0. | Text Box Types |
OPA-E00744 | Links can only be opened in the same tab in August 2016 interviews. | Switch a Project to Use Latest Version Interviews |
OPA-E00745 | The identifying attribute of mapped entity '{0}' should be a text attribute | Overview of Data Mapping |
OPA-E00746 | Attribute '{0}' cannot be mapped in because it is the identifying attribute of mapped entity '{1}'. | |
OPA-E00747 | The entity '{0}' is mapped both via a link and to a specific table. Please confirm which mapping is correct. | |
OPA-E00748 | The table '{0}' selected for {1} in mapping settings is invalid because it is inaccessible by both Contact and Account users. | |
OPA-E00749 | Test connector data may be required to debug and test this project effectively. | Test Dynamically Loaded Data |
OPA-E00750 | Form template file {0} does not exist. Default form template file {1} will be used. | Overview of Forms |
OPA-E00751 | Unknown field '{0}' for IsNull(). | Define Conditions for Loading Data During an Interview |
OPA-E00752 | IsNull() requires a field as a parameter. | |
OPA-E00753 | The IsNull() function cannot be used here. | |
OPA-E00754 | Field '{0}' must be compared with something. Fields can be tested via comparisons such as '=' or '<' or with one of the following functions: {1}. | |
OPA-E00755 | Field '{0}' cannot be used here. Fields can only be tested via comparisons such as '=' or '<' or with one of the following functions: {1}. | |
OPA-E00756 | Field '{0}' must be compared with something. Fields can be compared by '=', '<', etc and StartsWith() | |
OPA-E00757 | Field '{0}' cannot be compared via '{1}'. | |
OPA-E00758 | Incompatible comparison: Field '{0}' cannot be compared with {1}. | |
OPA-E00759 | Condition is not a boolean expression. | |
OPA-E00760 | A text field is required to search for text content. | |
OPA-E00761 | A text value is required. | |
OPA-E00762 | '{0}' is not a valid value for {1} ({2}). | |
OPA-E00763 | Field '{0}' does not exist. | |
OPA-E00764 | Field '{0}' cannot be used in a load filter. | |
OPA-E00765 | Can't find this attribute in the debugger. | Debug a Failing Test Case |
OPA-E00766 | Can't find the entity instance in the debugger. | |
OPA-E00767 | Can't show this attribute in the debugger because there is no instance of '{0}'. | |
OPA-E00768 | The selected connected application doesn't have enumeration values for the value list '{0}'. | Deploy a Policy Model |
OPA-E00769 | The enumeration value '{0}' isn't known in the value list '{1}'. Refresh the data model (see Mapping Settings). | |
OPA-E00770 | The value list item '{0}' in '{1}' doesn't exist in the selected data connection's enumerations. Refresh the data model (see Mapping Settings). | |
OPA-E00771 | Mapped children of a dynamically loaded entity can not be specified in a test case. | Add Values for Attributes and Relationships |
OPA-E00772 | Relationships that target a mapped child of a dynamically loaded entity can not be set in a test case. | |
OPA-E00773 | Hiding progress stages on a per screen basis is not supported in August 2016 compatible interviews. | Switch a Project to Use Latest Version Interviews |
OPA-E00774 | The translation language {0} is either invalid or not supported by the operating system. | Translate Policy Models Into Other Languages |
OPA-E00775 | The entity '{0}' is loaded as a child of a query mapped entity and cannot be collected on a screen. | Collect Entity Instances |
OPA-E00777 | The year range must either be absolute or relative. | Specify Minimum and Maximum Values |
OPA-E00778 | Can not extract form fields information of {0}. Reason: {1} | Design a PDF Template for a Form |
OPA-E00779 | The font {0} is either not TrueType or not embeddable, so the field {1} in {2} may not display correctly in the generated document. | |
The font {0} is either not TrueType or not embeddable, so fields {1} in {2} may not display correctly in the generated document. | ||
Fonts {0} are either not TrueType or not embeddable, so fields {1} in {2} may not display correctly in the generated document. | ||
OPA-E00780 | Sorting lists alphabetically is not supported in August 2016 compatible interviews. | Switch a Project to Use Latest Version Interviews |
OPA-E00781 | An upload must have a name. | Attach Documents to Interviews |
OPA-E00782 | Invalid upload name "{0}". Names can only have letters, digits, dots or underscores, and must start with a letter or underscore. | |
OPA-E00783 | There are multiple uploads with the same name "{0}". | |
OPA-E00784 | The upload name "{0}" is already used by an attribute. | |
OPA-E00785 | The upload name "{0}" is already used by a relationship. | |
OPA-E00786 | Invalid upload maximum: "{0}". The upload maximum value must be an integer value greater than or equal to 1. | |
OPA-E00787 | Limiting the number of uploads is not supported in August 2016 compatible interviews. | |
OPA-E00788 | Limiting the number of uploads is not supported for deployments to the Interview Service. | |
OPA-E00789 | Automatically naming uploads is not supported in August 2016 compatible interviews. | |
OPA-E00790 | Automatically naming uploads is not supported for deployments to the Interview Service. | |
OPA-E00791 | Specifying an extension allowlist on a per upload basis is not supported in August 2016 compatible interviews. | |
OPA-E00792 | Specifying an extension allowlist on a per upload basis is not supported for deployments to the Interview Service. | |
OPA-E00793 | Multiple uploads per entity are not supported in August 2016 compatible interviews. | |
OPA-E00794 | Multiple uploads per entity are not supported for deployments to the Interview Service. | |
OPA-E00795 | The upload group '{0}' is collected multiple times on the screen '{1}'. | |
OPA-E00796 | Argument {0} of '{1}': must be a relationship or entity. | Use an Entity Or Relationship In a Rule |
OPA-E00797 | Argument {0} of '{1}': Is not a single entity instance. | |
OPA-E00798 | Argument {0} of '{1}': Is not a set of entity instances. | |
OPA-E00799 | Argument {0} of '{1}': is the wrong type. It should be '{2}' but is '{3}'. | |
OPA-E00800 | Attribute '{0}' does not belong to the entity '{1}', so the alias '{2}' cannot be used to refer to it. | |
OPA-E00801 | The left side of '=' must be a relationship because the right side is a relationship expression. | Write Rules That Infer Relationships and Entities |
OPA-E00802 | Incompatible relationship rule. The relationship type ({0}) cannot hold the value ({1}). | |
OPA-E00803 | Relationship assignment rule cannot have a condition | |
OPA-E00804 | There are duplicate filenames for '{0}' for attachments that will be attached to the entity '{1}' of the submit button. | Attach Documents to Interviews |
OPA-E00805 | There are duplicate default filenames for signatures that will be attached to the entity '{0}' of the submit button. | Add signature controls to screens |
OPA-E00806 | The image has an unsupported extension. Please select a valid image. | Add Images to Screens |
OPA-E00807 | Enumeration '{0}' uses an unsupported image. | Set Up a Value List In a Project |
OPA-E00808 | Invalid {0} file. No attribute or relationship with the name {1} exists in the project. | Allow Interview Extensions to Access Data Not On a Screen |
OPA-E00809 | The containment relationship {1} must have a public name in order to make {2} available to interview extensions via the {0} file. | |
OPA-E00810 | The entity {1} must have a public name in order to make {2} available to interview extensions via the {0} file. | |
OPA-E00811 | The contents of {0} is invalid. The file should consist of a JSON array of strings, being the names of the attributes and relationships to be made available to interview extensions. | |
OPA-E00812 | Argument {0} of '{1}' must be an attribute. | Use an Entity Or Relationship In a Rule |
OPA-E00813 | Failed to update the endpoint: {0} | Overview of Data Mapping |
OPA-E00814 | The link '{0}' bound to relationship '{1}' targets the table '{2}' from '{3}', but the target entity is mapped to '{4}' and source entity to '{5}'. | |
OPA-E00815 | No case selected. | Import Batch REST Cases Into the Debugger |
OPA-E00816 |
Only the Global entity for a form is supported for August 2016 compatible interviews. |
Specify That a Form Belongs to a Particular Entity |
OPA-E00817 |
Only the Global entity for a form is supported for deployments to the 'Web Service - Interview' channel. |
|
OPA-E00818 |
The explanation attribute '{0}' does not belong to the form's entity '{1}'(or one of its ancestors and successors). |
Make an Explanation Available to a Form |
OPA-E00819 |
The form's entity '{0}' does not belong to the attachment's entity, one of its ancestors or one of its descendants. |
Save a copy of a form or signature to a connected application |
OPA-E00820 |
The entity '{0}' of the form '{1}' does not belong to the entity '{2}'. The entity '{0}' of the form '{1}' does not belong to the entity '{2}' or one of its ancestors. |
Add a Form Control |
OPA-E00821 |
Submitted data must be read-only in August 2016 compatible interviews. |
Allow Interview Data to Be Seeded From a URL |
OPA-E00822 |
The image URL must be an absolute URL. |
Make an Image a Clickable Link |
OPA-E00823 | Error event rule ('{0}') occurred while running test case {1}. | A test case is triggering an error rule. To resolve, change your test case data (see Create, Edit Or Delete a Test Case) or remove the error rule (see Write an Error Event Rule). |
OPA-E00824 | Error event rule ('{0}') occurred while running test case {1} in workbook '{2}'. | |
OPA-E00825 | Error event rule ('{0}') occurred while running tests. | |
OPA-E00826 | Error event rule ('{0}') occurred while running tests in workbook '{1}'. | |
OPA-E00827 | Error event rule ('{0}') occurred while running tests. | |
OPA-E00828 | Encoded character "{0}" in {1} at position {2} is invalid. | HTML Validation for Interviews |
OPA-E00829 | Encoded character "{0}" in HTML element "{1}" in {2} at position {3} is invalid. | |
OPA-E00830 | Encoded character "{0}" in image URL at position {1} is invalid. | |
OPA-E00831 | Encoded character {0} in image link address at position {1} is invalid. | |
OPA-E00832 | The "Oracle Fusion" theme is not WCAG 2.1 AA compliant. Please use the "Default" theme instead. | Design Accessible Interviews |
OPA-E00833 | The contrast ratio {0} between the {1} and the {2} styles are too low. WCAG 2.1 AA requires a contrast ratio of at least 3:1 between adjacent colors. | |
OPA-E00834 | The attribute input control has an invalid 'Auto fill input purpose'. | |
OPA-E00835 | Input controls of type '{0}' are not supported for deployments to the 'Web Service - Interview' channel. | Deploy a Policy Model |
OPA-E00836 | The upload name "{0}" is already used as an entity output mapping ID. | Create a New Upload Group and Upload Control |
OPA-E00837 | The upload name "{0}" is already used as an attribute output mapping ID. | |
OPA-E00838 | The upload name "{0}" is already used as a relationship output mapping ID. | |
OPA-E00839 | Mapping identifier '{0}' is reserved for system use with generic integration | Data Map to Oracle Integration Or Another Generic Integration Provider |
OPA-E00840 | Label style '{0}' is not supported for Redwood themed interviews. | Features of the Redwood Theme for Inteviews |
OPA-E00841 | Vertical layout for input button groups is not supported for Redwood themed interviews. | |
OPA-E00842 | Decision service does not exist | Valid references |
OPA-E00843 | Relationship '{0}' is not available from the entity '{1}'. Unknown relationship '{0}' used in decision service reference |
|
OPA-E00844 | Missing required field in decision service reference | If this error persists after the decision service contract has been updated, you may need to open the reference file in Policy Modeling. This will trigger a validation check and remove the error if it has in fact been resolved. Alternatively, you can click Debug in Policy Modeling, which will also re-validate the reference. See also Valid references. |
OPA-E00845 | Decision service configuration is no longer valid | Valid references |
OPA-E00846 | Decision service lists can only be mapped to containment relationships. '{0}' is not valid in this context. | |
Decision service list needs to map the identifying attribute '{0}' for the target entity '{1}'. | ||
Decision service list requires the entity '{0}' to have an identifying attribute. | ||
OPA-E00847 | Unable to merge differences: {0} | Merge a modified asset into the local project from the project in the Hub |
Unable to merge the difference: {0} | ||
OPA-E00848 | An error has occurred while comparing projects. | Compare Project Versions |
OPA-E00849 | An error has occurred while trying to retrieve the projects. | |
An error has occurred while trying to retrieve the project snapshot. | ||
An error has occurred while trying to retrieve the project versions. | ||
OPA-E00850 | Generated PDF may not be accessible when using a PDF form template. Consider using an RTF form template instead. | Design an RTF Template for a Form and Generate forms that conform to the PDF/UA standard |
Generated PDF for {0} may not be accessible when using a PDF form template. Consider using an RTF form template instead. | ||
OPA-E00851 | To generate accessible PDF choose PDF/UA in Generated PDF Options. | Generate forms that conform to the PDF/UA standard |
To generate accessible PDF for {0} choose PDF/UA in Generated PDF Options. | ||
OPA-E00852 | To generate accessible PDF use only embedded Fonts in Generated PDF Options. | Embed TrueType fonts in generated PDF forms |
To generate accessible PDF for {0} use only embedded Fonts in Generated PDF Options. | ||
OPA-E00853 | Attribute '{0}' is not available from the entity '{1}'. | Valid references |
OPA-E00854 | Decision service output attribute '{0}' must belong to target entity. | Valid references |
OPA-E00855 | Custom function '{0}' has an incorrect definition. | Create a Custom Function |
OPA-E00856 | There are multiple custom functions named '{0}' (see #{1}). | |
OPA-E00857 | Missing custom function argument attribute '{0}' | |
OPA-E00858 | Attribute '{0}' is the return value for the custom function '{1}' and should be inferred | |
OPA-E00859 | Attribute '{0}' is the return value for the custom function '{1}' and must belong to the entity '{2}' | |
OPA-E00860 | Attribute '{0}' is an argument for the custom function '{1}' and cannot be inferred by a rule. | |
OPA-E00861 | Attribute '{0}' is an argument for the custom function '{1}' and cannot have an automatic type | |
OPA-E00862 | Attribute '{0}' is an argument for the custom function '{1}' and must belong to the entity '{2}' | |
OPA-E00863 | The containment relationship for custom function entity '{0}' cannot have text. | |
OPA-E00864 | The relationship '{0}' is invalid because it targets an entity inside a custom function from outside the custom function. | |
OPA-E00865 | The relationship '{0}' cannot have reverse text because the relationship is to an entity outside of the custom function. | |
OPA-E00866 | Relationship '{0}' is used to infer instances from within a custom function. This is only allowed if the target instances are also within the same custom function. | |
OPA-E00867 | The screen entity cannot be part of a custom function | Custom Function Instance Visibility and Access |
OPA-E00868 | The entity '{0}' is part of a custom function and cannot be collected on a screen. | |
OPA-E00869 | Entity container controls can not list instances of custom function entities | |
OPA-E00870 | Attribute '{0}' has an invalid default value '{1}' for type '{2}'. Attribute '{0}' has an invalid default value. '{1}' does not exist in value list '{2}'. |
|
OPA-E00871 | Date and time input style 'Multi-input Drop Down' is not supported for Redwood themed interviews Date and time input style 'Multi-input Text' is not supported for Redwood themed interviews |
Features of the Redwood Interview Theme |
OPA-E00872 | Date input style 'Multi-input Drop Down' is not supported for Redwood themed interviews Date input style 'Multi-input Text' is not supported for Redwood themed interviews |
|
OPA-E00873 | Time of day input style 'Multi-input Drop Down' is not supported for Redwood themed interviews Time of day input style 'Multi-input Text' is not supported for Redwood themed interviews |
|
OPA-E00874 | A 'to Many' relationship cannot be mapped to a reference field. '{0}' is not valid in this context. A reference field cannot be mapped to a 'One to One' relationship. '{0}' is not valid in this context. A reference field cannot be mapped to a reverse relationship. '{0}' is not valid in this context. A reference list field cannot be mapped to a 'to One' relationship. '{0}' is not valid in this context. A reference list field cannot be mapped to a reverse relationship. '{0}' is not valid in this context. |
Write Rules Using Objects |
OPA-E00875 | '{0}' is not valid in this context. Expected relationship of '{1}' entities, relationship is of '{2}' entities. |