@uipath/case-tool 0.1.7 → 0.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +109 -2
- package/dist/index.js +6 -257657
- package/dist/tool.js +30577 -75478
- package/package.json +11 -11
package/README.md
CHANGED
|
@@ -34,7 +34,7 @@ uip case registry pull [options]
|
|
|
34
34
|
| :--- | :--- |
|
|
35
35
|
| `-f, --force` | Force refresh, ignore local cache |
|
|
36
36
|
| `-s, --solutionId <id>` | Include entities from a specific solution |
|
|
37
|
-
|
|
|
37
|
+
| `--output <type>` | Output format: `json`, `table`, `yaml`, `plain` (default: `json`) |
|
|
38
38
|
|
|
39
39
|
**Resource types pulled:**
|
|
40
40
|
|
|
@@ -80,13 +80,120 @@ uip case registry list [options]
|
|
|
80
80
|
|
|
81
81
|
| Option | Description |
|
|
82
82
|
| :--- | :--- |
|
|
83
|
-
|
|
|
83
|
+
| `--output <type>` | Output format: `json`, `table`, `yaml`, `plain` (default: `json`) |
|
|
84
84
|
| `-q, --quiet` | Quiet mode, no output |
|
|
85
85
|
|
|
86
86
|
If no cache exists, the command automatically fetches live data from the platform.
|
|
87
87
|
|
|
88
88
|
---
|
|
89
89
|
|
|
90
|
+
### `validate`
|
|
91
|
+
|
|
92
|
+
Validate a case management definition JSON file against all case management rules (structure, stages, edges, conditions).
|
|
93
|
+
|
|
94
|
+
```bash
|
|
95
|
+
uip case validate <file>
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
Returns a list of errors and warnings. Exits with code `1` if any errors are found.
|
|
99
|
+
|
|
100
|
+
---
|
|
101
|
+
|
|
102
|
+
### `cases`
|
|
103
|
+
|
|
104
|
+
Manage local case management definition JSON files.
|
|
105
|
+
|
|
106
|
+
```bash
|
|
107
|
+
uip case cases <action>
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
| Subcommand | Description |
|
|
111
|
+
| :--- | :--- |
|
|
112
|
+
| `add` | Create a new case management definition JSON file |
|
|
113
|
+
| `edit <file>` | Edit root-level properties of an existing definition |
|
|
114
|
+
| `validate <file>` | Validate a definition file (alias for `uip case validate`) |
|
|
115
|
+
|
|
116
|
+
**`cases add` options:**
|
|
117
|
+
|
|
118
|
+
| Option | Description |
|
|
119
|
+
| :--- | :--- |
|
|
120
|
+
| `-n, --name <name>` | Name of the case management definition *(required)* |
|
|
121
|
+
| `-f, --file <path>` | Output path for the new JSON file *(required)* |
|
|
122
|
+
| `--case-identifier <id>` | Case identifier string (defaults to name) |
|
|
123
|
+
| `--identifier-type <type>` | `constant` or `external` (default: `constant`) |
|
|
124
|
+
| `--case-app-enabled` | Enable the case app for this definition |
|
|
125
|
+
|
|
126
|
+
**`cases edit` options:**
|
|
127
|
+
|
|
128
|
+
| Option | Description |
|
|
129
|
+
| :--- | :--- |
|
|
130
|
+
| `-n, --name <name>` | New name |
|
|
131
|
+
| `--case-identifier <id>` | New case identifier |
|
|
132
|
+
| `--identifier-type <type>` | New identifier type |
|
|
133
|
+
| `--case-app-enabled` | Enable the case app |
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
### `stages`
|
|
138
|
+
|
|
139
|
+
Manage stage nodes within a case management definition JSON file.
|
|
140
|
+
|
|
141
|
+
```bash
|
|
142
|
+
uip case stages <action> <file> [stage-id]
|
|
143
|
+
```
|
|
144
|
+
|
|
145
|
+
| Subcommand | Description |
|
|
146
|
+
| :--- | :--- |
|
|
147
|
+
| `add <file>` | Add a new stage node |
|
|
148
|
+
| `edit <file> <stage-id>` | Edit an existing stage's label |
|
|
149
|
+
| `get <file> <stage-id>` | Print a stage and its connected edges |
|
|
150
|
+
| `remove <file> <stage-id>` | Remove a stage and its connected edges |
|
|
151
|
+
|
|
152
|
+
**`stages add` options:**
|
|
153
|
+
|
|
154
|
+
| Option | Description |
|
|
155
|
+
| :--- | :--- |
|
|
156
|
+
| `-l, --label <label>` | Display label for the stage |
|
|
157
|
+
| `-t, --type <type>` | `stage`, `exception`, or `trigger` (default: `stage`) |
|
|
158
|
+
|
|
159
|
+
---
|
|
160
|
+
|
|
161
|
+
### `edges`
|
|
162
|
+
|
|
163
|
+
Manage edges within a case management definition JSON file.
|
|
164
|
+
|
|
165
|
+
```bash
|
|
166
|
+
uip case edges <action> <file> [edge-id]
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
| Subcommand | Description |
|
|
170
|
+
| :--- | :--- |
|
|
171
|
+
| `add <file>` | Add a new edge between two nodes |
|
|
172
|
+
| `edit <file> <edge-id>` | Edit an existing edge |
|
|
173
|
+
| `get <file> <edge-id>` | Print an edge |
|
|
174
|
+
| `remove <file> <edge-id>` | Remove an edge |
|
|
175
|
+
| `validate <file> <edge-id>` | Validate a single edge in context |
|
|
176
|
+
| `list <file>` | List all edges in a definition |
|
|
177
|
+
|
|
178
|
+
**`edges add` options:**
|
|
179
|
+
|
|
180
|
+
| Option | Description |
|
|
181
|
+
| :--- | :--- |
|
|
182
|
+
| `-s, --source <id>` | Source stage or trigger ID *(required)* |
|
|
183
|
+
| `-t, --target <id>` | Target stage ID *(required)* |
|
|
184
|
+
| `-l, --label <label>` | Display label |
|
|
185
|
+
| `--source-handle <dir>` | `right`, `left`, `top`, `bottom` (default: `right`) |
|
|
186
|
+
| `--target-handle <dir>` | `right`, `left`, `top`, `bottom` (default: `left`) |
|
|
187
|
+
| `--z-index <number>` | Z-index layer for rendering order |
|
|
188
|
+
|
|
189
|
+
Edge type is inferred from the source node: Trigger → `TriggerEdge`, Stage → `Edge`.
|
|
190
|
+
|
|
191
|
+
**`edges validate` checks:**
|
|
192
|
+
- Source and target nodes exist
|
|
193
|
+
- No duplicate conditions on edges from the same source node
|
|
194
|
+
|
|
195
|
+
---
|
|
196
|
+
|
|
90
197
|
## Local Cache
|
|
91
198
|
|
|
92
199
|
Resources are stored in `~/.uipcli/case-resources/` as JSON files:
|