Additional Workflow Fields

Additional WorkflowFields are no longer added to the AdditionalWorkflowFieldsContainer . Now, they can be placed anywhere in a StartWorkflowForm or a WorkflowForm and will be automatically registered by the workflow framework.

All default implementations of WorkflowForm and WorkflowStartForm provide a new convenience property additionalFields where you can simply add your additional workflow fields. Fields, placed in that array will appear underneath the Workflow-Type chooser in a new area.

Additional workflow fields can now also write in process variables when a workflow is running.

Additional workflow fields are now implementations of the IAdditionalWorkflowDisplayFieldMixin or IAdditionalWorkflowInputFieldMixin . IAdditionalWorkflowField and IAdditionalWorkflowDisplayField do no longer exist anymore. All the already existing additional fields have been changed to the new API. If you have a component implementing IAdditionalWorkflowField you need to change it to IAdditionalWorkflowInputFieldMixin , for IAdditionalWorkflowDisplayField , you need to use IAdditionalWorkflowDisplayFieldMixin .

Be aware that implementations of a mixin have to declase all methods that are not overriden as native !

Workflow Validation

The workflow validation framework was enhanced to also provide access to the values, entered in an additional workflow field. To understand how to access the values of custom additional workflow fields during a workflow validation, please consult the Studio Developer Manual in section 7.22 Customizing Workflows .

Furthermore the way, how WorkflowValidators are added to a workflow has changed. Now, it is necessary to provide a so called WorkflowValidatorsModel which gathers all workflow validators for one workflow. This can also be found in the Studio Developer Manual in section 7.22 Customizing Workflows .

As a result of this, the WorkflowDateTimeField no longer has the properties onlyValidWhenLiesInFuture or allowBlank . Instead this can be handled with the DateLiesInFutureValidator or other custom WorkflowValidators. Also the defaultTimeFunction is no longer called with a bean that has to be filled anymore, but must return a Calednar Object now

Additional fields and the new workflow validation mechanism are now both available for publication and translation workflows.

(CMS-13798)