Issues fixed in Corticon 6.3
- Last Updated: January 21, 2026
- Corticon
- Version 6.3
- Documentation
Issues Fixed in Corticon 6.3.5
| 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-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:
|
Issues Fixed in Corticon 6.3.4
| 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) |
| 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-16244 | Fixed an issue in the Corticon WebConsole where the Corticon Server license path was not displayed in the Server Details. |
| 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-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. |
Issues Fixed in Corticon 6.3.3.7
| Item | Details |
|---|---|
| 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-16501 | Updated bundled Apache Tomcat from 9.0.86 to 9.0.102 to address potential vulnerability identified in CVE-2025-24813. |
Issues Fixed in Corticon 6.3.3.6
| Item | Details |
|---|---|
| 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-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. |
Issues Fixed in Corticon 6.3.3.5
| Item | Details |
|---|---|
| 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. |
Issues Fixed in Corticon 6.3.3.4
| Item | Details |
|---|---|
| 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. |
Issues Fixed in Corticon 6.3.3.3
| Item | Details |
|---|---|
| COR-15270 | Fixed an issue with inconsistent uses of <Internal Name> id#
and <External Name> id# in the returned JSON
response. Now, newly created entities are using the .new
operator, and will be assigned <External Name> id#. |
Issues Fixed in Corticon 6.3.3.2
| Item | Details |
|---|---|
| COR-14873 |
Updated multiple bundled Progress DataDirect Connect drivers. The updated driver versions are now: * SQLServer JDBC Driver Version: 6.0.0.001525 * Oracle JDBC Driver Version: 6.0.0.001235 * PostgreSQL JDBC Driver Version: 6.0.0.001395 * MySQL JDBC Driver Version: 5.1.4.000266 * DB2 JDBC Driver Version: 5.1.4.000413 Consult the DataDirect Connect documentation for more information. |
| COR-14839 | Optimized decision service code generation to improve rule execution performance when running with Java 11. Previously, some rule operations ran significantly faster with Java 8 vs Java 11. With the new optimizations, performance with Java 11 is generally on-par with or better then with Java 8. |
| 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. |
Issues Fixed in Corticon 6.3.3.1
| Item | Details |
|---|---|
| COR-14193 | Fixed an issue where collection conversion resulted in an error when generating an EDS file. |
Issues Fixed in Corticon 6.3.3.0
| Item | Details |
|---|---|
| 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 setOrder.approved. For rule 1 (the column) the
value is set to T: Edit the action to set make it a full
assignment and set Order.approved to
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:
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-13704 | Removed snakeyaml-1.33.jar from the default Server packaging. It is now part of the optional Swagger jar. Snakeyaml library is only used by Swagger. |
| COR-13622 | Fixed a decision service compilation error impacting rulesheets that use an alias as both a singleton reference and a collection reference and a rule that uses that same alias as a collection. This was a regression from Corticon 6.3.2. |
| COR-13533 | Updated the bundled logback libraries (logback-classic and logback-core) from version 1.2.9 to 1.4.14 to address the potential vulnerability identified in CVE-2023-6378. |
| COR-13472 | Updated the bundled jackson libraries from version from 2.12.7 from 2.15.2 to address the potential vulnerability identified in PRISMA-2023-0067. |
| COR-11516 | Fixed an issue where files names generated for reports created from Corticon Studio have '%20' in the generated file names in place of any spaces in the asset name. Now the generated file names contain spaces correctly. |
Issues Fixed in Corticon 6.3.2.3
| Item | Details |
|---|---|
| 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. |
Issues Fixed in Corticon 6.3.2.1
| Item | Details |
|---|---|
| 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-13395 | Updated the bundled Tomcat from version 9.0.75 to 9.0.82 to address the potential vulnerability identified in CVE-2023-44487. |
Issues Fixed in Corticon 6.3.2.0
| Item | Details |
|---|---|
| COR-12947 | Fixed a regression in rulesheet filter behavior introduced in Corticon 6.3. If a rulesheet contained filters on an entity and within a rule, the entity is used in an assignment action but not the rule conditions, the filter would yield an incorrect set of matching entities. |
| COR-12855 | Fixed a problem in the Corticon Web Console when displaying Corticon Server log files. Some log entries could be duplicated multiple times in the log file viewer. |
| COR-11592 | Fixed a problem where the Corticon Server installer would log an InvocationTargetException for the file "setrunas.exe". This error did not affect the validity of your Corticon installation. |
Issues Fixed in Corticon 6.3.1.9
| Item | Details |
|---|---|
| COR-12858 | Fixed an issue where Corticon Server was not honoring the passed in Entity id value which contained a zero at the end (Child_id_0). This confused the algorithm that assigned new ids to newly created instances through a .new call in Rules. |
| COR-12854 | Fixed an issue where combination use of alias as singleton and collection was being ignored in filters and non-conditional rules. |
Issues Fixed in Corticon 6.3.1.8
| Item | Details |
|---|---|
| COR-12841 | Modified the default logging configurations of the Web Console database to have trace logging disabled. This is a change from the previous configuration, in which trace logging was enabled by default. |
| COR-12628 | Fixed an issue with nested ruleflows not working for embedded branch nodes where branch is on the same parent entity but different associations. Now association filters are applied to all data layers. |
Issues Fixed in Corticon 6.3.1.7
| Item | Details |
|---|---|
| COR-12647 | Fixed an issue with the vocabulary search attribute function in Corticon Studio. If a space existed in a folder name, the search function would not find matching attributes in rulesheets within the folder. Corticon Studio now decodes the vocabulary URI before comparing and provide the 'Find references' search results correctly. |
| COR-12623 | Fixed a rulesheet compilation issue. If a rulesheet utilized a filter where an alias was used in conjunction with an equal or not equal operator and the only other reference to the alias within rules was with a collection operator, previously this would result in a compilation error. |
| COR-12592 | Fixed an issue when user overrides loglevel through Web Console. Updated value was not properly being interpreted by CcServer during CcServer startup. |
| COR-12569 | Resolved an issue where user was unable to deploy axis.war in JBoss 7.4. Thirdparty library cxf-jaxrs.ear has been reverted back to 3.4.5 from earlier packaged version of 3.4.10 since it was not working with JBOSS 7.4 in 6.3.1.6 hotfix but worked in version 6.3.1.0. |
Issues Fixed in Corticon 6.3.1.6
| Item | Details |
|---|---|
| COR-12567 | Fixed a problem where using the remove operator to remove an entity and its children could result in broken associations. This would occur when passing an input JSON payload that contained one or more references to a child entity and the entities parent is removed. Example: A JSON payload with entities A, B, and C may all have an association to entity X. A fully denormalized JSON payload would have a full definition of X under each of A, B, and C. To reduce duplication, it is possible for the JSON to have a single definition of X under one of A, B, or C and for the others to have references to this instance of X. The problem was that using the remove operator with the option to remove children set could delete a referenced child entity. In our example, if the input JSON had the full definition of X under A and references to X under B and C, a remove of A and it's child X would break the references from B and C to X. The new behavior is that X will not be removed but moved to either B or C. Which entity contains the full definition of a child entity and which contain the references is irrelevant to rule processing. The new behavior maintains reference integrity. |
| COR-12560 | Fixed the typographical error of 'variables' in the Swagger Batch API definition. |
| COR-12542 | Fixed the issue where integer literals enclosed by parenthesis were not universally supported in rule expressions. Previously deeply nested parenthesis containing integer literals could result in erroneous code generation. |
Issues Fixed in Corticon 6.3.1.5
| Item | Details |
|---|---|
| COR-12530 | Fixed the problem where Corticon Batch Processing would improperly accumulate cached entities across executions potentially resulting in increased payload size. |
Issues Fixed in Corticon 6.3.1.4
| Item | Details |
|---|---|
| COR-12434 | Fixed the behavior where collection filter was creating duplicate tuples. This would occur if using a collection operator in a filter with child entities in the parameters |
| COR-12402 | Updated the bundled cxf library from version 3.4.5 to 3.4.10 to address the potential vulnerability identified in CVE-2022-46363 and CVE-2022-46364. |
| COR-12270 | Fixed a problem where Corticon EDC would incorrectly store the string "null" for String attributes mapped to CHAR database fields when the attribute was null. The null value is now stored in the database. |
Issues Fixed in Corticon 6.3.1.3
| Item | Details |
|---|---|
| COR-12416 | Fixed a problem when using Corticon EDC with rule projects where the vocabulary has nested domains . When an EDC mapped vocabulary contained the domains D1 and below it the domain D2, rule sheet filters on entities in D2 would fail with the error "Filter expression cannot be processed by the database". |
| COR-12398 | Removed the jettison library from Corticon CcThirdPartyJars.jar. This library is no longer needed by Corticon. |
| COR-12242 | Fixed a problem where in some situations the Corticon rule test editor would not allow the test subject to be set on a test sheet when there were multiple test sheets in a rule test. |
| COR-12239 | Improved decimal precision comparison in rule test. Previously for Decimal data types, the output and expected values may not be flagged as different when they are. As an example the value 111.100002 would not be flagged as different from 111.100001. These values will now be flagged as differences in rule tests. |
Issues Fixed in Corticon 6.3.1.2
| Item | Details |
|---|---|
| COR-11961 | Improved runtime performance of rulesheets containing filters that uses entities not also used in a rule condition or action. |
Issues Fixed in Corticon 6.3.1.1
| Item | Details |
|---|---|
| COR-12151 | Updated the bundled jackson-databind library to version 2.13.4.2 to address the potential vulnerabilities identified in CVE-2022-42003 and CVE-2022-42004. |
| COR-12141 | Fixed a problem where the Corticon Server MultipleCompilation utility would recompile a Decision Service if an EDS file existed for the Decision Service and the property OverrideIfExists=false was set. The OverideIfExists property is set in the multipleCompilation.xml used to configure the utility. If OverrideIfExists is set to false, the utility should not recompile the Decision Service. If false, the existing EDS file should be retained. The utility was ignoring this property and always recompiling the Decision Service. |
| COR-12140 | Fixed a problem where the REST datasource would incorrectly add duplicate HREF associations for bi-directional associations during import. The REST datasource now only adds an association if it does not already exist. |
| COR-12126 | Related to COR-11180. Fixed a problem when using ADC to write a Date value to a database when performing Batch Insert operations. When the database Date value was read into ADC memory and stored into a Vocabulary Attribute with datatype Date Only, ADC time shifted the Date value to local timezone, which is expected behavior. But when ADC wrote that value back to the database, the Date value wasn't time shifted back to UTC, which would cause the storing of an incorrect Date value. This was not an issue with a Vocabulary Attribute with a DateTime datatype because no time shifting is needed. |
| COR-11966 | Fixed a problem where rulesheet filters were not executing correctly. If
a rulesheet contained:
|
| COR-11827 | Updated the Corticon Web Console's LDAP authentication to support OpenLDAP. The Web Console supports both Microsoft Active Directory and OpenLDAP. |
Issues Fixed in Corticon 6.3.1.0
| Item | Details |
|---|---|
| COR-11965 | Updated Corticon Server's bundled Apache Tomcat to version 9.0.65. |
| COR-11964 | Improved ADC handling of INSERT operations with database generated primary keys. Previously when using database generated primary keys, the generated keys were not retrieved by ADC after an INSERT operation resulting in an inability to INSERT associated child entities into the database, which are dependent on its parent's generated key value. ADC properly pushes the generated key value from the parent to the associated children when needed through the Vocabulary Association Join Expression definition. |
| COR-11523 | Fixed an error in the upgrade of disabled filters in a Corticon 5.3 rulesheet to Corticon 6.x. The disabled filter would incorrectly be enabled in the upgraded rulesheet. |
| COR-11108 | Fixed a problem when using ADC to write a Date value to a database. When the database Date value was read into ADC memory and stored into a Vocabulary Attribute with datatype Date Only, ADC time shifted the Date value to local timezone, which is expected behavior. But when ADC wrote that value back to the database, the Date value wasn't time shifted back to UTC, which would cause the storing of an incorrect Date value. This was not an issue with a Vocabulary Attribute with a DateTime datatype because no time shifting is needed. |
| COR-11591 |
Updated the bundled Data Direct JDBC drivers PostgreSQL. The current bundled versions are: * [Oracle JDBC Driver]Driver Version: 6.0.0.000707 (F001549.U000777) * [SQLServer JDBC Driver]Driver Version: 6.0.0.000998 (F001590.U000791) * [DB2 JDBC Driver]Driver Version: 5.1.4.000336 (F000525.U000273) * [MySQL JDBC Driver]Driver Version: 5.1.4.000223 (F000438.U000209) * [PostgreSQL JDBC Driver]Driver Version: 6.0.0.000318 (F001235.U000640) * [OpenEdge JDBC Driver]Driver Version: 5.1.4.000161 (F000502.U000252) |
|
COR-11457 |
Fixed a problem where user supplied database drivers could not be configured in Corticon Studio when using Java 11. User supplied drivers can now be specified as Corticon Extensions in the Studio Project Properties. Corticon Studio 6.3 bundles OpenJDK 11. |
Issues Fixed in Corticon 6.3.0.3
| Item | Details |
|---|---|
|
COR-11860 |
Updated the bundled jackson-databind library from version from 2.12.1 from 2.12.7 to address the potential vulnerability identified in CVE-2020-36518. |
| COR-11859 |
Updated the bundled Data Direct JDBC drivers for Oracle, SQLServer, and PostgreSQL. The current bundled versions are: * [Oracle JDBC Driver]Driver Version: 6.0.0.000707 (F001549.U000777) * [SQLServer JDBC Driver]Driver Version: 6.0.0.000998 (F001590.U000791) * [DB2 JDBC Driver]Driver Version: 5.1.4.000336 (F000525.U000273) * [MySQL JDBC Driver]Driver Version: 5.1.4.000223 (F000438.U000209) * [PostgreSQL JDBC Driver]Driver Version: 5.1.4.000352 (F000548.U000290) * [OpenEdge JDBC Driver]Driver Version: 5.1.4.000161 (F000502.U000252) |
|
COR-11827 |
Updated the Corticon Web Console's LDAP authentication to support OpenLDAP. The Web Console supports both Microsoft Active Directory and OpenLDAP. |
| COR-11240 |
Modified Corticon Server to correctly reject the deployment of an .eds file produced with a version of Corticon prior to 5.6, while also logging an error message stating that the .eds needs to be regenerated. An .eds file produced with Corticon 5.6 or earlier must be regenerated for use with Corticon 6.1 and later. It is best practice to regenerate all .eds files whenever moving to a new Corticon major.minor version. |
| COR-11294 |
Fixed a problem in Corticon Server execution where the execution thread would not terminate after execution timeout. Execution would cease but the thread would not terminate. This would eliminate the thread from availability to Corticon Server, reducing the number of threads available for execution. |
Issues Fixed in Corticon 6.3.0.2
| Item | Details |
|---|---|
| COR-11792 |
When using Corticon Server in-process, the ICcServer.execute methods now optionally throw as exceptions any runtime exception which occurs. Previously any exception which occurred once rule execution began would be returned as a rule message with severity violation in the response payload. This is still the default behavior. Setting the property: com.corticon.server.execution.processing.throw.exceptions=true will cause the exceptions to be thrown and not returned in the response payload. For in-process usage, this makes it easier to catch and handle runtime exceptions. |
| COR-11516 |
Fixed a problem where the files names generated for service contracts and reports created from Corticon Studio would have "%20" in the generated file names in place of any spaces in the rule flow name. The generated file names will now contain spaces. |
|
COR-11615 |
Fixed a problem where Corticon Server would fail to process JSON input payloads if the following conditions were met: 1) an Entity or Association in the JSON payload had a defined #id value in the __metadata object, 2) the #id value contained "_id_", and 3) the value to the right of the "_id_" was not a number (Entity_id_1a). Previously a "NumberFormatException" would be generated. |
|
COR-11779 |
Improved the performance of rule sheet operators on Integer attributes. Previously Corticon used the Java BigInteger type for these operators, it now uses Long. Long is a 64 bit integer with a range of values from -2^63^ to 2^63^-1. The Long type provides substantially better performance than BigInteger. This change is internal to Corticon and will have no visible effect, other than improved performance. |
| COR-11597 |
Added the default brms.properties to PROGRESS_CORTICON_6.x.x.x_DOCKER.zip file. The "DOCKER.zip" distribution is available on Progress ESD. It's a limited distribution of Corticon Server, providing just the components required for Docker deployment. Including brms.properties makes it easier to customize properties such as log settings when deploying Corticon Server with Docker. |
Issues Fixed in Corticon 6.3.0.1
| Item | Details |
|---|---|
| COR-11596 |
Fixed a problem where Corticon Server would not accept JSON payloads with "null" entity definitions when executing a decision service. Passing a "null" entity definition would result in a JSONArray[n] is not a JSONObject exception. Any "null" entities are discarded when parsing the input payload and will be excluded from response payload. |
|
COR-11524 |
Fixed the Corticon Studio and Corticon Server installers to support installation on Windows 11 systems. Previously installation would generate a "Flexeraaxd$aaa: Windows DLL failed to load" exception. |
|
COR-11291 |
Improved Corticon Studio performance when validating ruleflows. Previously redundant validations could occur when using nested ruleflows. The performance improvement can have significant benefits when working on large rule projects in Corticon Studio. |
| COR-11247 |
Fixed a problem where rulesheet filters with EDC were not executed if the filtered entities were within a user defined domain in the vocabulary. When using EDC, rulesheet filters on a table are executed in the database for efficiency. Previously the filters would not run if the entity mapped to the table was in a user defined vocabulary domain. |
| COR-11292 |
Fixed a problem where rulesheet filters could produce incorrect results. If a rulesheet contains a collection operator and a filter that references the collection operator alias as well as an entity outside the collection alias scope, the filter would fail to correctly filter the collection content. |
| COR-10986 |
Fixed a problem where the Web Console would fail to delete and undeploy a decision service when authentication was enabled. This would occur both in the Web Console browser UI and the corticonWebConsole command line utility. |
Issues Fixed in Corticon 6.3.0.0
| Item | Details |
|---|---|
| COR-10036 |
Incorrect results with Replace elements operator using XML payload in 5.7 |
| COR-10037 |
Fixed a problem where a Corticon Server execution thread would be orphaned if a server execution timeout occurred. When Corticon Server is servicing an execution request a timeout will occur if the execution time exceeds the server execution timeout. The timeout protects against execution requests hanging or dominating the server. The most frequent cause of timeouts is databases queries exceeding expected response times. When a server timeout occurs, the executing thread was not returned to the execution thread pool and thus would be unavailable to service future requests. This could reduce the overall throughput of the server. |
| COR-10110 |
Fixed a problem where Corticon could add a spurious duplicate entity at the root of the result payload. This would occur for associations where the XML/JSON mapping name for the association was overridden and the association was used in a filter. In processing the payload Corticon would erroneously add the associated entity to the root of the payload being processed causing the entity to be duplicated in the result payload, once on the association and once at the root. |
| COR-11168 |
Fixed a problem where Corticon Server would handle non vocabulary entities incorrectly. Corticon Server is designed to ignore entities, attributes, and associations not defined in the vocabulary. In some cases, a non vocabulary entity could cause Corticon Server to interpret the hierarchical relationship of an XML payload incorrectly. |
| COR-11201 |
Modified the Corticon Studio Rule Message View to persist column widths when changing views. |
| COR-8657 |
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-8665 |
Modified Corticon Studio to allow composite filters in a rulesheet where the filter performs a tabulation on a collection such as: Order.total -> sum >100 |
| COR-9495 |
Modified Corticon Studio Tester to support updates to REST datasource configurations after a Tester window is opened. Previously, changing a REST datasource configuration would require a ruletest to be closed and reopened for the REST change to be recognized. |
| COR-9587 |
Fixed a rulesheet code generation error which would occur when using truncate and other extended operators in complex expressions where the operator was used following another operator in the expression. For example here truncate is in a complex expression and used after the toDecimal operator: |
| COR-9674 |
Corticon now supports deployment to JBoss 7.3. See the supported platform matrix for details. |
| COR-9696 |
Fixed a problem in executing corticonManagement.bat provided with Corticon Server. Previously it would generate an invalid .eds file when the output directory was specified as a relative path. Relative paths can now be used. |
| COR-9697 |
Fixed a problem in executing multipleCompilation.bat provided with Corticon Server. Previously it could generate a class not found error. |
| COR-9733 |
Fixed the deployment of decision services from Corticon Studio to the Corticon Web Console where the decision service contains one or more datasources. Previously the deployment would fail. Deployment to a Corticon Server was unaffected. |
| COR-9739 |
Updated the Corticon Studio operator tool tip for the Date.toDateTime operator to match the documentation. |
| COR-9755 |
Fixed a potential code generation problem which would result in a "toDecimal symbol not found" error when compiling a rulesheet . This problem could occur in rulesheets using Decimal attributes in complex expressions. |
| COR-9928 |
Fixed a problem where Corticon Server deployed to IIS would not self-register with the Corticon Web Console. |