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 portal lookup step

Playbook editor: adding a portal lookup step

Summary In the Playbook editor, a portal lookup step reads what a ticket is about from the portal, without changing anything: an order, its products and their stock, an inwards shipment, or the…

Check yourself

Checking your PaT sign-in…

How To

On this page
  • Adding a portal lookup step
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • What each lookup reads
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Purpose / Intent of the Module
  • Header One

Summary In the Playbook editor, a portal lookup step reads what a ticket is about from the portal, without changing anything: an order, its products and their stock, an inwards shipment, or the customer's notification settings. A returns lookup step reads the customer's graded returns in Twoboxes, the returns portal, also without changing anything. On a Sandbox draft, add the step after the one it should follow, choose whether a failed lookup hands the ticket to a person, then save your changes.

Adding a portal lookup step

Step 1

On a Sandbox draft of the playbook, click the step in the diagram that the lookup should come after.

Step 2

Under Add a step after this one, choose the lookup you need: Tool: portal lookup for an order, Tool: order drop time & status to check when an order dropped in and whether it left in time, Tool: portal lookup, order lines and stock to check an order's products and their stock, Tool: portal lookup, inwards shipments for an inwards shipment, Tool: portal lookup, notification settings to see who is emailed when the customer's dockets are confirmed, or Tool: returns lookup (Twoboxes) for a customer's returns.

Step 3

If the step has more than one way out, choose which way out the new step goes on. Type a name for the step, or keep the one shown: Portal lookup, Check order drop time & status, Portal lookup: order lines and stock, Portal lookup: inwards shipments, Portal lookup: notification settings, or Returns lookup (Twoboxes).

Step 4

Leave If it fails, hand the ticket to a person (Lookup failed) ticked, so a failed lookup goes to staff. 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.

What each lookup reads

Step 1

Portal lookup reads the order by its number or reference, and its carrier and tracking.

Note. Check order drop time & status reads the order by its number or reference, and its status; when it dropped into the system, and the day it was due to leave: the same working day if it dropped before the cut-off (1 pm unless the company's settings say otherwise), else the next working day; and whether it left in time, or is overdue. Every order lookup makes this check: this step is named for it.

Note. Portal lookup: order lines and stock reads the order by its number or reference, and its lines: each product and the units ordered. For the first 10 lines it reads each product's stock on hand, the total units in the warehouse, and its stock available: on hand less the units for orders entered or picking, less stock on hold. Given a product code on its own, it reads that product's stock.

Step 2

Portal lookup: inwards shipments reads the inwards shipment by its number, PO or reference, open shipments first and then processed ones. It reads its lines: each product, the quantity expected, its batches, and what was received once it was processed.

Step 3

If the ticket gives no shipment number, the inwards lookup reads the customer's open shipments with the nearest ETAs, and any product the ticket asks about.

Note. Portal lookup: notification settings reads the customer's notification settings: who is emailed, and in which format, when a despatch, inwards or stock adjustment docket is confirmed. It also reads any recipient set for one docket only, account by account. It changes nothing: adding or changing a recipient stays with a CSR, who is told exactly what to add.

Note. Returns lookup (Twoboxes) reads the customer's graded returns in Twoboxes, found by the order, tracking or RMA number in the ticket. For each return line it reads whether it arrived, its grading, its disposition and the conditions graded, with its product and site. It never reads the end customer's name, email or address.

Step 4

All six lookups are read-only: under Changes anything? they say No: read-only. The notification settings lookup adds that a CSR makes any change to a recipient, and the returns lookup adds Never the end customer's name, email or address. The notification settings lookup makes up to 6 requests, the returns lookup up to 4, and the other portal lookups up to 20 each.

Step 5

The portal lookups are offered only when the portal tool is shared with the form, and the returns lookup only when the Twoboxes returns lookup tool is shared with it.

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 Admin: when your shadow run is ready to reviewNext Playbook editor: adding a step that cancels an order

On this page

  • Adding a portal lookup step
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • What each lookup reads
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • 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.