Global search
- Synopsis
- Full Details
In briefGlobal search finds objects of ten types — workflows, jobs, the Toolkit types, scripts and self service buttons — by name in one place. From the results you can open, copy or delete an object, export the list to CSV or Excel, and save the search for everyone in your organization to re-run.
WhereThe Global Search box in the header, on every page. Results open on the search page
(/search), where saved searches are under Select Saved Search.
When
- You know an object's name, or part of it, but not where it lives.
- You need a list of objects across several types, or an export of one.
- You want to copy a workflow or script, or delete an object, straight from its search result.
To report on configuration or history with chosen columns and filters, use Reports instead.
How
- Type at least two characters in Global Search.
- Choose the object types to search, and narrow the results with the per-type filters.
- Use a row's actions to open, copy or delete an object, or export the results.
- To keep the search, save it with a name. The full walkthrough is Search across OpCon Continuum.
- On the search page, the query is a plain, case-insensitive match on the name — and, for jobs,
the documentation. The quick results under the box also match descriptions and workflow
documentation.
*,%and_are matched literally. - Copy is offered for workflows and scripts only; Delete for every type except jobs.
- Saved searches are shared, and Select Saved Search lists the first 100 in name order.
- An export of one type stops at 100,000 rows, and one across several types at 5,000. Over the limit, the export is refused until you narrow the filters.
- An export is blocked if any selected type failed to load. Refresh and retry.
- Email Delivery settings on a saved search are stored, but no email is sent.
Task walkthrough: Search across OpCon Continuum. This page is the full configuration and troubleshooting reference.
Global search finds objects across the platform in one place, with bulk actions, export, and saved searches.
What's searchable
Ten entity types: Workflows, Jobs, Calendars, Frequencies, Thresholds, Resources, Tags, Properties, Scripts, Self Service Buttons. Any combination can be searched at once.
The last of those is the service request catalog — the interface calls the objects self service buttons, and a result opens the button for editing on Self Service Configuration.
A Toolkit result — a calendar, frequency, threshold, resource, tag or property — lands on that type's Toolkit tab with the object itself open for editing. See Toolkit overview.
Searching
- The query matches object names. A result is any object of the selected types whose name
contains the text you type, ignoring case —
payrollfindsNightly-PAYROLL-Export. For jobs the job's documentation is searched as well. It is a plain text match, not a word or full-text search: there is no stemming or ranking, and*,%and_are matched literally rather than as wildcards. A query can be up to 100 characters. - The quick results under the Global Search box match a little more. Before you open the search page, the list under the box also matches an object's description — for calendars, frequencies, thresholds, resources, tags, properties and scripts — and a workflow's documentation, as well as a job's.
- The query starts at 2 characters. A single character is treated as no query, so the results show every object of the selected types.
- Per-type filters, pagination (10/20/50/100 per page).
- A link that filters scripts by their type's name still works. A search URL bookmarked before
script types became a catalog carries the type's name, such as
PowerShell, rather than its id. The name is matched to its script type exactly, and a name no type has finds no scripts. The Script Type filter shows no selection for such a link, but the results are filtered. - You can page through at most 50 pages, whether you search one type or several. A result set over 5,000 rows shows a notice suggesting you narrow the search or run a report instead.
Saved searches
A search can be saved (entity types, query, filters, sort) and re-run from Select Saved Search. Saving needs at least one object type selected, and a name not already used by another saved search.
- Saved searches are shared. Every user in your organization sees the same list.
- Saving, changing and deleting a saved search are checked against your roles: they need Saved Searches Create, Saved Searches Edit and Saved Searches Delete. Reading and running one is not checked. See Environments and saved searches.
- Select Saved Search lists the first 100, in name order. A saved search past the first 100 cannot be picked from the list.
- Email delivery does not send anything. The save dialog has an Email Delivery switch with recipients, frequency, time of day and timezone. Those settings are saved with the search, but no email is sent.
Bulk row actions
| Action | Notes |
|---|---|
| Go to object / Open in new tab | Go to the object. |
| Copy | Supported for workflows and scripts only. For a workflow the dialog suggests <name> - Copy, shortened if that would exceed the 40-character limit. For a script it suggests <name>_Copy, with any spaces in the name turned into _, because a script name cannot contain spaces. The suggestion is checked against the naming rules as you type, so a name the save would reject is reported on the field instead. |
| Delete | Available for most types; not for jobs. The confirmation closes once the object is deleted, and its buttons are unavailable while the delete runs. A delete that fails keeps it open with the reason — Delete failed. when there is none to give — and closing it clears the message. |
Export
Export to CSV or Excel (xlsx). Exports include formula-injection protection and are
blocked if any selected entity type failed to load (with a clear error so the user can retry).
An export of one type is limited to 100,000 rows, and an export across several types to 5,000 rows. A search over the limit is refused with a message asking you to narrow your filters.
- Copy and delete availability vary by type (copy: workflows/scripts only; delete: not for jobs) — that's by design, not a missing feature.
- A blocked export usually means one entity type failed to load (timeout, unreachable, access denied) — refresh and retry.