Discovery connector request node actions and behavior

When you use a discovery connector request node in a message flow, the behavior of the flow depends on the actions that you set when you configured the node during discovery and on the availability of any objects that you want to retrieve or update.

After you configure the node, the connector properties that you set in the Connector Discovery wizard are displayed on the Basic tab in the property editor for the node. The properties include the Action property that you set in the wizard, such as RETRIEVEALL. The action that you set, along with the outcome of the message, affects whether the results go to the Out terminal, the Failure terminal, or the No Data terminal, or whether the local environment is updated or an exception is thrown.

Note that the maximum file size that can be processed by a discovery connector request node is 10 MB.

RETRIEVEALL actions

For RETRIEVEALL actions, if the connector is invoked successfully but the action returns no data (as no records were found), the message is sent to the No Data terminal. If an action returns no data and the No Data terminal is not wired, an exception is thrown.

UPDATEALL actions

For UPDATEALL actions, if the call to the remote service or server succeeds but nothing is updated, the value for isUpdated in the LocalEnvironment is set to false. Otherwise, isUpdated is set to true for a successful operation. For more information about the LocalEnvironment, see LocalEnvironment structure for connector input and request nodes.

DELETEALL actions

For DELETEALL actions, if the call to the remote service or server succeeds but nothing is deleted, the value for isDeleted in the LocalEnvironment is set to false. Otherwise, isDeleted is set to true for a successful operation. For more information about the LocalEnvironment, see LocalEnvironment structure for connector input and request nodes.

UPSERTWITHWHERE actions

For UPSERTWITHWHERE actions, you can assume that if the action succeeded and propagated to the output terminal, the call to create or update the requested object was successful.

All other actions

All other actions are regarded as 'custom actions.' If these actions succeed, a message is propagated to the OUT terminal. If the actions do not succeed, the message goes to the failure terminal if the failure terminal is wired. If the failure terminal is not wired, an exception is thrown.