|
Home
> Products >
Symphonia > Product History
Product History
Symphonia 3.7
(September 2003)
Symphonia 3.7 includes:
-
Integrated Debugging in the Map
Designer
-
Parsing of "undefined" messages
and segments
-
Support for the ANSI standard
HL7 2.xml profiles
-
Major Productivity enhancements
in all applications.
More information
Symphonia and Mapper 3.6.1
(November 2002)
-
New Validation Options
-
Syntax Rules
-
Unordered Groups
-
Validation Equations
-
Situational Equations
-
New Variable Datatypes
-
New Custom Primitive Types
-
New HL7 Profile Support
-
Optimised Load Time
-
Enhanced Programming Interface
More information
Symphonia 3.5 (including Symphonia
Mapper 1.2)
(May 2002)
-
UNICODE support in the Mapper
-
Import W3C schemas into
Symphonia XML
-
Access to MatchLists and
Validation table values through the API
-
Ability to modify the version
numbers of generated DLL's
-
EDI Message Designer
productivity enhancements
-
Ability to set default
separators from an API
-
Definition checking in Symphonia
Explorer
-
Autofilling multiple messages in
Symphonia Explorer
-
Autofilling validated fields and
match list field with valid items
-
Enhanced Java engine support
-
Additional Definition checking
in the EDI Message Designer.
Symphonia 3.4 (including Symphonia
Mapper 1.1)
(January 2002)
-
Database support through Stored
Procedures
-
Auto-Mapping of fields
-
Code Completion in the Mapper
-
Multiple Message Set Support in
the Mapper (support for batch messaging)
-
Ability to map binary fields
-
Global Variables in the Mapper
-
One to many support through
global variables in the Mapper
-
Ability to use COM components in
mappings
-
Ability to import existing
submaps in the Mapper
-
Find and Replace in the Mapper.
-
Explorer now supports Segment
and Field Index notation. (eg: for HL7, MSH.3 )
Symphonia 3.3 (including Symphonia
Mapper 1.0)
(August 2001)
-
Support for message item match
lists (support for HIPAA messages)
-
Extra definition validation in
the EDI message designer
-
Added Metaviewer interface for
programmatically accessing the Meta Data of as message
|