# What's new in User Experience '26: Add and configure complex fields directly in the View Rule form

**URL:** <https://forums.pega.com/t/whats-new-in-user-experience-26-add-and-configure-complex-fields-directly-in-the-view-rule-form/13826>\
**Category:** User Experience\
**Tags:** pega-knowledge\
**Created:** [October 20, 2026, 12:30pm UTC](https://forums.pega.com/t/whats-new-in-user-experience-26-add-and-configure-complex-fields-directly-in-the-view-rule-form/13826 "2026-10-20T12:30:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![popaa](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@popaa](https://forums.pega.com/u/popaa)\
**Post date:** [October 20, 2026, 12:30pm UTC](https://forums.pega.com/t/whats-new-in-user-experience-26-add-and-configure-complex-fields-directly-in-the-view-rule-form/13826/1 "2026-10-20T12:30:07Z")

</div>

Complex fields — references, embedded data, queries, locations, attachments — have always been the ones that send you somewhere else to finish the job. In ’26 they are configured where you are already working.

**What it means**

You can add and configure all complex Field Types directly in the View Rule form, without navigating to separate supporting Views. The View Rule becomes a unified authoring interface rather than a starting point that hands off.

Bundled with it is a second, less obvious improvement: query list fields and reverse reference fields now support a full, consistent set of read-only table features in the full object display of Case and Data objects.

**What it does**

- **All complex Field Types in one form.** References, Embedded Data, queries, locations, and attachments are configured in place.

- **Live preview.** You see the result of the configuration as you build it.

- **Local actions in read-only tables.** Actions such as Create are available from query list and reverse reference tables.

- **Automatic context passing.** Reverse reference fields pre-populate the correct field using context obtained from the field Rule, so the user is not asked to re-state something the system already knows.

**How it works**

The enhancements are enabled by default and require no configuration after you update. Open a View Rule and the complex Field Types are available to add and configure there.

**What to remember**

- **Automatic context passing is the detail that changes user experience.** A reverse reference field that pre-fills the linking field removes a step where users previously made mistakes. It is worth checking this behaves as you expect in your own model.

- **Consistency is the real deliverable.** Query list and reverse reference tables now behave like other tables. Users stop having to learn per-table exceptions.

- **No configuration, no update impact.** On by default, existing Views unaffected.

**📖 Technical documentation:** [Configuring fields in the UI](https://docs.pega.com/bundle/platform/page/platform/user-experience/configuring-fields.html)