Release Notes / Version 12.2406.0
Table Of Contents
Access to
/Settings/Options/Settings/WorkflowValidation had
some issues, that we fixed. Changes can be summarized as:
Rights Issue: If editors did not have rights on settings documents within
/Settings/Options/Settings, they experienced, for example, the workflow validation to never end loading when trying to start a workflow. This has been fixed.Publication Limits: Limits for publication validation could not be adapted as configuration within
WorkflowValidationsettings, as it caused an error. This has been fixed.Documentation: Documentation for
WorkflowValidationsettings has been straightened and missing parts got added. Corresponding updates have been applied to the Studio User manuals as well as to the Studio Developer Manual.German Localization: If limits got adjusted editors may have experienced warnings about limits reached within the Start Workflow Window containing badly formatted numbers or even “NaN” (Not a number). This has been fixed, the localization got aligned with the English localization.
Disable Validation: The option to disable the validation completely was inoperable. This has been fixed. The corresponding setting moved from
/Settings/Options/Settings/WorkflowValidationSettingsto/Settings/Options/Settings/WorkflowValidation, so that all validation settings are at a central place now. Note, though, that disabling validation should only be applied in exceptional cases. More details to be found in the manuals.
As part of addressing these issues, the former configuration structure had to be updated from:
{
"limits": {
"translation": {
"maxDepthToCompleteChangeSet": null, // type: integer
"limitForDependentContentItems": null, // type: integer
},
"publication": {
"maxDepthToCompleteChangeSet": null, // type: integer
},
},
}
to a new structure:
{
"disabled": null, // type: boolean, not part of Blueprint content
"localization": {
"maxDepthToCompleteChangeSet": null, // type: integer
"limitForDependentContentItems": null, // type: integer
},
"publication": {
"maxDepthToCompleteChangeSet": null, // type: integer
},
}
For compatibility reasons, the old settings structure, thus, for
example,
limits.translation.maxDepthToCompleteChangeSet will
still work, but the new settings, if set, take precedence.
Upgrade Steps:
It is not required to take any action on upgrade, as the previous
structure of
/Settings/Options/Settings/WorkflowValidation will
still work. You may want to think about adapting it to the new
structure as described above, though.
As the Blueprint Test-Data document
WorkflowValidation.xml got updated to reflect the
new structure, you may experience merge conflicts to resolve, if you
happen to have adapted this content in your workspace.
(CMS-23308)
