related
related add
Add a related case link
Usage
bash
pega related add <caseId> [flags]Source endpoint: POST /cases/{caseID}/related_cases — view command source
Arguments
| Argument | Required | Description |
|---|---|---|
caseId | Yes | Case ID |
Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--format | option | No | json | Output format (json, compact, yaml, table) |
--fields | option | No | Comma-separated top-level fields to include in output | |
--dry-run | boolean | No | Print HTTP request details and exit without executing | |
--quiet | boolean | No | Suppress all stderr progress/warning output | |
--verbose | boolean | No | Emit full HTTP request/response details to stderr | |
--no-cache | boolean | No | Bypass token file cache; perform fresh OAuth exchange | |
--profile | option | No | default | Named config profile |
--related-case-id | option | Yes | Related case ID | |
--relationship | option | Yes | Relationship type |
Examples
sh
pega related add MYAPP-CASE-1 --related-case-id MYAPP-CASE-2 --relationship parentrelated delete
Remove a related case link
Usage
bash
pega related delete <caseId> [flags]Source endpoint: DELETE /cases/{caseID}/related_cases/{related_caseID} — view command source
Arguments
| Argument | Required | Description |
|---|---|---|
caseId | Yes | Case ID |
Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--format | option | No | json | Output format (json, compact, yaml, table) |
--fields | option | No | Comma-separated top-level fields to include in output | |
--dry-run | boolean | No | Print HTTP request details and exit without executing | |
--quiet | boolean | No | Suppress all stderr progress/warning output | |
--verbose | boolean | No | Emit full HTTP request/response details to stderr | |
--no-cache | boolean | No | Bypass token file cache; perform fresh OAuth exchange | |
--profile | option | No | default | Named config profile |
--related-case-id | option | Yes | Related case ID |
Examples
sh
pega related delete MYAPP-CASE-1 --related-case-id MYAPP-CASE-2related list
List all related cases
Usage
bash
pega related list <caseId> [flags]Source endpoint: GET /cases/{caseID}/related_cases — view command source
Arguments
| Argument | Required | Description |
|---|---|---|
caseId | Yes | Case ID |
Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--format | option | No | json | Output format (json, compact, yaml, table) |
--fields | option | No | Comma-separated top-level fields to include in output | |
--dry-run | boolean | No | Print HTTP request details and exit without executing | |
--quiet | boolean | No | Suppress all stderr progress/warning output | |
--verbose | boolean | No | Emit full HTTP request/response details to stderr | |
--no-cache | boolean | No | Bypass token file cache; perform fresh OAuth exchange | |
--profile | option | No | default | Named config profile |
Examples
sh
pega related list MYAPP-CASE-1