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 different selections, which requires the use of display logic and skip logic in the form.
What are two considerations the developer should take into account when building the conditional logic in the form? (Choose two.)
- When copying an old form with display logic or skip logic, the logic is not copied to the new custom form.
- When editing objects in bulk, the custom fields display in the Edit objects box. excluding the fields that are skipped or hidden
- Custom fields not included in a display logic statement show on a custom form by default.
- Skip logic does not work with a widget or section break in the form
Answer(s): A,D
Explanation:
When building a custom form in Adobe Workfront that uses display logic and skip logic, developers need to consider the following:
When copying an old form: If you copy an existing custom form that includes display logic or skip logic, these logic settings will not be transferred to the new form. The logic needs to be manually recreated in the new form to ensure it functions as intended. Skip logic limitations: Skip logic does not operate effectively with certain elements like widgets or section breaks within the form. This limitation means that skip logic cannot be applied to control the visibility or behavior of these elements, potentially impacting how the form is structured and functions.
Reference
These considerations are detailed in advanced reporting and form customization documentation and have been highlighted in various Workfront admin training sessions.