epismo 1.14.0 → 1.16.0
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 +4 -1
- package/npm/vendor/darwin-amd64/epismo +0 -0
- package/npm/vendor/darwin-arm64/epismo +0 -0
- package/npm/vendor/linux-amd64/epismo +0 -0
- package/npm/vendor/linux-arm64/epismo +0 -0
- package/npm/vendor/windows-amd64/epismo.exe +0 -0
- package/npm/vendor/windows-arm64/epismo.exe +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -67,9 +67,10 @@ Use `visibility` and explicit editors instead of a raw ACL:
|
|
|
67
67
|
```sh
|
|
68
68
|
epismo playbook access get PLAYBOOK_ID
|
|
69
69
|
epismo playbook access set PLAYBOOK_ID --visibility public --editors USER_ID,TEAM_ID
|
|
70
|
+
epismo playbook owner PLAYBOOK_ID --owner-id WORKSPACE_OR_USER_ID
|
|
70
71
|
```
|
|
71
72
|
|
|
72
|
-
`public` permits published reads only. Editors can read and edit Playbook content; the owner is implicit and is not included in `--editors`. Owner managers, including Workspace Owners and Admins for a Workspace-owned Playbook, manage access and archive Playbooks or historical Versions.
|
|
73
|
+
`public` permits published reads only. Editors can read and edit Playbook content; the owner is implicit and is not included in `--editors`. Owner managers, including Workspace Owners and Admins for a Workspace-owned Playbook, manage access and archive Playbooks or historical Versions. `playbook owner` moves ownership from a User to a Workspace, or from a Workspace to that Workspace's Owner or the Playbook creator.
|
|
73
74
|
|
|
74
75
|
## Cases and handoffs
|
|
75
76
|
|
|
@@ -78,6 +79,8 @@ Start a Case, append timeline Records, connect dependent workflows, and explore
|
|
|
78
79
|
```sh
|
|
79
80
|
epismo case start --title "Customer Onboarding"
|
|
80
81
|
epismo case record append CASE_ID --kind result --content "Completed setup"
|
|
82
|
+
epismo case record update RECORD_ID --content "Revised setup notes"
|
|
83
|
+
epismo case record delete RECORD_ID
|
|
81
84
|
epismo case handoff FIRST_CASE_ID --to-case-id SECOND_CASE_ID
|
|
82
85
|
epismo case handoff graph CASE_ID --scope connected
|
|
83
86
|
epismo case record list CASE_ID --scope ancestors
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|