Bonita Open Solution version 5.6.1 is available for download – not really news, but hey, it’s a new year!
Usually our minor releases are maintenance releases only, but this time we’ve fixed a bunch of bugs and improved some annoyances to make using Bonita Open Solution just that much more user-friendly. (And - we’ve made some changes to the database schema that require a migration. See below.)
What version is this?
Have you upgraded more than once? If you’ve lost track of which BOS version you are using, you can now peek and see – whether you are in Bonita Studio* or in Bonita User Experience.
Dang it, this variable doesn’t belong here
BOS 5.6 allowed you to promote a variable from local (task level) to global (pool level). You can now move a variable from one task to another.
Data mapping is a snap!
Use best practice naming conventions for your variables, and mapping them between a parent and sub-processes just got a lot easier.
How do you say this in Java?
BOS displays the Java type associated with each variable type to make choosing the right variable type easier. (It may be an integer to some, but it’s a Java.lang.Long to the process developer…)
What is my connector returning?
Test it to see and browse its output.
Pick a date
The date field in an end user form now offers a date picker.
And…
- In the BOS Teamwork edition
- In the BOS Efficiency edition
*scroll all the way down to the bottom of the page
Migrate
We’ve also done some tinkering with the Bonita Execution Engine to fix an event related issue in the clustering environment. That means a migration from BOS 5.6 to BOS 5.6.1.
If you’re still using BOS 5.5 and are ready to upgrade, you can migrate directly to BOS 5.6.1.