Skip to content
← Practical configuration
LESSON 07 / Beginner

Validate a page change

5 min readConcept draftNot yet reviewed or tested in an IFS environment

Write checks for both intended behavior and unintended effects.

Prerequisites: IFS Cloud essentials. No IFS login is needed for this written exercise. Estimated reading time excludes practice.

Configuration review should separate appearance, data behavior, access, and existing workflows. A page that looks correct for its designer may behave differently for its intended users. This is a test-design exercise, not a menu-by-menu Page Designer procedure.

A new reference should be optional for old records. The team tests one newly created record and concludes the change is ready. That misses records with no reference, long values, and users who should not edit it.

  1. Write the expected result before running each case.
  2. Cover a new record, an existing record, an empty value, and a value at the agreed boundary.
  3. Repeat with the intended user role and a role without edit access.
  4. Check the unchanged workflow and capture a result or a reproducible defect.

Write four acceptance cases for an optional external handover reference. For each case state the starting data, action, and expected result.

See a suggested answer

An existing record with no reference still opens. A permitted user can save a valid reference. A value outside the agreed rule is handled as specified. A read-only user cannot make the change. Confirm the actual enforcement in the training system; do not infer it from a hidden control.

Treating a screenshot as proof of persistence. Reopen the record and verify the stored or derived value.

Expected result: a written answer that explains your decision and identifies what still needs confirmation in the actual environment.

Cleanup: none; this exercise changes no IFS data.

IFS Cloud 26R1 documentation. Source consulted 2026-09-23. The scenario and exercise are original fictional examples. This concept draft has not been reviewed by an IFS specialist or executed in an IFS environment.

Apply this lesson in the handover-reference project.

If validation invokes a custom event, review event actions and mutating-table errors and test rollback as well as a successful save.