DPS Import Form Library Dialog

Before attempting to use this dialog, review the topic Preparing to Use the DPS Import Form Library Dialog.

You use the DPS Import Form Library Dialog to perform the initial import of CONNECTOR and optional FLDP files into your ePortal data source project. Later, you use the same dialog if there are new or updated CONNECTOR and FLDP files.

You must select every CONNECTOR file associated with the TIP application that will be used in the new ePortal presentation method. The DPS Import Form Library Dialog creates an ePortal server message and client message (by default) for each selected CONNECTOR file.

Note: If a corresponding FLDP file exists, the server message contains presentation details, such as static form text. If the client message is automatically created, it includes links to the server message. Refer to the topic Creating Client Messages for more information.

To launch the DPS Import Form Library Dialog, do one of the following:

To use the dialog, perform these steps:

  1. Click Browse and browse to the folder that contains the CONNECTOR and optional FLDP files generated by the FLMU utility.

  2. Select Source Encoding from the dropdown menu.

    This specifies the character encoding that is used by the CONNECTOR and FLDP files.

    A data grid displays a row for each CONNECTOR file found in the folder. The columns in the grid are defined as follows:

    Attribute

    Description

    Name

    The name of the CONNECTOR file. This column also provides a check box which you use to determine whether to import the CONNECTOR file or not.

    Note: There is an additional check box in the column heading that can be used to check or uncheck all rows in the grid.

    State

    The state of the CONNECTOR file. The state is one of the following values:

    • New – This CONNECTOR file has not been imported into the data source project, or was previously deleted.

    • Imported – This CONNECTOR file was previously imported into the data source project. If you select this item, it will overwrite the existing server message.

    TIP Transaction Code

    The optional TIP transaction code.

    You can optionally supply the name of the TIP transaction as configured in VALTAB on the OS 2200 server that you will invoke with this message. If you supply a value, ePortal initializes the metadata field tiptrancode__ using the value you supply.

    Alternatively, you can leave the transaction code blank. Later, you can supply a value for the metadata field tiptrancode__ with Orchestration, or by using the code in your presentation projects. For example, you may decide to leave the transaction code blank if you plan to use this message to call more than one transaction on the OS 2200 server.

    Refer to the topic Handling Updates to the OS 2200 TIP Transaction Code for more information.

    Configuration

    Includes a Change link that you can click to configure the server message direction and/or discriminator field.

    If you want to change the server message direction or the discriminator value, click the Change configuration link, and the Configure Discriminator Field Dialog opens.

    By default, the fields Number and Check-Number in the record header are selected for discriminator fields, and server message direction is set based on DPS form Usage. Usually these defaults are adequate.

  3. Click the Import button to start the import process.

    The import process begins and the Import button becomes a Pause button.

    During the import process, the State column changes as the import progresses. If an error occurs, the State column is set to an error message.

  4. Click the Pause button to pause the import, if desired.

    If you click the Pause button, the button text changes to Continue.

    Click the Continue button to resume the import.

  5. When the import process is complete, click the Close button.