Agents
Send only the maintenance lookup fields
BOTIE
Examples, experiments and workspace controls
Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.
Try your own inputs
Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.
Context for this challenge
Connect the original record and needed-field names to Keep only the needed fields. Inspect which values remain.
The source record contains a private contact field that the manual lookup does not need.
Inspect the component calculation
Keep only the needed fields( Maintenance record: Original maintenance record Needed field names: Field names needed for this lookup )
Examples and results
- Original maintenance record
{ "asset": "P7", "symptomCode": "VIBRATION", "contact": "Private technician contact" }- Field names needed for this lookup
- 0asset
- 1symptomCode
- Required result
{ "asset": "P7", "symptomCode": "VIBRATION" }
- Original maintenance record
{ "asset": "P7", "symptomCode": "VIBRATION", "contact": "Private technician contact" }- Field names needed for this lookup
- 0asset
- 1symptomCode
- Required result
{ "asset": "P7", "symptomCode": "VIBRATION" }
Try a fresh construction
This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.
Stuck? Inspect a worked construction
The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.
Assumptions and test precision
The fixture assumes trusted classifications and controlled field values. It does not detect hidden personal data, enforce a network sandbox or make a request. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.
Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.
A new field has no release classification
This check uses the pieces from “Let only the needed fields reach release”.
BOTIE
- Original maintenance record
{ "asset": "P4", "siteCode": "NORTH-2", "contact": "Private contact" }- Field names needed for this lookup
- 0asset
- 1siteCode
- Server field classifications
{ "asset": "approved" }- Destination service ID
manual-index
- Approved service IDs
- 0manual-index
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
If symptomCode were replaced by unrestricted text, which privacy question would these field labels fail to answer?
Projection controls field selection. Free-text detection, destination enforcement and telemetry retention need their own evidence.
The fixture assumes trusted classifications and controlled field values. It does not detect hidden personal data, enforce a network sandbox or make a request.
Work through the Python challenges →