An interesting example may be a web application generating a search id named searchID, and this id being transferred from page to page as a request parameter. The request recording looks like this:

During a test, NeoLoad will play back the request using the searchID that was recorded. Therefore, you need to replace the searchID with the appropriate value. The preceding page contains the following link: <a href="http://loadtestauth/loadtest/search/index.jsp?searchID=&lt;mygoodsearchid&gt;&amp;page=2">Page2</a>

So this manual request must be changed to a "Follow a link from the previous request" type:

For example, the searchID value is set at <MUST BE PRESENT>, which means that the searchID may have any kind of value. Using this configuration, NeoLoad will search for a link using:

As the server response contains only one link matching the description, NeoLoad will use this link with the searchID parameter value present in the server response.

You can also set the page parameter to <MUST BE PRESENT>. If the response contains several links such as:

<a href="search.php?searchID=<mygoodsearchid>&page=2">page2</a> 
<a href="search.php?searchID=<mygoodsearchid>&page=3">page3</a> 
<a href="search.php?searchID=<mygoodsearchid>&page=4">page4</a>

then all these links match the definition and NeoLoad will select either one at random or a specific occurrence, depending on how the parameter has been configured.