UI/UX: Could the condition be managed through editing the form?

[sorenmalling]

Use case:
We are evaluating the the condition extension for a current project.
The editor creates a condition container in the same folder/site as the form is created.
Today a editor asked why the two conditions didn't work - but only one of them.
The editor created two separate conditon containers, and chose the same form in both records.
The initial ajax request only selects one, so one of the condition containers would not be respected.

Proposal:
This made me think about, if the conditions could be managed from within the form editing.
As a number of inline records similar to "pages"

Acknowledge the difference:
The conditions relation to the form lives through the condition containers "form" column.
This "glue" will be directly attached to the condition row it self with a change like this

Love to hear feedback on the proposal and if it would be something to look into doing a POC for

[julianhofmann]

I agree that improvements are needed in UI/UX, and I wanted to create an issue for this.

However, I don't think your idea of adding the condition containers inline to the form is a good approach. With extensive forms or conditions, it will become even more confusing.

---

[FEATURE] Visualisation of Conditions in backend

Current behavior / Backend views

At the moment, there are two ways to view the conditions:

1. via list view
2. via editing the condition container

via list view

Advantage

• very compact display

Disadvantage

• Record-based, i.e. you cannot see the specific rules in the container, for example.

via editing the condition container

Advantage

• The structure of rules and their consequences/effects is recognisable.

Disadvantage

• IRRE/inline data display makes it confusing when there are many conditions

Goal

The extension provides a back view that gives an overview of conditions, rules and affected fields.
The edit function is still mapped to the TYPO3 standard form; the view merely provides the entry point/link for this.