6.1.4 update

This section describes changes in Corticon 6.1.4:

  • Simplified .NET configuration—Installation of Corticon Server to IIS server now provides a folder structure that makes it easy to create multiple IIS applications that share one .NET Server. See Set up Corticon Server for .NET for multiple applications. .
  • Swagger Optional—Corticon Server no longer bundles Swagger for exploring and testing the Corticon Server REST API. Swagger is now optional and can be added to an instance of Corticon Server. See The REST API Swagger documentation for details. The use of Swagger is best limited to development deployments of Corticon Server. It is typically not needed, or wanted, in production deployments.
  • Corticon Server now enforces version check on EDS deployment—When an EDS is deployed, Corticon Server will inspect the EDS to determine which version of Corticon generated it. If the version is not the same major.minor version of Corticon Server, the EDS will not be deployed.

    For example:

    - 5.7.4 EDS deployed to 6.1.0.0. Corticon Server: Not Allowed

    - 6.1.0.8 EDS deployed to 6.1.0.0 Corticon Server: Allowed

    Enforcing version checks ensures compatibility between the EDS and Corticon Server. The generated EDS code is dependent on internal Corticon Server APIs which might change across major.minor releases which could result in an EDS failing to execute despite initially reporting successful deployment.

    When deploying an incompatible EDS, Corticon Server performs the validation check and, if it is a deployment error, it is logged.

6.1.2 update

This section describes a change in Corticon 6.1.2.

  • Decision Service compilation no longer includes the WSDL and the report in the EDS file by default. If you use WSDL or reports in the EDS, add the following lines to the brms.properties file of the Studio that is producing the EDS: 
    com.corticon.server.compile.add.wsdl=true
com.corticon.server.compile.add.report=true
    For more information about this change, see the topic Properties that impact Decision Service compilation .

6.1.1 update

This section summarizes changes in Corticon 6.1.1.

  • Microsoft Dynamics CRM data source integration has been refined and is now presented as Microsoft Dynamics 365 for accessing Dynamics data.
  • The Corticon Studio user interface is now simplified with unused Eclipse menu and toolbar items removed. This is the default Corticon Designer perspective. The previous UI remains available as the Corticon Classic perspective if you require the full set of Eclipse Workbench commands.
  • The SVN plug-in is no longer included in the Studio installation. The plug-in can be accessed and updated from Eclipse.

Corticon 6.1.0

This section summarizes new, and enhanced features in Progress® Corticon® 6.1.0.

Ability to generate a Vocabulary from a REST or database source—Accelerate project development by generating your rule vocabulary from existing data sources. The data models defined in your SQL databases or REST services can be used to create or update a rule vocabulary. This can save weeks in the development of new projects and helps ensure your rule vocabulary is in sync with your business data models. See the Rule Modeling topics under Populate a Vocabulary from a Datasource in the Rule Modeling guide for details.

Ability to use third party database drivers for data access—When you need to connect Corticon to a database that does not have a DataDirect driver packaged with Corticon, you can add it. You need the driver JAR from the supplier. Contact Progress support for details on the procedures. See the Data Integration topic Add your own database driver in the Data Integration guide for more information.

Database driver for Microsoft Dynamics and its authentication—Corticon 6.1 adds a new Microsoft Dynamics 365 datasource, allowing you to utilize the power of Corticon rules in your Microsoft Dynamics 365 applications. Invoke rules from Dynamics 365 applications using the Corticon REST API and your rules now have full CRUD access to your Dynamics 365 data. With Corticon you can define, document, validate and automate the complex business logic for your Dynamics 365 applications.
Note: The authentication options for this driver are in a pulldown menu. That menu called for redesigning the user interface for authentication options for other drivers so that Kerberos is now presented in the authentication pulldown menu, and Username/Password is available as appropriate. See Authentication on EDC and ADC connections in the Data Integration guide for more information.
New operators—The release adds the following Attribute operators:
  • replaceString - Returns a new string where the instances of the String to be replaced are replaced by the value of the replacement String. See Replace String in the Rule Language guide.
  • regexReplaceString - Returns a new String where the strings matching the regular expression are replaced by the replacement string. See Regular expression to replace String .
  • matches - Returns true if the regular expression matches the String. See Matches .
  • random - Returns a random value within a range. See Random.
Ruleflow version identifier displays in Web Console—You can add a text descriptor to the Ruleflow by typing in the Version Label field. The description stays with the Ruleflow file, and is packaged in any Decision Services created from the Ruleflow. In the Web Console, every deployed instance of the Decision Service now lists the Version Label on its details page, as illustrated:

Streamlined Eclipse Environment—Corticon Studio has reduced the number of plugins loaded by Corticon Studio by no longer bundling the Eclipse Plug-in Development Environment (PDE). The PDE is used for creating Eclipse plugins, and is not applicable to Corticon rule development. If you need the PDE, you can add it to your Corticon Studio installation from the Eclipse download site.

If you open workspaces created in previous releases, you might see that the Error Log tab displays that it could not create LogView. The error is benign as Corticon did not use this view when the PDE was installed.