Issues Fixed in Corticon 7.3.0

Item Details
COR-17527 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][Oracle JDBC Driver]Driver Version: 6.0.0.001574 (F002815.U001793)
  • * [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)
COR-17520 Fixed an issue in Corticon Web Console where license information was not displayed in the Web Console after restarting the Server and Web Console. The license details are now preserved and displayed correctly across restarts.
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-17352

Resolved an issue in the Web Console that caused Decision Service deployments from the Application Server view to fail with a MissingPropertyException. The deployment process now functions 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-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 releases.