Response Chain (httpClient-ResponseChain)

This component is functionally the same as the ResponseTrigger component, with two additional properties (Targets and Delay Between Each Request), which cause one or more secondary HTTP client components to send when the trigger logic fires.

You add this component to either a HttpClient component, or to the point’s Proxy Ext (HttpClientNetwork > HttpClientDevice > Points > StringPoint in the Nav tree. The ResponseChain evaluates its logic each time its parent receives a response.

Figure 35.   Response Chain properties
Image

To access, expand Config > Drivers > HttpClient > ResponseChain and right click Views > AX Property Sheet.

In addition to the standard property (Enabled), this component provides these properties.

Property Value Description
Fire On drop-down list
Defines the trigger criterion using a response code:

200 Response defines a specific response code.

On2xx (200 -299) provides a response code range.

Unauthorized/Forbidden provides an unauthorized (401) or forbidden (403) response.

Response Code Changed from previous defines any code that is different from the previous code.

All Responses defines any code.

Conditions additional properties
Provides a second way to define a trigger criterion by adding one or two conditions from the palette (BodyContains and HeaderContains), then configures the And Boolean property appropriately.

For property descriptions refer to “Conditions (httpClient-HttpConditions)”.

Triggered read-only
Reports true when the ResponseTrigger component’s logical criteria have been fulfilled. Otherwise, it reports (false).

true also fires the trigger topic when the logical criterion has been fulfilled. You may link either of these slots to Wire Sheet logic.

Targets drop-down list Selects one or more secondary clients to add (Image) to the list of targets.
Delay Between Each Request hours minutes seconds Defines the minimum amount of time to elapse between the invocation of the Send action for each target client.