The Section widget

1. What is a Section Brick?

The Section Brick is a tool used to organize your forms by creating hierarchies and grouping sets of tasks that belong to the same category. This allows for a clear and logical structuring of tasks.

Example:

Section 1: Start of intervention.
Section 2: Motor check.
Section 3: End of intervention.

2. How to create a section?

To create a section:

Drag and drop the Section Brick into the body of the form.
Integrate the different bricks (tasks, sub-sections, etc.) that will make up this section.

Sections and their bricks are numbered to reflect their position in the form's hierarchy:

A main section is assigned task number "1".
The bricks inside will be numbered 1.1, 1.2, 1.3, etc.
If a sub-section is added within a section, its bricks will be numbered 1.3.1, 1.3.2, 1.3.3, etc.

3. What is the difference between a section and a block?

It is possible to convert a section into a block.

Just like the section, the block allows you to structure your forms. However, unlike sections, during their intervention, the technician will not have to click on the block to see the tasks it contains.

💡

Notes

To load all data of a section without the operator entering it, all bricks contained in the Section Brick must be Task Bricks.
Additionally, all options "Allow editing in the application" must be disabled for each brick. For the Section Brick, you will only be able to retrieve the tag: title of the brick (e.g., ##reftasksection:title##).

4. Hidden Section – Limitations

A hidden section is not displayed by default in the mobile application.

It constitutes a separate screen, without automatic loading of the form’s global context.

In practical terms, a hidden section:

Does not load its context as it is opened.
Does not automatically retrieve dynamic form data.
Functions as an independent “new page”.

This has a direct impact on certain automatic mechanisms.

❌

Non-functional elements within a hidden section

The following elements may not work or may behave unexpectedly within a hidden section:

Current Date & Time: Since the section is not loaded, there is no loading timestamp.
User attributes: No user loads the section, therefore the system cannot determine which user attributes to access.
Job attributesWhen intervention attribute updates are configured in real time, the hidden section is not loaded and dependencies do not execute as expected.
Automatic selection: Automatic selection mechanisms do not run until the section is opened.

Conclusion
Using a hidden section as a logical space to group tasks while maintaining active dynamic mechanisms is not compatible with the mobile application logic.
If the objective is purely organizational (grouping tasks without dynamic links to other elements for easier administration), a hidden section is appropriate.
However, if the requirement involves dynamic or conditional behavior in mobile, an alternative configuration approach should be considered.