Challenge 3: Design a Chained Sequence — Possible Solution
====================================================================

Request 1: Create Order
  POST {{baseUrl}}/orders
  Body: { "productId": "P200", "quantity": 1 }

  Response: { "id": "O5521", "status": "processing", ... }
  -> Select the "id" value in the response -> "Set as variable"
     -> saved as {{orderId}}

Request 2: Get Order Status
  GET {{baseUrl}}/orders/{{orderId}}

WHY THIS WORKS AS AN ANSWER
------------------------------
The value that needs to flow from Request 1's response into Request 2
is the newly created order's id — Request 2 has no way to know this
value in advance, since it's generated by the server only at the
moment the order is created. Using this chapter's "Set as variable"
pattern on that response field, then referencing {{orderId}} directly
inside Request 2's URL (not just a header, unlike the login-token
example) is exactly the mechanism needed here.

This differs from the chapter's own login-chaining example mainly in
WHERE the chained value gets used: the auth token example inserted
{{authToken}} into a header, while here {{orderId}} needs to be
inserted directly into the URL PATH of the second request — the same
{{variable}} syntax works in either place, since Postman treats the
whole request (URL, headers, body) as one template that variables get
substituted into.