Using condition filtering with IBM App Connect Enterprise Designer

Applications in IBM App Connect Enterprise Designer provide a condition filtering capability, which you can use during retrieve or update actions. If you add conditions for retrieve or update actions, you can optionally use condition filtering to refine the conditions that are applied. This topic describes the additional configuration that is required when you want to use condition filtering.

Before you begin

Install IBM® App Connect Enterprise 13.0.1.0 or later to use IBM App Connect Enterprise Designer.

In IBM App Connect Enterprise Designer, create a message flow that contains an input node and an application node by completing Creating an event driven flow.

For example, the following message flow contains a GitHubnode for creating new issues, a GitHub node for retrieving issues, and a Log node.

1. If you have not clicked Add condition, click it now and then select the property that you want to filter on.
   The option Enable condition filtering becomes visible in the Map options menu.
2. In the Map options menu, select Enable condition filtering.
   
   
   The text "Filter mode" is displayed next to the Map options menu control.
   
3. Place the cursor in the input field, delete any existing text, and click Insert a mapping to open the Available mappings table.
   The mappings in the Available mappings table are derived from the input node ( in this example, the first GitHub node) in the message flow that you created in Creating an event driven flow. The mappings are referenced from the second GitHub node.
4. In the Available mappings table, click Map inputs GitHub New issues /Issue/ID

   The text 1 is displayed under the input field. (This is the data that is associated with the mapping ID and it is derived from the first GitHub node in the message flow that you created in Creating an event driven flow. The only if: field is displayed. The drop-down menu has the options True, False, and Custom.

   
5. From the drop-down menu in the only if: field, select Custom.
6. Delete any text from the only if: field and click Insert a mapping.
7. In the Available mappings wizard, click Map inputs GitHub New issues /Issue/Creator.

   The text The user that created the issue is displayed under the only if: field. (This is the data that is associated with the mapping /Issue/Creator and it is derived from the first GitHub node in the message flow that you created in Creating an event driven flow.

8. Optionally, you can populate the fields manually by typing in the required values. For example, you can type the value GitHub1 in Creator.
9. Optionally, you can edit the data that is associated with a mapping by completing the following steps:
   1. Place the cursor in the input field, delete any existing text, and click Insert a mapping to open the Available mappings table.
   2. Select a mapping from the Available mappings table, for example Map inputs / GitHub / New issues /Issue/Creator.
   3. In the "Retrieve issues" section, click the pencil icon to view available mappings and edit your sample data.
      
      The table "Map inputs and sample data" is displayed.
   4. In the table, select the mapping User / Login and change the data SampleLogin to Github1.
      
      The text "Github1" will be displayed after the field that you selected.

      
10. Optionally, you can set properties that specify the maximum number of records to retrieve and the action to be taken if that limit is exceeded by clicking + or - in Maximum number of items to retrieve and selecting the radio button Throw an error or Process 10 items from the collection.