@lotics/cli 0.321.17 → 0.321.19

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/docs/workflows.md CHANGED
@@ -895,7 +895,7 @@ write on that row; reads are real and nothing is written.
895
895
 
896
896
  | part of the header | what it holds |
897
897
  |---|---|
898
- | `type` | the write it follows: `create`, `update` or `delete` |
898
+ | `type` | the write it follows: `create`, `update` or `delete`; a `delete` workflow runs once, when the row is deleted; deleting it for good from the trash runs none |
899
899
  | `table` | the table's alias |
900
900
  | `when` | optional expression over `record`, `prev_record` and `changes`; the workflow runs only after a write where it is truthy |
901
901
  | `changed` | optional, with `type: "update"`: field aliases; the workflow runs only after an update that changes any one of them |
@@ -33,7 +33,7 @@ A record read carries `comment_count` (a workflow body gets it when it reads it)
33
33
 
34
34
  ## Deleting and restoring
35
35
 
36
- A keyed entry is removed by `null`: a field, check, view, option, instruction, query alias, a member or a group. A resource addressed by its id is deleted with `delete: true` and brought back with `restore: true`, beside its id: a table in a `set_tables` item (`{ table_id, delete: true }`; `cascade` deletes the links that point at the deleted tables and is refused unless the call deletes; `force` goes with a patch that loses stored values and is refused on a call that only deletes or restores), a knowledge doc (`set_knowledge` with `knowledge_doc_id`), a template (`set_template` with `template_id`), an app (`set_app` with `app_id`) and a workflow (`set_workflow` with `workflow_id`; a deletion only). Records are deleted by `delete_records` and brought back by `update_records` with `restore: true` and `record_ids` or `filters`: the rows their delete took come back with them, all or none, and a row needing its link stays deleted while the row it names does. `delete` takes no other key. A call that deletes asks for approval; one that does not never does.
36
+ A keyed entry is removed by `null`: a field, check, view, option, instruction, query alias, a member or a group. A resource addressed by its id is deleted with `delete: true` and brought back with `restore: true`, beside its id: a table in a `set_tables` item (`{ table_id, delete: true }`; `cascade` deletes the links that point at the deleted tables and is refused unless the call deletes; `force` goes with a patch that loses stored values and is refused on a call that only deletes or restores), a knowledge doc (`set_knowledge` with `knowledge_doc_id`), a template (`set_template` with `template_id`), an app (`set_app` with `app_id`) and a workflow (`set_workflow` with `workflow_id`; a deletion only). Records are deleted by `delete_records` and removed for good, once in the trash, by `delete_records` with `permanent: true` and `record_ids` or `filters` (an organization admin's own credential alone, never inside a workflow; the records and their comments go, their audit history stays), and brought back by `update_records` with `restore: true` and `record_ids` or `filters`: the rows their delete took come back with them, all or none, and a row needing its link stays deleted while the row it names does. `delete` takes no other key. A call that deletes asks for approval; one that does not never does.
37
37
 
38
38
  ## Locking and changing a locked record
39
39
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.321.17",
3
+ "version": "0.321.19",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {