Comala Workflows 5.1.0
Comala Workflows 5.1 is a feature update release.
Customizable State Colours
States can now be given their own custom colours. Using the Workflows Mark-up Editor you can set the color of your states to be nearly any shade, provided it is available as a hexadecimal value.
colour parameter on the state macro for more information on this new feature.
Approval Action Labels
Approvals can now be given custom action labels. Replace the standard "Approve/Reject" with custom labels such as "Agree/Disagree", "Yes/No" or any combination that fits your workflow's needs.
Refer to the approval macro and the new
rejectlabel parameters for use in your workflow markup, they allow you to change the default labels. At this time the labels are only applied in the user interface; when you view the workflow activity reports the default action names will still be applied.
Other Updates and Bug fixes
- Fixed a error when using the admin override state selection option in some situations.
- We've updated the way we validate the people who can be assigned to an approval, so it is now case insensitive when checking the user name.
- The page update reset approval setting was not saving correctly when applied on a space by space basis, this has been fixed.
- Globally linked workflows will now respect the condition to only be active on blog posts.
- A bug with the set-message macro (introduced in the 5.0.5 release) that prevented the message being shown on the approved version of a page has been fixed.
- Various minor UI tweaks and updates as we continue to get feedback about the new look first launched in the 5.0 release. We've also tweaked the design of the filters on the page activity report. There is a minor known issue here with layout of the activity filter buttons due to the UI changes in Confluence 6.7. We'll have a fix for that in the near future.
Developer and Integrator Updates
We have a few changes for people integrating with Comala Workflows in this release.
Java API Changes
As part of this feature release we are changing the way we package and release the Java API library.
- The API library will now be released each time we release a new version of the Workflows App. This will allow external developers to know exactly which version of the API library they should be targeting for compatibility with different releases. (Don't worry we still plan to keep the same deprecation timelines and package naming so earlier versions should continue to work as they do now.)
- Maven dependency name change,
workflows-apiso the API finally catches up with the rename of the core product.
- We've deprecated a few methods in the API library related to searching for content. Some of these are old and don't work quite correctly right now anyways. Moving forward our plan is to provide as much functionality as possible via the CQL interfaces so how you interact with Workflows is the same as other searching for other Confluence content
Our getting started page has been updated with the new maven settings if you want to jump straight to the new version.
New CQL Fields
We have added new CQL search fields to find content that has workflow tasks assigned to a specific user. Also a new has workflow field to help find content that has any workflow applied, not restricted to search for a specific state name.