RETRIEVES PROJECTS BASED ON FILTERS¶
Queries the d3VIEW platform project registry and returns a filtered, sorted list of projects. Use this worker to look up projects by name, bookmark status, lifecycle status, parent project, or date range before passing them to downstream workflow steps.
When to use¶
Tagged: filter, finder, project_lookup, projects, registry, search.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Search | search | text | — | Free-text keyword used to match against project names or descriptions; leave blank to return all projects subject to other filters. | |
| Bookmarked | bookmarked | select | — | Filter by bookmark status — select ‘Yes’ to return only bookmarked projects, ‘No’ for un-bookmarked; leave unset to include both. | |
| Status | status | text | — | One or more lifecycle status values (e.g. ‘active’, ‘closed’) to filter on; leave blank to include projects in all statuses. | |
| Parent Project | parent_project_id | remote_lookup | — | Remote-lookup selector for one or more parent project IDs; restricts results to direct children of the chosen parent project(s). | |
| Start Date | start_date | datetime-local | — | Inclusive lower-bound datetime filter (local timezone) on the project start date; leave blank to apply no lower date constraint. | |
| End Date | end_date | datetime-local | — | Inclusive upper-bound datetime filter (local timezone) on the project end date; leave blank to apply no upper date constraint. | |
| Limit records | limit | list | 25 | Maximum number of project records to return; defaults to 25 — choose a higher value or ‘No Limit’ (-1) for exhaustive queries. | |
| Sort By | order_by | list | srs.id:desc | Column and direction used to sort the result set (e.g. ‘p.name:asc’ for alphabetical, ‘p.id:desc’ for newest first); defaults to newest-ID-first. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Projects | projects | dataset | Dataset of matching project records (datatype: projects), each row representing one project with its metadata fields such as ID, name, status, and dates. |
Disciplines¶
- data.io.sql
- platform.workflow
Auto-generated from platform schema. Worker id: projects_finder. Schema hash: eae5ae22ad93. Hand-curated docs in workerexamples/ override this page when present.