Mapping data from/into multiple files, using input/output file names as parameters, and additional flexibility for EDI integration, and support for WSDL 2.0 are just a few of the exciting new features that have been added to MapForce® 2010 in response to a significant number of customer requests.

Mapping data from/into multiple files

MapForce now lets you process data from or into multiple files. This means that you can easily consolidate file collections by aggregating data from a directory into one file or output data from one file to many. Multiple file names can be specified through the use of wildcard characters (e.g., ? or *), through a database table, auto-number sequences, or through other methods.

For example, it may be necessary to create a mapping from a file collection, or to generate individual XML files for each main table record in a large database.

The simple example below shows a mapping in which two files from a directory are used as the source data for a mapping into a single target file.

The output file generated from this mapping is easily saved to any location from the Output Preview window.

In order to separate the output results into two separate XML files, simply add a connection between the two file items at the top of each mapping component.

Using input/output file names as parameters

A complement to the feature above, the ability to use input or output file names as parameters in MapForce lets you generate dynamic mappings in which this information is defined at run-time.

In the example below, this is accomplished by creating an input parameter and connecting it to the file item node of a mapping component.

This feature is extremely valuable for real-time transformations, when the input and output file names are not necessarily known until transformation occurs. Parameters created in MapForce mappings are passed on for use via the command line or generated code.

Support for xsi:type in XML Schema

MapForce now supports the use of <xsi:type> within XML documents. <xsi:type> is an attribute that can be used in any XML instance to explicitly select an element's type, for example if the corresponding schema specifies an abstract type only.

For example, if you are dealing with a collection of address elements it may be desirable to create an abstract type, AddressType, in your XML Schema and then have each instance of an address element determine the derived type (USAddressType, UKAddressType, GermanAddressType, etc.).

MapForce now properly analyzes XML Schemas to determine where in an XML instance document the <xsi:type> attribute could be applicable and displays this as a clickable button in the mapping component. This lets you choose to display the derived types as separate nodes if a different mapping is needed depending on the specifics of the derived types.

This often requested feature gives you increased flexibility in your XML data mappings.

EDI file validation in generated code

MapForce now lets you validate the EDI output of your mappings not just within MapForce but also within the generated code. This helps you to maintain the integrity of your infrastructure by ensuring that only valid EDI messages are processed.

The screenshot above shows EDI validation within MapForce, which has existed already in v2009. The same validation functionality is now available in v2010 in the generated code.

Support for additional EDIFACT messages

These are control messages and are not included in the standard EDIFACT directories, but are described separately under syntax documentation published by the Joint Syntax Working Group.

Support for WSDL 2.0

MapForce now supports WSDL 2.0 recommendation from the W3C for building and connecting to Web services MapForce automatically recognizes the syntax of WSDL 2.0 documents and applies appropriate processing rules.

MapForce automatically detects whether your Web service is based on WSDL 1.1 or 2.0 and components are depicted accordingly in the design interface.