Issues fixed in Corticon 7.2
- Last Updated: September 17, 2025
- Corticon
Issues Fixed in Corticon 7.2.0
| 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:
|
| 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. |
| 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. |
| COR-16527 | A new server property has been added to control how execution threads
are allocated when the Corticon Server is underutilized
By default, the allocation algorithm allows Corticon Server to temporarily exceed the configured maximum number of execution threads when the server is underutilized. Setting this property to *true* disables that behavior, ensuring that Decision Services will strictly adhere to the maximum thread limit, even if the server is not fully utilized. Default value: false *Note:* This property only takes effect if allocation is explicitly enabled. To enable thread allocation, the following property must be set to true. Default value is false. |
| 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-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 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-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-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-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-11493 | Fixed an issue in Corticon Studio Tester where Decision Services with effective dates failed to load for remote execution. Decision Services with effective dates are now handled and displayed correctly. |