NO MOM
I CANT PAUSE.
RowTether Documentation
Support
Browse lessons

5. Create and preview a game rule

Turn a game requirement into an explicit check.

On this page

Goal: Turn a game requirement into an explicit check.

Before you start: ConsumersByKey after correcting D2 in lesson 3.

The idea you will use

A valid reference can still violate a game rule. Previewing a draft does not save it.

Predict before running

Can two rows with valid destinations still violate a unique-label requirement?

Build and check

Turn a simple game requirement into an explicit check on the selected data.

  1. Select ConsumersByKey and click Use selected DataTables. If needed, reload name-string-profile.json to keep the TargetKey relationship declared.
  2. Open Configure references and game rules → References and game rules, then click Create rule.
  3. Choose ConsumersByKey as the source table, Label as the field and the uniqueness check. Give it a name and message that explain the requirement.
  4. Click Preview on selected tables. The three labels are distinct, so the rows should pass this rule.
  5. To try a failure, edit D3.Label to exactly match D2.Label. Preview again: the rule should flag the duplicate label.
  6. Restore D3.Label to Warehouse, preview again and, when the draft is correct, click Save rule and review.
  7. Check the new status and results. This rule is separate from the reference review; do not disable it to hide a data condition that still fails.

Preview on selected tables evaluates the draft without saving it. Editing the rule invalidates that preview. Check coverage and the Pass, Fail, Not applicable or Not evaluable outcome before acting.

If Label is not offered for the rule, confirm that ConsumersByKey is selected and Label is a top-level String property. A Not evaluable outcome requires reviewing its details and coverage; do not assume it passed.

Check your reasoning

See the explanation

Yes. Reference resolution does not automatically check every game rule.

Your turn: Test the duplicate, restore Warehouse and explain Preview versus Save rule and review.

Ready to continue when: you can distinguish Pass, Fail and a case that could not be evaluated.

Back to the path and its extensions