Plan a page change

What you will learn

Turn a request for a page change into a short, reviewable specification.

Prerequisites: choose a tailoring approach. This lesson is a planning exercise; it does not require opening Page Designer.

Understand what Page Designer does

Page Designer can adapt the layout and behavior of configurable application pages. Examples include changing labels, moving or hiding fields, and adding supported elements. Page changes are associated with a configuration context. Capabilities can differ between regular pages, dialogs, and assistants.

See the official Page Designer introduction for the reference release. We will add a click-by-click tutorial after testing a defined environment.

Describe a small change

In our fictional scenario, a coordinator repeatedly overlooks a field. Instead of “redesign the page,” propose one change and state why it should help.

Use this structure:

Page change brief

Person: Who uses this page?
Task: What are they trying to finish?
Current difficulty: What is hard to find or understand?
Proposed change: What single change should we evaluate?
Scope: Which page and configuration context are involved?
Success: What should a reviewer be able to do afterward?
Recovery: How will the practice configuration be restored?

Do not put a real customer name or confidential record into a public learning example.

Try it yourself

Write a change brief for moving an existing field closer to related information. Identify what you still need to confirm before implementation.

See a suggested answer

“A coordinator needs to locate a reference while reviewing a record. We propose grouping that field with related information. Before implementation, confirm the page supports the change, the intended context, the test role, and the restoration procedure. Success means a reviewer can find the reference without being coached.”

Check your understanding

The brief should identify one change and an observable result. Ask a colleague to explain the requirement back to you. If their interpretation differs, refine the brief.

Common mistake: assuming a layout change controls data access. Treat access requirements as a separate concern for the responsible administrator to evaluate.

Cleanup: none for this written exercise. A future hands-on lesson must include its own tested restoration steps.

Source and review status

Reference: IFS Cloud 26R1 Page Designer introduction. This is an unreviewed concept draft, not an environment-tested walkthrough.

Put this into practice

Use the configured-field procedure for a worked example with page placement and save/reopen checks.