What's new and changed in Corticon 7.1

Corticon 7.1.3

The 7.1.3 service pack includes critical third-party library updates and important defect fixes to ensure a secure, stable, and fully supported environment, while maintaining platform compatibility. See Issues fixed in Corticon 7.1 for details.

Corticon 7.1.2

The service pack release 7.1.2 extends AI development, and provides some customer-requested features:

• Updated .NET Server prerequisites- Removes dependencies on unsupported MS libraries. See the Corticon 7.1 Supported Platforms Matrix.
• Log filter changes—A new filter is available, PAYLOAD, that will put the request payload and the response payload in the log. The filter INVOCATION has been dropped.
• Corticon AI Assistant improvements include:
  • Supports Azure Open AI.
  • Supports OpenAI (and Azure) 4.1 models.
• Supports Windows Server 2025.
• Corticon Studio bundles Java 17.0.156.
• Export Web Console configurationTo upgrade from 7.1, export its Web Console configuration, and then import it into a 7.3 instance of the Web Console. The import will overwrite the existing configuration.
  Note: Do not copy the installed corticon.war file in an attempt an update to a newer version. Use the Web Console's dashboard Administration option to Export Configuration.

Corticon 7.1.1

The service pack release 7.1.1 extends AI development, and provides some customer-requested features:

• Corticon AI Assistant improvements include:
  • AI Assistant has access to all constructs in a ruleflow including branches and service callouts. This allows you to use AI to explore any aspect of a ruleflow.
  • AI Assistant can be used on rule assets containing errors. This allows you to use AI to explore rule assets even if they have unresolved errors.
  • AI Assistant is visible by default in all new project workspaces. If you do not use the AI Assistant, you can close it.
• New Utility for Custom Reporting— The corticonManagement command now allows you to create a JSON representation of the contents of any ruleflow. The genJson utility is useful for customer reporting solutions capturing the specifics of a decision service to be deployed or other use cases where a simplified format detailing the contents of a decisionService is needed. See the Deployment Guide topic Export a decision service as a JSON file.
• Updated REST Datasource—The REST datasource has been updated to new version of the Progress Autonomous REST Connector. Existing deployments using the REST connector are unaffected. Rediscovering the schema of a REST datasource in Studio may introduce mapping errors that you will need to address.
• Improved JSON Support in Tester— The Tester now supports the copying native JSON from the clipboard into the input or expected sections of a ruletest. The prior Corticon annotated format is still supported. See How to import a JSON document to a testsheet. .
• Log filter changes—A new filter is available, PAYLOAD, that will put the request payload and the response payload in the log. The filter INVOCATION has been dropped. See Configure Logs .
• New Server Execution Property: Turn off disabling of thread underutilization allocation— A new server property has been added to control how execution threads are allocated when the Corticon Server is underutilized:

  com.corticon.ccserver.allocation.disable.underutilization.algorithm =false

  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:

  com.corticon.server.decisionservice.allocation.enabled=false

  See Server Execution Properties "Server Execution Properties" in the Server Guide.

Corticon 7.1.0

New in Corticon 7.1.0 are the following features:

• AI Assistant – New in 7.1, the Corticon AI Assistant enables the use of artificial intelligence (AI) in Corticon Studio to explore assets in your Corticon rule projects by asking natural language questions and viewing the AI-generated responses. See Corticon AI Assistant for details.
• Corticon Studio – Corticon 7.1 Studio includes multiple new and modified features to enhance your rule development.
  • Ruletest Generation – New in 7.1, the ruletest generator provides the ability to automatically create unit tests for each rulesheet in a Ruleflow from an existing system test. This allows you to perform more targeted testing and more easily isolate issues. You can efficiently generate and run unit tests for individual rulesheets and ruleflow steps, improving their ability to isolate and fix problems. That simplifies the process of identifying issues in large decision services, helping both users and Progress support isolate changes or problems in behavior. Also reduces reliance on full system tests, making rule testing more efficient and allowing for targeted troubleshooting. See Generate Ruletests .
  • Vocabulary Generation from JSON– New in 7.1, the generation of a Corticon rule vocabulary from a JSON payload or JSON schema accelerates your rule project development and keeps your vocabulary in sync with the payloads that will be processed. See Generate a Vocabulary .
  • Complexity Reports – New in 7.1, complexity reports allow you to export CSV files with raw metrics about rule assets, such as the number of rules per rulesheet in a ruleflow. These reports can help you better understand and track complexity in your rule projects."Generate a Vocabulary" in the Corticon Rule Modeling Guide
  • Upgrade Wizard Report– New in 7.1, the upgrade wizard report provides a record of the files updated, or not updated, by the upgrade wizard.
  • Upgrade Wizard on Rule Projects – Changed in 7.1, the upgrade wizard now operates only on Corticon rule projects. Previously, it operated on any file system folder with Corticon rule assets. This change addresses potential upgrade issues where project context is necessary to upgrade a rule asset.
  • Simplified JSON and XML Mapping– Changed in 7.1, vocabulary elements now have separate fields for XML and JSON mappings. The mappings are used by Corticon Server to map an input payload to a decision service vocabulary.
• Web Console – Corticon 7.1 Web Console includes multiple new and modified features to better enable the management of Corticon Server deployments. See the Corticon Web Console Guide Corticon Web Console Guide for details:
  • One Web Console – New in 7.1, you can manage multiple versions of Corticon Server from one instance of the Web Console. This is helpful with large Corticon deployments or during upgrades. The 7.1 Web Console can manage Corticon Server 6.0 and later instances.
  • License Visibility – New in 7.1, the Web Console provides greater visibility of the Corticon licenses deployed across your Corticon servers and alerts when a server's license is expiring.
  • Configuration Export and Import– New in 7.1, the ability to export the Web Console configuration and import it into a separate instance is useful during upgrades or rehosting of the Web Console.
    Note: Do not copy the installed corticon.war"Generate a Vocabulary" in the Corticon file in an attempt an update to a newer version. Use the Web Console's dashboard Administration option to Export Configuration.
  • Cached Entities for Batch Processing – New in 7.1, the option to define a set of entities to be cached during batched rule processing can accelerate batch rule execution by limiting the retrieval of redundant data.
• Corticon Server– Corticon 7.1 Server and Server .NET include new and modified features to simplify Corticon Server deployments. See “The Corticon Server Guide” for details.
  • JSON Array Support – New in 7.1, support for object arrays in JSON input payloads simplifies the integration of Corticon decision services with external services.
  • EDS Version Enforcement– New in 7.1, enforcement of an EDS version check when deploying a decision service will reject a decision service deployment if the Corticon version used to compile the decision service is not compatible with the version of Corticon Server.
• Corticon Installers – Changed in 7.1, Corticon now consists of 5 separate installers, providing you greater control over installations and updates. See the Corticon Installation Guide for details.
  • Corticon Studio– Provides a complete platform for modeling rules for Corticon.
  • Corticon Server – Provides the Corticon Server for Java for deployment to supported J2EE application servers and Java applications.
  • Corticon Server .NET – Provides the Corticon Server .NET for deployment to Microsoft IIS application server and .NET applications.
  • Corticon Web Console – Provides a Web UI for managing Corticon Server and Server .NET deployments.
  • Corticon Utilities – Provides command-line utilities for automating the packaging, testing, and deployment of Corticon decision services.
  Note: A Corticon Server install provides the Docker configuration file, Dockerfile, and the .war files for Corticon Server and Corticon Web Console. See How to deploy Corticon on Docker.
• Java Requirement – Changed in 7.1 is the requirement for Java 17 and the packaging of Java. See “The Corticon Supported Platforms” for details on supported Java distributions.
  • Java 17 Not Bundled – Java is no longer packaged with Corticon Server, Server .NET, Web Console, or Utilities. You need to download and install Java 17 to use any of these Corticon installations.
  • Java 17 Bundled with Corticon Studio – Java is bundled with Corticon Studio, enabling you to use Studio without a separate Java 17 installation. The distribution of Java bundled with Studio should not be used with any other Corticon components.
  • Note: Cannot install Studio into an existing Eclipse— Corticon Studio ships with Java 11 or higher, which introduces changes in how JAR files are handled: Java no longer supports the direct addition of custom JARs to the classpath as earlier versions did. As a result, the ability to drop extension JARs into the Eclipse plugin folder is no longer functional. The recommended method for adding extension JARs is in an installed Corticon Studio either:

    • For Eclipse tools, choose Help > Install New Software, and then typically choosing tools at https://marketplace.eclipse.org/ .
    • For your extensions, such as extended operators and service callouts, in a Rule Project, choose Properties > Corticon Extensions.
• Tomcat Bundling – Changed in 7.1 is the removal of an Apache Tomcat distribution from Corticon Server and Corticon Web Console. If deploying to Tomcat, you need to download and install Tomcat 9 and manually deploy Corticon components. See Corticon Supported Platforms Matrix for details on supported application servers.