A flag is used to identify a request that fulfills certain criteria. When a request fulfilling the criteria has been identified, a mark appears next to its icon in the User Path tree. Any Transaction (Container, loop, User Path, etc.) containing a flagged item is itself flagged.
To flag requests
Display the flags pane:
Select the User Paths node or,
Right-click on an element on the User Paths tree and select Flag requests.
Select your flagging criteria.
The items that fulfill the criteria, as well as their parent items, are flagged.
Flags stay in place until the None criterion is selected.
Requests can be flagged according to the following criteria:
none: All flags are cleared.
with the variable: The request must use the variable defined with a click on the picker button:
as variable extractor: The request contains an extractor that extracts the specified variable.
used in request: The variable is used in the request content (URL parameters, form parameters...).
whose definition contains: The request contains a specific string defined with a click on the picker button. The search is carried out in request paths, parameter names and values, validations, names of the variable extractors variables, HTTP headers, and requests text content where the request is Post-type with a text-type content.
whose recorded response contains: The response to the request made during the recording contains the specified string.
with response validations: The response to the request must carry the validation criteria defined in the Design section.
with variable extractors defined on:
requests: The request contains at least one variable extractor defined on its response.
parameters: The request contains at least one variable extractor defined on one of its parameters.
is link/form extractor: The request type is "Follow a link from the previous request" or "Submit a form from the previous request".
with parameters: The request features at least one parameter.
is a POST form: The request method is Post.
disabled: The request execution is disabled in the Virtual User Profile.
whose type is: The request type must be selected in the drop-down list (SOAP, Media, Adobe Flex/AMF, or else).
with SLA profile: The item is linked to the selected SLA profile. The Any option designates any element linked to a SLA profile.
whose content has not been decoded: The request features binary content that needs additional libraries to work properly.
Match case: Enabled by default, this option ensures the request is written with its specific capitalization. To bypass case, disable the option.
Flags are restricted in scope to the User Path in which the item that was right-clicked is located. To carry out a search in all User Paths, click the User Pathsroot node.
To change the search scope on the fly, click the desired User Path or the root node while the validation dialog is visible.