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. Advanced
  3. Playbook editor: adding a step that cancels an order

Playbook editor: adding a step that cancels an order

Summary In the Playbook editor, the step Cancel the order in the portal comes after a conclusion. Once a person approves the run's card, it cancels the customer's order in the portal, but only while…

Check yourself

Checking your PaT sign-in…

How To

On this page
  • Adding the cancel step
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • What the step does
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • When it cancels, and when it does not
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Approving a cancel
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Purpose / Intent of the Module
  • Header One

Summary In the Playbook editor, the step Cancel the order in the portal comes after a conclusion. Once a person approves the run's card, it cancels the customer's order in the portal, but only while the order is Entered. First it adds the ticket number to the order's instructions and saves the order, then it cancels the order with a reason and says when it is done. A shadow run never cancels anything.

Adding the cancel step

Step 1

On a Sandbox draft of the playbook, click the conclusion step in the diagram: the step where a person approves the run.

Step 2

Under Add a step after this one, choose Writes: cancel the order in the portal. It is offered only after a conclusion, or after another step that writes.

Step 3

In the list beside it, choose the way out that starts On "Approved", so the order is only cancelled after a person approves.

Step 4

Type a name for the step, or keep the one shown: Cancel the order in the portal. Then click Add step.

Step 5

The page says Step added. Name it and fill in its details, then Save changes. Click Save changes to keep the new step.

Step 6

The cancel step is offered only when the portal's cancel tool is shared with the form.

What the step does

Step 1

The step's details say what it does: once a person approves the run's card, it cancels the order in the portal, only while it is Entered.

Step 2

Before it cancels, it adds the ticket number to the order's instructions, as PaT ticket: and the number, and saves the order.

Step 3

It cancels with a reason from the account's own list. Under Reason, the details say AI chooses (most often Customer Request).

Step 4

An order past Entered is never cancelled: it goes to a CSR.

Step 5

Under In shadow, the details say Never: a shadow run only says what it would do.

When it cancels, and when it does not

Step 1

The step needs an earlier portal lookup in the same run that found exactly one order. Without one, it cancels nothing and a person needs to look.

Step 2

At the conclusion, the AI decides whether the ticket asks for the order to be cancelled, and chooses the reason. If the ticket does not ask, nothing is cancelled.

Step 3

The run's card offers the cancel only when the ticket's title starts with its PaT ticket number and the ticket has a staff assignee.

Step 4

In a shadow run, the step's line says what it would do, or why it would not cancel.

Approving a cancel

Step 1

When the run would cancel, its card in the ticket's chat says Approve also cancels the order, and names the order.

Step 2

The card says what Pat Bot will do: add the ticket number to the order's instructions and save the order, then cancel it with the chosen reason, and say in the chat when it is done.

Step 3

If anything else on the order changes, or it is no longer Entered, nothing is cancelled and you are told.

Step 4

Disapprove cancels nothing.

Step 5

Approve does not send the reply to the customer: send it yourself once the cancel is confirmed.

Step 6

A cancel is never tried twice.

Step 7

Until PaT turns cancelling on, no card offers a cancel, and no order is changed or cancelled.

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…

PreviousPlaybook editor: adding a portal lookup stepNext Pure Forms

On this page

  • Adding the cancel step
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • What the step does
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • When it cancels, and when it does not
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Approving a cancel
  • 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.