rename_steps
Atomically updates a Workday Studio step ID across assembly.xml and assembly-diagram.xml, preventing diagram-open MatchError crashes from partial renames.
Instructions
Atomically renames a step ID in BOTH assembly.xml AND assembly-diagram.xml.
WHY THIS EXISTS: Renaming an ID in only one file causes a scala.MatchError crash when Studio opens the diagram. This tool updates all references in a single operation:
assembly.xml — id="OldID", routes-to="OldID", routes-response-to="OldID", endpoint vm:// paths containing /OldID assembly-diagram.xml — all href="assembly.xml#OldID" forms (visualProperties, connections source/target, swimlane elements)
SAFE TO USE FOR: cc:async-mediation, cc:local-in, cc:local-out, cc:route, cc:splitter, cc:send-error, cc:workday-out-*, cc:http-out, cc:workday-in, and any other element with an id= attribute.
Creates backups of both files before writing. Runs validate_assembly after.
BATCH RENAMES: call once per ID — do not batch multiple renames into one call.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_name": "<project_name>",
"old_id": "<old_id>",
"new_id": "<new_id>"
},
"name": "rename_steps"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| new_id | Yes | New step ID, e.g. "SetTransactionProps" — use verb+object PascalCase | |
| old_id | Yes | The existing step ID to rename, e.g. "AsyncMediation3" | |
| dry_run | No | If true, return the planned replacements without writing any files | |
| project_name | Yes | Project name, e.g. "INT999_Employee_Sync" |