Check out what's new regarding the configuration of dependencies between items in a checklist. Among the improvements, we have:
- Dependencies can be configured between areas and subareas;
- Interface improvements for better visualization.
What's New in Dependency Configuration
It is now possible to configure dependencies to be triggered between areas and subareas.
This way, it will be possible for an item in a first area to unlock one or more items in other areas/subareas, or even an entire area/subarea.
Operating Rules
Below are the new operating rules for dependencies. The dependency can:
- Unlock a complete area subsequent to the parent item's area;
- Unlock a subarea subsequent to the parent item's subarea, provided it is at the same area level;
- Unlock an item provided it is within the same subarea and area.
Important behaviors: • It is mandatory that the parent item of the dependency is of the Evaluative or Selection List type; • More than one response can be configured to unlock the child item, area, or subarea; • The child item of the dependency cannot have two parent items.
Interface Improvements
We made adjustments to facilitate the visualization and interpretation of the dependency configuration, with new icons to demonstrate:
- The parent item, which has configured dependencies;
- The child item that also has its own dependencies;
- The child item, which is dependent.
These icons will also be represented in areas and subareas, to identify which of these are dependent.
Frequently Asked Questions (FAQ)
1. Can I configure an item to unlock an entire area?
Yes, the dependency can unlock a complete area subsequent to the parent item's area.
2. Can an item have two parent items?
No, the child item of the dependency cannot have two parent items.
3. Which items can generate dependencies?
It is mandatory that the parent item is of the Evaluative or Selection List type.
❓Tem dúvidas? Entre em contato com nosso time de suporte.