Issues Fixed in Corticon 7.1.3

Item Details
COR-18052 Fixed an issue where incorrect values were being written to ServerState.xml, which could disable the Maintenance Thread (Update Service) and stop automatic CDD-based deployments. The server no longer persists service state and service enable/disable is now only controlled via brms.properties (effective after a server restart).
COR-17978 Fixed an issue in the Corticon 7.1 Studio installer to support Windows Server 2025
COR-17835 Updated the bundled Progress DataDirect Connect drivers. This delivers multiple driver level fixes. Consult the DataDirect Connect documentation for more details. The bundled Connect driver versions are now:
  • [progress][Oracle JDBC Driver]Driver Version: 6.0.0.001776 (F003210.U002087)
  • [progress][PostgreSQL JDBC Driver]Driver Version: 6.0.0.001856 (F003185.U002075)
  • [progress][MySQL JDBC Driver]Driver Version: 5.1.4.000364 (F000633.U000372)
  • [progress][SQLServer JDBC Driver]Driver Version: 6.0.0.001957 (F003175.U002068)

  • [progress][HDP JDBC Driver]Driver Version: 4.6.2

Issues Fixed in Corticon 7.1.2

Item Details
COR-16625 A new log filter, 'PAYLOAD,' has been introduced to control the logging of request and response payloads. Payloads will only be logged when this specific filter is enabled, ensuring that customer data is not inadvertently logged. Under all other log filters, payloads will not be captured. Additionally, the 'INVOCATION' filter has been removed.
COR-16600 Updated the bundled Progress DataDirect Connect drivers. This delivers multiple driver level fixes. Consult the DataDirect Connect documentation for more details. The bundled Connect driver versions are now:
  • [progress][SQLServer JDBC Driver]Driver Version: 6.0.0.001848 (F002859.U001849)
  • [progress][Oracle JDBC Driver]Driver Version: 6.0.0.001574 (F002815.U001793)
  • [progress][PostgreSQL JDBC Driver]Driver Version: 6.0.0.001733 (F002856.U001846)
  • [progress][DB2 JDBC Driver]Driver Version: 5.1.4.000455 (F000599.U000343) [progress][OpenEdge JDBC Driver]Driver Version: 5.1.4.000187(F000605.U000352)
  • [progress][MySQL JDBC Driver]Driver Version: 5.1.4.000330 (F000614.U000359)
COOR-16541 Fixed a performance degradation issue that occurred during rule execution when a remove operation was used in a rulesheet that was part of an iterative subflow. The underlying issue has been resolved, ensuring optimal performance during rule execution in such scenarios.
COR-16509 Fixed an issue with code generation that sometimes led to compilation errors when a rulesheet contained a large number of rules. This has been addressed, and now both rule compilation and execution function as expected.
COR-17277 Updated the web.config to enable the processing of large requests on IIS. By default, IIS only allows 28 MB payloads, which was causing issues when deploying .eds files larger than 28 MB. To resolve this, IIS has been configured to handle requests up to 50 MB.
COR-17340 Fixed a regression in ruleflow branching where the set of entities passing the branch condition could be incorrect, resulting in an incorrect set of entities being processed by the branch.
COR-17319 Fixed an error in rule execution where the set of entities passed to a ruleflow branch could not match the conditional criteria for the branch. This could occur in ruleflows containing nested branches where each branch had multi-level association for the conditional attribute. Example:"Patient.Provider.Facility.state = NY". This was a regression in behavior from earlier releases.
COR-17308 Fixed an issue in Corticon Studio where error or warning messages could appear in the Error Log when starting Studio or working with rule assets. In some cases, opening or editing rule assets in Studio triggered a "Not properly disposed SWT resource" error. While these messages did not impact functionality, they have now been resolved.
COR-16525 Removed the obsolete property com.corticon.studio.client.soap.clienttype from configuration files. In earlier versions (6.3 and prior), this property was required because Corticon used different mechanisms for SOAP calls to Tomcat (Java) and IIS (.NET) application servers. Starting with version 7.0, Corticon introduced a unified mechanism for SOAP calls, making this property unnecessary.

Issues Fixed in Corticon 7.1.1.2

Item Details
COR-17280 Fixed a regression where ruleflow branches were not executed correctly, leading to inconsistent behavior. This issue has now been addressed, ensuring consistent execution across 6.3.2 and 7.1.1.
COR-17277 Updated the web.config to enable the processing of large requests on IIS. By default, IIS only allows 28 MB payloads, which was causing issues when deploying .eds files larger than 28 MB. To resolve this, IIS has been configured to handle requests up to 50 MB.
COR-16508 Fixed an issue with code generation that sometimes led to compilation errors when a rulesheet contained a large number of rules. This has been addressed, and now both rule compilation and execution function as expected.

Issues Fixed in Corticon 7.1.1.1

Item Details
COR-16541 Fixed a performance degradation issue that occurred during rule execution when a remove operation was used in a rulesheet that was part of an iterative subflow. The underlying issue has been resolved, ensuring optimal performance during rule execution in such scenarios.

Issues Fixed in Corticon 7.1.1.0

Item Details
COR-15907 Fixed the issue where Rule tracing in ruletests in Corticon Studio could not disambiguate rulesheets with identical names in a ruleflow. Corticon Studio will now open the correct rulesheet link in the trace results.
COR-16475 Fixed an issue in the Corticon WebConsole where an error was logged when an optional field was missing in the Decision Service request.
COR-15930 Fixed an issue with the Corticon Studio installer that caused a 'java.io.IOException: The system cannot find the path specified' error to be logged.
COR-16236 Fixed an issue in Corticon Server where it now correctly loads the c3p0 connection pool used by Hibernate for executing EDC enabled Decision Services.
COR-16244 Fixed an issue in the Corticon WebConsole where the Corticon Server license path was not displayed in the Server Details.
COR-16246 Resolved an issue in the analytics handler sample where updates to the corticon_analytics_rule_execution table were not being applied.
COR-16243 Fixed an issue where the getXMLClassName Server API was removed; it has now been restored.
COR-16161 Fixed an issue in the WebConsole where the WSDL failed to display correctly for a Decision Service with a name containing Japanese characters.
COR-16199 Fixed a regression in Corticon WebConsole 7.1 where Decision Services deployed via CDD were editable in the Web Console. This issue has been resolved, and now Decision Services deployed via CDD cannot be edited through the Web Console.
COR-16009 Fixed an issue where the Vocabulary Complexity Report was inaccurate when running in supported locales. The report failed to correctly account for attributes when executed in locales other than English, resulting in discrepancies.
COR-16003 The License Database Access field has been removed from the Web Console display, as it is no longer required by the Corticon Server. Database access is now always provided.

Issues Fixed in Corticon 7.1.0.4

Item Details
COR-16236 Fixed an issue in Corticon Server where it now correctly loads the c3p0 connection pool used by Hibernate for executing EDC enabled Decision Services.
COR-16244 Fixed an issue in the Corticon WebConsole where the Corticon Server license path was not displayed in the Server Details.

Issues Fixed in Corticon 7.1.0.3

Item Details
COR-16246 Resolved an issue in the analytics handler sample where updates to the corticon_analytics_rule_execution table were not being applied.
COR-16243 Fixed an issue where the getXMLClassName Server API was removed; it has now been restored.
COR-16199 Fixed a regression in Corticon WebConsole 7.1 where Decision Services deployed via CDD were editable in the Web Console. This issue has been resolved, and now Decision Services deployed via CDD cannot be edited through the Web Console.
COR-15930 Fixed an issue with the Corticon Studio installer that caused a 'java.io.IOException: The system cannot find the path specified' error to be logged.

Issues Fixed in Corticon 7.1.0.2

Item Details
COR-15907 Fixed the issue where Rule tracing in ruletests in Corticon Studio could not disambiguate rulesheets with identical names in a ruleflow. Corticon Studio will now open the correct rulesheet link in the trace results.
COR-16161 Fixed an issue in the WebConsole where the WSDL failed to display correctly for a Decision Service with a name containing Japanese characters.
COR-16003 The License Database Access field has been removed from the Web Console display, as it is no longer required by the Corticon Server. Database access is now always provided.
COR-16009 Fixed an issue where the Vocabulary Complexity Report was inaccurate when running in supported locales. The report failed to correctly account for attributes when executed in locales other than English, resulting in discrepancies.
COR-15995 Fixed an issue in the Corticon WebConsole that prevented deploying a Decision Service with the same name but a different version.

Issues Fixed in Corticon 7.1.0.0

Item Details
COR-13434 In Corticon Studio, when editing a rulesheet, Corticon is not marking as errors invalid assignments to Date, Time and Datetime attributes. For example, a rule action which assigns an integer value to a Date attribute should be marked as an error. This data type mismatch can result in errors during decision service execution.
COR-15270 Fixed an issue with inconsistent uses of <Internal Name> id# and
lt;External Name> id# in the returned JSON response. Now, newly created entities are using the .new operator and will be assigned <External Name> id#
COR-15911 Fixed an issue where in some cases rule execution could produce different results when a rulesheet contained multiple filters and the filters did not overlap on the rules impacted.
COR-15626 A new optimization was added to post-process the removal of Entities from the payload at the end of the rule execution rather than removing them inline during rule execution.
COR-15489 Fixed an issue when using the WebConsole on a Windows server to manage a Corticon Server running on a Linux server. The log path for a Batch Configuration specified in the WebConsole was not being honored.
COR-15432 Fixed an issue where different associations from a Parent entity with multiple filters was not filtering a rule that uses an association with the same parent entity. Now this rule configuration is working correctly.
COR-15266 Fixed an issue in Corticon Studio with Java 17. When running ruletests against remote Corticon servers, rule execution would fail.
COR-14191 Fixed the default LDAP configuration shipped for Corticon WebConsole. Added the missing "memberOf " attribute in attributesToReturn to allow users to login with LDAP as Active Directory user.
COR-14415 Fixed an issue with the Corticon upgrade wizard where during the upgrade of rulesheet that uses extensions an error was written into the rulesheet file.
COR-14143 Fixed a decision service compilation error that could occur in rulesheets using limited filters with unrelated entities in the conditions and actions of a rule.
COR-13766 Fixed an issue where if a user was part of both admin and user groups for IBM Open LDAP the user was not granted admin access for Web Console. Now, if a user is part of admin and user groups in IBM Open LDAP, the user will be logged in as an admin in Web Console.
COR-13778 Fixed a problem where a specific sequence of edits to a rulesheet could result in the rulesheet displaying incorrectly in Corticon Studio. In a rulesheet, assignment expressions in an action can be either partial or complete assignment expressions. A partial assignment expression identifies an attribute to update but does not provide the value, the value is specified in individual rules. By contrast, a complete assignment expression identifies both an attribute to update and the value to assign. The assignment occurs for any rule in the rulesheet where the action is selected.

Adding a partial assignment expression to a rulesheet and later switching it to be a complete assignment expression could result in one or more corresponding rule cells for the action being corrupted. The Corticon Studio rulesheet editor would appear to show the correct value for the cells even though the underlying definition for the cells are incorrect. This could result in rule execution not matching what is shown in the rulesheet.

Example: A rulesheet contains a partial assignment action to set Order.approved. For rule 1 (the column) the value is set to T: 
| Action         | 1 | 	
---------------------- 
| Order.approved  | T |
Edit the action to set make it a full assignment and set Order.approved to F:
| Action             | 1 | 			
--------------------------
| Order.approved = F |   |
This would result in a corrupt definition for the action in rule 1. This corrupt state can be seen in the Corticon Studio Rule Canonical Model view as: 
Order.approved = F = T
The double assignment is invalid.

Corticon Studio now prevents this sequence of actions from causing the corruption of action rule cells.

This problem dates back to Corticon 5.6 or earlier. Running the Corticon upgrade wizard will check for this condition and correct any corrupted cells.
COR-13781 Fixed potential problems in the use of Corticon Studio's Upgrade Wizard to upgrade rulesheets using extension operators. The Upgrade Wizard now uses project information to correctly resolve the location of extensions.
COR-13728 Restored ADC supported execution of UPDATE/DELETE that do not include a WHERE clause. This behavior was modified where it only supported UPDATE/DELETE for entities with non-null primary keys. Due to this restriction SQL without WHERE clause were not executed. This fix restores earlier behavior of allowing UPDATE/DELETE SQL statements that do not include WHERE clause
COR-13475 Fixed an issue where EDC vocabulary did not display 'Extend to Database' in Scope section and/or 'Database Filter' in the filter section.
COR-13471 Fixed a regression issue where an extra rule was firing in Corticon Studio 6.3 versus 5.6 when a collection operator is used with a filter that references a collection operator with an unrelated entity when the rule does not also reference the unrelated entity.
COR-13457 Fixed an issue where different rule message results were returned in Studio version 5.6.1.40 compared to 6.3.1.9 if rulesheet had combination of filters, collection operators and remove operator on the same rulesheet.
COR-13442 Fixed the error message logged in the WebConsole log file when deploying a decision Service to a Corticon Server with an expired license.
COR-13428 The Web Console Decision Service list page now retains the correct expansion state of page sections if the page contains both discrete decision services and applications.
COR-13402 The WebConsole now correctly displays an error message when setting an invalid max pool for a decision Service.
COR-10081 Fixed an issue with the Corticon Studio extended operator sample project. Dragging a sample collection extended operator from the operator list into a rulesheet now correctly will drop the operator using the collection notation