CREATES A NEW STUDY¶
Creates a new Study entity on the d3VIEW platform, registering it with a name, optional description, tags, and an associated response template. Use this worker at the start of a workflow to provision the study container that downstream workers will populate with simulation or test results.
When to use¶
Tagged: create, platform, registry, study, study_create.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Study Name | study_name | text | — | ✓ | Human-readable name for the new study (e.g. ‘Frontal_ODB_Run42’); required — the study cannot be created without it. |
| Description | description | textarea | — | Free-text description of the study’s purpose or scope; optional, leave blank if no additional context is needed. | |
| Tags | tags | textarea | — | Comma- or newline-separated keywords to tag the study for search and filtering (e.g. ‘crash, odb, v2’); optional. | |
| Response Template | responsetemplate_id | remote_lookup | — | Remote-lookup reference to an existing Response Template that defines the KPI schema for this study; leave unset if no template is required. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Study Id | study_id | scalar | Integer or UUID identifier of the newly created study, returned by the platform; pass this value to downstream workers that need to attach data or results to the study. |
Disciplines¶
- platform.workflow
Auto-generated from platform schema. Worker id: study_create. Schema hash: 5a85d6d92c9c. Hand-curated docs in workerexamples/ override this page when present.