Designer 10.7 | webMethods Service Development Help | Working with Elements | Finding Elements and Variables | Guidelines for Searching for Variables in Elements
 
Guidelines for Searching for Variables in Elements
You can search for variables (fields) within Integration Server elements and define the scope of the search operations. Search can be performed on IS document types, flow services, Java services, specifications, and triggers.
The following table identifies where you can search for field names in specific Integration Server elements.
Element
What can you search for?
IS Document Types
Variable names in a document type.
Flow services
Variable names in the service signature.
Variable names used for pipeline variable substitution in the following properties of flow steps:
*Label property in all the flow steps
*Scope property in all the flow steps
*Switch property in the BRANCH step
*Input array and Output array properties in a LOOP step
*In a MAP step
*Indices of link
*Copy condition properties of linked variables
*Map set (assign a value to a variable) and map delete
*Timeout property of the flow steps: BRANCH, CATCH, FINALLY, INVOKE, LOOP, MAP, REPEAT, SEQUENCE, and TRY
*Count and Repeat interval properties of REPEAT step
*Failure message, Failure name, Failure instance properties of the EXIT step
Note:
You can search only on the variable names used in any of the specified flow steps.
Java services
Variable names in the signature.
Note:
Search within Java code is not supported.
Specifications
Search for field names in the signature.
Triggers
Variable names used in a local filter of a webMethods messaging trigger. The variable names used in a filter can only be searched if they are enclosed within %.
Note:
Provider filters cannot be searched. You must manually examine provider filters.
Note:
If a document type is referenced or used in other elements, the field names inside the reference or usage are not searched. For example, suppose an IS document type named address includes a field named country and the address document type is referred to by a document reference named billingAddress and is used in the signature of a flow service named processOrder. Searching for country returns only address. The result set does not include the billingAddress document reference or the processOrder flow service.