@lotics/cli 0.321.126 → 0.321.128
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/dist/src/cli.js +11 -3
- package/docs/build.md +1 -1
- package/package.json +1 -1
package/docs/build.md
CHANGED
|
@@ -8,7 +8,7 @@ Before the first table, `set_workspace` states the business's `timezone` (how ev
|
|
|
8
8
|
|
|
9
9
|
## 0. The day's work
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Name the jobs done most often and first in the day, the ones the request names and the rest a business of its kind does daily (what comes in, what goes out, what is counted or billed), and the exceptions each meets (the common ones: going back a step, correcting a locked record, work in parts or split, data late or out of order, a cancel, closing only once the work before is done; build those this work meets, not the list). Build those jobs first, each from the screen it starts on, from what you have and, where it is silent, from how this kind of business runs; name each assumption in your report for the owner to change. Who does a job matters where the work says so: a step another person approves, data not everyone may see, and who each app is given to (`get_workspace` kind `member` lists the organization's people, not who does what here). Whether to ask the person who asked is your call; three questions usually settle a workspace: what work happens most often, the papers and lists the business keeps (attached as files), and what must never go wrong.
|
|
12
12
|
|
|
13
13
|
## 1. Tables and their checks: `set_tables`
|
|
14
14
|
|