I would like to thank all of you who downloaded and tested the first 6.4 RC. I would like to introduce the 6.4 RC3, and it should be the last RC before the final release of 6.4. As you can imagine, we are very excited at Bonitasoft, and our R&D and consultant team are doing intensive testing to ensure that everything will be fine. And your
help is still well appreciated ;-)
I am pleased to introduce Philippe Ozil, our new Technical Evangelist. Philippe has been a consultant for Bonitasoft since 2010 and he has been involved in more than 80 customer projects. He knows Bonita BPM more than very well ;-)
In order to start his new mission with some useful content, Philippe just gave a very interesting webinar: "Integrating AngularJS with Bonita BPM".
It has been recorded and is available on our French corporate website. There will be two other webinars on the same topic:
I am sure that most of you know what is Open Source: a bit of history, and how it works for Information Technology. But, what if you would have to explain what it is with some day to day life examples? Skateboarding with friends, building a house?
Well, at Bit Blueprint , they though about that, and did a very good video that explain Open Source in a very simple way. Something you might want to share with your friends and family, to help them better understand what you do.
When executing UI tests, such as SWTBot tests, when a test fails some popups might stay open and cause subsequent tests to fail. Even worse, the whole test suite execution can take longer than usual because all the following tests might fail after waiting for a timeout (of 5 seconds by default). It will also kill the visibility of the scope of impacted components.
To make sure you have UI tests that will evolve seamlessly with UI naming modification, use the Internationalized String and not the hardcoded value of text displayed in the UI. Even if hardcoding seems simpler at test writing time!
Here's how you can implement it with SWTBot and NLS.
We would like to inform you about an issue found in version 6.3.4 and 6.3.5 that impact the Studio environment.
On the Connector wizard, the default behavior of the "If connector fails..." information has been changed from "put in failed state" to "ignore error and continue process". As a consequence, importing a process or migrating a workspace from a previous version may change the behavior of your processes.