Pipeline taskbar

Complete the following actions while mapping input and output fields in a flow service. The taskbar is located in the upper-right corner of the Pipeline page.

Name and Icon Description
Recommended Mappings ( ) Recommends mappings based on the pattern of previous mappings. The recommended mappings are represented with dotted lines. For more information, see Smart Mapping.
Show only Mapped () Displays only the mapped fields.
Copy () Copies a field from the Pipeline Input and Pipeline Output sections. This icon is enabled only when a field is selected. For more information, see Copy and Paste Fields.
Clear () Clears all mappings and values set for fields in the pipeline. This icon is always enabled. For more information, see Clear Values.
Delete () Deletes the selected mapping. You can also delete the values set for input and output fields, delete the map between fields, and delete the drop value. This icon is enabled if a particular mapping is selected by clicking the mapping line. For more information, see Delete Mappings.
Move () Moves the selected field to either left, right, up, or down in the pipeline. The left and right icons are enabled only when the selected field has a possibility to move to the immediate parental hierarchy (if any). The up and down icons are enabled only when the selected field has a possibility to move one level up or down its sibling field.
Map () Connects service and pipeline fields in the pipeline with a line called a map (link). For more information, see Map Pipeline Fields.
Set Value () Sets the values for input and output fields. For more information, see Set Values.
Drop () Drops a field from the Pipeline Input or Pipeline Output sections. For more information, see Drop Fields.
Map by Condition () Sets a condition on a pipeline map. Only when the condition is satisfied the target field is assigned a value. For more information, see May by Condition.
Expand () Expands the Pipeline page.
Toggle Pipeline page () Enables efficient management and inspection of pipeline data. Offers a flexible way to control screen space.
Close () Closes the mapping page and returns to the flow service. This icon is always enabled. Whatever the state of mappings or data manipulations that are done till that point is saved.
Paste () Pastes the field in the pipeline after a copy field action. For more information, see Copy and Paste Fields.
Add () Adds a field to the pipeline. You can add fields that were not declared as input or output fields (through Define IO) of the flow service. For more information, see Add Fields.
Note: You can also access these actions by right-clicking a field in the pipeline:

Set Values

The Set Values feature is used to assign values to fields by selecting the field in the Pipeline page.

.

The behavior of the set values feature is as follows:

  • For String type fields

    • Accepts any non null value such as alphabets, numbers, and symbols.
    • Sets the field with an empty (blank) value if you open the Set Value screen and do not specify any value.

  • For PickList

    • PickList is a drop-down list where you can choose one of the values from a predefined list. Based on the operation selected, you can either provide custom values or select a value from the predefined list. This operation is decided by the Service for the respective fields.
      When a User is Allowed to Enter Custom Values On Default Set Value On Clear All
      True "(empty) "
      False Options[0] Options[0]
Note: When running a set value operation on the root document node, if the document node contains more than 60 child nodes, the set value operation may experience slight performance issues.

For example, let us see the Adding Integers (AddInts) functions that use the Math service.

  1. Create a flow service. For example, AddingIntegers. A flow service step is created initially without any data.
  2. Select the AddInts operation in the flow service step.

  3. Click on the flow service step. The Pipeline page appears. Two service input fields num1 and num2 are listed in the Service Input column.

  4. Click any of the fields, for example, num1. The Set Value dialog box appears.
  5. Enter the value in the num1 field.
    Note: When you paste data equal to or exceeding 0.5 MB in the text box, the system disables editing due to performance limitations. However, you can still use the respective buttons to copy and paste the data and perform editing in an external tool.
  6. Click Save. The value is set and the corresponding field is represented with the Set Value icon. If you export this step, the set value of this field is exported.
  7. Repeat the preceding steps to set values for the required fields.

Pipeline Variable Substitution

The Perform pipeline variable substitution checkbox indicates whether you want the application to perform pipeline variable substitution at run time. If selected, the application replaces the pipeline variable with the runtime value of the variable while running the flow service.

Note: You can assign values of string or string[] fields to other string or string[] fields in the pipeline.

The Perform pipeline variable substitution checkbox indicates whether you want the application to perform pipeline variable substitution at run time. If selected, the application replaces the pipeline variable with the runtime value of the variable while running the flow service.

Note: You can assign values of an only string or string[] fields to another string or string[] fields in the pipeline.

Clear Values

The Clear Values feature is used to reset field values. For document or document reference types, Clear All also resets the nested fields. The default values of different types on Set Value (without giving any input, just opening the Set Value page and save) and Clear All are as follows:

Field Type On Default Set Value On Clear All
String "(empty) "
Boolean False False
Array [] []
Float, Int, Double, Long, Short nothing set "
Document, Document Reference An object with all String fields at all levels is set to '', nothing is set for other types. An object with all String fields at all levels is set to '', nothing is set for other types.

Map Pipeline Fields

The Map Pipeline Fields feature allows you to connect service and pipeline fields in the pipeline with a line called a map (link). You can select two input fields and click the Map icon to create a map between them. Creating a map between fields copies the value from one field to another at run time. There are two types of mapping -

  • Implicit Mapping
  • Explicit Mapping
Note: When migrating integrations from Flow Editor to flow services, the existing mappings with references to fields whose definition has changed become invalid. For example, if a mapping references a field test, which was originally an integer, but later became a float, then the existing mapping to the field test as integer is invalid. Following migration, you are prompted to remove these invalid references. Either remove those references or reassign correctly in order to proceed.

Implicit Mapping

Within a flow service, IBM webMethods Integration implicitly maps fields whose names are the same and whose data types are compatible. Flow service connects implicitly mapped fields with a dotted line.

Explicit Mapping

You can map input fields from the Pipeline Input column to Service In fields, and also can map the output from the Service Out to a different field in the Pipeline Out column. Explicit Mapping can be achieved in the following ways:

  • Drag and Drop - Drag the mouse pointer from the source field and drop on the target field.

    Note: In order to map fields, you must drag the mouse pointer from the source field on to the text of the target field. Otherwise, the mapping does not happen.

  • Map Icon - Select a source field and target field by clicking it and then click in the toolbar. The fields are mapped.

Delete Mappings

The Delete Mappings feature allows you to remove mappings. You can delete each map individually or all mappings at a time.

  • Remove each mapping - You can do this in one of the following ways:

    • Using toolbar - Select a map by hovering on the map line (arrow) and click Delete in the toolbar.

    • Keyboard - Select a map by hovering on the map line (arrow) and press the Delete key.

  • Removing all Mappings - Click the icon in the toolbar to delete all maps at a time.

Search Fields

The Search feature allows you to search fields. When you type field names in the Search text box, IBM webMethods Integration performs a dynamic search across all fields (including nested fields), and displays the resultant fields in the respective pages. Also, each column has its own search bar that allows you to search in the respective column.

Expand Mapping page

The expand feature allows you to resize the Pipeline page. On clicking the Expand icon, the Pipeline page size increases and you can resize the column widths as per your requirements to view the mappings clearly.

Tip: The Expand Mapping page option is useful in scenarios when there are many mappings and the current default column width is not sufficient for clear view of the mappings. You can click Expand to increase the Pipeline page size and resize the column for viewing the mappings with more clarity.
Note: For any nested structures, you can easily expand or collapse all nodes by clicking the Expand All and Collapse All buttons. The Expand All and Collapse All buttons appear only when there are nested structures in a Transform step.

When any parent node is in expanded mode, then the button name is changed to Collapse All until all nodes are in collapsed state

Copy and Paste Fields

The Copy and Paste feature enables copying any field and pasting it in the pipeline.. Depending on the context, you can either paste the field or the field path. For example, if you copy a field and paste the field in the Set Value dialog box, the field path is pasted. Alternatively, you can use keyboard shortcuts Ctrl+C to copy and Ctrl+V to paste fields. You can perform the copy and paste actions in the following ways:

  • Copy the fields within the Pipeline page.
  • Copy and paste fields between the Define IO screen and the Pipeline page.
  • Copy across flow services
Note: To copy any field name in the pipeline page, you right-click the field and select Copy field name from the displayed menu. The complete path of the field is copied. You might use this option if you would like to extract field names only.

You cannot copy or paste flow steps or fields between flow services, deploy anywhere flow services, and API Flows.

Drop Fields

The Drop feature allows you to remove fields from a pipeline that are no longer used by the subsequent steps. You can drop fields from only the Pipeline Input and Pipeline Output columns.

By dropping the unwanted fields, you can reduce the size of the pipeline at run time. Also, the length and complexity of the Pipeline Input and Pipeline Output columns is reduced, thus making the pipeline page much easier to use when you are working with a complex flow service. If any output field is dropped, then that particular field is not sent as Pipeline Input to the next step. This way that you can restrict the flow of fields from one step to another.

For easy identification purpose, the Drop icon appears after a field is dropped.

You cannot drop a field in the following scenarios:

  • If the field has a value set.
  • If the field belongs to another flow service that is a parent of the existing flow service.

Add Fields

The Add Fields feature allows you to add fields to a pipeline.

Map by Condition

The Map by Condition feature allows you to define conditions for the maps (links) drawn between fields in a pipeline. A condition consists of one or more expressions that allow you to:

  • Check for the existence of a field in the pipeline
  • Check for the value of a field
  • Compare a field to another field

At run time, the application runs all conditional mappings and assigns a value to the target field only when the condition is true. Otherwise, the application ignores the mapping. In scenarios where the fields are mandatary and the conditions are not satisfied, you might observe flow service runtime failure issues.

You can map multiple source fields to the same target field if the mappings to the target have conditions. In some scenarios, where you have mapped multiple source fields to a single target field, at most, only one of the conditions you define can be true at run time. If more than one condition to the same target field evaluates to true, then the result is not definite because the order in which the conditions are run is not guaranteed.

You can define conditions for a map using the Condition Editor page. The Condition Editor page can be accessed by selecting the map and clicking the Map by Condition icon on the Pipeline page or by double-clicking the map.

The Condition Editor screen functions is similar to that of the Expression Editor screen. For more information about the Condition Editor screen description, see Expression Editor.

Adding Conditions to a Map

Example

Assume that there is a flow service CentimetertoMeterConversion that converts the values that are provided by you from centimeters to meters. If the meter value is zero, then a custom message is logged. The flow service includes the following:

  • Service: Math multiplyFloats
  • Service Input - num1 and num2
    • num1 takes the input values that are provided by you. num2 is a constant conversion unit, 0.01
  • Service Output - value
  • Pipeline Input - centimeters, minValue, maxValue, default
  • Pipeline Output - meters
  • Conditional Step: If meters value is equal to zero, then display a custom message

Let us modify the logic of the flow service such that it converts only specific values instead of all values based on the following conditions:

  • num1 = minValue > 1 and maxValue < 9999
  • default = minValue < 1

Before you Begin

  • Log in to your tenant.
  • Ensure that you have created the flow service as described in the example.

Basic Flow

  1. Go to the CentimetertoMeterConversion flow service.
  2. Select the centimeters to num1 map and click from the pipeline toolbar. The Condition Editor page appears.

    By default, the first field is selected and displayed in the editor.

  3. Ensure that the Enable Condition during execution checkbox is selected. Otherwise, the condition is not considered at run time.
  4. Define the conditions. For more information on how to define conditions and sub conditions, see Creating Complex Expressions.

    As per the example, the condition minValue > 1 and maxValue < 9999 is defined for the selected mapping .

  5. Click Save. The condition is added to the map and the icon is added to indicate that the map has a condition that is defined .
  6. Map the default pipeline Input field to num1.
  7. Define the condition for the Default pipeline Input field.
Note: To remove a condition from a map -
  • Select the map and click the Map By Condition icon. The Condition Editor appears.
  • Click Remove Condition.
  • Click Run. The results are displayed based on the values that you provide.

Default Pipeline Mapping Rules and Behavior

Before you start mapping fields, it is recommended to go through the mapping guidelines to avoid runtime issues due to incorrect mappings.

  • If a field has a Set Value, you cannot either map or drop fields and vice-versa.
  • If a field is defined in a pipeline and if the field is not mapped or a value is not set, then the field is not available in subsequent steps.
  • Set Value cannot be configured in the Pipeline Input and Service Output columns.
  • If a parent is mapped, child field of that parent cannot be mapped.
  • If a child field is mapped, parent of that child field cannot be mapped.
  • Target field can be mapped only once, except in case of array indices and map by condition.
  • Fields with different Object constraints cannot be mapped. If you map fields with different Object constraints and the Validate Input or Validate Output options are selected, the runtime result is undetermined.
  • Data type mappings that are allowed between pipeline fields is as follows:
    • Character Data Type
      Source Field Target Field Behavior
      Char Boolean, Char, Double, Object, Float, Integer, Long, Short, Date, Byte Array (b[]),Big Integer, Big Decimal Mapping occurs. Target field data type is typecasted to Character. For example, if there is a mapping between Character A and Integer X, then Integer X is typecasted as Character and the value of A is mapped to X.
      Char String Mapping does not occur at run time.
      Char Char[], Object[] Mapping occurs.Target field is type casted to Character data type and by default zeroth index (Index[0]) is mapped with Character value.
      Char Boolean[], Char[], Date[], Double[], Float[], Integer[], Long[], Short[], BigInteger[], BigDecimal[],String[], String[][] Mapping does not occur at run time.
      Char Document, Document[], DocumentReference, DocumentReference[] Mapping does not occur at run time.
      Char[] Boolean, Char, Double, Object, Float, Integer, Long, Short, Date, Byte Array (b[]),Big Integer, Big Decimal Target field data type is typecasted to Character.For example, if there is a mapping between Character A and Integer X, then Integer X is typecasted as Character and the value of A is mapped to X.
      Char[] Char[], Object[],Short[], Long[], Integer[], Float[], Double[], Boolean[], BigDecimal[], BigInteger[] Mapping Occurs. For more information, see Default Pipeline Rules for Mapping Array Fields
      Char[] String Mapping does not occur at run time.
      Char[] String[], String[][] Mapping does not occur at run time.
      Char[] Document, Document[], DocumentReference, DocumentReference[] Mapping does not occur at run time.
      Date Data Type
      Source Field Target Field Behavior
      Date Boolean, Char, Double, Object, Float, Integer, Long, Short, Date, Byte Array (b[]),Big Integer, Big Decimal Mapping occurs. Target field data type is typecasted to Date. For example, if there is a mapping between Date A and Integer X, then Integer X is typecasted as Date and the value of A is mapped to X.
      Date String Mapping does not occur at run time.
      Date Date[], Object[] Mapping occurs.Target field is type casted to Date data type and by default zeroth index (Index[0]) is mapped with Date value.
      Date Boolean[], Char[],Double[],Float[],Integer[],Long[],Short[],BigInteger[], BigDecimal[],String[], String[][] Mapping does not occur at run time.
      Date Document, Document[], DocumentReference, DocumentReference[] Mapping does not occur at run time.
      Date[] Boolean, Char, Double, Object, Float, Integer, Long, Short, Date, Byte Array (b[]),Big Integer, Big Decimal Mapping occurs.Target field data type is typecasted to Date.For example, if there is a mapping between Date A and Integer X, then Integer X is typecasted as Date and the value of A is mapped to X.
      Date[] Boolean[], Char[], Double[], Object[],Float[],Integer[],Long[],Short[], BigInteger[],BigDecimal[] Mapping Occurs. For more information, see Default Pipeline Rules for Mapping Array Fields
      Date[] String Mapping does not occur at run time.
      Date[] String[], String[][] Mapping does not occur at run time.
      Date[] Document, Document[], DocumentReference, DocumentReference[] Mapping does not occur at run time.
    • String Data Type
    Source Field Target Field Behavior
    String String, Short, Long, Integer, Float, Double, Boolean, Byte Array (b [ ]), Big Decimal, Big Integer, Object, Char, Date Mapping occurs.Target field data type is typecasted to String.For example, if there is a mapping between String _ABC_ and Integer _X_, then Integer _X_ is typecasted as String and the value of _ABC_ is mapped to _X_.
    String String [ ], Object [ ] Mapping occurs.Target field is type casted to String data type and by default zeroth index (Index\[0\]) is mapped with String value./td>
    String Short [ ], Long [ ],  Integer [ ], Float [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ], Char [ ], Date [ ] Mapping does not occur at run time.
    String Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at run time.
    String String [ ], Object [ ], StringTable [ ] [ ] Mapping occurs.Target field is type casted to string data type and by default zeroth index (Index\[0\]) is mapped with the string value.
    String [ ] Short [ ], Long [ ], Integer [ ], Float [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ], Char [ ],Date [ ] Mapping does not occur at run time.
    String Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at run time.
  • Float Data Type
Source Field Target Field Behavior
Float String Mapping does not occur at runtime.
Float Short, Long, Integer, Float, Double, Boolean, ByteArray (b [ ]), BigDecimal, BigInteger, Object, Cahr, Date Mapping occurs. Target field data type is typecasted to Float.For example, if there is a mapping between Float _F = 55.25_ and Integer _X_, then Integer _X_ is typecasted as Float and the value of _55.25_ is mapped to _X_.
Float Float [ ], Object [ ] Mapping Occurs. Target field data type is typecasted to source field data type and by default the zeroth index (Index\[0\]) is mapped with the Float value.
Float String [ ], Short [ ], Long [ ],  Integer [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ],Char [ ],Date [ ],StringTable [ ] [ ] Mapping does not occur at runtime.
Float Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at runtime.
Float [ ] Float [ ], Object [ ], Short [ ], Long [ ],  Integer [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ], Char [ ],Date [ ] Mapping Occurs. For more information, see [Default Pipeline Rules for Mapping Array Fields](/saas/webmethods-integration/11.0.10/flow_services/flowservices/#default-pipeline-rules-for-mapping-array-fields).
Float [ ] String\[\, String [ ] [ ] Mapping does not occur at runtime.
Float [ ] Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at run time.
  • Integer Data Type
Source Field Target Field Behavior
Integer String Mapping does not occur at runtime.
Integer Short, Long, Integer, Float, Double, Boolean, ByteArray (b [ ]), BigDecimal, BigInteger, Object, Char, Date Mapping occurs. Target field data type is typecasted to Integer.For example, if there is a mapping between Integer _I = 55_ and Float  _F_, then Float _F_ is typecasted as Integer and the value of _55_ is mapped to _X_.
Integer Integer [ ], Object [ ] Mapping Occurs. Target field data type is typecasted to Integer and by default the zeroth index (Index\[0\]) is mapped with the Integer value.
Integer String [ ], Short [ ], Long [ ], Float [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ],Char [ ],Date [ ], String [ ] [ ] Mapping does not occur at runtime.
Integer Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at runtime.
Integer [ ] Integer [ ], Object [ ], Short [ ], Long [ ], Float [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ], Char [ ],Date [ ] Mapping Occurs. For more information, see [Default Pipeline Rules for Mapping Array Fields](/saas/webmethods-integration/11.0.10/flow_services/flowservices/#default-pipeline-rules-for-mapping-array-fields).
Integer [ ] String [ ], String [ ] [ ] Mapping does not occur at runtime.
Integer [ ] Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at run time.
Source Field Target Field Behavior
Short String Mapping does not occur at runtime.
Short Short, Long, Integer, Float, Double, Boolean, Byte Array (b [ ]), Big Decimal, Big Integer, Object, Char, Date Mapping occurs.Target field data type is typecasted to Short.For example, if there is a mapping between Short _325_ and Integer _X_, then Integer _X_ is typecasted as Short and the value of _325_ is mapped to _X_.
Short Short [ ], Object [ ] Mapping Occurs. Target field data type is typecasted to Short and by default the zeroth index (Index\[0\]) is mapped with the Short value.
Short String [ ], Long [ ],  Integer [ ], Float [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ], Char [ ],Date [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
Short Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at runtime.
Short [ ] Integer [ ], Object [ ], Long [ ],  Integer [ ], Float [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ], Char [ ],Date [ ] Mapping Occurs. For more information, see [Default Pipeline Rules for Mapping Array Fields](/saas/webmethods-integration/11.0.10/flow_services/flowservices/#default-pipeline-rules-for-mapping-array-fields).
Short [ ] String [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
Short [ ] Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at run time.
Source Field Target Field Behavior
Long String Mapping does not occur at runtime.
Long Short, Long, Integer, Float, Double, Boolean, Byte Array (b [ ]), Big Decimal, Big Integer, Object, Char, Date Mapping occurs.Target field data type is typecasted to Long.For example, if there is a mapping between Long _L_ and Integer _X_, then Integer _X_ is typecasted as long and the value of _L_ is mapped to _X_.
Long Long [ ], Object [ ] Mapping Occurs.Target field data type is typecasted to Long and by default the zeroth index (Index\[0\]) is mapped with the Long value.
Long String [ ], Short [ ],  Integer [ ], Float [ ], Double [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ], Char [ ],Date [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
Long Document, Document [ ], Document Reference, DocumentReference [ ] Mapping does not occur at runtime.
Long [ ] Long [ ], Object [ ],Short [ ],  Integer [ ], Float [ ], Double [ ], Boolean [ ], Big Decimal [ ], Big Integer [ ], Char [ ],Date [ ] Mapping Occurs. For more information, see [Default Pipeline Rules for Mapping Array Fields](/saas/webmethods-integration/11.0.10/flow_services/flowservices/#default-pipeline-rules-for-mapping-array-fields).
Long [ ] String [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
Long [ ] Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at runtime.
Source Field Target Field Behavior
Double String Mapping does not occur at runtime.
Double Short, Long, Integer, Float, Double, Boolean, Byte Array (b [ ]), Big Decimal, Big Integer, Object, Char, Date Mapping occurs.Target field data type is typecasted to Double.For example, if there is a mapping between Double _D1 = 4.673854_ and Float _F_, then Float F is typecasted as _Double_ and the value of _4.673854_ is mapped to _F_.
Double Double [ ], Object [ ] Mapping Occurs.Target field data type is typecasted to Double and by default the zeroth index (Index\[0\]) is mapped with the Double value.
Double String [ ], Short [ ],  Integer [ ], Float [ ], Long [ ], Boolean [ ], BigDecimal [ ], BigInteger [ ], Char [ ],Date [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
Double Document, Document [ ], Document Reference, DocumentReference [ ] Mapping does not occur at runtime.
Double [ ] Double [ ], Object [ ], Short [ ],  Integer [ ], Float [ ], Long [ ], Boolean [ ], Big Decimal [ ], Big Integer [ ], Char [ ],Date [ ] Mapping Occurs.
Double [ ] String [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
Double [ ] Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at runtime.
Source Field Target Field Behavior
Boolean String Mapping does not occur at runtime.
Boolean Short, Long, Integer, Float, Double, Boolean, ByteArray (b [ ]), BigDecimal, BigInteger, Object, Char, Date Mapping occurs.Target field data type is typecasted to Booelan.For example, if there is a mapping between Boolean _B = True_ and Double _D_, then Double _D_ is typecasted as Boolean and the value of _True_ is mapped to _D_.
Boolean Boolean[ ],  Object [ ] Mapping Occurs.Target field data type is typecasted to **Boolean** and by default the zeroth index (Index\[0\]) is mapped with the Boolean value.
Boolean String[ ], Short[ ], Long[ ],  Integer[ ], Float [ ], Double[ ], Big Decimal[ ], Big Integer[ ], Char [ ],Date [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
Boolean Document, Document [ ], Document Reference, DocumentReference [ ] Mapping does not occur at runtime.
Boolean [ ] Boolean [ ],  Object [ ], Short [ ], Long [ ],  Integer [ ], Float [ ], Double [ ], BigDecimal [ ], BigInteger [ ], Char [ ],Date [ ] Mapping Occurs.
Boolean [ ] String [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
Boolean [ ] Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at runtime.
Source Field Target Field Behavior
BigDecimal String Mapping does not occur at runtime.
BigDecimal Short, Long, Integer, Float, Double, Boolean, ByteArray (b [ ]), BigDecimal, BigInteger, Object, Char, Date Mapping occurs.Target field data type is typecasted to Big Decimal. For example, if there is a mapping between Big Decimal _D1 = 4.673854_ and Float F, then Float _F_ is typecasted as Big Decimal and the value of _4.673854_ is mapped to _F_.
BigDecimal BigDecimal [ ],  Object [ ], BigInteger [ ] Mapping Occurs.Target field data type is typecasted to **Boolean** and by default the zeroth index (Index\[0\]) is mapped with the Boolean value.
BigDecimal String [ ], Short [ ], Long [ ],  Integer [ ], Float [ ],  Double [ ], Boolean [ ],Char [ ],Date [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
BigDecimal Document, Document [ ], Document Reference, DocumentReference [ ] Mapping does not occur at runtime.
BigDecimal [ ] BigDecimal [ ],  Object [ ], Short [ ], Long [ ], Integer [ ], Float [ ],  Double [ ], Boolean [ ], BigInteger [ ], Char [ ],Date [ ] Mapping Occurs.
BigDecimal [ ] String [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
BigDecimal [ ] Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at runtime.
Source Field Target Field Behavior
BigInteger String Mapping does not occur at runtime.
BigInteger Short, Long, Integer, Float, Double, Boolean, ByteArray (b [ ]), BigDecimal, BigInteger, Object, Char, Date Mapping occurs.Target field data type is typecasted to Big Integer. For example, if there is a mapping between Big Integer _B1 = 4673854_ and Float _F_, then Float _F_ is typecasted as Big Integer  and the value of _4673854_ is mapped to _F_.
BigInteger BigInteger [ ],  Object [ ], BigDecimal [ ] Mapping Occurs.Target field data type is typecasted to Big Integer and by default the zeroth index (Index [0]) is mapped with the Big Integer value.
BigInteger String [ ], Short [ ], Long [ ],  Integer [ ], Float [ ], Double [ ], Boolean [ ], Char [ ],Date [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
BigInteger Document, Document [ ], Document Reference, DocumentReference [ ] Mapping does not occur at runtime.
BigInteger [ ] Big Integer [ ], Object [ ],Short [ ], Long [ ],  Integer [ ], Float [ ], Double [ ],  BigInteger [ ], BigDecimal [ ], Char [ ],Date [ ] Mapping Occurs. For more information, see Default Pipeline Rules for Mapping Array Fields
BigInteger [ ] String [ ], StringTable [ ] [ ] Mapping does not occur at runtime.
BigInteger [ ] Document, Document [ ], DocumentReference, DocumentReference [ ] Mapping does not occur at runtime.
  • String Table[][] Data Type
    Source Field Target Field Behavior
    String[][] String, Boolean, Char, Float, Double, Integer, Long, Short, Date, Byte Array (b[]),Big Integer, Big Decimal Mapping occurs. For more information, see Default Pipeline Rules for Mapping Array Fields
    String[][] Date[], Object[],Boolean[], Char[],Double[],Float[],Integer[], Long[], Short[], BigInteger[], BigDecimal[],String[], String[][] Mapping occurs. Target field data type is typecasted to String[] and the first row elements are considered.
    String[][] Document, Document[], DocumentReference, DocumentReference[] Mapping does not occur at run time.
Note:

  • Mapping between a multidimensional data type (Target) and any single dimensional data type (Source), then the Target field is assigned to the specified element of the Source field. For rules to know whether mapping occurs at runtime, see the tables in the Default Pipeline Mapping Rules and Behaviour section.

    • Single Dimension Data Types - String [], Short[] , Long[], Integer[], Float[], Double,[] Boolean[], Big Decimal[], Big Integer[], Object []
    • Multi Dimension Data Types - String , Short , Long , Integer ,Float , Double , Boolean , Big Decimal , Big Integer , Object
    • Document, Document References can be mapped only with Document, Document References And arrays of these (Document[], Document Reference[]).