Request Chaining

Help Topics
Chaining items enable execution engine to use data of the previous request with the current request. For example, you can define chaining with the type Complete or partial RESPONSE URL and then use it in the URL field of particular request item. This will ensure that every execution of the request item will use response URL obtained from the previous execution for its request URL. For more information on using chaining items in request item properties, see the corresponding topic.
Important
Chaining items can be managed in the Chaining tab of project properties.

Add chaining

To add chaining, click Add new button in the toolbar located above the chaining list. New chaining with default name is automatically added to the list. Name of chaining must contain only alphanumeric characters or underscore, you can safely rename chaining even after it is in use by request items and name will be changed everywhere chaining is used.
Important
Chaining item names in particular project must be unique.
Important
Because parameters and chaining items can be used in the same properties of request item, HttpMaster does not allow project parameters and chaining items to share the same name.

Specify properties of chaining

Properties of the chaining are managed in the pane located next to the chaining list. You have to select chaining type and specify possible chaining values, for example, regular expression to extract data.

Obtain chaining data only once and then reuse it

Whenever execution engine encounters new usage of the chaining item, it tries to obtain relevant data for it from the execution data of the previous request. This behavior can be overriden with this option in chaining definition. If this option is turned on, execution engine will obtain relevant data only at the first chaining item use and will maintain this value during the whole execution batch. If execution engine will then encounter any further uses of this chaining item in the execution batch, it will immediately use this stored value and will not try to extract anything from the execution data of the previous request. This behavior can be useful in some cases, for example, if you need to obtain some authentication token in the first request and then reuse it in all subsequent batch requests.

For a step-by-step tutorial on using chaining, see the corresponding topic in How to section.