PPaT Wiki
DokumentationPathwayWissensdatenbankForumBlogKontakt
Week streakFOUNDATION0 badges
Sprache: Deutsch
  • English
  • Nederlands
  • Karen (S'gaw)
  • Français
  • Deutsch
  • Lea faka-Tonga
  • Te reo Māori
Community fragen

Your PaT Pathway

0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User

Practitioner

  • ○Pop-Out Chat Feature (not passed yet)
  • ○Chat reminder (not passed yet)
  • ○Chat to SD (not passed yet)
  • ○Chat to email to chat (not passed yet)
  • ○Email to chat to email – non PaT users (not passed yet)
  • ○C2E Attachments (not passed yet)
  • ○Email to BFF (not passed yet)
  • ○How SD chats work with SD Members and External Users (not passed yet)
  • ○Docked Chats (not passed yet)
  • ○Inline chats (not passed yet)
  • ○Multi-Tasks (not passed yet)
  • ○Task Integrity: what it is and why it drops (not passed yet)
  • ○Chat to task to project (not passed yet)
  • ○SD Task wall view (not passed yet)
  • ○Using SDs as a report or meeting minutes app (not passed yet)
  • ○Running Meetings with SDs (not passed yet)
  • ○Invite Attendees (not passed yet)
  • ●Recurring tasks: create and edit (this page)
  • ○Info Icons (not passed yet)
  • ○Moving Section Headers (not passed yet)
  • ○SD Element Categorisation (not passed yet)
  • ○Add any Image as a Section Header Icon (not passed yet)
  • ○Embedding SDs in SDs (not passed yet)
  • ○Assigning an SD to a new parent (not passed yet)
  • ○Filing and retrieving SDs (not passed yet)
  • ○SD Owner Functions (not passed yet)
  • ○Docking SDs and Updating Images (not passed yet)
  • ○Embedding live data in an SD (graphs and spreadsheets) (not passed yet)
  • ○PaT AI (not passed yet)
  • ○Track Engagement (not passed yet)
  • ○Share and record your screen (not passed yet)
  • ○Different Form Uses (not passed yet)
  • ○Form Wall (not passed yet)
  • ○SD Form Responses: finding and exporting form responses (not passed yet)
  • ○Video rooms: guests joining and asking to record (not passed yet)
  • ○Comprehension Audits (not passed yet)
  • ○Evidential audits: completing one (not passed yet)
  • ○LMS Architecture (not passed yet)
  • ○Safe Walks (not passed yet)
  • ○Customer-specific training: how it works (not passed yet)
  • ○How PaT Manages Inactive Users (not passed yet)
  • ○How to unlock a module for a staff member (not passed yet)
  • ○Health and safety templates (not passed yet)
  • 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
  • Aufgabenintegrität: Was sie ist und warum sie sinkt
  • 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
  • Mehrfachaufgaben
  • Moving Section Headers
  • 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
  • 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
  • Aufgabe erstellen
  • Aufgabenübersicht
  • Aufgabenverwaltung
  • Aufgabenverwaltungssystem
  • Capture and Manage Accidents
  • Capture and Manage Hazards
  • Chat to task
  • Chat Wall
  • Contextual Communication
  • Convert a Note to a Task
  • Create a new SD
  • Critical Chrome Extensions
  • Document Store: shared links, your folders and favourites
  • Fast Notes
  • Getting help: the PaT Helpdesk
  • Global Search
  • Gruppenchats
  • 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 – Überblick
  • PaT Mobile App – Overview
  • Preview, download and share files
  • Publish a Bulletin Board Post
  • Reading an SD in another language
  • 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
  • Traffic light progress
  • Upload file attachments
  • Video calls on the mobile app
  • Automatische Eskalation
  • Build a reporting system
  • 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
  • Endpoint Manager: finding endpoints and building your own UDF
  • Form builder: field types
  • Forms - Extract Data (the AI form builder)
  • Formular-Testmodus
  • 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
  • Pure Forms
  • SD Dashboard: building a dashboard
  • SD Forms
  • SD Security Settings
  • SD Template Helper Functions
  • Strategy System
  • Throttling
  • Using Chat to SD to go from being a good manager to a great one
  • Using SDs as the LMS Document
  • Wie Manager für ihre Mitarbeitenden OOF aktivieren können
  • PaT Lite: Wichtige Aspekte von PaT, die Sie verstehen sollten
  • Was ist PaT und warum ist es wichtig
  • PaT Lite: Vom Chat zur Aufgabe
  • PaT Lite: Einführung von Strategy Documents
  • PaT Lite: Kernphilosophie – Standards und taktische Umsetzung
  • PaT Lite: Intelligente Tools, die mit Ihnen mitdenken
  • PaT Lite: Die Zukunft des Unternehmens ist Kultur
  • Willkommen im PaT-Wiki
  • Ihren Arbeitsbereich einrichten
  • Ihre erste Woche
  • Strategy Documents
  • Aufgaben und Zuweisungen
  • Berechtigungsmodell
  • Chat und Diskussion
  • Formulare und Einreichungen
  • Dashboards und Berichte
  • Benutzer verwalten
  • Workspace-Einstellungen
  • Buchhaltungssystem verbinden
  • Single Sign-on
  • API-Übersicht
  • Zugriffstoken
  • Webhooks
0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User
Practitioner quizzes: 0 of 43 passed
  • ○Pop-Out Chat Feature (not passed yet)
  • ○Chat reminder (not passed yet)
  • ○Chat to SD (not passed yet)
  • ○Chat to email to chat (not passed yet)
  • ○Email to chat to email – non PaT users (not passed yet)
  • ○C2E Attachments (not passed yet)
  • ○Email to BFF (not passed yet)
  • ○How SD chats work with SD Members and External Users (not passed yet)
  • ○Docked Chats (not passed yet)
  • ○Inline chats (not passed yet)
  • ○Multi-Tasks (not passed yet)
  • ○Task Integrity: what it is and why it drops (not passed yet)
  • ○Chat to task to project (not passed yet)
  • ○SD Task wall view (not passed yet)
  • ○Using SDs as a report or meeting minutes app (not passed yet)
  • ○Running Meetings with SDs (not passed yet)
  • ○Invite Attendees (not passed yet)
  • ●Recurring tasks: create and edit (this page)
  • ○Info Icons (not passed yet)
  • ○Moving Section Headers (not passed yet)
  • ○SD Element Categorisation (not passed yet)
  • ○Add any Image as a Section Header Icon (not passed yet)
  • ○Embedding SDs in SDs (not passed yet)
  • ○Assigning an SD to a new parent (not passed yet)
  • ○Filing and retrieving SDs (not passed yet)
  • ○SD Owner Functions (not passed yet)
  • ○Docking SDs and Updating Images (not passed yet)
  • ○Embedding live data in an SD (graphs and spreadsheets) (not passed yet)
  • ○PaT AI (not passed yet)
  • ○Track Engagement (not passed yet)
  • ○Share and record your screen (not passed yet)
  • ○Different Form Uses (not passed yet)
  • ○Form Wall (not passed yet)
  • ○SD Form Responses: finding and exporting form responses (not passed yet)
  • ○Video rooms: guests joining and asking to record (not passed yet)
  • ○Comprehension Audits (not passed yet)
  • ○Evidential audits: completing one (not passed yet)
  • ○LMS Architecture (not passed yet)
  • ○Safe Walks (not passed yet)
  • ○Customer-specific training: how it works (not passed yet)
  • ○How PaT Manages Inactive Users (not passed yet)
  • ○How to unlock a module for a staff member (not passed yet)
  • ○Health and safety templates (not passed yet)
  1. Dokumentation
  2. Practitioner
  3. Recurring tasks: create and edit

Diese Seite wurde noch nicht übersetzt und wird daher auf Englisch angezeigt.

Recurring tasks: create and edit

Summary This module shows how to create a recurring task in PaT and how to change it later. You add a task, turn on recurring in its Advanced options, then set how often it recurs, how many times…

Auf dieser Seite
  • Creating a recurring task
  • 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
  • Step 14
  • Step 15
  • Step 16
  • Step 17
  • Step 18
  • Recurring tasks in an SD
  • Step 19
  • Step 20
  • Step 21
  • Editing a recurring task from the Activity tab
  • Step 22
  • Step 23
  • Step 24
  • Step 25
  • Step 26
  • Step 27
  • Step 28
  • Step 29
  • Step 30
  • Step 31
  • Step 32
  • Step 33
  • Step 34
  • Changing the assignor, title or parent SD
  • Step 35
  • Step 36
  • Step 37
  • Step 38
  • Step 39
  • Step 40
  • Step 41

Summary This module shows how to create a recurring task in PaT and how to change it later. You add a task, turn on recurring in its Advanced options, then set how often it recurs, how many times, when it first starts and how many days the assignee has to complete it. To change it later, open Recurring Tasks in your Activity tab. It has two parts: “Creating a recurring task”, then “Editing a recurring task from the Activity tab”.

Creating a recurring task

Summary This part covers creating a recurring task: add a task from the PaT Menu, open its Advanced options and turn on Recurring Task, then set its Frequency, Cycle, Occurances, Start Date and Days to complete. PaT then creates each task for you and escalates it automatically if it is missed, so important recurring work is never forgotten. It also shows where a recurring task sits in an SD.

Introduction. Recurring tasks are among PaT's most powerful features. Think of them as a personal assistant that manages tasks 24/7, so you can focus on the more critical parts of your work. Once you master recurring tasks, you can build processes and systems that never fall over.

Step 1

Open the PaT Menu: click the round + button at the bottom centre of the screen. A fan of round icons opens above it.

Step 2

Click Add a Task, the green icon with a tick in a box, at the left end of the fan. The Create a Task box opens.

Step 3

In Assign To, choose the assignee: the person who will do the task. Your own name is there to start with, so leave it to give the task to yourself. Then type the task's title in Task, in up to 100 characters.

Step 4

Click Advanced at the bottom right of the box, beside Submit. More options appear.

Step 5

Under the task's title is a text box. The title usually explains what's needed, but use the text box to give extra context if it helps. Anything you type there shows as a comment on the task each time it is triggered, so the assignee can always refer back to it.

Step 6

To make the task recurring, click the recurring task icon (two arrows in a loop), between the deadline and the priority. The Recurring Task panel opens.

Step 7

Tick the box to the right of the Recurring Task heading to make it a recurring task. To deactivate a recurring task later without deleting it, untick the box; tick it again to reactivate the task.

Step 8

In Frequency, choose how often the task recurs. For a task every 6 months, choose 6.

Step 9

In Cycle, choose days or months. For a task every 6 months, choose months.

Step 10

In Occurances, choose how many times the task occurs: from 1 to 52, or 4 ever (for ever).

Step 11

In Start Date, set when the first task starts: click the arrow at the right of the box to open the date selector.

Step 12

Select the date you want in the calendar.

Step 13

To change the task's due time, use the hour, minute and second boxes at the top of the calendar.

Step 14

Click OK at the bottom of the calendar to confirm your choice.

Step 15

Lastly, in Days to complete, choose how many days the assignee has to complete each task once it appears. Start Date tells PaT when the recurring task should be created; Days to complete sets how far ahead each task's deadline is, meaning when it must be completed by.

Step 16

For example, choose 7 days for a task that takes about a week. Each task then appears on the assignee's Task Wall 7 days before its due date, giving them a full week to complete it before the deadline.

Step 17

Click the back arrow under the settings, at the bottom left of the Recurring Task panel. You return to the task.

Step 18

Click Submit at the bottom right of the box.

Result. PaT now creates each task for you. Moving from calendar reminders, to-do lists and memory to a database you have programmed automates your task reminders, and lets PaT act for you, for example by escalating a task automatically when it is missed. This brings lasting benefits to the business and frees you from ever having to worry about the task again.

Recurring tasks in an SD

Step 19

When you create a recurring task, PaT generates an SD that acts as a folder for all the tasks it creates automatically. In the SD that holds it, the recurring task shows in blue as the last entry, with "RECUR:" before its title. The "RECUR:" prefix shows that the SD holds recurring tasks. Open it to see every task that has fired over time and its current status, such as WIP, Completed, Overdue, Pending RTC or Negotiating Deadline.

Step 20

To see the recurring task's details, click the edit icon (a pen on a square) at the right end of its row, just left of the flag.

Step 21

The Edit SD panel slides in from the right, with the Task Description, Due Date, Assignee, Assignor, Parent SD and Task Status. The note under them reads Only the task Assignor can edit this task. Parent SD links the recurring task to the SD it belongs to. The Assignee completes each task, and the Assignor reviews the work and approves or rejects each request to close it.

Note. To change how a recurring task recurs, such as its Frequency, Cycle, Occurances or Days to complete, use the Recurring Task editor, as the next part of this module shows.

Why recurring tasks are powerful. - If the Assignee leaves or becomes inactive, PaT automatically reassigns their recurring tasks to the Assignor, who must accept the work or delegate it to someone else. Tasks don't fall through the cracks during staff changes. - Where people forget, PaT never does. Once repetitive tasks are managed by PaT, they stop being missed. - If the Assignee misses a deadline, PaT's auto-escalation raises the issue up the chain of command, all the way to higher management or even the CEO if needed, so nothing important is overlooked.

Editing a recurring task from the Activity tab

Summary This part covers changing a recurring task you have created, from your Activity tab: its frequency, cycle, occurrences, next date, days to complete and assignee, its assignor and title, and the comments of the source task. It also covers deactivating a recurring task, and how to move one to a different parent SD.

Step 22

Click the orange Activity tab on the left edge of the screen. A panel opens on the left.

Step 23

Click Recurring Tasks at the top of the panel, between How To and Out Of Office. The panel becomes my Recurring Tasks.

Step 24

Click Active: by me to see the recurring tasks you have created.

Step 25

Each recurring task shows as a card, with its title, its frequency, how many have been completed, its next date and its parent SD. To edit one, click the recurring icon (two arrows in a loop) at the right of its card.

Step 26

The Recurring Task editor opens. It has the settings you chose when you created the task, with Next Date in place of Start Date, plus Assignee and two links under it.

Step 27

To deactivate a recurring task, untick the box to the right of the Recurring Task heading. The task becomes inactive.

Step 28

If that is the only change you want, click Submit at the bottom of the editor.

Step 29

To change how often the task recurs, choose a new number in Frequency.

Step 30

In Cycle, choose days or months.

Step 31

In Occurances, choose how many times the task occurs: from 1 to 52, or 4 ever.

Step 32

In Next Date, change the date the next task will be due.

Step 33

In Days to complete, change the number of days the assignee has to complete each task.

Step 34

To change the assignee, choose a new one in Assignee.

Changing the assignor, title or parent SD

Step 35

To change the task's assignor or title, click the first link under Assignee: click here to change the Assignor or Title of the source task. A window opens with the source task's details.

Step 36

Change the title in Title, at the top of the window.

Step 37

Change the assignor in Assignor.

Step 38

The parent SD can't be changed in this window, as the note under Parent Strategy Document explains. To move the recurring task to a different parent SD, open its current parent SD and find the row the recurring task is on. Click the edit icon on that row and select a new Parent SD.

Step 39

When you have finished, click Update at the bottom of the window.

Step 40

To edit the comments of the source task, click the second link in the editor: click here to edit the comments of the source task.

Step 41

When you have finished, click Submit at the bottom of the editor.

Check yourself

Checking your PaT sign-in…

ZurückPop-Out Chat FeatureWeiter Running Meetings with SDs

Auf dieser Seite

  • Creating a recurring task
  • 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
  • Step 14
  • Step 15
  • Step 16
  • Step 17
  • Step 18
  • Recurring tasks in an SD
  • Step 19
  • Step 20
  • Step 21
  • Editing a recurring task from the Activity tab
  • Step 22
  • Step 23
  • Step 24
  • Step 25
  • Step 26
  • Step 27
  • Step 28
  • Step 29
  • Step 30
  • Step 31
  • Step 32
  • Step 33
  • Step 34
  • Changing the assignor, title or parent SD
  • Step 35
  • Step 36
  • Step 37
  • Step 38
  • Step 39
  • Step 40
  • Step 41
PPaT Wiki

Dokumentation, Wissensdatenbank und Community-Support für People and Tasks.

Dokumentation

  • Erste Schritte
  • Grundkonzepte
  • Integrationen
  • API-Referenz

Support

  • Wissensdatenbank
  • Community-Forum
  • Kontakt
  • Dienststatus

Unternehmen

  • PaT
  • Blog
  • Nutzungsbedingungen
  • Datenschutz

© People and Tasks. Alle Rechte vorbehalten.