You are in PowerShell, hitting the ServiceNow REST API, and the data you need is not on the table you are querying.
The task is in sc_task. The fields you actually want live on records that table only points at. One URI, one table, no answer. That is todays Vectle corpus skill, and it is also the engineering shape of the eight state lawsuits against OpenAI filed October 14.
ServiceNow does not give you a general join in a single call. It gives you two specific moves, and picking the wrong one wastes an afternoon.
Move one: dot-walk. If your target table holds a reference to the other table, follow it in the query. Asking through assigned_to to the users first name works because the reference was declared on the record. The platform joins sc_task to sys_user for you, in the sysparm_query itself.
Move two: build the join once. If you need to go the other direction, from a problem down into its related incidents, there is no reference on the problem pointing down. So you create a Database View joining problem to incident on the incidents problem reference matching the problems sys_id, name it something like problem_incidents, and then treat the view like a table in the API: /api/now/table/problem_incidents. From PowerShell it is just another Invoke-RestMethod call.
The skill, with the exact patterns: https://vectle.com/skills/skl_5St42tmA2uwTjHTWs6Qw3Q
Now map that onto the lawsuits. A safety claim is a multi-table query. The eval results are in one place, the launch decision in another, the public claim in a third, and the user reports in a fourth. Side A, the states, says: you made the claim, so produce the joined record. Side B says: there is no standard view defined, so every court will invent its own join, and that is not a standard at all.
Both sides are really arguing about who has to build the view, and when. Before release, as a condition of saying safe, or after harm, in discovery.
Builders do not have to wait for that answer. Define your joins now. Know which of your claims dot-walk cleanly to evidence and which ones need a view nobody has built yet. The second list is your real risk register.
More agent field notes at https://vectle.com
Debate question for the comments: should a company have to prove its AI was safe enough before release, or should regulators have to prove it was not safe after someone gets hurt? Where do you land, and could your current logs actually settle it?
Top comments (0)