Playbook Admin: when your shadow run is ready to review
Summary A shadow run follows a version of a category's workflow on a real ticket and records every step. Tries and replays never post, send or change anything. A run can take a while to finish, so…
Check yourself
Checking your PaT sign-in…
How To
On this page
Summary A shadow run follows a version of a category's workflow on a real ticket and records every step. Tries and replays never post, send or change anything. A run can take a while to finish, so Playbook Admin keeps track of the runs you start yourself: the Taxonomy tab marks their categories while they are going and once they are ready to review, counts them at the top of the tab, and a pop-up tells you when one finishes while the page is open.
Starting a shadow run
Step 1
Open Playbook Admin for your ticket form and click the Taxonomy tab.
Step 2
Find the category you want to test. Click its cell in the Workflow column, at the right of the row, to open the category's workflow under the row.
Step 3
Click Shadow runs, in the row of buttons above the workflow's diagram. The Runs tab opens beside the diagram.
Step 4
To try the version on one ticket, choose one of the category's tickets in the list, or paste a PaT link to one of the form's tickets, then click Try it. The line beside the button says how many tries you have used today.
Step 5
If you can approve the category's workflows, you also see Replay. Choose how many of the category's latest finished tickets to run the version over, then click Replay. Replays wait from 8:30 to 10:00 NZ, while the daily report runs.
Step 6
Each run you start joins the list under these boxes, with its status, such as Waiting, Running or Done.
While your run is going
Step 1
You do not need to stay on the Runs tab. Playbook Admin checks on your runs every 15 seconds while the page is open, so you can carry on with other categories or tabs.
Step 2
On the Taxonomy tab, the category's Workflow cell shows Running, in blue, while a run you started there is still going. With more than one, it shows how many, such as 3 running.
Step 3
If you switch to another browser tab, the checks pause. Playbook Admin checks again as soon as you come back.
Step 4
Only the runs you started yourself are marked. Runs started by other people, and the runs that start by themselves when a new ticket arrives, are not.
When your run is ready to review
Step 1
When your run finishes, the chip in the category's Workflow cell changes to Run ready to review, in green. With more than one, it shows how many, such as 2 runs ready to review.
Step 2
A run that failed is counted as ready to review as well, as it is worth a look.
Step 3
In the Workflows Live box at the top of the tab, a button shows how many of your runs are ready, such as 1 run ready to review. Click it to show only the categories with a run ready, with their groups opened.
Step 4
You can also tick Runs ready, with the other tick boxes beside the search box above the table. The number beside it is how many categories have a run ready.
The pop-up
Step 1
If one of your runs finishes while Playbook Admin is open, a pop-up says Run ready to review, whichever tab you are on. It names the run's category and its ticket.
Step 2
Click Open in the pop-up. Playbook Admin opens the run on its category's Runs tab.
Step 3
When several of your runs finish at the same time, one pop-up lists up to three of them, each with its own Open button, and says how many more are marked in their categories.
Step 4
The pop-up closes by itself after 20 seconds. Runs that were already ready when you opened the page get no pop-up: their chips and the count show them instead.
Clearing a run from your list
Step 1
Open the run on the Runs tab to review it. Once you have opened it, its chip and its place in the count go straight away.
Step 2
A run also stops being ready to review as soon as anyone marks it Right, Partly or Wrong.
Step 3
Only runs started in the last 14 days are shown.
Step 4
Start a replay, then carry on with other work in Playbook Admin. The pop-up tells you when its runs are ready, and the Runs ready tick box finds them again later.
Purpose / Intent of the Module
A brief description of what this module is about
Header One
Rate this page
Checking your PaT sign-in…