Details
-
Improvement
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
1.02.04
-
None
-
None
-
5
-
Essentials Plugin SDK, 7.10 compliance sprint 2
Description
After installing the Selections feature the next step is adding the Spring config for the Valuelist Manager. Only after that installation step it is possible to configure the selecions fields and add them to existing document types.
Switching the last two steps seems to make more sense. First let the developers add a Value list and configure a field in a document type to use that list. After that it makes sense to add the valuelist manager config. That can then be populated with the existing valuelists too. Can the feature detect that new valuelists have been added to document type config or old ones have been removed? Then that can trigger the rebuild step for it.
Attachments
Issue Links
- relates to
-
ESSENTIALS-502 Selections plugin will become a default dependency as of archetype 7.10
- Closed
-
HIPPLUG-1015 Selections: Add utility to retrieve ValueList
- Closed