AlmondTill/G3N API

On this page

updateTaskLabel

mutation · in the family Task label

What it does

Edit a label for organizing tasks — change its details.

Edit a TaskLabel's mutable attributes. Requires the unrestricted capability + the record's CURRENT revision.

Careful

Edits take effect immediately and write a new revision; the old revision stays in history.

Who may call it

Capability area: Places and layout — How your organizations and facilities are arranged day to day — facilities, zones and bins, teams and labels.

Arguments

NameTypeRequiredNotes
idID ID!yesThe id of the record.
revisionID ID!yesThe revision id you read on the record; the change is refused if an edit landed in the meantime.
inputEditTaskLabelInput EditTaskLabelInput!yesNo further notes.

Returns

TaskLabel TaskLabel! — A TaskLabel — the WORK vocabulary: a group-defined label attached to Tasks by reference (labelIds). DELIBERATELY its OWN master, NOT a reuse of the catalog Tag — catalog vocabulary (what we sell) and work vocabulary (how we operate) must not blend, and dooming a work label must never referential-gate against catalog nodes. The Tag SHAPE otherwise (caption + optional #rrggbb color; free-string labels stay unrepresentable — typo-proof, rename-safe via caption). FSM: active(i) ⇄ inactive → doomed (the template — ≠ the Tag's two-state: work vocabulary retires seasonally and comes back, so inactive earns its keep; 'blocked' lives HERE as a label because it has no machine consequence — the disclosed states-vs-labels lean). NOT searchable (supporting vocabulary — the Decoration SB-d class; reached via the tasks list filter, never name-found). The ops event domain (at.ops.task_label.*).

Example request

mutation ExampleUpdateTaskLabel($id: ID!, $revision: ID!, $input: EditTaskLabelInput!) {
  updateTaskLabel(id: $id, revision: $revision, input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    color
  }
}

Variables:

{
  "id": "01900000-0000-7000-8000-37386ae00000",
  "revision": "01900000-0000-7000-8000-b7960e180000",
  "input": {
    "caption": "Blue jeans"
  }
}

Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.

Example response

{
  "data": {
    "updateTaskLabel": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "LB-EXMP-0000-000F",
      "type": "TaskLabel",
      "caption": "Blue jeans",
      "status": "active",
      "parentId": "01900000-0000-7000-8000-065235280000",
      "rootId": "01900000-0000-7000-8000-a093dd800000",
      "createdAt": "2027-01-31T00:00:00.000Z",
      "updatedAt": "2027-01-31T00:00:00.000Z",
      "revisionNum": 1,
      "revision": "01900000-0000-7000-8000-b7960e180000",
      "color": "<color>"
    }
  },
  "extensions": {
    "at": {
      "callId": "01EXAMPLE-CALL-ID",
      "version": {
        "requested": {
          "name": "genesis",
          "number": 0
        },
        "serviced": {
          "name": "genesis",
          "number": 0
        }
      }
    }
  }
}

Errors this call can answer

Dry run

Add dryRun: true to the request envelope (extensions.at) to rehearse this call: every check runs, the write is rehearsed against the current records and nothing is stored; the answer is the refusal a real call would give, or the record it would create. Every response to a rehearsal carries dryRun: true, so a rehearsed record is never mistaken for a saved one.