Text Enhance moves from icon/menu to in-field button in 2026.1

In 2026.1, the Text Enhance entry point on text area and rich text fields is changing from the existing Enhance Text icon and menu to a single button rendered in the lower-right corner of the field. The stated goal is discoverability of the AI-powered actions.

What changed

• The Enhance Text icon and its associated menu are removed from text area and rich text fields.
• A new button replaces them in the lower-right corner of any field that has Text Enhance enabled.
• Clicking the button executes the field's default Text Enhance action — typically Clean up, or Generate where the field supports generation.
• An arrow on the button opens a dropdown with the remaining actions: Clean up (when Generate is the default), Translate to, Make Longer, Make Shorter, and any custom Text Enhance actions configured in the account.

What is not specified

The release note is UI-only and does not name any affected records, scripts, APIs, or governance changes. In particular, Oracle does not document:

• Whether the button is rendered for custom fields of type Text Area / Rich Text on custom records, or only on standard records.
• Whether SuiteScript-injected fields (e.g. serverWidget.FieldType.TEXTAREA / RICHTEXT on Suitelets and UserEvent beforeLoad forms) get the button automatically.
• Any DOM/CSS changes — if you have client scripts or browser automation that selects on the old icon/menu markup, expect breakage.
• Any changes to the underlying Text Enhance permission, feature flag, or supported-field list.

Verify each of these in your sandbox before 2026.1 hits production.

What to do

1. Audit client scripts and customizations that interact with text area or rich text fields. Anything keying off the old Enhance Text icon's selectors, classes, or menu structure will need to be updated to target the new button.
2. Test browser automation and end-to-end tests (Selenium, Playwright, Cypress, RPA flows) that click into or around text area fields — the new button changes the lower-right hit area of the field.
3. Re-test custom Text Enhance actions defined in your account to confirm they still appear in the new dropdown.
4. Check accessibility — if you maintain a11y standards, validate keyboard navigation and screen reader labels on the new button before rollout.
5. Update internal documentation and training for users who were taught to look for the icon/menu.

Migration impact

No SuiteScript, SuiteTalk, SOAP, REST, or record-schema changes are described. This is a presentation-layer change only. Code-level impact is limited to anything that depends on the previous DOM of the Text Enhance control.