Overview
A Water Quality ruleset stores the limits used to check readings. It contains one or more rules, each with selected parameters and minimum and maximum values. This guide covers creating, changing and deleting rulesets, and when changes apply.
At a glance |
|
Who can do this | Super Users only. Other users may see the ruleset table, but saving fails with an error such as The ruleset could not be created. |
Where | Configuration › Checklists tab › ruleset table (titled Checklist Water Quailty Ruleset) |
Works on | Backend (web). Rules are applied to readings in the Mobile app. |
Availability | Early access — contact Mobaro Support to request access. |
🚀 Early access: Water Quality is an early-access feature and may not be enabled for your account. Contact Mobaro Support to request access. Until it's enabled, the ruleset table and the Water Quality Question element don't appear.
Ruleset tasks
Task | How | Full guide |
Create | Click + (Create Ruleset), name the ruleset and its first rule, tick parameters and enter limits. | |
Edit | Select the ruleset and click the pencil (Edit Ruleset), or double-click it. | |
Add or remove a rule | + at the bottom (Add rule) adds a rule to the end; the trash icon (Remove rule) removes one. A ruleset keeps at least one rule. | |
Set limits | Tick a parameter in a rule and enter its Minimum and Maximum. | |
Delete | Select the ruleset and click the trash icon (Delete Ruleset), then Delete. |
What a ruleset needs to save
Save stays unavailable until the ruleset and every rule have a name, and every ticked parameter has both a Minimum and a Maximum. Limits can't be lower than 0, and the minimum must be lower than or equal to the maximum. Collapsed rules can hide the problem, so expand each one.
When changes take effect
Saved changes apply to readings taken afterwards, in every Checklist whose Water Quality Question links the ruleset. Submitted Results aren't recalculated.
Readings are checked on the phone, against the rulesets the app last downloaded. The app downloads fresh data when its copy is more than 15 minutes old, or when staff refresh it; a phone that's offline keeps using the limits it last downloaded.
Rules keep the order they were added in. Mobaro uses the first rule in the list that either has no Location Groups or has a Location Group containing the Checklist's Location.
🛑 Critical: Some changes can't be undone. Deleting a ruleset sets every Water Quality Question linked to it to no ruleset, so readings there are no longer checked. Unticking a parameter discards its limits when you save. Rulesets have no change history, so keep a record of your limits outside Mobaro.
🛑 Critical: If no rule matches a Location, readings there aren't checked against any limits, and nothing warns you. Make sure every Location is covered — for example, end the ruleset with a rule that has no Location Groups.
How rulesets connect
Water Quality Questions link one ruleset each and choose which parameters staff record. See How to add water quality checks to a checklist.
Location Groups decide which rule applies where. See Best practices for structuring rulesets.
Require validation on rule deviation on a Schedule routes Results with Low or High readings to validation. See Understanding validation warnings and failures.
Best practices
Edit a ruleset rather than deleting and recreating it.
When replacing a ruleset, link the new one on every Water Quality Question before deleting the old one.
Tell staff when limits change, so their expectations match the High and Low markers.
Frequently asked questions
How do I correct a water quality limit that's wrong?
A Super User edits the ruleset: open the rule, change the Minimum or Maximum and click Save. The new limit applies to readings taken afterwards; past Results keep their original Low/High markers.
Can I undo changes to a ruleset?
No. Rulesets have no version history or undo. Change the values back by hand, using your own record of the previous limits.
Can I copy a ruleset?
No. Create a new ruleset and re-enter the limits. See Best practices for structuring rulesets.