Commands & Designer

Click + Add Object Type

The button on the Designer toolbar (test id add-object-type-button) opens the Create Object Type modal. Provide:

• Name — singular noun: user, group, incident.
• Display name — title-cased label shown in UIs and pickers.
• Description — what this object represents in the source system.
• Schema source — pick from the imported OpenAPI definitions, paste a JSON Schema, or start empty.

Click + Command on an object type

Each object-type card has its own + Command button (test id add-command-btn, aria-label "Add command"). The Enhanced Command Modal opens with the object type pre-selected.

When to use

For commands with non-trivial JSON bodies, the Body tab lets you paste a template that maps parameter values into the right structure:

{
  "accountEnabled": true,
  "displayName": "{{ params.displayName }}",
  "mailNickname": "{{ params.mailNickname | default(params.displayName | replace(' ','')) }}",
  "userPrincipalName": "{{ params.userPrincipalName }}",
  "passwordProfile": {
    "forceChangePasswordNextSignIn": true,
    "password": "{{ secret:initial_password }}"
  }
}

The template engine supports the same expression syntax as Orchestration Studio — pipe filters, defaults, conditionals.

Open the Schema Mapper

Click 🗺 Map schema on a command row, or use Ctrl + Shift + M from the command modal. The Schema Mapper opens with two side-by-side schemas: Source (the system's native fields) on the left, Canonical (EmpowerNow Person/Account/Group) on the right.

Two modes

• Visual (default) — drag to draw mappings between fields; right-click a mapping for transform options (uppercase, default, jsonpath).
• YAML — text view of the same mapping. Use for bulk edits or when you want to copy mappings between commands.

The mode toggle is at the top-right of the Mapper. The filter input (test id schema-mapper-filter) hides fields not matching your search.

Select multiple tools

Tick the checkboxes on the left of each row. The bulk action bar appears at the top of the MCP Tools tab once any are selected.

Bulk actions

• Enable all / Disable all — flip many tools at once.
• Edit annotations — open a small editor that applies the same annotation set to every selected tool.
• Set delegation scopes — apply the same scopes to every selected tool.

Bulk operations require system-editor:command · edit on every selected row.

Resource kinds & operations

The tab lists each resource kind the system supports (e.g. Person, Account, Group, Entitlement). For each, you map the standard operations: create, update, read, delete, list, link, unlink.

Why it matters

Fulfillment is what lets canonical platform features ("offboard this person across all systems", "do an access review") work without the orchestration layer needing to know each system's specific verbs. Configure it once per system; the platform calls the right command automatically.

Validation drawer

Press Ctrl + Shift + V (test id fulfillment-validate-button) to open the validation drawer. The drawer lists every resource kind with its operation coverage:

• ✓ Mapped — operation has a target command.
• ⚠ Unmapped — operation has no target. The platform feature that uses it won't work for this system.
• ✘ Broken — target command doesn't exist anymore (e.g. someone deleted it).

Click any row in the drawer to jump to the failing mapping.

Override

Validation errors block save by default. The Override action (test id fulfillment-override-button, requires the system-editor:fulfillment · override permission) lets a privileged operator save anyway — for example, when a connector is being authored over multiple sessions and you want to commit partial work.