With this release, we are bringing advanced workflows along with version branching to Core dna. We additionally launch the first phase of our forms improvements, allowing further customize your forms.
Version branching
Ever wondered what has changed in a previous content version, or when a certain change was introduced? With branches, we now give you the power to structure your content versions by grouping them together into named branches, making it much easier to navigate through previous content versions.
Customizable workflows
Want to have your content reviewed by QA or your legal department first before it is shows to visitors? Customizable workflows allows you to create individual steps content has to go through, and even customize possible transitions between these steps. Transitions can be limited to certain user groups or to require prior approval, and notifications for content reaching a certain workflow steps can automatically be sent out through email and admin panel notifications, making it easy to keep up to date with the status of your content. Furthermore, workflows support hook automations, allowing you to integrate them into your own processes - for example to send get notified via Slack or Teams. For an example on how to set up workflows, we've prepared a video for you:
Content drafts
During content editing, our system automatically saves drafts of your progress. In the past, it was not that obvious that you were editing a draft, and this draft can potentially have been created by other editors without you noticing. Now, drafts are user specific, and you will only automatically get to see the draft of a page if you have created it. Draft ownership is also made more obvious in the version history. Additionally, we now make it much more obvious that a draft version is being edited by showing a banner at the top.
Version updating
In the past, content versions could only be created, but never altered after their creation. Editor would this either create a lot of versions, making them hard to navigate, or would have to stick to the draft which could be overwritten by somebody else. Now, we support updating content versions. For all content that is not shown on the page yet (as active revision), existing versions can be updated by the user that created them.
Explicit active revisions
Following the new possibility to update content versions, we additionally made it more obvious to users when content will be shown to visitors. The save button for versioned content now allows you to explicitly choose between different actions: You can either Save and activate a version, displaying it to visitors, or just choose Save new version to keep working on your content before making the changes visible.
Forms improvements
- Support for layout areas for forms, allowing you to add any type of content to your form, and including custom entities
- Every input field now supports custom CSS classes, further allowing you to customize the look and feel of your forms
- Possibility to re-order options of select fields through drag and drop
- Richtext editors in forms will now use the same configuration as other richtext editors, allowing you to sanitize content, use custom lists and styles and more
- Placeholders can now be specified for select fields as well
- Hidden input fields can now also be validated
- The Date/Time input fields have received an update to allow specifying a minimum and maximum date, which will get validated on form submission