ExecuteContivoMap Function Expanded
The “ExecuteContivoMap” function now supports the passing of extra parameters to the Contivo map.
Dynamically Set URL for WebServiceRequest() Function
Delta now includes a “WebServiceRequestEx” function which allows users to dynamically set the URL and HTTP verb used in their WebService connections.
UN/EDIFACT D.16A Dictionary Now Available
A new dictionary for the UN/EDIFACT D.16A standard is now available for use within Delta, Dictionary Viewer, and EDI Notepad.
New Feature: Ignore Caching of Database Connections
When creating database access models, users now have to option to forcibly close connections to the database immediately after mapping is complete. This can be helpful in situations where a database only supports a limited amount of simultaneous open connections. With this feature enabled, connections are made available as soon as possible.
Selecting the Ignore Caching of Database Connections checkbox instructs Delta to disconnect a data link after a map is run. To activate this feature, right click or double click on a data link object and select Properties from the shortcut menu. Next, select the Advanced button located on the General tab.
From here, simply select the Ignore caching of database connections checkbox then click OK. The feature is now activated.
Enhanced Support for Mapping Repeat EDI Elements
Delta now includes enhanced support for mapping of repeating elements from an EDI source model. Delta 6.1 Build 108 introduced writing to repeats; Delta 6.1 Build 109 introduces support for reading the repeats by adding an EDI Repeat Array, which allows users to save repeating EDI element values. This array is specifically designed to loop over and store any number of repeat values that a repeating EDI element may contain.
When an EDI Repeat Array rule is run, Delta automatically detects the number of repeating elements in the source and fills the array accordingly. In order for the user to determine the size of these arrays and assist in mapping, Delta automatically creates a “count” or “length” variable when initializing an EDI Repeat Array. This variable uses the same name as the array, but with “_length” appended to the end of the name. For example, if the array is named “RepeatArray”, the length variable is called “RepeatArray_length”, and contains the size of the array.
The default value for these arrays (unless otherwise specified via the InitArray function) is an empty string, so any attempt to access a value out of the range of the array returns as such. EDI Repeat Arrays also automatically clear and reinitialize the contents of the array if map execution causes the rule to be run again. The contents of EDI Repeat Arrays are accessed and used in the exact same manner as normal arrays.
EDI Repeat Arrays are implemented similarly to traditional arrays. To introduce a repeat array into a ruleset, select the Repeat Array option from the from the Element drop-down list.
HIPAA 5010 Dictionary Support/Built-in 999 Support
Delta now ships with HIPAA 5010 dictionaries and can generate 999 Implementation Acknowledgments. This operates similarly to the 997 generation with the exception that if Delta detects that the message is using a HIPAA standard, a 999 is generated by default.
Repeated Sub-Elements Now Supported For EDI Maps
You now have the option to enable EDI repeats for your new and existing EDI maps. The EDI Repeat option is enabled by default for new maps, but disabled for existing maps. When this option is enabled, Delta automatically loops back and maps repeated elements when the EDI source contains repeats. When this option is enabled and the user is writing to an EDI target, Delta automatically adds repeats to the output EDI if it detects that the same segment/element object is created multiple times.
Enabling the EDI Repeats Option
Repeats are enabled from the Map Properties screen (File > Properties).
Figure 1: The Data Handling section includes a new option that enables EDI repeats during mapping.
In the Data Handling section, select the Enable EDI repeats during mapping checkbox then click the OK button. Note: The Enable EDI repeats during mapping option displays only when you are working with an EDI map.
Updating Existing Maps
When enabled, Delta automatically reads and loops through repeated EDI elements that are included in the source data. For maps where only the target model is EDI based, you will need to manually specify repeats within the rules via the Rule Insert Location dialog.
Figure 2: Use the Add Repeat button to manually specify repeats within rules.
Notice that there is a new button called Add Repeat. If the Add Repeat button is disabled here, ensure that you are working with an EDI map and the Enable EDI repeats during mapping checkbox is enabled on the Map Properties screen.
Note: You can bypass opening the Rule Insertion dialog by clicking the shift key then dragging the source object and dropping it onto the target object. This automatically adds the repeat.
User-Defined “Escape Character” Now Available
Delta users now have the option to change the default escape character used in database commands. Escape characters are used when a database command includes a special word or character (such as the dash character) in a table name (e.g.,Test-Table). The keyword or character is “escaped” so that it can be passed to the database and recognized as a command. By default, brackets are supported, but as brackets do not work for all databases, users now have the option to set their own escape character. You can set the escape character from the Advance Data Link Properties screen (Data Links tab of a Database Model’s root node properties).
Figure 3: Use the Add Repeat button to manually specify repeats within rules.
Use the drop-down arrow to select one of the three pre-defined options – brackets (default value), accent mark, or double quote. Alternatively, you can click in the box and type the character that you want to use. Once the value is updated and saved, subsequent runs will use the newly defined escape character.
Ability to Copy and Paste Rules Between Delta Instances
Delta now supports the ability to copy and paste rules between different instances of Delta or between Delta and a plaintext editor. This can reduce the effort spent in migrating maps from legacy mapping products and other disparate formats to Delta.
New Function to Convert EDI to XML
Delta has added a new function named ConvertEDItoXML that converts any X12, EDIFACT, or TRADACOMS document to the XML format. Use the XMLLookup function in conjunction to access any portion of the XML.
ENCRYPTDATA and DECRYPTDATA Functions Support AES Algorithms
The EncryptData and DecryptData functions now support the AES128, AES192, and AES256 algorithms, allowing for stronger cryptographic security in Delta.
Addition of ANSI X12 7010 Dictionary
Delta’s list of ANSI X12 versions and releases now includes the ANSI X12 7010 dictionary.
Updated Predefined EDI Models
Predefined EDI models have been updated in Delta. Over 2000 predefined models are available when creating a new EDI model using the Predefined – Prebuilt trading partner models available from Liaison option.
Support for Oracle MySQL
ECS and Delta now support the Oracle MySQL 5.6 database server in addition to Microsoft SQL Server. This allows the ECS database to reside on different system platforms. MySQL support is not available for ECSArchiver and WebECS.
Note: If you are upgrading from a prior version of ECS that uses SQL Server, selecting MySQL results in a new ECS installation.
Ability to Execute a Contivo Transform in Delta
If ECS is running in conjunction with Delta, Delta can execute a Contivo transform via the ExecuteContivoMap () API function. This allows both Delta and Contivo maps to be called if needed.
Delta now supports the JSON data format. JSON consists of collections of named value pairs and arrays of values. You can create JSON models for mapping by importing a sample JSON document.
Source Dependent Timing Feature in Maps (Sourceless Mapping)
This new feature allows you to trigger a rule independent of the existence of a source object. It is only available in maps that use EDI, XML, or JSON as the source model. The options available are: source object exists (the default), source object does not exist, and regardless of whether the source object exists.
Improved ValidateEDI Function
The ValidateEDI function has been enhanced with two new optional parameters:
- Get All Errors: This parameter gathers all errors that have been reported. The default option only returns the first error.
- Format: This parameter dictates whether the errors are returned in text, HTML, CSV, XML, or JSON format. The default format is text.
New Function to Support OpenAPI Calls
The ECSOpenAPI function has been added to Delta, utilizing the existing OpenAPI functionality in ECS. This function allows for easy building and customization of OpenAPI calls to query or update the ECS database.
Liaison ECS customers can find out more about this release at: Liaison eService
HL7 Now Supported
Delta now supports the Health Level Seven International (HL7) standard. HL7 is an interoperability standard for healthcare-related data. Within Delta, you can now map to and from an EDI document that contains HL7 2.x transactions. You can also use Liaison’s EDI Notepad and EDI Dictionary Viewer to view any transaction and definition within the HL7 2.x dictionary in an easy-to-use electronic format. EDI Notepad allows for easy viewing, validation, and acknowledgement of HL7 v2.x data. EDI Dictionary Viewer is a valuable reference tool and also allows for the creation of customized HL7 message definitions.
“Step-into” Functionality Added to Debugging Process
Debugging maps containing submaps is now even easier! Users now have the ability to “step into” submaps during the map debugging process. When working with a parent map, there is now a Step into Map option that appears below the Open Map option.
Figure 1. Step into Map Menu Option
Selecting “Step into Map” opens the next map in a new tab in the UI.
Inbound EDI Source Validation
Increase mapping accuracy with our new EDI Validation options. You can now check map input against a source model and/or EDI dictionary before map execution. In the event that the validation fails, an error message indicating the reason for failure displays so that you can easily locate and fix any issues. This feature allows for improved validation against a business specification without having to add all of the business logic to the map rule set.
You can all of Delta’s Data Validation options on the General tab of Map Properties screen.
Figure 1. Data Validation Options on the Map Properties screen
Select one of the following new options:
• Validate EDI source data against source model. Selecting this option tests the source model against the source data. The validation checks for the following:
- Mandatory objects or elements contained in the source model, but not found in the source data.
- Codepairs in the source data that are not allowed by the source model.
- Element data that fails minimum and maximum checks as defined by the source model.
Delta’s built-in function ‘ValidateEDI()’ has also been enhanced to support validating EDI data against an EDI model.
Note: When both the dictionary and model validation are enabled, the dictionary validation runs first and the model validation second.
Look Ahead Feature PeekElement()
Users can now peek and match the first occurrence of a segment/element by using the PeekElement() look ahead function. This function retrieves the value contained in the first occurrence of a specified segment. The PeekElement() function searches from the current position to the end of the document so if you want to search all data within a structure, be sure to start at the beginning of the document. This feature can be helpful if you want to populate a header or other element with information contained later in an EDI document. The search can be scoped to a current loop, so for example, if currently mapping a line item, PeekElement() can be called to locate information relevant to the current line item only.