Support for field set in Workfront Custom Forms

How it should work:

I would like see field set or container of multiple fields which the user can add multiple times when filling the form. The field logic inside the field set should be self sufficient, which means that when I select a select a value in drop down in instance 1 of the field sets, the fields of instances 2-n are not impacted.

The field set should be like a repeatable subform in form. I don’t know if you can make a section repeatable as it it already a container of fields.

What it should solve:

We had multiple time the situation that we have to add the same combination of fields to the same custom form.  Here is two examples from our project history:

1. Service and Complaints Management (Request), where you have to add add multiple times for same information. E.g:

• SKU (External Lookup Fields)
• Count (Textfield with Number)
• Failure Type (Drop Down)
• Failure Description (Textarea, but only showed when specific Failure Type was displayed)

We ended up adding the same fields multiple and used logic to control the number of fields which were displayed.

2. Using Workfront Projects and Tasks to model Campaign data so that they can be approved by management:

• Campaign (Project)
  • Target Audiences (Task Level 1)
    • Activities (Task Level 2)

The custom forms of the project and tasks contained the detailed information for each element.

Why not use Workfront Planning:

I hoped that Workfront Planning can solve this issue, but I see seven problems:

1. You can’t add approvals on entries when they are changing stages. Important for regulated industry)
2. You can’t set permission on a specific entry like you can do on projects. (Important for regulated industry)
3. While you can create 1-n connections in Workfront Planning and also directly change them in the connected page view (great solution), you would give the user full access to the connected entity to create the connected entites.
4. Lookup fields for connected entities, projects or assets which contain multiple values are really hard to read in the table view.
5. No logic for skip, display or validation on the details view.
6. While Workfront Planning has a custom form, it has the same and more limitations as the normal Workfront Custom Forms. It is also limited to properly handle requests like queue can.
7. Licensing/costs

Similar problem in AEM and how it was solved:

In AEM had the same problem and the community developed so called nested multi fields:

https://aemhints.com/2020/10/24/coral-nested-multifield-aem65/