Filtering ASAP Response Data

The amount of response data returned by an activation system can be very large, while the needed data might be quite small. Parsing large amounts of response data can affect OSM performance. If you notice a reduction in OSM performance due to large amounts of response data, you can specify a condition on specific parameters to limit the response data. You can create response data limitations for as many events or exceptions as you choose by binding the activation response data to the desired OSM data.

To limit response data:

In the Task editor Response Data tab, select an event or exception from the Event/Exception list.
In the Response Mapping are, select the Set Data Location tab.
In the Activation Response area, right-click InfoParm.

The Response Filter Properties view is displayed.
Drag and drop a parameter into the Response Filter Condition field.

The XPath representation of the parameter is created in the Condition field.
Add the desired condition to the XPath representation.

For example, consider that you only want to update infoParm data in OSM if the serviceId infoParm parameter from orderCompleteEvent is equal to 2. First, select orderCompleteEvent in the Event/Exception field. Then click Detailed Parameters and infoParm in the Activation Response field. Drag and drop serviceId into the Condition field. The XPath representation of serviceID is as follows:

mslv-sa:serviceId

Now set the desired condition by adding ='2':

mslv-sa:serviceId='2'
Click Save.