You will often want to specifically handle the case when a connection action either:
•Generates a general connection error (Error Code 200)
or
•Returns no data although the connection was successful (Error Code 201)
You can do this very easily with a behavior configured to check for all possible outcomes of a Connect command. The example uses the Multiple Branch command to detect both error conditions. If neither error occurs, then the behavior simply exits.
The next image shows how the Multiple Branch condition is set using the Edit Condition dialog (see the Using the Formula and Condition Editor topics).
See also: Using Single Sign-On
Return to: Integration
