Third Quarter 2026 Administrator enhancements

This page describes Administrator enhancements made with the Third Quarter 2026 release to the Preview environment. These enhancements will be made available in the Production environment as noted.

For a list of all changes available at this point in the Third Quarter 2026 release cycle, see Third Quarter 2026 release overview.

New license type fields for Access Levels

We have made the following field changes in the Access Level box:

Internal lookup field replacing Typeahead field type

The new Internal lookup field type in custom forms provides dynamic filtering. It is similar to the Typeahead field type and allows users to search and select existing Workfront objects by typing part of the name. The filter on the internal lookup can reference the value in another field on the form, which is not possible with Typeaheads.

Multi-select is supported on internal lookups, and this field type also provides improved performance for large datasets. The following native Workfront objects are supported in internal lookups: Project, Company, Group, Job Role, Portfolio, Program, Team, Template, User, Task, Issue, Document, and Location.

The Internal lookup field type is replacing the Typeahead field type. You can quickly convert existing Typeahead fields to Internal lookups by clicking the button in the field options on the right. When you convert, historical data remains on the field and it is used the same way in reports.

For more information, see Create a custom form.

Default value logic supported on native reference fields

In custom forms, native reference fields now allow you to add default value logic.

This logic type on native reference fields is available only in the user interface and not in the Workfront API.

For information, see Add default value logic to a custom form in the article Add logic rules to custom forms and fields.

Updates to native field filtering in custom forms

System filters that exist on native fields are now applied to the fields in custom forms and are visible to administrators.

When you add a native reference field that has a system filter applied, you can apply the same filter to the field in the custom form and modify the filter if needed in the Text Mode box.

Adding your own custom filter to the field overrides the system filter for the field. If you do not enter a custom filter, the system filter is applied by default.

Also, dynamic filtering is now available on native reference fields. A dynamic filter allows you to narrow the list of items based on the value of another field.

For example, when you use ?portfolioID={portfolio}.{ID} in a Project field filter and a Portfolio native field is on the custom form, the Project field shows only projects that are in the selected portfolio. If the Portfolio field is left blank, then all projects are available in the Project field.

For information, see Create a custom form.

Protect field names from accidental renaming

To protect integrations and data integrity, we’ve updated how field names can be edited in the field settings panel of a custom form.

Field names in the field settings panel are now read-only by default. You can still edit the field name, but renaming requires an explicit confirmation step. The field previously called Name has also been updated to API Name to better reflect its technical significance. The Label field remains editable.

For information, see Create a custom form.

View change history for Workfront objects

To make it easier for you to see the changes that have occurred in one central list, we’ve create the Change History List. This list displays information such as the object, the operation, and the source of the change (such as a user or the Workfront system).

Previously, Audit logs were available but did not cover objects.

For more information, see View and manage change history.

New system preference to convert legacy storage portfolios to Adobe cloud storage

Workfront administrators can now convert legacy storage portfolios to Adobe cloud storage directly from System Preferences. To convert portfolios, select them in the new Select portfolios to convert to enterprise storage field and save the page.

When a portfolio is converted to Adobe cloud storage:

Previously, adding an Adobe cloud storage project to a Legacy storage portfolio automatically converted the portfolio to Adobe cloud storage.

For more information, see Configure system preferences.

Rich Text replacing Text with Formatting field type

The new Rich text field type in custom forms is a robust text editor, with formatting options such as superscript and subscript, headings, and tables, in addition to the traditional options of bold, italics, underline, bullets, numbering, hyperlinks, and block quotes. The character limit remains 15,000.

The Rich text field type is replacing the Text with formatting field type. You can quickly convert existing Text with formatting fields to Rich text, by clicking the button in the field options on the right. When you convert, historical data remains on the field and it is used the same way in reports.

For more information, see Create a custom form.

Native financial fields supported in custom forms

You can now include Workfront native financial fields in custom forms. Previously, the financial fields were not supported.

The available financial fields that you can reference depend on the type of form.

For more information, see Create a custom form.

Custom forms can be shared system-wide with access to attach

A new sharing option, “Everyone in the system can view and attach,” has been added to custom forms. When you select this option, all users system-wide can attach the form to other objects.

Sharing system-wide eliminates the need to manually share forms and update permissions across groups or agencies when new groups are added.

For more information, see Share a custom form.

New system preference to enforce required fields in bulk edit

Currently, when bulk editing objects, required fields are only enforced when a user modifies the field. If a field is not modified, it is treated as optional and not validated.

A new system preference now allows you to enforce required fields in bulk edit. To not allow bulk edited objects to be saved unless all required fields have values, select the option Always enforce required fields in bulk edit on the Setup > System > Preferences page.

For more information, see Configure system preferences.