Release Notes / Version 13.2512.1
Table Of ContentsChanged Workflow Validator Configuration
The concept of configuration of workflow start validators has been
revised to ease configuration of project-specific validators. Instead
of a static list of validator bean names (Spring properties
studio.workflow.validation.start-validators.*),
validator beans are now annotated to be evaluated by an established
Spring mechanism. Should you have customized workflow start validation
in your project, see Studio Developer Manual,
section Customizing Validation of Built-In
Workflows for details on the new configuration concept.
Publication Workflow Validator for Navigation Hierarchy Consistency
A new validator NavigationParentValidator has been introduced for publication workflows. It helps editors in keeping the navigation hierarchy consistent on the live side. Consistency means that
no navigation node is orphaned, i.e., has no parent (except for a site’s navigation root), and
no navigation node has two or more parents.
While this validation checks consistency for new publications, it cannot correct already present inconsistencies on the live side. These need to be corrected manually by withdrawing orphaned navigation nodes or publishing missing changes on parent nodes, respectively.
In certain situations, the validator does not issue an ERROR but a WARNING. This happens when a consistent navigation may rely on withdrawal of contents. As this cannot be done in a publication workflow, it must be performed as a follow-up task in Studio. Editors may thus sometimes publish changes to the navigation that will leave the live side in an inconsistent state temporarily. They are responsible for performing the necessary follow-up withdrawal as soon as possible to re-establish navigation consistency.
Upgrade Information
Should you have customized workflow start validation in your project, see Studio Developer Manual, section Customizing Validation of Built-In Workflows for details on the new configuration concept.
(CMS-25431)
