Skip to content
Learn
Presentations P-00000 to P-00999
What runs on your tenant when nobody presses a button

What runs on your tenant when nobody presses a button

Which automation runs on your tenant, and how to switch one on · presentation 1 of 2 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Which automation runs on your tenant, and how to switch one on · presentation 1 of 2

What runs on your tenant when nobody presses a button

You can tell the work a button starts from the work a clock starts…

Two kinds of automation

Step 1 — Separate the button from the work it starts

You will know why the screen comes back before the work is done.

What this step names
  1. When you finalise a sales invoice at GS-KV-01
  2. BigLedger writes one row into your tenant's job queue and hands it…
  3. Your screen returns at once

Step 2 — Tell a subscription from a clock

You can say which of two kinds of automation you are looking at.

Screen capture pending the demo tenant

Scheduler applet, the listing

Step 3 — Know which clocks came with your tenant

You will know where your clocks came from.

What this step names
  1. When a tenant is created
  2. BigLedger inserts a set of default clocks
  3. All active: the e-invoice submission and status passes every ten minutes
  4. The consolidation pass every twenty
  5. The stock-balance queue every fifteen
  6. The deposit rollover and the monthly aging snapshot on the first of…

Step 4 — Read what the listing says, and what it does not

You can read what each clock says about itself.

  • Open the Scheduler applet
  • Read that date carefully
Screen capture pending the demo tenant

Scheduler applet, the listing, with the Status and Last Run Date columns

Step 5 — Check the four gates before you wait for a job

You will stop waiting for jobs that cannot come.

Screen capture pending the demo tenant

Scheduler applet, a new row, the Select Processor picker

How you know it worked

Step 6 — Check that one document's jobs happened

You can prove, for one document, that the jobs behind it ran.

  • Open a finalised purchase invoice from GS-PEN-01 and its Posting tab
Screen capture pending the demo tenant

Purchase Invoice, the Posting tab with its five statuses

Step 7 — Make the checks nothing else will make

You will know which checks are yours, because no screen will make them.

Where this step sits
    flowchart TD
  s1["1. Separate the button from the work…"]
  s2["2. Tell a subscription from a clock"]
  s3["3. Know which clocks came with your…"]
  s4["4. Read what the listing says…"]
  s5["5. Check the four gates before you…"]
  s6["6. Check that one document's jobs happened"]
  s7["7. Make the checks nothing else will…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s7 here;

NarrationSlide 1 of 10

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.

Last updated on
The other company's copy: what it carries, when it posts, and keeping both books in step — transcriptWhat runs on your tenant when nobody presses a button — transcript