1Open the Test System modal
From the editor toolbar
Click the 🧪 Test button on the editor toolbar (test id test-system-button, aria-label "Test System"). The Test System modal opens (aria-label "Test System Modal") and lists every command this system defines.
Pick a command
Use the search box at the top of the modal to filter, then click a command row to select it. The right panel shows the command's parameter form ready for you to fill.
2Configure parameters
The form is generated from the command's parameter list. Required fields show a red *; AUTO fields are greyed out and show their generated value.
Unlike Orchestration Studio's pinning, the Test System modal calls the live upstream. Use a sandbox tenant or a dedicated test account when you're trialing destructive commands like delete.
3Run a command
Click ▶ Run command
The button (test id test-run-button) is disabled until all required fields are filled. Once clicked, the request is sent and a response panel opens at the bottom of the modal.
Cancel a long-running call
If the upstream is slow, a Cancel button replaces Run. Cancelling aborts the request from the platform side; the upstream may still complete the operation.
4Read the response & error tabs
The response panel has three tabs.
| Tab | Contents |
|---|---|
| Response | Pretty-printed body. Status code in the tab label. JSON is auto-formatted; binary responses are summarised. |
| Headers | All request & response headers. Useful when an upstream returns rate-limit or correlation IDs. |
| Raw cURL | The exact request as a copy-pasteable cURL command. Hand it to support, paste it into a terminal — same wire bytes EmpowerNow sent. |
When it fails
If the response status is 4xx or 5xx, the Response tab styling flips to red and an extra Error tab appears. The Error tab parses the body looking for the upstream's error description, error code, and any retry hint.
5Quick Test from the Designer
Right-click a command row
The Designer tab has a context menu on every command row with ⚡ Quick Test. It opens a compact panel inside the command modal's Test tab — the same form as in the full Test System modal, but tied to a single command.
Use Quick Test when you're already in the Designer and want to verify one command without opening the bigger modal.
Quick Test is recorded for audit
Both Test System and Quick Test runs are logged with the operator's identity, the command, the inputs (with secret redaction), and the response status. Visible to admins via the platform audit log; useful when investigating "who triggered that ticket?".
6The API Docs tab
The 📚 API Docs tab generates Swagger-style documentation from the Designer's command set. Read-only; updated live as you add or edit commands.
id (path).userPrincipalName, displayName.| Per-command block | Contents |
|---|---|
| Header | Method, path, command name, and a Quick Test link. |
| Description | Plain-English summary plus required parameters. |
| Request schema | Expandable JSON Schema for the request body / query parameters. |
| Response schema | Expandable JSON Schema for the success response. |
| Examples | Sample request & response payloads, drawn from MCP examples on the command (when configured). |
The API Docs tab is deep-linkable: the URL /system-editor/<name>?tab=api-docs opens directly to it. Send this link to anyone authoring workflows or integrating with the system from outside the platform.