Configuring to fire secondary components

You can set up one or more secondary HttpClient components to send when the trigger logic fires. The ResponseChain is functionally the same as the ResponseTrigger component with some additional properties. It evaluates its logic each time a response is received by the parent.
Prerequisites: The httpClient palette is open.
  1. Expand ResponseChaining in the palette.
  2. Do one of the following to configure secondary components:
    • For an HttpClient, drag a ResponseChain from the palette to your HttpClient component in the station.
    • For an HttpClientDevice, expand HttpClientNetwork > HttpClientDevice > Points > StringPoint and drag a ResponseChain from the palette to the Proxy Ext node in the Nav tree.
  3. Double-click the ResponseChain.
    The component’s AX Property Sheet opens.
    Image
  4. To add a secondary client, expand the Targets drop-down list, select a client and click the plus button (Image).
    The secondary clients appear below the drop-down list.
    Image
  5. To remove a secondary client, click the X next to the client.
  6. Configure the Delay Between Each Request and click Save.
    This defines the minimum amount of time to elapse between the invocation of the Send action for each target client.
    When a parent client receives a response, if the conditional logic and Fire On logic are met, each of the secondary clients in the Targets list sends in sequence.