PPaT Wiki
DocumentationPathwayForumBlogContact
Week streakFOUNDATION0 badges
Language: English
  • English
  • Nederlands
  • Français
  • Deutsch
  • Lea faka-Tonga
  • Te reo Māori
  • မြန်မာ (Burmese)
Ask the community

Your PaT Pathway

0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User
  • Company Structure: adding a new user
  • Company Structure: customer companies
  • Company Structure: departments, job titles and roles
  • Company Structure: modules for a site or a country
  • Company Structure: process categories
  • Connections: linking PaT to Microsoft 365
  • Forms - API Integration
  • How to create a campaign for the PaT Lite training portal
  • How to edit an existing Bulletin Board Post
  • How to set up your SD Map
  • LMS Feedback: learner ratings and comments
  • LMS Metrics - If you can't measure it, you can't manage it
  • Manage users
  • Pacing recertifications and escalations
  • PaT Business Unit Template Overview
  • SD Workflows - Multi Submit
  • SD Workflows - Workflow Settings
  • System Activity: escalations, logins, emails and more
  • System Config: company settings
  • The org chart
  • Add any Image as a Section Header Icon
  • Assigning an SD to a new parent
  • C2E Attachments
  • Chat reminder
  • Chat to email to chat
  • Chat to SD
  • Chat to task to project
  • Comprehension Audits
  • Customer-specific training: how it works
  • Different Form Uses
  • Docked Chats
  • Docking SDs and Updating Images
  • Email to BFF
  • Email to chat to email – non PaT users
  • Embedding live data in an SD (graphs and spreadsheets)
  • Embedding SDs in SDs
  • Evidential audits: completing one
  • Filing and retrieving SDs
  • Form Wall
  • Health and safety templates
  • How PaT Manages Inactive Users
  • How SD chats work with SD Members and External Users
  • How to unlock a module for a staff member
  • Info Icons
  • Inline chats
  • Invite Attendees
  • LMS Architecture
  • Moving Section Headers
  • Multi-Tasks
  • PaT AI
  • Pop-Out Chat Feature
  • Recurring tasks: create and edit
  • Running Meetings with SDs
  • Safe Walks
  • SD Element Categorisation
  • SD Form Responses: finding and exporting form responses
  • SD Owner Functions
  • SD Task wall view
  • Share and record your screen
  • Task Integrity: what it is and why it drops
  • Track Engagement
  • Using SDs as a report or meeting minutes app
  • Video rooms: guests joining and asking to record
  • Activity Notifications
  • Add members and set permissions
  • AI Summary: a quick summary of an SD
  • Capture and Manage Accidents
  • Capture and Manage Hazards
  • Chat to task
  • Chat Wall
  • Company wiki: searching your company's own modules
  • Contextual Communication
  • Convert a Note to a Task
  • Create a new SD
  • Create a Task
  • Critical Chrome Extensions
  • Document Store: shared links, your folders and favourites
  • Fast Notes
  • Getting help: the PaT Helpdesk
  • Global Search
  • Group Chats
  • How to embed Outlook onto your PaT
  • How to resize your browser to best view PaT
  • How to use the PaT Lite training portal
  • Insert links
  • Module Learning - Desktop
  • Module Learning - Mobile
  • My Profile
  • Newbie PaT Intro – Chats and SDs
  • Notes
  • Out Of Office: turning it on, and the calendar on your Task Wall
  • Outlook 2FA Issue
  • PaT Chat Overview
  • PaT Mobile App – Overview
  • PaT service status: the status page, status alerts and status notices
  • PaT Wiki: finding your way around
  • PaT Wiki: searching, the AI answer and rating it
  • Preview, download and share files
  • Publish a Bulletin Board Post
  • Reading an SD in another language
  • Release-note alerts: a Sys Bot chat when PaT's release notes change
  • SD Elements
  • SD Main page useful features
  • SD Overview
  • Section Headers
  • Security measures for multiple users on a device
  • Share Feedback
  • Signing in to PaT and resetting your password
  • Signing in with MFA: the second step
  • Task Management
  • Task Management System
  • Task Wall
  • The connection icon on your PaT desktop
  • Traffic light progress
  • Upload file attachments
  • Video calls on the mobile app
  • AI Playbook: checking for other tickets with the same number
  • Auto Escalation
  • Build a reporting system
  • Calculated fields and calculated columns
  • Charts: options for lines, bars, axes and single values
  • Chat Management - Pro Tips
  • Conditional Formatting
  • Configuring a UDF: columns and calculated columns
  • Configuring a UDF: filters, grouping and endpoint details
  • Customer-specific training: setting it up
  • Data sources: stage filters, dynamic dates and page values
  • Endpoint Manager: finding endpoints and building your own UDF
  • Form builder: field types
  • Form Builder: layout at each screen size
  • Form Builder: tools and shortcuts
  • Form buttons, PDFs and what happens after submit
  • Form fields: defaults, read-only and other settings
  • Form Test Mode
  • Forms - Extract Data (the AI form builder)
  • Grids linked to a reporting SD: history charts and review comments
  • Grids: columns, formats and filters
  • Grids: conditional formatting
  • Grids: flatten and transpose data
  • Grids: rows, default values and editing rules
  • How managers can turn on OOF for their staff
  • How to build modules in the Module publisher
  • How to create module comprehension audits
  • How to create module evidential audits
  • How to create module quizzes
  • How to embed an SD into the LMS
  • How to make form templates live for everyone to use
  • How to upload form elements to an SD
  • How to use the PAR SD
  • Live H&S Reporting
  • Mastering the Business Strategy Template
  • Module Admin: finding and managing modules
  • Module Completion Notification Setup
  • Module Publisher Content Options
  • PaT SD Map Overview
  • PaT SD Map Presentation
  • PaT SD Templates Overview
  • Playbook Admin: the tickets behind each Quality and Cost category
  • Playbook Admin: when your shadow run is ready to review
  • Playbook editor: adding a portal lookup step
  • Playbook editor: adding a step that cancels an order
  • Pure Forms
  • Required fields, validation and containers
  • Rich text, file uploads and speech to text
  • SD Dashboard: building a dashboard
  • SD Forms
  • SD Security Settings
  • SD Template Helper Functions
  • Stacked views, flip cards, tabs and stages
  • Strategy System
  • Throttling
  • Using Chat to SD to go from being a good manager to a great one
  • Using SDs as the LMS Document
  • PaT Lite: Key aspects of PaT you need to understand
  • What is PaT and why it matters
  • PaT Lite: Chat to Task
  • PaT Lite: Introducing Strategy Documents
  • PaT Lite: Core Philosophy - Standards and Tactical Execution
  • PaT Lite: Intelligent tools that think with you
  • PaT Lite: The Future of business is Culture
  • Security
  • Integrations
0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User
  1. Documentation
  2. Foundation
  3. PaT service status: the status page, status alerts and status notices

PaT service status: the status page, status alerts and status notices

Summary PaT's service status page, at wiki.peopleandtasks.com/status, shows whether PaT is working, whether every chat, form, email and attachment got through, and how the outside services PaT…

Check yourself

Checking your PaT sign-in…

How To

On this page
  • Opening the status page
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • The banner at the top
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Our servers
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Every message processed
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Connected services
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Step 9
  • Step 10
  • Step 11
  • Step 12
  • Step 13
  • Updates
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Switching status alerts on
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • What the alerts send you
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Switching status alerts off
  • Step 1
  • Step 2
  • Step 3
  • For PaT super users: posting a status notice
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Purpose / Intent of the Module
  • Header One

Summary PaT's service status page, at wiki.peopleandtasks.com/status, shows whether PaT is working, whether every chat, form, email and attachment got through, and how the outside services PaT relies on are doing. PaT checks its servers every 5 minutes, day and night. Switch on status alerts, and Sys Bot sends you a chat when something affects PaT's service, and again as it is fixed. The PaT team can also post a notice on the page, for example about planned maintenance.

Opening the status page

Step 1

Open the PaT Wiki at wiki.peopleandtasks.com. At the bottom of any page, under Support in the footer, click Service status. You can also go straight to wiki.peopleandtasks.com/status.

Step 2

The page is called PaT service status, and only people signed in to PaT can see it. If you are not signed in, the page shows its title and Sign in to PaT to see the service status. Click Sign in to PaT, sign in in the tab that opens, then come back to the status page. If it still asks you to sign in, refresh it.

Step 3

The page shows PaT's latest checks a moment after it opens, and refreshes them every minute.

Step 4

Times are shown in your own time zone, and the line under the banner names it, for example Times are in your time zone: New Zealand Daylight Time. The page is in English: if you read the wiki in another language, a note at the top says so.

The banner at the top

Step 1

The banner near the top sums up PaT right now, and Last checked beside it gives the time of the newest check. When everything is fine, it says All servers working, often followed by no chats, forms, emails or attachments missed today.

Step 2

If something was missed today, the banner still says All servers working, then what was missed, for example 1 chat missed today.

Step 3

If a server is not answering, the banner names it, for example PaT web app not answering.

Step 4

If the page cannot vouch for a server right now, the banner turns grey and says which, for example No recent check of Cloud services. If PaT's checks stop reporting for more than 15 minutes, it says Status data is out of date, with the time of the last report.

Our servers

Step 1

Under Our servers are four rows: PaT web app (www.peopleandtasks.com), PaT agents (the server PaT's AI agents run on), Database (where your SDs, chats and forms are stored) and Cloud services (chat, forms, email and the PaT agents' tools, checked from outside the cloud).

Step 2

The label at the right of each row says how that server is now: Working, Not answering, No recent check, or No data yet if it has not been measured yet.

Step 3

Each row has one bar per day, with today on the right: the last 30 days on a phone, and up to 90 on a wider screen. Under the bars, the middle line gives the uptime, for example 99.93% up over 90 days.

Step 4

Below the day bars, Today, by hour has one small bar for each hour of today.

Step 5

The key under the rows says what each colour means: green, Every check passed; orange, One check missed (down up to 5 min); red, More than one missed; grey, No data; white, Not yet today. On a computer, point at a bar to see its checks.

Every message processed

Step 1

Under Every message processed are four rows: Chats, Form submissions, Emails into PaT and Email attachments.

Step 2

If PaT's first try at handling one fails, PaT tries again automatically. A miss is one where the second try failed too. One that was put right on its second try counts as processed.

Step 3

The label at the right of each row says how today is going: Nothing missed today, One missed today, or how many were missed. On Emails into PaT, once a whole hour has passed with no emails coming in, the label turns grey and says since when, for example No emails since 6 am, or No emails since Wed, 11 Nov, 4 pm if that was not today.

Step 4

Under the name, Today so far gives today's counts, for example Today so far: 1 put right on a second try · 0 missed. Yesterday gives yesterday's.

Step 5

The bars work as they do for the servers. In the key: green, Nothing missed; orange, One missed; red, More than one missed; grey, No data. On Emails into PaT, an hour in which no emails came in is grey too, and so is a whole day with none: on a computer, pointing at it says no emails. Pointing at a day that had emails in only some of its hours also says how many, for example (3 of 13 hours with emails).

Connected services

Step 1

Connected services comes after Every message processed. It lists the outside services PaT relies on, one row each: AI answers, Live updates on screen, Phone notifications, Incoming email (Microsoft Outlook), Outgoing email (SendGrid), PDF documents, Xero link, Parcel tracking, Calendar (Google), Calendar (Outlook), Voice and Video meetings.

Step 2

Under each name, a short line says what the service does, for example The AI behind PaT's answers, summaries and agents.

Step 3

Under the section's introduction, one line sums up the rows, for example 8 working · Not used recently: PDF documents · Not connected: Calendar (Google) and Calendar (Outlook) · Not yet reporting: Voice. It counts the rows that are working and names every other row.

Step 4

The banner at the top is about PaT's servers only. A problem with a connected service shows on its own row and in the line under Connected services, not in the banner.

Step 5

The label at the right of each row says how the service is now. Working or No failures found means all is well. Not working, Failures found or Problem reported means something is wrong.

Step 6

A grey label means there is nothing to go by right now, for example Not used recently (no one has used it in the last hour or so), Not connected (PaT is not linked to that service) or Not yet reporting (PaT does not check it yet).

Step 7

Under the short line, another line says how the row is checked. Checked every 15 minutes or Checked every hour means PaT tests the service itself, on that schedule.

Step 8

Failures found in PaT's own records means PaT looks through its own records for failures. From real use means PaT counts each real use and each failure, for example PDFs made.

Step 9

As reported by OneSignal, or As reported by Whereby, shows what that supplier says about its own service, followed by the supplier's own words, for example Push: operational, API: operational. It does not show whether each PaT message got through.

Step 10

The two email rows also count the failures PaT found itself. Incoming email (Microsoft Outlook) says As reported by Microsoft 365 and PaT's own records, and Outgoing email (SendGrid) says As reported by SendGrid and PaT's own records. The two are kept apart: Problem reported comes only from the supplier, and Failures found only from PaT's own records. A bar's colour counts both together. On a computer, pointing at a bar names what each one found, for example Microsoft 365: 12 checks, all passed · PaT's own records: 1 failure found. While PaT's own records are not reporting, the row says only As reported by Microsoft 365, or As reported by SendGrid.

Step 11

A grey row, such as Calendar (Google), has no such line. The words under its bars say why instead, for example Not connected.

Step 12

Each row has a day bar and Today, by hour, as for the servers. The line under the day bars sums up the days, for example 100% up over 90 days, 89 of 90 days with no failures found, or Not used in 90 days. A new row counts only the hours or days measured so far, for example No failures found in the 18 hours measured.

Step 13

The key under the rows says what each colour means: green, No failures; orange, One failure; red, More than one; grey, No data, not used, or not connected; white, Not yet today. On a computer, point at a bar to see what happened in it, for example 4 checks, all passed.

Updates

Step 1

Under Updates, PaT posts when something affects you, and again as it is fixed. When all is well, it says Nothing is being worked on right now.

Step 2

PaT opens an update by itself when the PaT web app or the Database misses two checks in a row, about 10 minutes. It adds a Resolved step when that server answers again.

Step 3

Each update shows its title, for example PaT (www.peopleandtasks.com) is not responding, what it affects, and its steps, newest first. Each step has a stage (Investigating, Identified, Monitoring or Resolved), its time, and what happened.

Step 4

An open update says Ongoing, since and the time it started. Once it is resolved, it moves to Past updates, which keeps the last 90 days and says when each one ended and how long it lasted, for example Yesterday, for 12 minutes.

Step 5

The PaT team can also post a notice under Updates, for example about planned maintenance. It shows the same way, with its own steps.

Step 6

How we measure, at the bottom of the page, explains how the checks and the counts work.

Switching status alerts on

Step 1

Near the top of the status page, beside Want to know when something changes?, click Get status alerts in PaT. The Status alerts page opens in PaT, in a new browser tab.

Step 2

If you are not signed in to PaT, the page says Please sign in to PaT, then open this page again. Sign in to PaT, then open the page again.

Step 3

The page says Status alerts are off for you, or Status alerts are on for you.

Step 4

Click Send me status alerts. When your setting is saved, the page says Done, and the button changes to Stop the status alerts.

Step 5

The first time you switch them on, Sys Bot starts a new chat with you, called PaT service status for (your name). Its first message says Service status alerts are on, with a See the service status button.

Step 6

If Sys Bot cannot start the chat straight away, the page says Your PaT service status chat starts with the next update. The alerts are still on.

Step 7

If the page says PaT could not save that just now, wait a minute and click the button again.

What the alerts send you

Step 1

Sys Bot posts in your PaT service status chat each time an update on the status page gets a new step: when it opens, as it changes, and when it is resolved. You get each step once.

Step 2

Each message starts with the stage and the update's title, for example Investigating: PaT (www.peopleandtasks.com) is not responding. Then it says what has happened, and what it affects.

Step 3

Click See the service status in the message to open the status page.

Step 4

You are alerted when the PaT web app or the Database stops answering for two checks in a row (about 10 minutes), when it answers again, and for each step of a notice the PaT team posts. A single missed chat, form, email or attachment shows on the page, but sends no alert.

Switching status alerts off

Step 1

Open the Status alerts page: click Status alerts in the last line of any of Sys Bot's messages, or click Get status alerts in PaT on the status page.

Step 2

Click Stop the status alerts. The page says Done, and Sys Bot sends you no more status alerts.

Step 3

Your earlier alerts stay in their chat. To get alerts again later, click Send me status alerts: new updates then appear in the same chat.

For PaT super users: posting a status notice

Step 1

This part is for the PaT team. Only PaT admins can post a notice: anyone else who opens the Status notices page is told Only PaT admins can post status notices.

Step 2

Sign in to PaT, then open the PaT Wiki. Click Admin in the top menu, then click Post a status notice at the top of the Admin page. The Status notices page opens in PaT, in a new browser tab.

Step 3

To open a notice, fill in New notice: a Title of up to 160 characters, for example Planned maintenance on Sunday; tick each area under What it affects, such as PaT web app or Database; pick a Stage (Identified, Investigating or Monitoring); and write What people should know, up to 500 characters.

Step 4

Click Post the notice. The page says Posted. It is on the status page now. The notice shows under Updates at once, and everyone with status alerts on gets it as a Sys Bot chat.

Step 5

To add a step, find the notice under Open notices. Under Next step, pick the stage, write what has changed, then click Add this step.

Step 6

To resolve the notice, write how it ended, for example All done, then click Resolve with these words. The page says Resolved. The status page shows it as resolved now, and the notice moves to Resolved in the last 7 days.

Step 7

A notice is public, and it goes to everyone with status alerts on, so write it in plain words, with no names or customer details. If a box is empty, the page says what to write first.

Purpose / Intent of the Module

A brief description of what this module is about

Header One

Ready? Back to the quiz

Rate this page

Checking your PaT sign-in…

PreviousPaT Mobile App – OverviewNext PaT Wiki: finding your way around

On this page

  • Opening the status page
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • The banner at the top
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Our servers
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Every message processed
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Connected services
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Step 9
  • Step 10
  • Step 11
  • Step 12
  • Step 13
  • Updates
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Switching status alerts on
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • What the alerts send you
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Switching status alerts off
  • Step 1
  • Step 2
  • Step 3
  • For PaT super users: posting a status notice
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Purpose / Intent of the Module
  • Header One
PPaT Wiki

Documentation, knowledge base and community support for People and Tasks.

Documentation

  • Getting started
  • Core concepts
  • Integrations
  • API reference Coming soon

Support

  • Knowledge base
  • Release notes
  • Community forum
  • Contact us
  • Service status

Company

  • PaT
  • Blog
  • Terms
  • Privacy

© People and Tasks. All rights reserved.