• All Files

Export Step

This section describes how to add and set up the connection for the Export step applicable to the tasks in the interface. For more information about steps, see Defining Steps

 

The Export step allows exporting entities from IConduct to MongoDB. To create the Export step, navigate to Interfaces> Default> Tasks> Steps >New >New Export Step.

 

  1. Select the target connection from the Connection drop-down list. Press Open for your reference, or if modifications or any changes are required in the pre-defined connection.
  1. Select the target entity from the Entity Name drop-down list.
  1. Select the required action from the Action drop-down list:
  • 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).

 

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 %Document% and %Filter% fields appear by default in the Target Column. These fields contain the document body and filter values for export.

 

IConduct works with MongoDB following one of these scenarios:

Scenario 1. If the Schema already contains a document, map the corresponding Schema column to the %Document%. All other fields do not apply for schema mapping. Each Schema field is exported to MongoDB as a separate document.

 

Scenario 2. If the document is not made part of the Schema, it is created using the structure from the JSON Schema of the MongoDB document field (see Configuration Instructions) and Shema-to-Target columns mapping.

 

Working with scenario two, create these mandatory service fields in Schema:

 

IconductKey

To separate the documents and for their appropriate export in one step, create the IConductKey schema column. This column allows distinguishing schema fields that pertain to different documents. IConductKey should contain a unique ID value for each document.

 

{path to array}.PUID

To separate different array elements within one JSON schema, for each array create a schema column that includes the path to array and .PUID in its name. This column allows distinguishing array elements. {path to array}.PUID should contain a unique ID value for each element of the array.