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. Stacked views, flip cards, tabs and stages

Stacked views, flip cards, tabs and stages

Summary A PaT form can have stacked views: the main form, called the Default View, plus an Introduction Screen shown before it and a Call to Action Screen shown after it. Shared as a flip card, the…

Check yourself

Checking your PaT sign-in…

How To

On this page
  • Opening Manage Views in the Form Builder
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Adding an Introduction Screen or a Call to Action Screen
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Building each view on the canvas
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Sharing the form as a flip card
  • Step 1
  • Step 2
  • Step 3
  • Filling in a flip card form
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Standard, staged and flip card pages on phones
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Tabs in the Edit form field window
  • Step 1
  • Step 2
  • Step 3
  • Purpose / Intent of the Module
  • Header One

Summary A PaT form can have stacked views: the main form, called the Default View, plus an Introduction Screen shown before it and a Call to Action Screen shown after it. Shared as a flip card, the form shows them one after the other, turning over like a card. This lesson is for people who build forms in the Form Builder, and for anyone who fills them in. It also covers the standard, staged and flip card form pages on phones, and the tabs in the Edit form field window.

Opening Manage Views in the Form Builder

Step 1

Open the SD that holds the form and click Advanced, then click SD Form Builder in the menu on the left. The Form Builder opens (see the lesson SD Forms).

Step 2

Manage Views is the teal button at the right end of the bar along the top of the Form Builder, after Settings, Schema and Reorder. It stays grey until the canvas has at least one element.

Step 3

Click Manage Views. The Manage Form Views window opens, with a table of the form's views.

Step 4

The first time, the table has one view, Default View, marked Default and Fixed Position. It is the main form, and every element already on the canvas is in it. It cannot be edited, moved or deleted.

Adding an Introduction Screen or a Call to Action Screen

Step 1

Click Add View, at the top right of the Manage Form Views window. The Select View Type window opens, with two choices.

Step 2

Click Introduction Screen to add a screen that people see before the main form, typically for instructions or context information.

Step 3

Or click Call to Action Screen to add a screen that people see after they submit the main form, typically for next steps or a thank you message. To have both, click Add View again and choose the other. Each screen can be added once: a screen the form already has is faded in the Select View Type window and says Already added.

Step 4

The screen joins the table straight away, in its fixed place: the Introduction Screen before the Default View, the Call to Action Screen after it. Neither can be edited or moved.

Step 5

To remove a screen, click its red Delete view button (the bin) in the Actions column.

Step 6

While you have changes, the bottom of the window says You have unsaved changes. Click Save Configuration, at the bottom right, to keep them, or Cancel to close the window without them.

Step 7

Then click Save, the green button at the top right of the form on the canvas, to be sure the views are saved with the form.

Building each view on the canvas

Step 1

Once the form has views, a grey button beside Save, at the top right of the form on the canvas, names the view you are working on, such as Default View.

Step 2

Click it to open Available Views, then click the view to build, such as Introduction Screen. The canvas shows only that view's elements.

Step 3

Drag elements onto the canvas as usual: each one goes into the view you chose. An Introduction Screen suits elements that show information, such as Banner, HTML Viewer or Video (see the lesson Form builder: field types).

Step 4

To work on the main form again, choose Default View from the same button. Manage Views, at the bottom of its list, opens the Manage Form Views window.

Step 5

To move an element to another view, click Reorder at the top of the Form Builder. The Reorder Form Controls panel lists the elements of the view you are working on.

Step 6

Click the element's Transfer to another view button (the layers icon), then choose the view under Transfer to View.

Step 7

Click Apply and Close at the bottom of the panel, then click Save Form Now at the top of the canvas.

Step 8

Preview shows only the view the canvas is on, such as the main form when the canvas is on the Default View. To see the Introduction Screen and the Call to Action Screen as people will, open the form's flip card link.

Sharing the form as a flip card

Step 1

Click Share, the blue button near the top left of the Form Builder. The Share window opens, named after the form. The SD must be a template; otherwise the window asks you to convert the SD to a template. If it shows Activate Sharing, click it first.

Step 2

Under Presentation, choose Flip Card. A form with views starts on Flip Card. Standard Form shows the main form only, without the Introduction Screen or the Call to Action Screen.

Step 3

Click Copy Link at the bottom of the window, then send the link. The lesson SD Forms explains Single Submit and Multiple Submits.

Filling in a flip card form

Step 1

The person who opens a flip card link sees the form on a card. If the form has an Introduction Screen, it comes first, with a Begin button.

Step 2

Clicking Begin turns the card over to the main form.

Step 3

When the person submits the main form and the answers are saved, the card turns over again, to the Call to Action Screen. To choose what people see after they submit, give the form a Call to Action Screen.

Step 4

If the answers cannot be saved, the card stays on the main form, and a message says Oops, there has been an error. Please try again.

Step 5

To let people start again from the first screen, for example on a shared tablet, the person who builds the form adds a Reset Button (in the Custom control) to the Call to Action Screen. Its Start Over button turns the card back to the first screen with a fresh form. Its words can be changed in its Button text setting.

Step 6

If the form's Settings switch on Enable Post-Submit Redirect, people go to the Redirect URL after they submit the main form, instead of staying on the Call to Action Screen.

Step 7

On a form with an Introduction Screen, Begin turns the card over to the main form as usual, even when Enable Post-Submit Redirect is switched on. People are sent to the Redirect URL only once the main form's answers are saved.

Standard, staged and flip card pages on phones

Step 1

A form link opens one of three pages: the standard page, for a form submitted in one go; the staged page, for a multi-stage form filled in one stage at a time; or the flip card page. On a phone, each fits the width of the screen.

Step 2

In a Dropdown (Single selection) on a phone, the list opens wide enough to read, even when the dropdown sits in a narrow column.

Step 3

In a Dropdown (Multiple selections) on a phone, the answers already chosen leave room for the arrow.

Step 4

After a person's answers are saved on the standard or the staged page, the page says Thank you for your time ... We have submitted your data. You may close this browser.

Step 5

If the link was already used to submit the form, the standard and flip card pages say It looks like you have submitted this form already.

Step 6

To send people to a web page after they submit, click Settings at the top of the Form Builder. In the Settings window, under Post-Submit Redirect, switch on Enable Post-Submit Redirect.

Step 7

Type the web address in Redirect URL. Redirect Target reads Redirect entire page (the default) until you choose; left like that, it acts as Redirect entire page (recommended for iframes). The other choices are Open in new tab, Redirect parent frame and Redirect current frame only.

Step 8

Click Save at the bottom of the Settings window. If the Canvas heading then shows (Unsaved changes) in red, click Save Form Now, at its right, to save the form.

Tabs in the Edit form field window

Step 1

On the canvas, click an element's edit button (the pencil) at its top right. The Edit form field window opens, named after the element.

Step 2

The element's settings are split into tabs along the top of the window, from General to Conditional Formatting, such as Default Value, Advanced and Conditional Logic. Which settings each tab holds depends on the element.

Step 3

Click a tab to see its settings, instead of scrolling through one long list. When you have finished, click the save button at the bottom right of the window, such as Save and Close Date Selector.

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…

PreviousSD Template Helper FunctionsNext Strategy System

On this page

  • Opening Manage Views in the Form Builder
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Adding an Introduction Screen or a Call to Action Screen
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Building each view on the canvas
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Sharing the form as a flip card
  • Step 1
  • Step 2
  • Step 3
  • Filling in a flip card form
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Standard, staged and flip card pages on phones
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Tabs in the Edit form field window
  • Step 1
  • Step 2
  • Step 3
  • 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.