Difference: 530DataExchange (10 vs. 11)

Revision 112020-05-12 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="Main.APPX530Features"

Data Exchange Application

Line: 15 to 15

The 'import' subroutine must be run. This is a subroutine (created by 0DX based on the mapping) that will read the internal files and move the data to the final files and fields based on the user defined mapping.

Alternatively, an external Appx process can read the extracted data & process it without defining a mapping or creating a subroutine.

Changed:

<
<

An API allows a programmer to perform one or both of those steps under ILF control. Mapping the data is optional, the programmer can just use the API to process the file and then read the extracted data directly.

>
>

When defining the mapping, the user can enter the tags directly or they can choose to process an actual XML file first, and then refer to the tags found in that XML file in their mapping. This is often easier, as the user will be able to see the actual tags and the data associated with the tag.

Installation

Line: 24 to 24

Next, add 0DX as a related application to any Databases that will use it, and run Create Files for that Database.

Changed:

<
<

If you plan to expose the user interface, define an Optional Child somewhere in your application that invokes application 0DX, process type MENU, with no process name. If you only plan to use the API, you can skip this step.

>
>

Your client screen size should be set to 28 x 120 minimum to run 0DX interactively.

Usage

Line: 49 to 49

The Processing options give you various ways of loading data into Appx.

Changed:

<
<

The API allows you to process and optionally import data under ILF control.

>
>

The API allows you to process and optionally import data under ILF control.

Comments:

Read what other users have said about this page or add your own comments.

View topic | History: r11 < r10 < r9 < r8 | More topic actions...