Skip to content
AssureSwarm Docs

Agent Operating Guide

/bridge-mapping-edit

Interactive editor for a bridge's field mapping: view, add, remove, or edit field mappings and re-validate them against your Canvas schema.

Configure the field mapping a bridge uses to translate records between Canvas and an external system. This skill is an interactive editor over a bridge’s mapping: view the current mapping, add a field, remove one, or edit one, and re-validate the whole file against your Canvas schema after each change. Set it up once before your first sync: the Archer and ServiceNow syncs and the AuditBoard migration are then mapping-driven.

When to use

Section titled “When to use”

Before the first sync or migration with a system, to define how its fields map onto your item types. And whenever a Canvas schema change breaks an existing mapping: this is how you repair it.

Inputs

Section titled “Inputs”
Flag Required Notes
--system <name> Yes Which bridge to edit: archer, snow, auditboard, or workday.
--item-type <name> Yes Which item type’s mapping to edit.
Subcommand No view (default), add-field, remove-field, or edit-field.

Example

Section titled “Example”

/bridge-mapping-edit --system archer --item-type issue add-field walks you through one new field mapping, the external field name, the Canvas field name, its type, whether it’s required, and any enum value-map, then checks against get_schema that the Canvas field exists and the types are compatible, flagging any lossy coercions before it saves. The default view subcommand just prints the current mapping as a table.

Good to know

Section titled “Good to know”
  • Every successful edit bumps the mapping’s version. The sync skills refuse to run against a version they haven’t seen before without your re-confirmation, so a mid-stream mapping change can’t silently alter a sync.
  • Lossy coercions, string truncation, enum narrowing, decimal precision loss, and unmapped fields are surfaced rather than silently dropped.
  • A schema refresh can invalidate a mapping; pair this with /coach-setup after your schema changes.
Section titled “Related”