A Workfront developer is tasked with building a new custom form to collect project requests. The form will display different sets of options based on…

When building a custom form with conditional logic, a developer must understand the default behavior of fields and the limitations of the logic types. By default, all custom fields added to a form are visible unless a specific display logic rule is created to hide them. This is a foundational principle for the developer to consider when deciding which fields need rules. Additionally, it is a critical technical limitation that skip logic cannot be applied to non-input elements like widgets or section breaks; it can only target fields. This directly impacts how the developer must structure the form to achieve the desired conditional navigation.

A. When a custom form is copied, all associated display and skip logic rules are copied with it, which is contrary to the statement.

B. When bulk editing, fields hidden by display logic are displayed in the edit dialog, as the logic cannot be evaluated across multiple, potentially different, objects.

1. Adobe Workfront Documentation, "Add display logic and skip logic to a custom form."

For Answer C: In the "Overview of display logic" section, it is stated: "By default, all fields, widgets, and section breaks you add to a custom form are visible to users." This confirms that fields not included in a display logic statement are shown by default.

For Answer D: In the "Skip logic" section, a note explicitly states: "You cannot apply skip logic to a widget or a section break." This confirms the limitation.

2. Adobe Workfront Documentation, "Copy a custom form."

For Incorrect Option A: The article states, "When you copy a custom form, any display and skip logic on the form is also copied." This directly refutes option A.

3. Adobe Workfront Documentation, "Edit information for multiple projects in a list."

For Incorrect Option B: Under the section "Understand how custom forms work with bulk editing," it explains: "Fields that are revealed by display logic in a custom form are always displayed when you edit objects in bulk using that form." This refutes option B.