Understanding rule warning messages
Question
A developer asks: What is the significance the warning messages that appear at the bottom of the form when I save a rule?
When you save a rule form and a warning message appears, one or more warning conditions were detected. Warning conditions do not prevent the rule from saving or working correctly. Warning conditions identify unexpected and possibly unintended situations, practices not recommended, or variances from best practices. Consult the messages for details on the cause of the condition.
Ideally, you can revise the rule or other rules to remove the condition, which may improve performance, maintainability, user productivity, or usability.
Using the Application Preflight tool to report on warnings
Use the Application Preflight tool to list each rule in an application that contains a warning message. The tool reports the results of several checks on the rules in your application RuleSets and the currently selected work pool name.
To the start the tool:
- Click the link containing your name at the top of the navigation panel to see the profile display. Review the area titled Application RuleSets to confirm which RuleSets are to be checked by this tool.
- Select Application > Preflight. Here is an example of the first chart that appears.
- Click All Warnings by Rule Type to open the same chart and a summary report.
- Click a Rule Type item in the report to open a list report of the rules with warnings.
Here is an example list report of Rule Type: Section.
- Click on a rule instance (FlowActionHTML in this example) to open the rule form and view the warning message:
High priority warnings
Performance and DataIntegrity warning types are considered to be high priority. They are most likely to degrade system reliability by slowing performance or by violating data integrity. You should correct the warning conditions before you put the rules into a production environment.
If you are using v5.4 sp2 or greater, you can create and download a list report of these warning to an Excel spreadsheets by selecting Download High Priority Warnings in the tool. You can also use this option to create spreadsheets containing all warning types (by access group). The Excel spreadsheet includes links to this article. For more information, see PRKB 25497— How to download a list of high priority rule warnings.
About this article
This article contains a list of rules types and their related warning types. High priority warnings are listed first. Each entry contains the following information:
- Rule Type
- Warning Type
- Name
- Message
- Details
- Severity
Each high priority warning (Performance and DataIntegrity) contains a link to a PDN article, which contains additional diagnostic and troubleshooting information.
Technical note: Process Commander provides a set of CheckForWarnings activity instances, which apply to specific work types (for example, Rule-Declare-Expressions.CheckForWarnings). The activity uses uses a Java method that calls parameters in the addWarning function. The parameter values provide the content of one or more warnings including warning type, warning name, warning message, warning details, and severity. You can create custom warnings as described in PRKB-21872 How to create a rule warning.
Note: Severity is not correlated to priority. There are four severity levels, Severity 1 being the most serious. When remediating warning conditions, it is suggested that you first correct high priority warnings, followed by Severity 1, Severity 2, and so on.
Answer
High Priority Warning List
| Rule Type | Warning Type | |
|---|---|---|
| Rule- | Performance | |
| Name | PRPC_CircumstanceIndexWarning | |
| Message | Can't create Circumstance Index because the following column(s) can't be created: <column name(s)> Alter table pr_index_circumstance_def. Add <column name><data type> | |
| Details | (Database-specific message explaining reason for warning condition.) | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Circumstance-Definition | Performance | |
| Name | PRPC_CircumstanceIndexWarning | |
| Message | Can't create Circumstance Index because the following column(s) can't be created: <column name(s)> Alter table pr_index_circumstance_def. Add <column name><data type> | |
| Details | (Database-specific message explaining reason for warning condition.) | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Expressions | Performance | |
| Name | Context Free | |
| Message | For best performance, avoid defining expressions that execute regardless of page context | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Expressions | Performance | |
| Name | Whenever Used | |
| Message | For best perfomance, avoid the Whenever Used option for change tracking. | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-FlowAction | Performance | |
| Name | Using Whens with Bulk Processing | |
| Message | Check 'Disqualify this action from bulk processing' whenever you specify Whens to improve the performance of showing the list of bulk processing assignments | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-ListView | Performance | |
| Name | Case Insensitive | |
| Message | Case Insensitive search operation can adversely impact performance.To improve performance create functional index using UPPER() function on the columns that need case insensitive search. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-ListView | Performance | |
| Name | Not column or scalar | |
| Message | These properties are neither database columns nor scalar properties in database tables and can adversely impact performance: <.property (in database table)>. Read-only mode can not be used. | |
| Details | <n> properties where n equals the number of properties within a given database table that are causing the warning condition. | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-ListView | Performance | |
| Name | Not restrictive JOIN condition | |
| Message | One or more JOIN conditions potentially lead to cartesian product of tables and can adversely impact performance. | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-SummaryView | Performance | |
| Name | Case Insensitive | |
| Message | Case Insensitive search operation can adversely impact performance.To improve performance create functional index using UPPER() function on the columns that need case insensitive search. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-SummaryView | Performance | |
| Name | Not column or scalar | |
| Message | These properties are neither database columns nor scalar properties in database tables and can adversely impact performance: < .propertyin database table>.
Read-only mode can not be used. | |
| Details | <n> properties where n equals the number of properties within a given database table that are causing the warning condition. | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-SummaryView | Performance | |
| Name | Not restrictive JOIN condition | |
| Message | One or more JOIN conditions potentially lead to cartesian product of tables and can adversely impact performance. | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Index | DataIntegrity | |
| Name | Named Page Reference | |
| Message | If you reference a named page as a source within a Rule-Declare-Index, the value will be correctly read and populate the index. However, changes to that property on the named page will not trigger re-indexing. | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Trigger | DataIntegrity | |
| Name | Not Trigger Activity | |
| Message | To ensure transaction integrity, specify an activity that has its type defined as Trigger. | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | DataIntegrity | |
| Name | Commit | |
| Message | Use of the Commit method should be carefully considered to insure data integrity. In most cases, you will want to allow PRPC to handle committing a transaction. | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | DataIntegrity | |
| Name | Write Now | |
| Message | Use of the write now option should be carefully considered to insure data integrity. In most cases, you will want to allow PRPC to handle committing a transaction. | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Expressions | Accidental system damage (DataIntegrity) | |
| Name | Cannot be a Declarative Target | |
| Message | The property <target property> cannot be the target of an expression. | |
| Details | N/A | |
| Severity | 2 | |
Standard Priority Warning List
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Connect- | Functionality | |
| Name | Requestor Login | |
| Message | Requires Authentication in < ServicePackage> Service Package is checked. Please provide Requestor Login user details to do Authentication. | |
| Details | <n> properties where n equals the number of properties that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Connect-JMSListener | Functionality | |
| Name | Etier deployment | |
| Message | This JMS listener is available only when PRPC is deployed as a Web application. | |
| Details | <n> properties where n equals the number of properties that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Connect-JMSListener | Logic | |
| Name | Messaging Model | |
| Message | You have configured response for Publish and Subscribe | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Connect-JMSListener | Logic | |
| Name | Reference Format | |
| Message | Response destination reference must start with 'java:/comp/env' | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Connect-JMSMDBListener | Functionality | |
| Name | Etier Deployment | |
| Message | This JMS MDB listener is available only when PRPC is deployed as an Enterprise application. | |
| Details | <n> properties where n equals the number of properties that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Connect-JMSMDBListener | Logic | |
| Name | Reference Format | |
| Message | Response destination reference must start with 'java:/comp/env' | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Connect-MQListener | Functionality | |
| Name | Etier Deployment | |
| Message | This MQ listener is available only when PRPC is deployed as a Web application. | |
| Details | <n> properties where n equals the number of properties that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Operator-AccessGroup | Deprecated | |
| Name | ProdRSEntryNotInApp | |
| Message | The Production RuleSet entry <RuleSet name> does not exactly match <RuleSet name>,defined in the Application <application name, application version> Future releases will not support this configuration. For details, see KB 25289 - How to configure production RuleSets and WorkPools. | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Data-Admin-Operator-AccessGroup | Deprecated | |
| Name | Work Pool Not From Application | |
| Message | The workpool <workpool name> is part of the RuleSet <RuleSet name>, which is not included in the Application RuleSets portion of the < application name, application version> definition. Future releases will not support this configuration. For details, see KB 25289 - How to configure production RuleSets and WorkPools | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Agent-Queue | BestPractice | |
| Name | Whenever Used | |
| Message | One or more agents are in Legacy Mode. For more information, see KB 25050 How to upgrade a Legacy-mode agent. | |
| Details | N/A | |
| Severity | 4 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Application | Compatibility | |
| Name | Compatibility | |
| Message | Please note that Place properties on thread pages only checkbox on the Manage Tab is unchecked because the Built on Application has it unchecked. | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Circumstance- | Logic | |
| Name | Conflicts | |
| Message | Click Show Conflicts to see details. | |
| Details | <n> conflicts where n equals the number of conflicts that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Cirumstance-Definition | Logic | |
| Name | Conflicts | |
| Message | Click Show Conflicts to see details. | |
| Details | <n> conflicts where n equals the number of conflicts that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Circumstance-Template | Logic | |
| Name | Conflicts | |
| Message | Click Show Conflicts to see details. | |
| Details | <n> conflicts where n equals the number of conflicts that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Connect-HTTP | BestPractice | |
| Name | An explicit URL is not recommended | |
| Message | An explicit URL is not recommended. Provide the URL as a parameter in the connect calling activity instead. | |
| Details | Provide the URL as a parameter in calling activity. | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Run-Connect-JMS | Logic | |
| Name | Reference Format | |
| Message | Response destination reference must start with 'java:/comp/env' | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-DecisionTable | Logic | |
| Name | Conflicts | |
| Message | Click Show Conflicts to see details. | |
| Details | <n> conflicts where n equals the number of conflicts that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-DecisionTree | Logic | |
| Name | Conflicts | |
| Message | Click Show Conflicts to see details. | |
| Details | <n> conflicts where n equals the number of conflicts that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Expressions | Functionality | |
| Name | Change Tracking | |
| Message | Change tracking will not occur on named-page references either as an input or as an additional dependency such as < property >. | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Expressions | Logic | |
| Name | Expression Overridden | |
| Message | There is another expression using 'value of first matching property' with the same property name defined on ancestor class < AppliesTo class name>. This expression will never be evaluated. | |
| Details | Overriding ancestor expression: <first matching property instance> | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Expressions | Logic | |
| Name | No Source Property Defined | |
| Message | None of the ancestors of this expressions' Applies To class have a property named < target property > defined. This expression will never be evaluated. | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Declare-Expressions | BestPractice | |
| Name | When | |
| Message | As best practice, ensure that the Pages & Classes definition for Top <current class name> matches the top level class of this rule < top level class name>. | |
| Details | Top page class mismatch | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Edit- | Java Warning | |
| Name | Analyze Java | |
| Message | <Java code warning> <error line > <error line number> | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-File-Text | JavaScript Compacting Disabled | |
| Name | JavaScript Performance | |
| Message | For performance reasons, it is recommended to enable JavaScript compacting. | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-File-Text | JavaScript Syntax Errors | |
| Name | JavaScript Validation | |
| Message | reporter (0) | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-HTML-Harness | Deprecated | |
| Name | HTML Directives | |
| Message | HTML Directives are deprecated. Please use JSP for new rule instances. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-HTML-Section | Deprecated | |
| Name | HTML Directives | |
| Message | HTML Directives are deprecated. Please use JSP for new rule instances. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-HTML-Section | Deprecated | |
| Name | Mode Display | |
| Message | The 'when' tag keyword '$mode-display' is deprecated. Please use '!$mode-input' instead. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-HTML-Section | BestPractice | |
| Name | Not Auto-Generated | |
| Message | Whenever possible, use the Auto-Generated HTML option for ease of maintenance. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | Java Warning | |
| Name | Analyze Java | |
| Message | <Java code warning> <error line > <error line number> | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | Deprecated | |
| Name | API v02 | |
| Message | API version 02 is deprecated . Use 03-02 instead. | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | History-Add | |
| Message | Entering a simple text message in the Message field means that this information will not be localizable. PegaRULES Best Practice recommends that the data in the MessageKey field be a reference to a Field Value, so it will not be necessary to find this message and rewrite it later for a localization effort. | |
| Details | N/A | |
| Severity | ||
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | Java | |
| Message | Reduce or eliminate Java steps whenever possible for ease of maintenance. This activity contains <n> lines of Java. | |
| Details | <n> lines where nis the number of lines causing the warning condition. | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | Obj-List | |
| Message | The Obj-List activity method is deprecated. Please use Obj-Browse or Obj-List-View instead. | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | Obj-Open | |
| Message | If the Step Page field of Obj-Open method is blank, this method opens the object into the primary page of the current activity, replacing the current contents of the primary page and changing the class of the primary page to match the class of the object. | |
| Details | Blank Step Page | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | Obj-Open-By-Handle | |
| Message | If the Step Page field of Obj-Open-By-Handle method is blank, this method opens the object into the primary page of the current activity, replacing the current contents of the primary page, and changing the class of the primary page to match the class of the object. | |
| Details | Blank Step Page | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | Page-New | |
| Message | If the Step Page field of Page-New method is blank, this method create a page of the class specified in NewClass parameter, replacing the current contents of the primary page, and changing the class of the primary page to match the class of the new page. | |
| Details | Blank Step Page | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | Page-Set-Messages | |
| Message | Entering a simple text message in the Message field means that this information will not be localizable. PegaRULES Best Practice recommends that the data in the Message field be a reference to a Field Value, so it will not be necessary to find this message and rewrite it later for a localization effort. | |
| Details | Text Message | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | Property-Set-Messages | |
| Message | Entering a simple text message in the Message field means that this information will not be localizable. PegaRULES Best Practice recommends that the data in the Message field be a reference to a Field Value, so it will not be necessary to find this message and rewrite it later for a localization effort. | |
| Details | Text Message | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | RDB-Open | |
| Message | If the Step Page field of RDB-Open method is blank, this method opens the object into the primary page of the current activity, replacing the current contents of the primary page and changing the class of the primary page to match the class of the object. | |
| Details | Blank Step Page | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Activity | BestPractice | |
| Name | Unused Precondition | |
| Message | Precondition filled in step <step number>, but not used | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Class | BestPractice | |
| Name | Bad class name | |
| Message | The name of class <class name> should not start with the name of classgroup <classgroup name> unless the class belongs to the classgroup | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Class | Logic | |
| Name | Saves to tableName | |
| Message | Instances of this class save to the pr_other table which has few properties exposed as columns. Consider mapping to a different table. | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Flow | BestPractice | |
| Name | Overloaded assignments | |
| Message | <n> overloaded assignment(s) in this flow. | |
| Details | <n> assignments where n equals the number of assignments that are causing the warning condition | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Flow | BestPractice | |
| Name | Too many shapes | |
| Message | For clarity and ease of maintenance, limit the flow to no more than 15 shapes. This flow contains <n> shapes. | |
| Details | <n> shapes where n equals the number of shapes that are causing the warning condition | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-FlowAction | Deprecated | |
| Name | HTML Directives | |
| Message | HTML Directives are deprecated. Please use JSP for new rule instances. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-FlowAction | Deprecated | |
| Name | Mode Display | |
| Message | The 'when' tag keyword '$mode-display' is deprecated. Please use '!$mode-input' instead. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-FlowAction | BestPractice | |
| Name | Not Auto-Generated | |
| Message | Whenever possible, use the Auto-Generated HTML option for ease of maintenance. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-MapValue | Logic | |
| Conflicts | Conflicts | |
| Message | Click Show Conflicts to see details | |
| Details | <n> conflicts wheren equals the number of conflicts that are causing the warning condition | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Obj-Property | Deprecated | |
| Name | Reserved Property Name | |
| Message | The property name matches a reserved keyword. | |
| Details | N/A | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Service- | BestPractice | |
| Name | 1 ambiguous parse rule definition | |
| Message | This configuration is acceptable if the parse rule to be called is of DOM type. If it is a SAX type parse you will get a failure unless you specify the element name. To avoid the difference in behavior we recommend you always provide the "element name." | |
| Details | Specifying the full "element-name" is recommended | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Service- | BestPractice | |
| Name | <n> ambiguous parse rule definitions | |
| Message | This configuration is acceptable if the parse rule to be called is of DOM type. If it is a SAX type parse you will get a failure unless you specify theelement name. To avoid the difference in behavior we recommend you always provide the "element name." | |
| Details | Specifying the full "element-name" is recommended" | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Service-HTTP | BestPractice | |
| Name | Custom Cookies may interfere with stateful sessions | |
| Message | Setting custom cookies may interfere with stateful session management | |
| Details | Setting custom cookies may interfere with stateful session management | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Stream | Deprecated | |
| Name | HTML Directives | |
| Message | HTML Directives are deprecated. Please use JSP for new rule instances. | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Stream | Logic | |
| Name | HTML Generation | |
| Message | JSP generation selected but no Pega JSP tags found and possible HTML directives detected. Should this instance use HTML generation? | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Stream | Deprecated | |
| Name | Mode Display | |
| Message | The ' | |
| Details | N/A | |
| Severity | 3 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Stream | Deprecated | |
| Name | Stream Version Conflict | |
| Message | This unqualified rule is generated for JSP but a qualified version of the same rule is generated for HTML (or) This unqualified rule is generated for HTML but a qualified version of the same rule is generated for JSP Note: It is suggested that you not use directive-based streams and JSP-style streams for the same rule (for example, a rule that is qualified by multiple circumstances or date ranges). | |
| Details | This Rule <rule using JSP tag> conflicts with <rule using HTML directive > This Rule <rule using HTML directive > conflicts with <rule using JSP tag> | |
| Severity | 1 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Utility-Function | Java Warning | |
| Name | Analyze Java | |
| Message | <Java code warning> <error line > <error line number> | |
| Details | N/A | |
| Severity | 2 | |
| Rule Type | Warning Type | |
|---|---|---|
| Rule-Utility-Function | Java Warning | |
| Name | Function Not Compiled | |
| Message | Compile Checkbox Not Checked | |
| Details | N/A | |
| Severity | 2 | |