Overview
Use Based on a property to show a Checklist page or element only when the Checklist's Location has the required Location Properties. This lets one Checklist adapt to different rides or sites.
This article covers the Checklist side. To create Properties and tag Locations, see Creating and assigning Location Properties; for how to plan them, see Understanding Location Properties.
At a glance |
|
Who can do this | Super Users, a Role with Checklists › Modify (or Create, for Checklists you created), or an Administrator or Editor of the Checklist's permission folder |
Where | Checklists › a Checklist › Edit › a page header or element › Logic |
Works on | Backend (web) to set up. The logic runs in the Mobile app and RideOps. |
Availability | All organizations |
Add a property condition
1. Open the logic panel
Go to Checklists, select the Checklist and click Edit. Click the page header or the element you want to show or hide, and expand Logic.
2. Add the condition
Click Add Logic and choose Based on a property. Under Property, Location is selected; it's the only option.
3. Choose the operator and Properties
Pick one of the four operators below, then select one or more Location Properties. Both are required before you can save. If the picker says No properties are configured for this organization, create Properties first.
4. Save
Click Accept Changes, then Save the Checklist.
Choose an operator
Operator | The page or element shows when the Location has |
contains any | At least one of the chosen Properties |
contains all | Every chosen Property |
does not contain any | None of the chosen Properties |
does not contain all | Not every chosen Property (it may have some) |
With a single Property, contains any and contains all give the same result, and so do the two negative operators. Properties are tags, not numbers: there's no "greater than". To show content for several values, select them all with contains any.
Which Location counts
Mobile app — the Location the Checklist is completed for, which is also the Location recorded on the Result. For a Continuous Checklist that targets several Locations, that's the Location the User picks.
RideOps — the ride's Location.
No Properties — at a Location without the chosen Properties, contains conditions aren't met and does not contain conditions are.
Timing — the mobile app uses the Location data it has downloaded, so a Property change applies once the app has updated its data. Results already recorded don't change.
Content hidden at a Location doesn't need an answer there, so a question shown only at water rides is required only at water rides.
🛑 Critical: Changing a Location's Properties changes which questions its Checklists show, including safety checks. Deleting a Property or Category removes it from every logic condition that uses it, and deletes conditions left with no Properties, so hidden content can start to show. This can't be undone. Check which Checklists use a Property before you change or delete it. See Creating and assigning Location Properties.
Combine with other conditions
A page or element can have several conditions. At the top of the logic panel, choose Show this element if All conditions are met, or One or more. For example, contains any Water Ride and Weekday equal to Monday, combined with All, shows a weekly water check only at water rides.
Properties belong to one organization. When you copy a Checklist to another organization, Property conditions on elements are removed, but Property conditions on pages are kept and point at Properties the other organization doesn't have. Check and redo page logic after copying.
Examples
One inspection for several ride types. Tag each ride with a Ride Type Property. The track page has contains any Coaster; the water chemistry page has contains any Water Ride. A new ride is onboarded by tagging its Location, with no Checklist changes.
Questions that build up. Tag each unit with one size, 1 bed to 4 bed. The Bedroom 1 page has no Property logic; Bedroom 2 has contains any 2 bed, 3 bed, 4 bed; Bedroom 3 has 3 bed, 4 bed; Bedroom 4 has 4 bed.
Leave some Locations out. Outdoor checks have does not contain any Indoor, so they show everywhere except indoor attractions.
Best practices
Prefer contains any: it's the easiest operator to read later.
Put Property-specific questions on their own page and use page logic.
Tag every Location that runs the Checklist consistently, so a missing tag doesn't silently hide a question.
Test the Checklist in the mobile app at a Location with and without the Property before you schedule it.
Frequently asked questions
How do I show questions only for a particular ride or location?
Tag those Locations with a Location Property, then give the questions or page the condition Based on a property contains any that Property. For a Continuous Checklist, the Location the User picks when starting counts.
How do I show the bedroom 1, 2 and 3 questions for a three-bedroom unit?
Tag the unit with one Property, 3 bed. Give each bedroom page contains any with every size that includes it: Bedroom 2 gets 2 bed, 3 bed, 4 bed; Bedroom 3 gets 3 bed, 4 bed. Leave Bedroom 1 without Property logic.
Why is Location the only option under Property?
Location Properties are the only kind of property logic can read, so Location is the only choice. If no Properties appear, your organization hasn't created any yet. For other conditions, such as User Groups, pick another type under Add Logic.
A question doesn't show at a location that has the property. Why?
Check the operator (contains all needs every Property), the page's own logic, and which Location the Checklist was completed for. In the mobile app, a recent Property change applies once the app has updated its data.