CHECKS IF A TEST HAS A RESPONSE BY NAME¶
Checks whether a physical test record has at least one response matching a given name, using configurable string-matching logic (contains, starts_with, ends_with, excludes). Use this worker in workflow branches that need to gate downstream steps on the presence of a named response (vector, scalar, view, or dataset) within a physical test.
When to use¶
Tagged: branching, existence_check, name_check, physicaltest, response, simulation.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Physicaltest | physicaltest_id | remote_lookup | — | ✓ | Remote lookup reference to the physical test record to interrogate; must resolve to a valid physical test entity in the platform. |
| Response Name | response_name | textarea | — | ✓ | The name (or name fragment) of the response to search for within the selected physical test; evaluated against response names using the matching rule defined by the location input. |
| Type | type | select | vector | ✓ | Response type to filter by when searching for the named response; one of vector, scalar, view, or dataset — defaults to vector. |
| Location | location | select | contains | ✓ | String-matching rule applied to response_name; one of contains (default), starts_with, ends_with, or excludes. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Physicaletst Id | physicaletst_id | integer | Integer primary key of the physical test record that was queried, passed through for chaining into downstream workers. |
| Result | result | scalar | Boolean-style scalar result indicating whether a matching response was found (true/1) or not (false/0). |
Disciplines¶
- data.dataset.ingest
- platform.workflow
Auto-generated from platform schema. Worker id: physicaltest_has_response_by_name. Schema hash: fcb2c77ac2bf. Hand-curated docs in workerexamples/ override this page when present.