Explore LABS

Follow

Cortex 1.0.7 Release Notes

Cortex 1.0.7 contains the following:

To download version 1.0.7 of Cortex, open a ticket with Syniti support at support.syniti.com.

New Features 

matchIT hub 3.1 

The latest version of matchIT hub is included with the Cortex installation. Refer to matchIT hub 3.1 Release Notes for more information about this product upon which Cortex runs. 

New Database Input and Output Connections

New database inputs include MongoDB and Salesforce. MongoDB can now be used as an output. Refer to Connecting to a Database for more information.

Basic and Advanced Mappings on the Input Task

These new features have been included to make the mapping process easier and quicker. 

In previous versions of Cortex, you performed mapping on input data during Processing tasks (Match, Address and Normalize). This caused issues as you moved between the workflow configuration and mapping set up, and could cause duplicate work during remapping or if you were using multiple sources with the same columns. Now, mapping is part of the Input task. 

You can map columns manually using Basic or Advanced options. 

  • Basic provides you with a smaller, simplified set of selections in the list box when setting a match manually. Refer to Basic Mapping Columns for a list. 
  • Advanced allows you to select from a list of all available supported columns when manually mapping, including all the columns in the Basic mode, along with the address lines by number and all the multiple element mapping options such as SecondFullname.

For more information on these features, refer to Mapping Input Data.

Change Default Mappings

Change the default setting for a mapping using the new Column Header Alias Editor. The new feature recognizes the additional aliases as part of the specified  column type. Refer to Setting Default Mappings for more information. 

Enhancements

The output option configured for Matching called output exact match scores is now enabled by default on new installations. With this option enabled, a total score is output for exact matches that is the sum of the sure score setting for all mapped components plus one. Otherwise, the score field is blank for exact matches.

NOTE: No changes to this setting are made on upgrades unless you have not specified this setting in your current configuration XML’s.  If you want to continue with the old behavior,  add the setting to your XML and set it to false.

NOTE: This setting does not have an effect on component scores for exact matches, which are always blank.

Additional Mapping Updates

Other updates allow you to: 

  • Return mapping settings to their defaults by clicking the new Reset Mappings button on the Mappings tab. 
  • Select options in the Column list boxes while mapping more easily due to updates to how options display

For more information on these features, refer to Mapping Input Data.

SAP Fields Included as Header Column Aliases

Some SAP fields are now included in automatic mapping, as they have been added as column header aliases. Refer to SAP Column Aliases for more information. 

Resolved Issues

  • Fixed an issue when using custom SQL as part of a Database input type. After running a workflow and closing it, then opening it, the custom SQL no longer displayed at the bottom of the Input Database tab. It had been saved in the xml. With the fix, custom SQL displays as expected.  [MTC-259]
  • An issue causing control characters in a text input file to produce corrupt Excel file output has been fixed by replacing our previous Excel connector with Aspose.Cells. Control characters are now output to Excel as expected. [MTC-48]
  • Issues that occurred when an Excel spreadsheet with blank rows was used as part of a matching process have been fixed by replacing our previous Excel connector with Aspose.Cells. When a pairs output was attached to this type of process, a matching error was displayed and a blank output file was generated. When a matching group was added to this process, Cortex became unstable. With the fix, Cortex completes the job in full. [MTC-21]
  • An issue in Cortex with output to Excel has been fixed by replacing our previous Excel connector with Aspose.Cells. Cortex added time to the dates of columns formatted as Short Date. With the fix, the time data is no longer added. [MTC-19]
  • An issue causing control characters in a text input file to produce corrupt Excel file output has been fixed by replacing our previous Excel connector with Aspose.Cells. Control characters are now output to Excel as expected. [MTC-48]
  • An issue in Cortex with output to Excel has been fixed by replacing our previous Excel connector with Aspose.Cells. Cortex added time to the dates of columns formatted as Short Date. With the fix, the time data is no longer added.  [MTC-19}
Was this article helpful?
0 out of 0 found this helpful

0 Comments

Please sign in to leave a comment.