Overview
Property-based logic shows or hides an element or page based on a Location Property — a characteristic set on the Location itself. It lets one Checklist adapt to where it's being run, so a site with an extra feature picks up the extra checks automatically.
Why this matters: Run the same Checklist across many Locations and they're rarely identical — some have a water feature, a second exit, a particular equipment type. Property-based logic means you maintain one Checklist, and each Location automatically shows only the checks that apply to it, based on its Properties.
How it works
Attach the logic to the element or page and point it at a Location Property and the value that should reveal it. When the Checklist runs at a Location, Mobaro reads that Location's Properties and shows the element only where the condition is met.
Note: This relies on the relevant Location Properties being configured and set on your Locations. If a Property isn't set on a Location, the condition can't evaluate true there.
Example
A general area-opening Checklist has a page, "Splash pad checks," with property-based logic set to show only where the Location Property Has water feature is Yes. Dry Locations never see the page; water-feature Locations get the extra checks from the same shared Checklist.
Frequently asked questions
Q: Where do Location Properties come from?
A: They're defined and assigned in your Location configuration. The logic reads whatever Properties are set on the Location running the Checklist.
Q: What if the Property isn't set on a Location?
A: The condition won't evaluate true there, so the element stays hidden. Make sure Properties are set consistently across the Locations that should show the content.
Q: How do I set it up?
A: Add logic to the element or page and choose the "based on a property" condition. See Adding logic to a Checklist.