GLOBAL FINDER¶
Find d3VIEW objects across domains using structured filters, returning lightweight {id, name} pairs. Supports simulation, projects, studies, physicaltest, responses, templates, hpcjobs, hpcjobsettings, user_workflows, library_workflows, and users. Use the companion finder_get_configurations worker first to discover which filter keys are valid for a given domain.
When to use¶
Tagged: cross-domain, filter, global_finder, hpcjobs, lookup, objects, physicaltest, projects.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Domain | domain | select | — | ✓ | The object type to search; must be one of: simulation, projects, studies, physicaltest, responses, templates, hpcjobs, hpcjobsettings, user_workflows, library_workflows, users. Common singular/plural aliases (e.g. ‘simulations’, ‘user’) are normalised automatically. |
| Filters | filters | textarea | — | Optional JSON object of domain-specific filter key-value pairs (e.g. {“search”: “barrier”, “project_id”: [123], “status”: “active”}); call finder_get_configurations to learn available keys for the chosen domain. Leave empty or {} to return all results up to the limit. | |
| Limit | limit | integer | 50 | Maximum number of {id, name} pairs to return; defaults to 50 if omitted or set to 0/negative. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Status | status | text | Human-readable success or error message, e.g. ‘Found 12 result(s)’ or ‘Error: Domain is not supported.’. |
| Results | results | string | JSON-serialised array of {id, name} objects matching the query, e.g. [{“id”: 42, “name”: “Run_001”}, …]; empty array ([]) on error or no matches. |
Disciplines¶
- data.io.sql
- platform.integration
- platform.job_submission
- platform.workflow
Auto-generated from platform schema. Worker id: global_finder. Schema hash: 39e456c178a9. Hand-curated docs in workerexamples/ override this page when present.