Export/Import Step

The Export/Import step is mainly used to run functions in an end-system after exporting data to the end-system. The data that results from the function run is returned to the Schema table. To create the Export/Import step, navigate to Interfaces> {Specific Interface}> Tasks> {Specific Task}> Steps >New >New Export/Import Step.

 

For more information about steps, see Defining Steps .

 

To manipulate your data, follow the steps below:

  1. Select the REST connection from the Connection drop-down list. Click Open for your reference, or if modifications or any changes are required in the pre-defined connection.

Warning: If you can't find the necessary Connection in the list, go to the connection page and make sure the Is Active checkbox is enabled.

  1. Select the required function from the Function drop-down list.

The REST functions supported by IConduct are:

  • DELETE
  • GET
  • HEAD
  • OPTIONS
  • PATCH
  • POST
  • PUT

Note: "GET" and "HEAD" entities don't have a REST request body.

  1. Using the Action drop-down list, choose the action you want to perform.
  • Insert: Put data into the schema.
  • Update: Add the latest data to the existing schema fields.
  • Delete: Delete data from the schema.
  • Upsert: Select to either update or insert rows of data depending upon whether a specific set of conditions are met (or not).

Note: On selecting Update, Delete, Upsert from drop-down list, the Schema Column and Source Column appear. These fields associate a specific field in the source system to a specific field in the Schema. The rows from the source system will Update/Delete or Upsert rows in the Schema based on this association. Select required columns to enable automatic updates.

  1. Once done, press Create and proceed with mappings. In mappings, the REST service affixes mandatory columns - BODY for export and ResultText for import. The BODY column sets the request body, while the ResultText envelopes the response body.

Note: At Export Mappings, single mapping applies to the connections with the application/x-www-form-urlencoded or multipart/form-data content types. The single mapping allows working with the data within single schema to set the data values before sending a request to an end-point.

 

For the mappings created using the IConduct version below 6.2, the following applies to Export Mappings should the application/x-www-form-urlencoded and multipart/form-data content types be used for the connection:

  1. Export Mappings from the Admin Navigation opens the ordinary two-direction mapping page.
  2. The REST request will be sent with the content within the mapped fields.
  3. If the Schema contains the columns that start with "parameter_" or “file_” than these fields will be used, the usual mapping will be ignored.
  4. If a field is mapped using the single mapping page, then the schema columns that start with "parameter_" or “file_” are ignored and the single mapping applies