Manage integration templates

  1. In the navigation pane, select Integration Designer > Manage Templates.
  2. Specify this information:
    Task type
    Select Integration as the task type.
    Templates
    Select a template from the list.
    • To copy the selected template, click Copy and specify a template name.
    • To delete the selected template, click Delete.
    • To create a new template, click New and specify a template name.
    Integration Type
    Select any of these integration types from the list:
    • Entity
    • BOD

      This integration type performs a BOD/XML type operation.

    • BODArea

      This integration type maps the value from the flow to a specific BOD or XML area.

    • M3WS

      This integration type performs an MI transaction operation.

  3. Based on the selected integration type, specify this information:
    • Entity integration type:
      Entity Alias
      Select an entity alias from the list.

      You can add entity aliases in the Database Entities module.

      See Identifying supported database tables.

      Note: Entity aliases depend on the selected connection string.
      Entity
      Select an entity from the list.
      Transaction Type
      Select a transaction type from the list.
      Note: The available transaction types are insert and update.
      If Exist
      Select skip or update from the list.

      If you select skip and the condition on the Condition table is satisfied, the integration task will perform a skip operation and the data will not be processed.

      If you select update and the condition on the Condition table is satisfied, data with the corresponding values will perform an update instead of inserting the data or record.

      Leave this field blank if you don't want to perform any of the available operations. Values selected on this operation will look-up from the Conditions table.

    • BOD integration type:
      BOD Type
      Select any of these BOD types from the list:
      • Acquire from XML Parameter

        This BOD type obtains the BOD/XML value from the xml parameter within the flow.

      • Acquire from File

        This BOD type obtains the BOD/XML value from a file.

        Note: This is applicable for Work unit type FileUnit.
      • Dump to XML Parameter

        This BOD type saves the BOD/XML value to the xml parameter within the flow.

      • Dump to File

        This BOD type saves the BOD/XML value to a file.

        Note: This is applicable for Work unit type FileUnit.
      Integrate From
      Specify a path where the values are acquired.
      Note: This field is available only if you select Acquire from XML Parameter or Acquire from File as the BOD type.
      Integrate To
      Specify a path where the values are dumped.
      Note: This field is available only if you select Dump to XML Parameter or Dump to File as the BOD type.
      Folder
      Specify a folder path where the XML files are located. Click the ellipsis button to browse for a folder.
      Note: This field is available only if you select Dump to File as the BOD type.
      Prefix
      Specify a prefix to be used for the file names of the XML files.
      Note: This field is available only if you select Dump to File as the BOD type.
      Null Parameter Skip
      If selected, parameters that contain null values will be skipped during the processing of the integration task.
    • BODArea integration type:
      Note: In BODArea integration types, you can specify a condition field to target in which element the BODArea is placed. A parameter should be created first then indicate the parameter in the Conditions area for proper placement of the XML element.
      Integrate To
      Specify a path where the values are dumped.
      Null Parameter Skip
      If selected, parameters that contain null values will be skipped during the processing of the integration task.
    • M3WS integration type:
      Program
      Select a program from the list.
      Note: The list contains the available and supported MI programs. To add an MI program, specify an MI program name and click Add.
      Transaction
      Select a transaction from the list.
      Note: The list contains all available transactions for the selected MI program.
  4. On the Parameters tab, specify this information or update the existing parameters:
    Note: When integrating to BOD or BODArea types and specifying an XML attribute or '@ parameter', place the parameter below the XML element where the parameter should be generated. For example, to create Item/Item@ItemId, the Item/Item parameter field should precede the parameter.
    Name
    Specify a parameter name.
    Column Name
    Select a column name from the list.
    Field Name
    Specify a field name.
    Note: This field is available only if you select M3WS as the integration type.
    Inline Type
    Select an inline type from the list.
    Note: This field is available only if you select Entity as the integration type.
    Default Value
    Specify a default value.
  5. On the Conditions table, specify this information or update the existing conditions:
    Field Name
    Specify a field name.
    Condition Type
    Select a condition type from the list.
    Condition Value
    Specify a condition value.
    Use as Variable
    Select if you want to use the field name as variable to be used when mapping flows. This field is automatically checked if the Condition Value contains the Field Name preceded with a hash.
  6. Click Save.
    Note: To see the integration flows that uses the selected integration template, click the Where Used tab.