The Search for Use function lets you search where an object is used in other objects. This helps you understand object dependencies and the potential effect of modifying, transporting, exporting or importing, deleting or otherwise handling your search object. The Search for Use function is available from all lists that contain objects, from combo boxes, and from the global search dropdown list.
- Right-click your search object and select Search for Use from the context-menu.
A list opens up that contains all the objects in which your search object is used. For each of these objects you can see the following information:
This column shows you the exact location in which your search is used.
Your search object is used in a Workflow. This column shows Task(2). This means that the object is the task number 2 in the Workflow.
Your search object is an Include called JOBI.JOBS.STD_POSTSCRIPT. It is used in a Job. This column shows Post Process(Line 4)/:INC JOBI.JOBS.STD_POSTSCRIPT . This means that your search object is used in line 4 on the Post Process page of the Job.
If another user has opened this object, this column indicates who.
Double-click an object in the list to open it and see where your search object is used. Alternatively, middle-click it to open it in a new browser tab.
Tip: If the object is used in a Workflow or in a Schedule, the Workflow or the Schedule opens to show you exactly where in its structure that particular task is located. The task is highlighted.
In scripts this function is deactivated by default. Administrator users can activate it in the UC_CLIENT_SETTINGS variable (see UC_CLIENT_SETTINGS - Various Client Settings) using the SEARCH_SCRIPT_FOR_USAGE key. Two methods are available:
The searched string must be somewhere in the script as otherwise it cannot be displayed.
Example: The search for MM lists results in which it is included as a whole or partially.
The searched string is handled as a word which is enclosed in delimiters such as blanks, left and right parentheses, equals (=), comma, single quotations, double quotations, end of lines and script ends.
Note: Underscores are not delimiters. Searching for MM in _MM_ does not return a result.
Example: The search for MM lists results in which it is enclosed in the described delimiters:
- =MM at the end of a line
Calendar Events in Scripts
When searching for Calendar Events in scripts, the result only includes lines that contain both the Calendar Event and the name of the Calendar object.
The search function does not find Calendar and Calendar Event usages if the settings of recurring tasks are concerned. See Executing Objects - Recurring.
The Calendar object ON_CALL_DUTY has two calendar events, MONDAY_TO_FRIDAY and WORKDAYS. The latter one is a group Calendar Event that contains the Calendar Event MONDAY_TO_FRIDAY. The result of searching the use of MONDAY_TO_FRIDAY does not include the calendar event WORKDAYS because it is stored in the same Calendar object.
The search function does not find Agent usages if the filter specifications refer to Agent Groups (HOSTG).
The search for use function also includes fields that include an object but have been deactivated and are grayed out.
The object type is not considered if the wildcards "?" and "*" are included in your search for object names.