Bonita Changelog

What's new in Bonita 2023.2-b2 Beta

Nov 4, 2023

Self Contained Application (SCA):
Build, package, run, update. SCA is the new differentiating deployment mode of Bonitasoft is ready to go live and in production. By embracing the latest containerization approach, users will experience faster deployment times, allowing your IT team to respond rapidly to business needs.
In 2023.2 version, we will keep the platform mode in parallel with the SCA mode which is Bonitasoft’s recommendation in order to correspond to market standards from an application development point of view. It is simply deprecated because we want to highlight the new SCA mode. Platform mode allows you to generate an application which will then be launched on an existing Bonita runtime, while SCA mode allows you to build an application which integrates a runtime and can therefore be directly launched. Our dedicated team will be here to guide you through this new updated mode, answer your questions, and provide the assistance you need.
User sharing session mechanism between nodes:
Service continuity is a key element of operational performance, so we are introducing a new native capability to help to ensure access to applications. Even when a node experiences downtime, users will remain seamlessly connected and will be able continue working without interruptions, ensuring smooth operations and increased user satisfaction.
Test toolkit V2:
Ensuring effective testing by keeping track of the scope performed and identifying errors is a real concern for our developers. To support this, a test report is generated, which is adding a visual representation of the test sequence directly on the BPMN diagrams. This provides a clearer and more intuitive way of tracking progress, collaborating effectively and aligning with business/process owners. A concrete step towards shorter iterations and streamlined project tracking.
Maintenance page/service interruption notification:
Our latest feature designed to be proactive and keep users informed/prepared of service interruptions. A new kit to build info page on service maintenance and page interruption to notify users and ensure a smoother and more predictable experience.
New product values:
Bonita Runtime:
User session sharing between nodes (Cluster):
When configuring a Bonita cluster (Enterprise and Performance editions only), HTTP sessions are now shared between all the nodes of the cluster. As a result, the load balancer no longer needs to be configured to use sticky sessions. If a node becomes unavailable, and a user request to this node fails, the user won’t need to log back in as their session will remain active. The load balancer will dispatch the new requests to the other nodes.
Maintenance mode:
A new 'Maintenance mode' replaces the 'pause/resume BPM services' feature.
The behavior when activating this mode is the same as what was happening when pausing the BPM services (making the BPM and BDM services and API unavailable to users aud pausing the scheduled work while updating the platform, BDM, apps, etc…) except the user sessions are no longer destroyed. A 'Platform under maintenance' 503 error page is displayed instead. Like the other Error pages, this page is part of Bonita App Directory application and can be modified with Bonita UI Designer.
In Bonita Super Administrator Application, the page 'BPM services' has been replaced with a new 'Platform maintenance' page allowing to activate/deactivate the maintenance mode and set a scheduled maintenance message to inform the users that a maintenance is scheduled and the platform will not be available for a while. This message, when activated, appears in Bonita Layout, as an alert header that can be hidden and in the user details modal. It also appears on the Maintenance page (503 error page) during the maintenance operations.
To benefit from this feature when updating to Bonita 2023.2, it is required to use the provided Bonita layout or to re-base your custom layout modifications on the provided Bonita Layout.
At REST API level, when the maintenance mode is active, the BPM and BDM API (except BDM installation) will respond with a 503 error. Bonita UI Designer pages now handle this error code and display a modal dialog informing the users of the running maintenance and proposing to redirect them to the maintenance page. To benefit from this feature when updating to Bonita 2023.2, it is required to migrate existing pages by migrating your apps using Bonita Studio 2023.2.
Exit on error:
When starting a Bonita application, if an error occurs during the startup phase, the process will now exit with an error status code (1).
Default log pattern with color highlighting in console output"
The default log configuration enables color highlighting in the console output.
Development suite:
Bonita UI Designer:
Session timeout and Maintenance handling:
Bonita UI Designer pages now handle 401 and 503 errors for requests to Bonita REST API and display a modal dialog informing the users of the invalid session (401) or the running maintenance (503) and proposing to redirect them to the login or maintenance page. By clicking on cancel in this dialog, the users can remain on the current page (to not lose unsubmitted form content) and log in in an other tab to renew their session or wait for the maintenance to end.
To benefit from this feature when updating to Bonita 2023.2, it is required to migrate existing pages by migrating your applications using Bonita Studio 2023.2.
Bonita Test Toolkit V2:
The tests essentials to the successful completion of you project are now enhanced with the ability to provide the test results for a process execution under the form of a process diagram with an enhanced BPMN visualization. The result of your test is generated in an HTML file including BPMN diagrams, execution counters and execution paths.
Functional changes:
REST API and file upload:
When using the end point portal/fileUpload to upload a file before using it in Bonita REST API or a REST API extension, the size of the file that can be uploaded is now limited to 25MB. This can be changed in the configuration file console-config.properties using the setup tool, but be aware that this will affect upload limit for all users.
Feature deprecations and removals:
Legacy custom connectors and actor filters:
Since Bonita Studio 2021.2 it was not supported anymore to create custom connectors or actor filters in a Bonita project. Using the project composition with Maven extensions is the recommended way to integrate custom extensions.
In this version, those deprecated custom extensions are removed from the project when importing a .bos file or cloning a Git repository from an older version.
If you were coming from an older version of Bonita Studio with those custom connectors and actor filters, it will be required to migrate them into a separate Maven project using the dedicated archetypes. Visit their respective documentation pages for connectors and actor filters.
Provided Groovy classes:
Deprecated since 2021.1, BonitaUsers, BonitaSql, BonitaXML and BonitaTypes Groovy classes are no more available. You may use suggested code templates in the Groovy script expression editor instead.
API Deprecations:
Tenant pause and resume:
With new Maintenance mode, following API resources are deprecated.

New in Bonita 2023.1 Beta 1 (Mar 15, 2023)

Technical version change to 8.x.y:
Bonita 2023.1 introduces a new multi-runtime architecture. This change comes with a new way to handle multi-tenants use cases and thus the removal of the multi-tenancy as it is currently known. Based on the semantic versioning management standards, these changes require a technical version change.
Starting with Bonita 2021.1, creating user accounts on the fly at user authentication through SSO (Single Sign-on) was possible with configuration in Bonita Runtime. The user accounts were created with a username attribute, a default role and group - created beforehand in Bonita Runtime database.
Development suite changes:
Bonita project layout:
Bonita projects layout has been changed to take advantage of Maven multi-module project perks.
First project component that will benefit from Maven multi-module project is the Business Data Model. We decided to align the way the Business Data Model is handled in Bonita with the standard dependency handling practices by using Maven submodules. Submodules, or subprojects, are regular Maven projects that inherit from the parent POM.
With the chosen solution, the users will have the possibility to publish and consume the Business Data Model java dependencies independently. The project will pull the required dependencies from a specified repository - Maven Central or Bonita Artifact Repository - to generate the BDM java sources.
Business Data Model content check at build or deploy will still be developer’s responsibility along with handling data-deletion risks at build or deploy. For this Bonita version, reusing the generated artifacts in another Bonita project is not supported with refactoring capabilities. All changes will have to be handled manually by developers.
Bonita UI Designer:
Develop digitally accessible applications:
The following improvements have been made so that digitally accessible applications could be developed natively with Bonita UI Designer with less custom code:
An attribute lang is now available and based on the BOS_locale cookies at page initialization will automatically get filled without developer’s or end-user’s action.
Table and data-table widget have a new caption property available for adding a title
The default widgets in the palette that contain a html input tag have now an associated label, which will facilitate the use of computer tools (screen readers for example)
To be more accessible for speech synthesizers, screen readers or some other tools, the internal html template of checklist and radio buttons widget has been updated.
Manual web resource declaration in UID page metadata:
In addition to the automatic permission mapping done at a Custom page deploiement, it is now possible to declare web resources manually in a page/fragment/widget metadata. Less time spent now on post deployement configuration requests by DevOps team mananing Bonita instances
_ It is the good practice we are introducing regarding web resource’s for a page declaration. _
AngularJS version used by Bonita UI Designer Artifact builder security fixes:
During the last year we explored all possible options for providing a supported AngularJS version. In the end we decided to handle the need in-house. The first step of the long term project we initiated is correcting all critical and high CVEs in Bonita UI Designer Artifact builder. For that, we made a fork of the AngularJS project and adapted the fixes to the version that is used by the module.
What to hear more? Check this page xref:version-update:angular-js-UID-fork.adoc.
Default Bonita application AngularJS pages version update:
An update to the latest version of AngularJS (1.8.3) was done on the following pages provided by Bonita:
User task list
Admin application list
Admin application details
BDM page (both Admin and Super-Admin applications)
Admin user details
Admin process details
Admin license
Admin monitoring
Feature deprecations and removals:
Custom Rest API Extension and BDM dependencies:
When updating a Bonita project in Bonita Studio 2023.1 version, BDM dependencies will be directed to use the new the *-bdm-model artifact introduced with the Bonita project layout changes. Meaning that bdm-client and bdm-dao dependencies will automatically be replaced with project’s bdm-model dependency.
Additionnally, the dependency containing the client DAO implementation will be removed from the dependencies list. It can affect the code directly referencing the *DAOImpl classes. To avoid this situation, change the code to use the DAO interfaces present in the bdm-model dependency. The changes can be done before or after updating to the 2023.1 version without breaking the project.
Multi-tenancy removal:
Deprecated multi-tenancy has been removed.
To cover the multi-tenancy use cases in the best technical way, Bonitasoft is proposing a new architecture solution. For customers running a Bonita multi-tenancy platform, the technical path from multi-tenancy proposed by Bonitasoft is multi-runtime. This choice will require to split the current multi-tenant platform into several runtimes, each one with their own Bonita engine database.
As this path can be challenging for customers using multi-tenancy, Bonitasoft developed a conversion tool, available for download on Bonitasoft Customer Portal. We strongly suggest our customers to take the time and use the tool in a pre-production environment before using it on a production environment.

New in Bonita 2022.2-u0 (Oct 4, 2022)

New added values:
Bonita process monitoring now with embeded bpmn-visualization library:
Bonitasoft launched the open source project Process Analytics two years ago in response to the market need to perform BPMN process monitoring using BPMN standards. The deliverable of this project is called the bpmn-visualization library. You can find a nice array of examples of what it can do in its demo web site, and you can even contribute to this initiative in its Github repository.
Till Bonita 2022.2, another library has been used to display process execution data for administrators at both process and case levels. This library had some limitations and was not easy to improve with new features.
Hence, integrating the bpmn-visualization library to Bonita, was a very natural choice.
The new values are available for Bonita Subscription Editions starting with the Efficiency edition.
Bonita Administration application users will get a faster and more robust view on the process execution data (thanks to the library and new REST APIs)
As the bpmn-visualization library evolves, more interactivity and information for a better monitoring capacity will be provided
Since the pages have been created by using Bonita UI Designer, developers can:
Use the custom widget embedded in the new pages in their own application pages. The widget has been wrapped into a fragment that makes it very easy to use.
Modify the process or case visualization page, and use it in any Bonita application
For more details, check How to page to customize the display of process execution monitoring:
Bonita Reporting Application:
Here it comes, Bonita Reporting Application is now available for download on Bonita’s Customer Service Center/Customer Portal and is compatible starting with Bonita 2021.2.
A subscription account is required for downloading the .jar , that contains “Process Historical Data” and “Human tasks historical data” reports, designed for process performance and human tasks execution analysis. More details are available in the dedicated documentation page Bonita application for analytics and reporting.
A new widget to deal with Currencies:
A new input widget is now available in UI Designer to manage financial data using currencies at ease in pages or forms.
Improvements:
Development suite changes:
A new first-start flow for the Studio:
When launched for the first time after an install, the Studio will no longer start with a default project. The goal is to make this first start less cumbersome. Also, to increase user guidance, the Welcome page has been improved with clear call-to-action buttons.
Bonita Marketplace - Display installed extension:
A new filter was added to display the already installed extensions in order to help users know the extensions installed in their project while browsing the Bonita Marketplace
Detecting extension’s related issues at import:
With the previous version, you could import malformed extensions in your project without any warnings. This leading to errors downstream and confused users. From now, when importing or updating an extension, errors will be detected and users will be informed in Studio.
Improved guidance when the actor mapping is not defined:
With the previous version, if the actor mapping of a process was not defined, an unclear error message was displayed to the user. To help our users move forward with the deployment of their processes, we have improved the error detection by providing a clear message when this issue occurs.
New Menus for Bonita Studio:
The menus have been reviewed for an easier user journey.
Added Environment duplication feature:
With the previous versions, creating a new environment required to set up the whole project configuration entirely, including configuration of each process, what could be time consuming and error prone with big projects. From now on, users can create environments starting from duplicating an existing one.
Functional changes:
Case info REST API resource- Subscription editions:
Case info bpm/caseInfo REST API resource which is used for process and case user tasks visualization is now available.
For Community users who update to 2022.2, if you need this API resource, you can create a REST API extension that leverages Bonita Engine java API to get the same functionality as in 2022.1.
Technical updates:
UI Designer frontend has been migrated to AngularJS 1.8.
Only the UID application has been upgraded to AngularJS 1.8. Your applications will still generated with AngularJS 1.3. Stay tuned for further updates.
Feature deprecations and removals:
SVN:
SVN integration in Bonita Studio Subscription has been removed. You may migrate an existing SVN repository to a Git repository following this guide.
Multi-tenancy deprecation:
Multi-tenancy has been deprecated commercially by Bonitasoft starting from Bonita 2021.1.
To cover the multi-tenancy use cases in the best technical way, Bonitasoft is proposing a new architecture solutions. For customers running a Bonita multi-tenancy platform, the technical path from multi-tenancy proposed by Bonitasoft is multi-runtime. This choice will require to split the current multi-tenant platform into several runtimes, each one with their own Bonita engine database.
As this path can be challenging for customers using multi-tenancy, Bonitasoft developed a conversion tool. We strongly suggest our customers to take the time and use the tool in a pre-production environment before the production.
Multi-tenancy to multi-runtime conversion tool can be executed on Bonita Platforms starting from Bonita 7.11. In case you are in version not supported (<7.11) perform first an update of the platform.

New in Bonita 2022.1-u0 (Mar 31, 2022)

Improvements:
Runtime Health check endpoint - Subscription editions:
General status and connection type
Uptime in seconds
Platform state
Platform version
Platform node status started
Days till license expiration
Execution time in milliseconds
Changing the Log level without restart:
It is now possible to change the log level of Bonita Runtime without restarting it, thanks to Log4j2 (details available in the Technical updates chapter).
Functional changes:
Engine HTTP APIs protected with Basic Auth:
Previously, engine HTTP APIs were used to access Bonita Engine Java APIs directly through HTTP. starting with Bonita 2022.1, their access is protected with Basic Access authentication.
The configuration is different depending on the Bonita package:
In Bonita Tomcat bundle, HTTP APIs are active by default and default credentials are the same as the ones used when configuring the client by using programmatic configuration.
In Bonita Docker image, HTTP APIs are disabled by default, with http-api as the default username, and no default password. The password must be provided, otherwise the Docker container will refuse to start.
For Community users who update to 2022.1, dynamic permission authorization checks will not be executed anymore, even if the configuration stays unchanged. Obviously, you can develop a custom execution script or upgrade to Bonita Enterprise edition (as the configuration will not be changed by Bonita, it will be fully functional).
Connector Retry:
When Bonita Engine fails to evaluate the output operations of a connector, the retry mechanism is not automatic. It is the platform administrator’s choice to re-execute the connector or not, based on the impact analysis. Go through the connector documentation for details about connector failure and replay.
Log4j2 Logger:
Bonita Runtime now uses Log4j2 as its logger. One of the multitudes of advantages brought by this tool is the automatic reload of configuration files. There is no more need to restart Bonita Runtime to have the log level change effective. In the configuration file, the log level can be changed ON THE RUN and can be different for each package.
Enterprise Docker image:
Docker image is now focused on the RUN phase, with environment preparation being handled as on-premise installations. This means that the database schema and the associated user will not be created when starting the Docker image. The database has to be created before the Docker image starts. NOTE: We provide pre-configured database images with included schema and users on Bonitasoft Docker Hub.
LDAP Synchronizer is now out of Bonita Docker image and is available as an independent Docker image ready for download from quay.io as detailed in the documentation.
Robustness and self-recovery capabilities were added to the data source to overcome network lags.
Folder structure inside Bonita Docker images has been simplified: instead of having /opt/bonita/BonitaCommunity-2022.1 or /opt/bonita/BonitaSubscription-2022.1, we now simply have /opt/bonita.
Also, to make the Bonita Docker image configuration easier, new environment variables have been added:
HTTP_API_USERNAME
HTTP_API_PASSWORD
JMX_REMOTE_ACCESS
REMOTE_IP_VALVE_ENABLED
ACCESSLOGS_STDOUT_ENABLED
ACCESSLOGS_FILES_ENABLED
ACCESSLOGS_PATH
ACCESSLOGS_PATH_APPEND_HOSTNAME
ACCESSLOGS_MAX_DAYS
HTTP_MAX_THREADS
SVN:
The SVN feature is now deprecated. We recommend that you migrate your repositories to a GIT repository. This documentation page describes how to migrate an SVN repository to Github.
REST API:
Deprecated: filter page using the isHidden attribute on the api API/portal/page. That field is not used anymore and is always false. Bonita Runtime produces a warning log if the filter is set and ignores it.
Removed:
The ReportingAPI is removed as well as its associated engine API.
Multi-Tenancy:
The tenant creation method has been deprecated following our 2021.1 decision to deprecate the Multi-Tenants architecture.
Fixes in Bonita Runtime (including Bonita native Applications):
RUNTIME-178 - Case deletion throws 500 instead of 404 when the case does not exist
RUNTIME-477 - Case overview does not paginate attached document list
RUNTIME-814 - [Security] Update several dependencies
RUNTIME-885 - [Security] Issue with authorization mechanism

New in Bonita 2022.1 Beta 1 (Feb 10, 2022)

New values added:
Bonita Test Toolkit (Subscription editions)
When working on complex, core, and critical automation projects it is critical to ensure the right business logic is applied. Secure your automation project with the new development suite component: the Bonita Test Toolkit.
This toolkit allows professional developers to write end-to-end or integration test scenarios for your automation project. It provides powerful methods to execute all the steps of a process and check the corresponding outputs (statuses, business data, tasks used)
It can be used in any IDE and can easily be integrated into a Continuous Integration.
Improvements:
Runtime Health check endpoint (Subscription editions)
A health check endpoint has been added to the Bonita Runtime to help you monitor the status of your runtime.
This end-point is available on the https://myruntime/bonita/healthz URL and provides key information such as the runtime status(OK, NOK), the platform state, or the number of days until the license expiration.
Its access is now protected with Basic Auth authentication to protect against DOS attacks.
These credentials can be consulted and modified:
In the <BONITA>/server/conf/tomcat-users.xml file in a Bonita Tomcat bundle
Using specific Environment parameters when starting a Bonita Docker image
Changing the Log level without restart
It is now possible to change the log level of your platform without restarting it thanks to Log4j2 (see the technical updates chapter)
Functional changes:
Prometheus monitoring active by default (Subscription editions)
From Bonita 2022.1, the Prometheus metrics publisher is now active by default and can be disabled if needed.
Its access is now protected with Basic Auth authentication to protect against DOS attacks.
Thus, when reaching the Prometheus metrics endpoint, typically https://localhost:8080/bonita/metrics, you will have to manually enter the configured username and password information for your access to be granted.
These credentials can be consulted and modified:
In the <BONITA>/server/conf/tomcat-users.xml file in a Bonita Tomcat bundle
Using specific Environment parameters when starting a Bonita Docker image
Dynamic authorization checking active by default (Subscription editions)
Dynamic authorization checking is now only available in the Enterprise editions, and is also active by default for new installations.
Existing installations that update to 2022.1 stay unchanged, but we encourage customers to activate dynamic authorization checking, once they have benched that the performance cost is reasonable.
For Community users who update to 2022.1, dynamic authorization checking does not work anymore.
However, the configuration stays unchanged, even if it is not used anymore.
If they want to reuse the configuration in a custom manner or upgrade to Enterprise edition, the configuration will be back there and fully functional.
Technical updates:
Log4j2 Logger
Bonita Runtime now uses Log4j2 as logger. One of the great feature that it brings is the automatic reload of configuration files. There is no more need to restart the platform if you only want to change a log level.
Enterprise Docker image:
Docker image is now focused on the RUN phase, environment preparation will be handled apart (as on-premise installations) so docker image does not create anymore the database schema and the associated user. Still, the database must be created before the docker image starts. We provide pre-configured database images with included schema and users Docker Hub.
LDAP Synchronizer is now out of Bonita docker image and is available as an independent docker image ready to use (available on quay.io)
For assuring a smooth and obvious Runtime confirmation management, environment properties and configuration variables nomenclature has been reviewed to provide homogeneity among all of them. See dedicated documentation for details.
Robustness and self-recovery capabilities were added to the data source to overcome network lags.
Folder structure inside Bonita Docker images has been simplified: instead of having /opt/bonita/BonitaCommunity-2022.1 or /opt/bonita/BonitaSubscription-2022.1, we now simply have /opt/bonita.
If you have scripts using the former folder structure, please update them.
Feature deprecations and removals:
SVN:
The SVN feature is now deprecated. We recommend that you migrate your repositories to a GIT repository. This page describes how to migrate a SVN repository to Github.
REST API:
Deprecated: filter page using the isHidden attribute on the api API/portal/page. That field is not used anymore and is always false. The platform produces a warning log if the filter is set and ignores it.
Removed: the ReportingAPI is removed as well as its associated engine API.
Multi-Tenancy:
The create tenant method has been deprecated following our 2021.1 decision to deprecate the Multi-Tenants architecture
Bug fixes:
RUNTIME-178 - Case deletion throws 500 instead of 404 when the case does not exist.
RUNTIME-4777 - Case overview does not paginate attached document list

New in Bonita 2021.2 Beta 2 (Oct 24, 2021)

New:
Bonita Studio and Bonita UI Designer:
Bonita Studio Project Composition:
Automation projects now use the power of Maven. You can now compose your project of extensions (connectors, Rest API extensions, themes, and actor filters).
All these extensions, which are technical components, have to be built outside of the Studio with our SDK (except for Rest API extensions that can still be developed in the Studio). This will allow the developer to use their preferred tooling. It will also help the industrialization of your project as you will be able to implement tests for each extension making your project more robust.
As the extensions are developed outside the Studio, they are no longer bound to a specific Bonita project. They can be easily reused in a different project - thus improving your efficiency. More information on how Bonita projects are structured.
The Studio is stripped of its major coding editor (except for the REST API Extensions), and has now a dedicated view for extensions. This view is used to get extensions from different sources:
From the Bonita marketplace, which contains all the connectors and actor filters made and maintained by Bonitasoft
From maven repositories (private or public)
From files (jar or zip)
Bonita Studio becomes more and more accessible to citizen developers. Any technical development should be made outside the Studio.
As connectors are now extensions of a project, their version is not bound to the Bonita Studio version anymore. Therefore, you do not need to update Bonita Studio to migrate a connector or to migrate your connectors when updating Bonita Studio. This will simplify version updates.
Finally, your sources will be lighter as the dependencies will be pulled by the project.
Project Overview:
Understanding all the elements of a Bonita project has never been easier thanks to the Project Overview. Accessible from the coolbar, this new page displays all the elements that can be used in a state-of-the-art Bonita project. From this view, you can create, view or edit the different elements. You can also find documentation on the different components.
Studio Organization Editor:
In Bonita Studio, the Organization wizard has been reworked into an editor, to improve your experience and your efficiency.
Bonita Runtime:
SSO with OpenID Connect:
It is now possible to configure Bonita to use OpenID Connect (OIDC) as an authentication mechanism to access your Bonita applications and achieve Single Sign-on with an external OIDC provider.
The Authorization Code Flow of OpenID Connect is supported to authenticate when accessing Bonita applications as well as the Resource Owner Credentials Grant and Authorization Code Grant of OAuth 2.0 to authenticate when requesting Bonita REST API.
Improvements:
Bonita Studio and Bonita UI Designer:
Expression type simplification:
Bonita 2021.1 introduced a new expression editor. This new expression editor covers the existing editor expression type use cases.
Therefore, to simplify the expression flow in Bonita Studio, we are removing the following expression types:
Constant
Comparison
Constant
Parameter
Variable
Contract
Connector Output
If your project is using these expression types, they will be migrated to the new expression editor when you import your project in Bonita Studio 2021.2.
"Switch" widget better guidance:
The Switch widget feature has been improved to guide the user efficiently to avoid incompatible properties mapping that may lead to inconsistent states of widgets.
Tab widget possibility to define the selected tab:
It is now possible to define the tab that will be selected by default in the tabs group with the new "Selected" field on the tabs.
API Variables response Metadata usage:
It is now possible to easily bind the metadata of an API variable response (header, status code, and response value) to other variables.
Bonita Runtime:
New Bonita Applications:
Bonita Portal is now removed, meaning that:
Bonita Mobile Portal has been removed
Custom profiles with Portal navigations are converted into custom Applications with default Bonita layout and Bonita theme
If you had customized Bonita Portal, please note that the Look & Feel files are removed too: you will need to create a theme an apply it to the newly created applications
The Process Manager profile is temporarily discontinued
The Analytics page is also temporarily discontinued
Technical updates:
Java 11 Compliance:
Bonita 2021.2 is now only compatible with Java 11. Support with Java 8 has now been removed.
Tomcat:
Tomcat has been updated to version 9.0.52.
Configuration file changes:
The unused configuration file forms-config.properties has been removed.
The optional configuration file jaas-standard.cfg has been removed from Tomcat Community bundle (because JAAS is now Enterprise).
CAS and Kerberos configuration files have been moved to folder tools/SSO/ (Bonita Enterprise only).
Bug fixes:
Fixes in Studio and UI Designer:
UID-459 - BO variable cannot be edited in fragment after workspace import from previous version and error message is wrong
STUDIO-4126 - Process execution errors: bcd-dependencies:7.11.5 generates a .bar different from Studio 7.11.5
STUDIO-4113 - Process Validation freezes after process import
STUDIO-4086 - Expression editor inserts the wrong operator ' =<' instead of '⇐' in groovy script
STUDIO-4066 - java.lang.NullPointerException at build when wrong variable entered in script but not shown in validation
STUDIO-4043 - errors while importing .bos in studio
STUDIO-3962 - Release note view is broken on windows
STUDIO-3953 - LA Builder is slow
STUDIO-3936 - EMF resources not in synch after using Git operations
STUDIO-3898 - Model - annotations are positioned relatively to lanes coordinates (not absolute)
STUDIO-3880 - Editing domain can be null on an opended diagram
STUDIO-3875 - Issue with "Switch project" function
STUDIO-3793 - UIPath connector is not working with cloud orchestrator
Fixes in Bonita Runtime:
RUNTIME-479 - CVEs in OpenSSL version in Docker images
RUNTIME-447 - Security vulnerability REST API portal/runreport open to all profiles
RUNTIME-271 - Archived cases query fails with 'operator does not exist' error when filtering on process name
RUNTIME-261 - BDM installation failed when a bdm was already installed
RUNTIME-138 - Entire BDM install history lost when BDM deployment issue
RUNTIME-132 - [SAML] Getting the default loging page when signing in on a guest app
RUNTIME-84 - Loading a class with Class.forName can keep references in VirtualClassloader
RUNTIME-70 - BDM schemas changes are not rolled back after a failed installation of a new BDM over an existing one
RUNTIME-34 - Install a BDM with an invalid custom query fail silently
RUNTIME-27 - Services resume failures after the la-deployer detects bdm deployment timeout
RUNTIME-23 - Installing BDM with a wrong custom query corrupts the BDM database without any rollback option

New in Bonita 2021.1 Build 7.12.1.1 (Mar 3, 2021)

Democratization of process automation technology:
This version of Bonita offers significant improvements and new values, among which the clarification of both Enterprise and Community editions:
Bonita Community:
The open source edition of the platform including all capabilities required to develop and deploy process automation projects. The platform is based on Bonitasoft's genuine approach to low-code and clearly separates visual programming vs coding capabilities to drive collaboration and simplify project governance.
Bonita Enterprise:
The commercial edition of the platform to address core and critical process automation use cases. This edition adds capabilities to Bonita Community to secure, scale, monitor and continuously improve process automation projects. The Enterprise edition is bundled with a customer success subscription that provides full project lifecycle support and services from development to operations.
The changes:
This means an unprecedented number of features were added in Community, so users can achieve the target goals. Alternatively, some values, linked to the goals of Enterprise, have been moved from Community to Enterprise.
As a direct benefit, upgrades/downgrades operations between Community and Enterprise editions will be simplified. Both operations still require the re-installation of the targeted platform but there is no need for project re-development anymore.
Create state-of-the-art and successful automation projects with the Community edition:
Bonita has always been a highly open-source project, and we strongly think that it is the best to create a great and extensible platform.
These are the features you will find in the Community edition of Bonita 2021.1:
Git plug-in in the Development Suite: teamwork and versioning control:
Multi environment management: configure for CI, Testing, UAT, Staging, or Production environments
All connectors (SAP, Office, Salesforce, UI Path) and all advanced connector wizards (email, web service, database, Twitter)
All editors with simplified UIs (Rest API Extension, application descriptor, BDM access control, easier theme editing)
Translation asset in the UI Designer: translate pages, forms, and layouts, of have them translate by business team members
Widgets (save form, rich text area, chart, data grid (advanced table))
Responsiveness: create pages and forms for multiple screen sizes
Fragments: reuse groups of widgets in multiple pages of forms, with just a different configuration
Search keys: allow users to search their cases with business data
Full power to the Enterprise edition
To ensure consistency with Community vs Enterprise concepts, in 2021.1, we have moved from Community to Enterprise edition the following capabilities:
PurgeTool to manage Bonita Platform scalability. The tool allows to purge finished (archived) process instances from a Bonita Runtime environment.
Maintenance releases. From now on, maintenance releases are only available to customers (Enterprise users). Community users will benefit from all fixes done on a minor release in the next minor release.
JMX metrics publisher, monitoring log files and API dynamic security capabilities will be removed from Bonita Community 2021.2 and will be part of the set of Enterprise features related to security and monitoring themes respectively. As a matter of clarification, operational logging capabilities of the platform will remain in the Community edition. Moreover, the Enterprise offering now encompasses the availability of Bonita Continuous Delivery, our powerful tool to deploy Living Applications on subsequent environments during the initial lifecycle of the Bonita project, and for every improvement or evolution.
The version name:
So, how should we name this version? Not 7.12 because of all those changes, and all the following ones, but not 8.0 either, as it does not embed backwards incompatible APIs or any other breaking changes. And because of its new clear concepts, Bonita will now follow a special type of #CalendarVersioning, with a YEAR.NUM pattern. So we are proud to present the new (and fresh) Bonita 2021.1! As for the Maintenance versions, they will be taggued yyyy.#-mmdd like 2021.1-0212 for the maintenance release of Feb 12th, based on the first minor release of 2021. New releases will continue to be rolled out on a 6-month cycle to provide new values. And the technical components of Bonita will keep their semantic versioning numbers, that you should not see too often.
Now, for the brand new values added:
New Bonita Administrator Application available
As Bonita Portal is turning into Living Applications, to give you more flexibility and opportunities of customization, you now have two applications to try.
After the Bonita User Application in 7.11, give a try to our new Bonita Administrator Application!. You can get it from Bonita Studio Welcome page, in the Resources tile. Starting now, you can use it as is, but you can also customize the pages that have been recreated with the UI Designer, or create your own Administrator Application from a handy starting point. It replicates the current Administrator Portal profile, except for the Analytics page, available in the Enterprise edition.
In a later version of Bonita, this application will replace the current and now deprecated Administrator Portal profile.
Development Suite supports multi-maintenance versions:
For a given YEAR.NUM version of the development suite (Studio and UI Designer), you can now seamlessly work on projects that have a different maintenance version (but the same version). For example: if your Studio is in a later version of 2021.1, you will be able to work on all 2021.1 projects without migrating the project or being blocked.
Simplified Expression editor:
Writing a script expression has never been easier with the reviewed expression editor. You can drag and drop variables and quickly access operators.
Improvements:
Development suite changes:
Warning before the migration when cloning a project
If you are cloning a repository branch that required migration then you will be informed of the need for migration before it is actually done. This allows you to cancel the operation and change the branch if needed.
Project Problem view and Project validation:
A new view is now available in the Studio to see all the project issues and warnings. It is also possible to validate a project through the contextual menu.
Dark mode theme for the Studio:
In the "Appearance" section of the Studio settings, you can now change the theme. You have two possibilities: light (default) and dark.
Multi-selection for REST API and Theme build:
You can now select several REST APIs or themes to build in the Studio
Displaying the fragments and custom widgets full name in the UI Designer:
When editing a UI Designer artifact, you can now see the full name of the available fragments and custom widgets in a new tooltip. Previously, fragments and custom widgets with long names were truncated, making their selection cumbersome.
Google Calender New authentication method;
The google connector can now use JSON tokens to authenticate.
Java REST API Extension;
It is now possible to create REST API Extensions in Java.
Autocomplete Widget returned value:
Within the autocomplete widget, you can select a returned value different from the displayed value, opening for new use-cases.
Runtime changes:
New Monitoring metrics available
Notably two new hibernate metrics: hibernate.cache.query.plan respectively hit & miss, to help troubleshoot performance problems. How to activate this metrics is documented here.
Fault tolerance mechanism:
It was already possible to ensure the high availability using a clustered architecture, Bonita Platform is now even more tolerant to incidents like database outages thanks to the brand new Recovery mechanism.
New properties added are:
bonita.tenant.recover.consider_elements_older_than
bonita.tenant.recover.delay_between_recovery
See Fault tolerance mechanisms documentation page for more details.
User creation on the fly for SSO Authenticated users:
You can now configure Bonita to allow Bonita Engine to create user accounts on the fly as soon as they have been previously authenticated in their SSO (SAML or Kerberos). Find more information on how to configure it here.
REST API and portal login:
The redirect parameter is now optional when logging in to the REST API using /bonita/loginservice as well as when logging out using /bonita/logoutservice.
This means it is no longer needed to put redirect=false in the request to log in/out using the API. However, previous login requests with a redirect URL will continue working as the redirect parameter is optional.
If you use a customized login page to log in to Bonita portal UI and your page don't send any redirectURL=<targetBonitaURL> parameter to the login service, then you need to make sure your page send a parameter redirect=true in the request to the login service. Same thing if you have a logout link in a custom page that does not pass a loginUrl or a redirectUrl parameter.
Application layout:
If you use Bonita layout version 5 or a customized version of it in your applications, make sure you upgrade to version 6 when migrating. Otherwise, the logout button will not redirect to the login page when clicked due to the above changes on the login/logout service.
Search keys:
As part of the reinforcement of our Open Source DNA, Search keys can now be defined and used in the Community edition.
Take a look at the search keys documentation to learn more about it.
BDM (Business Data Model) class generation:
In Bonita 2021.1, we changed the way ID's are generated when you deploy a (new version of a) Business Data Model.
Previously, the strategy to generate table ID's of BDM objects was left to Hibernate to decide. It could be a database SEQUENCE, an auto-incremented column, ...
Now, the specific implementation is explicitly set on each ID column during the BDM class generation. It is however different from one Database vendor to another (a database SEQUENCE for Oracle and PostgreSQL, an auto-incremented column for MySQL and MS SQL Server).
Note that no change is required from you, and upgrading to Bonita 2021.1 does not affect your already generated BDM until you actually redeploy it (next time you update it).
Technical updates:
Libraries
Groovy updated to 2.4.20 Micrometer updated to 1.6.1
Support Matrix:
Bonita now supports Red Hat Enterprise Linux (RHEL) and CentOS 8.2 version
Feature deprecations and removals:
Deprecations:
Bonita Portal transformation:
Bonita Portal is being transformed into Bonita Applications. When Bonita Applications are ready, Bonita Portal will be removed. Developers and users will need to learn how to stop using the Portal and start using Bonita Applications instead. This change will allow Bonita and its users to get free from Google Web Toolkit (GWT) technology and offer opportunities for customization. Indeed, some Portal pages (built with GWT) are being totally recreated with our own UI Designer. They will be customizable. Other pages (those that were already using another technology than GWT) are being wrapped and will not be customizable. Moreover, as any Living Application, Bonita applications will be extensible to add any page the users need. More details in the upcoming versions of Bonita. Until then, we strongly advise not to create Custom Portal Profiles anymore but applications instead. When Bonita Portal will not exist anymore, the existing Portal Custom Profiles will need to be migrated into Living applications.
Java 8 support:
Bonita 2021.1 (7.12) is the latest version fully compatible with java 8 in production and development environment. JRE or JDK 11+ will be required to run. Bonita 2021.2+ won't be operated on Java 8.
Removals:
IE11 support:
Internet Explorer 11 is not supported anymore through the Bonita Platform. The web browsers supported by Bonita 2021.1 are Mozilla Firefox, Google Chrome and Microsoft Edge.
Legacy third party format importers:
In the Community edition, XPDL and jBPM importers have been removed.
In Enterprise edition, Visio and Aris importers have been removed.
Use BPMN 2 importer for model exchange with third-party editors.
Bug fixes:
Fixes in Bonita 2021.1-0218 (2021-02-18)
Fixes in Bonita Development Suite (Studio and UI Designer)
STUDIO-3830 - Performance decreases direly as the number of diagrams and process definitions in the project increases
STUDIO-3835 - Expression dialog is slow to open
STUDIO-3819 - Documentation generation is missing task contract inputs
STUDIO-3766 - Missing scroll bar on BDM editor queries table
STUDIO-3800 - Validation error in a process when the call Activity does not have a version
UID-364 - When the first fileUpload widget is removed from a collection, the new first widget still displays the file chosen in the removed item
Fixes in Bonita Runtime (including Portal)
RUNTIME-69 - LDAP Synch: NullPointerException during manager synchronization makes synchronization fail and exit
RUNTIME-63 - Different xstream 1.4.14 and 1.4.13 versions between Bonita 7.11.4 and 7.12.0
RUNTIME-62 - Only finished gateway should be selected as a recover candidate
RUNTIME-50 - LDAP Synch: LDAP group objectclass check should be case insensitive
Fixes in Bonita 2021.1 (2021-01-28)
Fixes in Bonita Development Suite (Studio and UI Designer)
STUDIO-3630 - More log messages are needed to debug the SAP Connector
STUDIO-3694 - User password is not retrieved from the active organization when logging in Portal/App
Fixes in Bonita Runtime (including Portal)
BS-17167 - Live update of connector fails after BDM redeployment
BS-18685 - Portal's task REPLAY says failed connector will be re-executed but it is not true if task's prev_state_id=4 (ready)
BS-19410 - Failed Flownodes after a database server restart
BS-19453 - no state found after AbortedFlowNodeStateImpl for flow node of type SBoundaryEventInstance
BS-19455 - Performance: 10 sec SQL request on ARCH_FLOWNODE_INSTANCE with 13500000 rows
BS-19497 - NullPointerException is generated after replaying a call activity in a failed state
BS-19534 - no state found after CancelledFlowNodeStateImpl for flow node of type SBoundaryEventInstance CANCELLING
BS-19538 - Cancel of process instance fails because MULTI element cancelled before all children call activities are cancelled
BS-19543 - Cannot create case because hibernate_sequence table or sequence is missing after migration to 7.11
BPO-307 - Process manager can assign a task and execute a task on behalf of a user which is not associated to the process in the actor mapping with our without Dynamic authorization checking
BPO-643 - Not all processes get disabled when multiple ones are selected in Portal - Administration - BPM - Processes page
BPO-645 - Erroneous space at the end of property value breaks the standard authentication allowed functionality
BPO-648 - Load more limitation when result is multiple of number per page
BPO-655 - LoginServlet redirect param should be optional and default to false
BPO-662 - Expanding/collapsing the form resets input data
BPO-664 - Security risk: API/formsDocumentImage executes injected script
BR-454 - Sometimes CallActivity are left Completed without target process
RUNTIME-50/BR-621 - All LDAP group objectclass checks are now case-insensitive.

New in Bonita 7.12.1 (Feb 19, 2021)

Bug fixes:
Fixes in Bonita 2021.1 (2021-01-28)
Fixes in Bonita Development Suite (Studio and UI Designer)
STUDIO-3630 - More log messages are needed to debug the SAP Connector
STUDIO-3694 - User password is not retrieved from the active organization when logging in Portal/App
Fixes in Bonita Runtime (including Portal):
BS-17167 - Live update of connector fails after BDM redeployment
BS-18685 - Portal's task REPLAY says failed connector will be re-executed but it is not true if task's prev_state_id=4 (ready)
BS-19410 - Failed Flownodes after a database server restart
BS-19453 - no state found after AbortedFlowNodeStateImpl for flow node of type SBoundaryEventInstance
BS-19455 - Performance: 10 sec SQL request on ARCH_FLOWNODE_INSTANCE with 13500000 rows
BS-19497 - NullPointerException is generated after replaying a call activity in a failed state
BS-19534 - no state found after CancelledFlowNodeStateImpl for flow node of type SBoundaryEventInstance CANCELLING
BS-19538 - Cancel of process instance fails because MULTI element cancelled before all children call activities are cancelled
BS-19543 - Cannot create case because hibernate_sequence table or sequence is missing after migration to 7.11
BPO-307 - Process manager can assign a task and execute a task on behalf of a user which is not associated to the process in the actor mapping with our without Dynamic authorization checking
BPO-643 - Not all processes get disabled when multiple ones are selected in Portal - Administration - BPM - Processes page
BPO-645 - Erroneous space at the end of property value breaks the standard authentication allowed functionality
BPO-648 - Load more limitation when result is multiple of number per page
BPO-655 - LoginServlet redirect param should be optional and default to false
BPO-662 - Expanding/collapsing the form resets input data
BPO-664 - Security risk: API/formsDocumentImage executes injected script
BR-454 - Sometimes CallActivity are left Completed without target process
RUNTIME-50/BR-621 - All LDAP group objectclass checks are now case-insensitive.

New in Bonita 7.11.4 (Jan 19, 2021)

New in Bonita 7.11.3 (Nov 26, 2020)

New in Bonita 7.11.2 (Oct 1, 2020)

New in Bonita 7.10.5 (Jun 4, 2020)

New in Bonita 7.10.3 (Mar 6, 2020)

New in Bonita 7.8.4 (Apr 18, 2019)

New in Bonita 7.8.3 (Mar 7, 2019)

New in Bonita 7.8.2 (Feb 14, 2019)

New in Bonita 7.8.0 (Dec 7, 2018)

Fixes in Engine component:
BS-16972 Engine classloader refresh should use less Heap memory on Engine startup and BPM services
Resume
BS-17905 LDAP Synchronizer failure with Microsoft Active Directory when MaxValRange limit reached for
Member in a uniq group
BS-18131 Performance issue when retrieving process.bpmn from bar resources
BS-18528 Engine logs should allow to troubleshoot why licence in DB is not loaded
BS-18563 Engine arbitrarily fails with License Error 51,27 at server start-up on Windows
BS-18615 Missing Hibernate query searchSProcessInstancewithSProcessSupervisor
BS-18741 Operation does not apply changes within the same transaction for document list
BS-18745 Operation: Assignment to a list of document from a list of File from the contract is failing
When one element is null
BS-18783 SKIP button on a Failed Task, with Interrupting boundary event, does not cancel the event
BS-18847 Parallel archive cases deletion via REST API does not delete all rows
BS-18866 Deletion of archived case times out because it takes too long to execute
BS-18900 Operation does not apply changes within the same transaction for single document
BS-19062 Lazy referenced BO field to itself fails to serialize with StackOverflowError
BS-19073 Archived contract data are never deleted
Fixes in Studio component:
BS-18588 String process variable in diagram appears as Boolean in .proc file
BS-18664 Studio thread takes 100% CPU when selecting a call activity
BS-18707 UI designer forms and pages SVN delete only remove file in Local and tag as Missing instead of
Delete
BS-18708 The bonita la builder doesn't build the global zip correctly (add a slash root folder)
BS-18861 Typo in description Git Clone assistant 2nd window clone destination
BS-18903 Nothing indicates you cannot click OK because your Groovy script is not named
BS-18946 Studio launches several processes to open BDM H2 console
BS-19033 Git reset leaves files that should not be there
BS-19105 Studio Import: unable to recognize git repositories after studio migration
Fixes in UI Designer component:
BS-18472 Rename fragment does not rename fragment used in a container in a form
BS-18860 Date widget input not removed from binded variable
BS-19006 Cannot use a exported page from UID if one of widget asset is inactive
BS-19100 Rename a fragment replace others fragments reference use in a page same page
Fixes in Web component:
BS-18847 Parallel archive cases deletion via REST API does not delete all rows
BS-18672 Do some check in caseOverview to ensure display in any case.
BS-18770 Profile User should not be able to see the list of users installed on the platform using a call to
API/identity/user
BS-18816 Due Date translation is lost in the tasklist page imported inside a custom profile or living
Application
BS-18818 Due Date format is wrong in japanese
BS-18968 Security issue on Tomcat (CVE-2018-8037) impact Tomcat bundle
BS-19032 404 not found: Task's form and process' form displayed in a living application cannot load the
Assets (image and font) listed in the CSS of the application's theme

New in Bonita 7.7.5 (Nov 23, 2018)

New in Bonita 7.7.4 (Sep 7, 2018)

New in Bonita 7.7.3 (Aug 3, 2018)

New in Bonita 7.7.2 (Jul 13, 2018)

New in Bonita 7.7.1 (Jul 12, 2018)

New in Bonita 7.7.0 (Jun 7, 2018)

New values added:
Collaborative development with Git (starting with Teamwork edition)
Business data access control (BDM AC) (starting with Efficiency edition)
Save Form (starting with Teamwork edition)
Improvements:
LDAP synchronizer to synchronize Custom User Information too (starting with Teamwork edition)
Readable UI Designer artifact names in Bonita repositories
UI Designer artifacts last update date
BDM meta-information for Portal Administrator
New layout for the Administrator Portal "User details" page
Business objects relationships
API error messages
Studio status bar
Application descriptor "deploy"
Official signatures on Windows
Technology updates:
Other dependency updates
Feature removals:
Jasper 5 connector
API behavior change:
Add comment in an open case
UI Designer URL change
Jasper 5 connector
Deprecated Workspace API
Fixes in Bonita 7.7.0:
Fixes in Documentation:
BS-16862 Cannot fully deploy a REST API extension with Engine APIs
BS-17598 Documentation steps about "Create your own password validator" lead to maven error: Could not find artifact
BS-17659 "BDM Management in Bonita Portal" section leads customer to believe updating the BDM in production is supported
BS-17699 Broken link to 7.6 Engine Javadoc
BS-17770 Studio preferences Documentation still speaks about Studio profiles
BS-17795 Single sign-on with SAML not described with Wildfly
BS-17930 Documentation about 'Changing technical user' needs more detailed explanations
BS-18134 Workaround or guidance missing for time-zoned Java 8 Date types usage in REST API extensions
BS-18167 Live update of script fails if a new "provided variable" is added to the script
Fixes in Engine component:
BS-15900 EventTriggers are not always deleted from the EVENT_TRIGGER_INSTANCE table
BS-16750 FILE contract input type generates a big usage of the heap memory with big documents
BS-17009 Hazelcast jar is no more available for AWS Discovery
BS-17267 engine-server temp folder keeps growing in size on windows environment
BS-17464 CMIS list documents connector and probably the others CMIS connectors generate a ClassNotFoundException on WildFly only
BS-17514 Setup tool should release files after a pull operation
BS-17624 7.3.3 and prior java client failed to deserialize an object when communicating with java Engine API 7.4.0 or higher
BS-17679 Prevent unsupported use case when defining BDM
BS-17716 Setup tool does not prevent the removal of critical configuration files
BS-17725 add() to an empty multiple BO (List) is failing
BS-17726 Case counter for Unlimited instances license is not incremented
BS-18196 BoundaryEvent stays behind in 'waiting' state if task is skipped
BS-18201 ProcessAPI.searchConnectorInstances fails with SearchOptions using .filter(ConnectorInstancesSearchDescriptor.STATE, ConnectorState.FAILED)
BS-18208 logged user / task assignee : Task Operation behavior has changed
BS-18228 Terminate and End event is not terminating the process after a failed task with a boundary event had been skipped
BS-18336 HazelcastSerializationException: Failed to serialize 'org.bonitasoft.engine.work.WorkDescriptor'
BS-18350 Fix Aws discovery sample hostHeader in bonita-platform-sp-cluster.properties
BS-18389 Tomcat outputs TechnicalLoggerSLF4JImpl for all logs in subscription editions
Fixes in Studio component:
BS-17267 engine-server temp folder keeps growing in size on windows environment
BS-17749 : surounded with space chars in task name generates an error when user clicks on the task in the portal's tasklist
BS-17939 Content Assist doesn't work without keyboard shortcut in Groovy expression editor
BS-18101 Process contract inputs missing from process-design.xml when building with BonitaStudioBuilder
BS-18154 Catch message - Correlation mapping value doesn't display expression editor properly
BS-18178 Studio splash screen doesn't work on windows
BS-18191 Automatic dependency resolution can fails in Groovy Expression Editor
BS-18197 Studio deploys too many sub process versions and the wrong one is used at run-time.
BS-18269 "Create a parameter..." wizard is not popping-up
BS-18270 Parameter type is lost on version when re entering process to call section
BS-18301 Welcome page displays outdated RSS flux content in welcome page
BS-18343 Using loop "for" in Input Constraints fails with a validation error and a warning in the Editor
BS-18344 CPU spike and GC overhead limit exceeded when using groovy editor for Inputs constraints
BS-18381 Installer fails to launch BonitaStudio at end, if path contains space characters
Fixes in UI Designer component:
BS-16696 Autocomplete widget issue with asynchronous data (Rest API call)
BS-16997 File viewer preview display cut and not scrollable with pdf file in Mobile portal
BS-17809 HTML is not interpreted anymore after page import in studio 7.7.0 from 7.6.x and lower
BS-18062 UI Designer Devices size Preview doesn't reflect the one selected in the main UI Designer
BS-18179 Form import in UI Designer displays a non-translated artifact type
BS-18222 Bonita API resource not exported in page.properties when single resource call with id
BS-18256 Infinite loop creating css file after migration error
BS-18385 URL parameters are not decoded in UI Designer
Fixes in Web component:
BS-16440 Instance counter starts one day before subscription start date
BS-17924 CSRF cookie needs to be handled when implementing authentication manager
BS-18137 Changing filter does not refresh the case list properly
BS-18149 REST API Not compliant with the If-Modified-Since HTTP header
BS-18223 Licensing admin page does not handle unlimited case number correctly
BS-18231 Select widget fails to pre select Value
BS-18335 Process visu is not display when process contains an intermediate catch event signal
BS-18341 Error message not explicit in Portal when change password policy enforced
BS-18367 Click inside a Living application raises a warning in the logs and a 404 on an undefined URL path
BS-18375 User profile - Done Task list cannot be ordered on 'performed date' column or any other date column; it used to be possible in 7.2.2

New in Bonita 7.6.3 (Mar 6, 2018)

New in Bonita 7.6.2 (Feb 1, 2018)

New in Bonita 7.6.0 (Dec 9, 2017)

Bonita BPM becomes Bonita
New values added:
Industrialization of Living Applications in Bonita Studio: Profiles
Process display name
SAML logout
New API method to protect task assignation
Improvements:
UI Designer performance improvement: artifacts loading and display
Engine performance improvement: startup and BPM Services resume
Workspace import moved to a menu in Bonita Studio
Button widget and forms integration improvements
User management page in Administrator Portal is all new
Time picker improvement
"Initiator" switch for actors
UI Designer properties autocomplete for variables
Technology updates:
Other dependency updates
Feature removals:
Early warning: v6 forms removal in 2018
Studio profiles
Connectors
Deprecated BDM API
Configuration: platform_init_engine/bonita-platform-init-community-custom.properties file
API behavior change
Limitations and known issues
Bug fixes:
Fixes in Documentation:
BS-16697 internal.properties doc still not enough
BS-16862 Cannot fully deploy a REST API extension with Engine APIs
BS-16884 bpm/processSupervisor missing in the documentation
BS-16955 Link from 7.3+ documentation website to Corporate blog/news is incorrect
BS-16970 Install a Bonita BPM cluster Doc page unclear
BS-17061 Missing doc info: diagram REST API is only available in Subscription edition
BS-17251 apiAccessor.processAPI.getHumanTaskInstances doesn't work in call activity
BS-17479 IE11 missing from 7.5 list of supported browsers
BS-17527 Javadoc navigation bars rendering glitch
BS-17598 "Create your own password validator" steps lead to maven error: Could not find artifact
Fixes in Engine component:
BS-11460 Slowness in retrieving Dependencies blocks server from starting up
BS-15944 StaleObjectStateException: Row was updated or deleted by another transaction or unsaved-value mapping was incorrect
BS-15960 Using REST API to call BDM decreases the performance
BS-15975 process instance id and flownode instance id not found when executing the work for the Start event
BS-16519 Inconsistent behavior of Bonita Portal for multiple group with same name
BS-16595 "My Tasks" view displays executing tasks
BS-16612 Re-Import organisation file: errors and duplicate if some element name contains slash character
BS-16791 Can not have two extensions within the same REST API extension definition if one's pathTemplate is a prefix of the other's
BS-16862 Cannot fully deploy a REST API extension with Engine APIs
BS-16868 When there is communication issues with database sever, the works are lost
BS-16960 Issue with REST Connector stuck on sockRead no default timeout.
BS-16969 No license error in the logs when the performance activeProfile is set but the license is not performance
BS-16980 spring-web-4.3.7.RELEASE.jar requires more recent version of jackson than the ones included in the bonita.war
BS-16999 Cannot use $ and character for password defined in database.properties and use by setup tool
BS-17527 Javadoc navigation bars rendering glitch
Fixes in Studio component:
BS-16686 Studio migration 7.5 result in empty workspace
BS-16928 Links to documentation on Studio welcome page lead to the wrong doc version
BS-16971 Provided engine variables are not available in pattern expression completion
BS-16991 Not possible to remove "initiator" flag on an actor in the Studio
BS-17047 BDM pom generated from studio does not have all required dependencies
BS-17049 Groovy script size limited to 64k
BS-17067 Unable to create a new parameter from connector config
BS-17093 Expression editor return type set at null
BS-17121 Workspace API succeeds to build on rare ocassions
BS-17127 Focus problem on CTRL+f search pop-up in groovy script editor
BS-17154 Installer try to load invalid URL on macOS
BS-17156 .bar file generation failed: corrupted .proc file
BS-17199 "select / unselect all" buttons from export organization dialog box do not refresh validation status
BS-17206 CTRL+A does not work in pattern expression editor
BS-17210 Download defaut confirmation layout does not work for V6 forms
BS-17299 Call activity Data to send fetch Data button throw error and broken empty popup
BS-17447 "Multiple Document" type lost in migration and operation fails
Fixes in UIDesigner component:
BS-16708 Time picker doesn't behave the same if, in the date picker, a date is selected or if Today is selected
BS-16854 Part of "Filters" embedded help is not translated
BS-16923 Put only 1 proposal instead of 3 in time picker
BS-16977 Link widget additional url parameters are not passed (based on a contribution of a Community member)
BS-16983 File viewer and link widget use wrong docbase URL to display document
BS-16996 External System Document not usable in file viewer widget or Overview
BS-17278 Cannot update custom widget property
BS-17526 Label property of input widget has not correct type
Fixes in Web component:
BS-15960 Using REST API to call BDM decreases the performance
BS-16519 Inconsistent behavior of Bonita Portal for multiple group with same name
BS-16595 "My Tasks" view displays executing tasks
BS-16612 Re-Import organisation file: errors and duplicate if some element name contains slash character
BS-16791 Can not have two extensions within the same REST API extension definition if one's pathTemplate is a prefix of the other's
BS-16980 spring-web-4.3.7.RELEASE.jar requires more recent version of jackson than the ones included in the bonita.war
BS-15849 Internal Server Error in Report when report has a space, and clicking on date range.
BS-16097 Dynamic CaseContextPermissionRule implementation always provides access when requested by an archived case
BS-16234 Download servlets not secured by authorization filter + dynamic rule invalid
BS-16324 Living Application ressources are not cached
BS-16449 Administrator "Do for" raises a 403 error when security.rest.api.authorizations.check.enabled is set to false
BS-16481 Process Manager profile can't Edit case variable
BS-16678 Portal displays "Successfully updated categories" when the category is not created
BS-16685 Executing a task or instantiating a process from Mobile Portal redirects to Portal
BS-16756 Resize window cuts the Instantiation form
BS-16774 Get HTTP 400 Error page, on redirect after submit task in the portal and on Mobile
BS-16790 ClientAbortException are generated in the log files when a submit button redirect on success on an application page
BS-16858 Pager empty pager_bottom using Bonita Wildfly Bundle in HTTPS in Chrome
BS-16929 Security Issue: Autocomplete Enabled inForm
BS-16953 CustomPage servlets do not set a content-type in the response
BS-16992 CannotResolveClassException: org.apache.catalina.util.ParameterMap on engine on Wildfly when portal is on separate Tomcat
BS-17119 Cannot load ressources or classes from the custom Rest API
BS-17176 new line in human step comment are lost when the comment is displayed in the portal
BS-17204 Layout iframe always display a border
BS-17207 Calendar Date picker + Suggest box v6 are not displayed under/above their input fields in Chrome v61 when the scroll bar is used
BS-17231 CSRF token cookie missing when accessing a form URL directly after loging in with SAML
BS-17285 Profile token loss makes "View case design" show blank page in Process Manager's Cases tab
BS-17495 displayName Update breaks the view diagram
BS-17550 Do not encode URL param on redirect in living application servlet
BS-17574 v6 form broken when task name contains special character

New in Bonita 7.5.4 (Aug 4, 2017)

New in Bonita 7.5.2 (Jul 22, 2017)

Bonita BPM 7.5 includes a set of new features related to Living Application development and deployment as well as UI personalization, in addition to
important technology updates and bug fixes.
Living Application development and deployment:
New wizard to import a process in the studio & compare the artifacts:
Bonita BPM Studio provides a wizard when importing a .bos that displays the duplicate artifacts (forms, connectors, ...) and asks for user actions,
between keeping the existing artifact and overwriting with the newly imported artifact:
Ease collaboration between teams who work with .bos exchange
Reduce drastically the risk of overwrite error during import of a .bos.
Industrialization of Living Application (in Studio):
Bonita BPM Studio provides an editor to create the Living Application descriptor (metadata and navigation) that took place in Bonita BPM Portal
(Administrator profile) in previous versions. This is the first step towards a full Application artifacts development into Bonita BPM Studio in future
versions (Efficiency, Performance edition) :
Create and edit application descriptors in Studio.
Construct application navigation from inside Studio based on existing artifacts.
Store the descriptor in a VCS.
Deploy on the local portal to preview the Living Application and export for your production environment.
UI personalization:
New management of date/time in BDM, contracts, and user interfaces:
New management of date and time used in Living Applications across multiple timezones. It now follows the philosophy of Java 8 date management:
Benefit from Java 8 improvement of date/time management in order to better manage timezones in BDM, contracts, and UI (forms and
pages). Covers the following use-cases:
input and display a birthdate (not time related).
define and display meeting date and time (displayed in user timezone).
define and display a flight arrival date and time (displayed the same anywhere on the globe).
Note: this update does not change the way dates are displayed on Bonita BPM Portal.
Link widget and preview improvement:
The Link widget as been improved in order to support more use-cases; it can now be tested in the preview window in most cases. Improvements are:
Addition of a new property to pass additional query parameters when creating a link to a form or a page
Addition of a new property to pass the name of the target application (useful in the preview when you want to test a link to an application
page or when you need to redirect to another application)
The URL of the preview can be edited to pass additional parameters in the query string in web browsers supporting it (currently, only
Firefox)
Technology updates:
Full Java 8 support:
Bonita BPM is fully compatible with java 8 in production and development environment. It allows to write java 8 extension points (Connectors, Actor
Filters, Custom Pages, ...). Java 8 syntax and specific APIs can now be fully used in all Bonita BPM extensions points. JRE or JDK 8+ is required to
run. Bonita BPM 7.5.0+ cannot be operated on Java 7.
Support of Microsoft Edge:
Bonita web tools and user interfaces are fully compatible with Microsoft Edge and IE 11 browsers (UI Designer editor, all artifacts generated by the UI
Designer (Forms, Pages, ...), Bonita BPM Portal).
Integration of SSO SAML 2.0:
Bonita BPM works with Single-Sign-On (SSO) solutions using SAML V2 protocol (Teamwork, Efficiency, Performance edition) :
Use standard authentication service
Connect to Bonita Living Applications with company credentials (per tenant configuration)
Common SAML 2.0 Identity providers: ADFS (MS Active Directory Federation Services), SalesForce, Open AM, Google Auth,...
Removed support:
Oracle Weblogic application server:
Bonita BPM 7.5.0+ does not support Oracle Weblogic application server anymore.
Refer to full software requirements for more details on supported environments.
Internet Explorer 9 and 10:
Bonita BPM 7.5.0+ does not support Internet Explorer 9 and 10 anymore.
Refer to full software requirements for more details on supported environments.
Other dependency updates:
hibernate is updated to 4.3.11, to support JPA 2.1 specification
httpclient is updated to httpclient 4.5.2
httpcore is updated to httpcore 4.4.4
spring is updated to spring 4.3.7
API removals:
Engine APIs have been cleaned up from some deprecated methods:
ProcessAPI.addComment() - replacement method is ProcessAPI.addProcessComment()
Breaking changes in UI Designer:
Ui-bootstrap.js library removed from runtime:
In our first design iteration, forms, pages and layouts designed with the UI Designer embedded UI Bootstrap js, version 0.13.4 by default and silently,
even when not needed. We have removed it so you can use it only when you need it, and with the version you choose.
Before this change, custom widgets could be created based on angular-bootstrap v0.13.0 with no explicit addition of angular-bootstrap as an asset
and without declaring required modules.
This will not affect any artifact that has been created with the UI Designer and is currently deployed in Bonita BPM Platform.
In development though, if your custom widgets use angular-bootstrap, you need to add angular-bootstrap as an asset at widget level, and declare the
appropriate required modules.
Forms, pages, layouts CSS cleaned:
The default CSS file embedded in UI Designer artifacts (except custom widgets) has been cleaned. Indeed, some of this CSS rules were overall not
used and cluttered this file.
This will not affect any artifact that has been created with the UI Designer and is currently deployed in Bonita BPM Platform.
Nevertheless some unwanted style could appear when importing a custom layout based on the default layout of Bonita BPM prior to 7.5.0. If you do so
and observe that the layout menu does not fit the whole width of your page, you can bring back the default style by adding the following lines in
layout.css file.
.component .container{
width: 100%;
We recommend that you re-create your custom layout based on Bonita 7.5.0+ default layout.
Limitations and known issues:
MacOS Sierra (10.12): Bonita BPM Studio installed using the zip package fails during launch. Bonita BPM can successfully be installed
on MacOS Sierra using the dmg package
MacOS environment: starting from MacOS El Capitan 10.11.4 (March 2016), new security rules block the launch of Bonita BPM Studio.
You must temporarily remove security on App launching in System Preferences→Security & Confidentiality.
Bug fixes:
Fixes in Documentation:
BS-16372 7.4.x Deploy bundle installation procedure in not clear enough
BS-16731 Applications Portal doc page still states that application development occurs in the Portal
Fixes in Engine component:
BS-16482 REST API Extensions are unstable in debug mode
BS-16611 Alfresco connector breaks case instantiation
BS-16629 Issue while resuming BPM services in Wildfly and cluster mode
Fixes in Studio component:
BS-16684 Business Object attributes table with height too short to access buttons on BDM Management
BS-16692 Incoherence after contract type update
BS-16699 In application page tokens,"-" and "_" are not considered as valid characters
BS-16705 .proc file size is too BIG due to complex contrat input references in expression
BS-16723 Wrong studio warning: cannot store the count query in a process data of type long
BS-16729 When switching from one diagram to another, tab operations is not updated
BS-16730 Missing import of BPMN2 diagram in the Studio
BS-16732 Cannot assign a Parameter to a Data to send to a child process
Fixes in UI Designer component:
BS-16736 leaving the Rich text Area Max value empty leads to an error message
Fixes in Web component:
BS-16482 REST API Extensions are unstable in debug mode
BS-16021 Http 400 response for font resources in an application page designed with UID
BS-16263 Security fails in bonita/portal/resource/app and LivingApplicationPageServlet
BS-16350 While using IE, IFrame removal causes loss of the ability to focus input elements
BS-16474 Analytics Case history japser report broken
BS-16758 Bonita wildfly bundle startup failure with the MS SQL Server 6.0 JDBC Driver Version
BS-16809 File contract input is loaded twice in memory

New in Bonita 7.5.1 (Jun 8, 2017)

New in Bonita 7.5.0 (Jun 8, 2017)

BS-12872 Cannot retry a task if the displayName script fails
BS-15232 Web Service Connector fails when receiving HTTP Code status 307
BS-15721 Import a layout from 7.x (prior to 7.3) into 7.3 UIdesigner overrides the widgets
BS-15730 getProcessBusinessDataReferences : NullPointerException if BusinessData is multiple AND list contains a null
BS-15796 Angular bootstrap 0.13.0 is included in vendor.js during runtime
BS-15799 When path contains a special character (accent) then widget directive fails to build
BS-15822 Cannot use SOURCE_OBJECT_ID in the Search API of Archived Comments
BS-15868 Upload field in V6 legacy forms raises a SEVERE harmless error
BS-15899 With CAS, Redirect URL drops id parameter if the process name contains "id" in the name
BS-15913 SSO - CAS: service parameter is not properly checked on the URL
BS-15949 Form V6 URL can be used to list all process instance variable values (autogenerated form)
BS-15956 Postgres processes are stuck to 100% for a while due to SQL requests involving user_ and actor tables
BS-15962 bonita.cluster.name property is not used to set the cluster name for the MulticastJoiner from Hazelcast
BS-15977 Variable completion does not work if NOT operator (!) is used
BS-15984 Custom Layout - Adding widgets on top of the widget menu increase its height
BS-16006 Impossible to add row on a editable grid in a V6 form
BS-16046 File name not refreshed in File upload widget after file deletion and re-upload of the same file
BS-16067 Data Table paging footer is not usable when too many records
BS-16078 widget link + Human Task / Instantiation / Overview is broken in preview
BS-16105 UI Designer Editor 7.4 is not working on Safari
BS-16115 Request Key and License file contain a wrong osName with Windows 10 and java8_u40 - License Error 27,423
BS-16121 Only one translation key between server/"build" menu and REST API/"build" button which leads to a wrong translation
BS-16168 Several catch Link events and inclusive and parallel gateways wrong behavior
BS-16169 Unique catch Link event receiving several throw links event and inclusive and parallel gateways wrong behavior
BS-16187 Updating MULTI_INSTANCE_ACTIVITY task state to "skipped" does not update state of "child" task instances
BS-16213 OracleXAException when resuming BPM Services with WildFly + Oracle /11g R2 after installing Business Data Model
BS-16221 Page title is incoherent with page message, 404 error vs. 403
BS-16241 X-Bonita-API-Token Duplicated in login response header
BS-16273 SVN repository Migration loses Form critical files
BS-16280 StringIndexes / search keys are not updated in sub-processes
BS-16282 Parent process stringindex (search key) is updated with a human task's operation part of a subprocess
BS-16288 Cannot use Japanese characters in Repository name
BS-16291 Deleting and re-instantiating a Business Object in the same task fails
BS-16292 Create a new form is missing
BS-16298 TimeoutException is hidden when it occurs during actor filter execution
BS-16311 BDM deployment confirm message not translated in French
BS-16339 Browse H2 database not working on Windows if install folder includes spaces
BS-16345 Rich text Area Preview raises errors in the developer tool console debug
BS-16364 Enable to type € character in custom widget template on Windows
BS-16366 Can not reopen the preview popup on Safari
BS-16377 Generated documentation on non-interrupting boundary events not reported properly
BS-16409 Whole Portal displays Half screen in IE11 version 11.0.40 (windows Update KB4012204)
BS-16410 Remove example on businessDataReference API since it is deprecated
BS-16415 Typo in BOSWebServerManager.java implies that tech user password MUST equal tech user name
BS-16451 taskAssigneeId cannot be resolved in groovy script editor in an Activity operation
BS-16454 Cannot initialize a business object with a query with parameters - value not saved in Studio
BS-16486 Documents cannot be used as connectors inputs
BS-16504 Business object lost and transformed in string when used in a email connector after a change
BS-16507 UI Designer Preview: Uncaught DOMException: Failed to construct 'WebSocket'
BS-16511 Editing group description breaks relation with child group
BS-16517 Contract "Add Data" with a document fails
BS-16531 Contract input description should not be linked to widget placeholder in form generated by the developer

New in Bonita 7.4.3 (Jun 8, 2017)

New in Bonita 7.4.2 (Mar 9, 2017)

New in Bonita 7.4.1 (Feb 1, 2017)

New in Bonita 7.3.3 (Oct 19, 2016)

Bonita home removal:
Starting from Bonita BPM 7.3.0, there is no more Bonita Home to store the configuration, all the configuration is in the database.
Please refer to the platform configuration page to find out how to manage configuration.
It simplifies bundle configuration and cluster deployments by removing file system dependencies (no more shared filesystem) and enables hot backup of runtime data. Here are more details
Fewer files to configure
Configuration can be managed remotely (new admin tool in command line)
Deployment process is ready to be automated with scripts
Database schema creation can be reviewed by DBA
Database can be created before the first start of the engine
Improved messages in the logs explain the checks done by the Engine at startup.
Backup is easier (no need to synchronize database backup with filesystem anymore)
Backup is possible without downtime (depending on DBMS vendor capabilities)
The migration tool is impacted by the removal of the Bonita Home folder. Please see the associated release notes for further details.
User task list re-design
The users can now:
Choose between 2 view modes to efficiently pick the right task and do it fast:
Master / Details: when selecting a task in the list, a detail panel displays the form to submit so you don't go back and forth between list and forms.
Wide table: a large table displays task details with the possibility to use display name for tasks that include business data. In this view, the form is displayed in a popup
Easily view large forms with the option to expand the form panel to any size
Select columns to be displayed in the list
Select the number of elements per page
Retrieve information on the case thanks to the case overview, displayed just a tab away from the form.
Allow users involved in a case to exchange comments on the case directly from the task list, just a tab away from the form.
Note: User display preferences are stored in the Browser Local Storage
New UI Designer widgets
New widgets in UI Designer for Subscription edition:
File viewer
It adds the capability to preview or download a file or a process document in a page or a form.
With this new widget, you can display a document in a modal dialog box or directly in the page.
The documents displayable are limited to the document supported by the end user browser (by default pdf and images on usual browsers). Documents that are not displayable are prompted to be downloaded.
Rich Text Area
It adds the capability to edit formatted text from a page or a form.
With this new widget, you can add rich text area for end users to create text to be exported in HTML format for integration on emails, etc.
Text area can be prefilled with an HTML template.
Toolbar options exposed to end users can be customized and localized with the usual localization mechanism (localization.json file).
UI Designer usability improvements
Many improvements to existing features:
Generated form from contract (in the Studio) are filled into a Form Container using basic form validation.
Quick save everywhere on the editor with the usual keyboard shortcut Ctrl-S.
Custom Widgets and Fragments have now their own icons with an auto-generated image displayed on the editor palette and whiteboard. For Custom Widget, it is now possible to customize the template for better whiteboard rendering.
New icons for the different containers.
In Custom widget editor, it is now possible to add a caption and tooltip when adding or editing a widget property.
In Fragment Editor, when a data is exposed, it is shown as (exposed) in the variables panel.
Subscription Edition: On DataTable widget, when there is only one page, the pagination footer is removed.
Home Page: when clicking on Create, the selected artifact type is the same as the current selected tab.
UI Designer Date Picker improvements
Capability to edit and set manually the dates with a format validation (works within a Form Container)
Capability to add a "Today" button to select automatically and quickly the current day.
Subscription Edition: Calendar can be localized with the usual localization mechanism (localization.json file).
Other minor changes
Tomcat has now better default log messages: clearer, less redundant, shorter log lines
Limitations and known issues
MacOS environment: the new version of MacOS El Capitan 10.11.4 (March 2016) has introduced new security rules that block the launch of Bonita BPM Studio. You must temporarily remove security on App launching in System Preferences→Security & Confidentiality.
6.x legacy forms: There might be some graphical issues (CSS) when displaying 6.x forms in the right panel of the new user tasklist. Use preferably the expended mode (full page list + popup for the form) or modify the portal look & feel in order to add a min-width to the from container in BonitaForm.html
Default applications layout is not compatible with new task list custom page
Having executed a task in a subprocess, I cannot see the overview of the root process instance
Bug fixes
Fixes in Bonita BPM 7.3.3 (released on October 7th, 2016):
BS-15920 "Thank you" page does not open at the end of installer execution on Windows
BS-15904 Studio does not use embedded JRE on Mac OS X 10.11.1
BS-15888 Cannot run process when Actor mapping defined with Group starting with the same string
BS-15875 Data table: Runtime page and Preview reloads when user click to order a column
BS-15831 push enter when an input is selected do a bad submit of the form
BS-15816 User/group/role avatar does not refresh when updated
BS-15806 Fail to compile bonita-web
BS-15802 Placeholder font style is too close from input style
BS-15793 Cannot Select element when using the search of user/role/group/membership in the Process Manager and Actors mappings
BS-15792 Impossible to remove user/role/group/membership one by one from the Process Manager mapping
BS-15791 Process manager Mapping only shows 5 elements
BS-15783 Impossible to edit the list of member/role/group/membership in the Process Manager mapping
BS-15774 Error when editing group or role in Portal
BS-15759 Portal - Can't switch to profile "Process manager" in Internet Explorer 11
BS-15752 Instantiation form submit: Impossible to retrieve the process definition id value from the URL
BS-15743 Classloader remove when the first node of a cluster is shutdown
BS-15713 Fileviewer widget does not use the right id to preview document
BS-15535 engine do not start if no licenses in platform_conf folder even if platform already initialized
BS-15486 Wrong archived case ID retrieved from URL parameter in overview page for archived case
BS-15485 Rest API Extensions broken after migration - Error 403
BS-15356 IE9: Select widget with dynamic list does not show all the values in the list.

New in Bonita 7.3.2 (Sep 5, 2016)

Studio Switch Repository (Teamwork Edition):
There is now one Bonita Home folder (bonita_home) per Studio repository. The folder is located at the root of the repository.
The embedded Tomcat is configured to use the bonita_home folder of the repository currently in use. That is to say that each time a developer switches repository, the Tomcat switches Bonita Home. As a consequence each repository uses a different database; this allow to keep data consistency between runtime data and current repository content.
On a repository switch we do not lose Living Applications, Processes, BDM, Organization data...
REST API Extension Development tooling (Teamwork Edition):
New development tooling to speed up REST API extension implementation. It improves developer efficiency with automated testing and deployment.
This helps Java developers creating new custom APIs by assisting and automating the development, testing, and deployment of REST API extensions. It also helps front-end developers to access and use REST API extensions directly from UI Designer. The guided development framework reinforces the best practice of creating REST API extensions to read data needed in forms or pages.
Office connectors (Teamwork Edition):
Insert information into a Microsoft Word *.docx or OpenOffice *.odt template to produce a document based on data collected in a process case. In addition to Word and OpenOffice output format you can also generate a PDF document.
Insert data in a .docx/.odt template
Generate PDF from an Office document.
BDM Paged results:
Retrieve results of a query on business data a page at a time. Previously, a BDM query returned all the matching results.
The paged results feature enables you to know how many pages of results exist when calling a BDM query via the REST API. It ensures a better integration of BDM with UI Designer DataTable widget.
To benefit from this improvement and use the UI Designer DataTable widget for custom BDM queries, you need to create a count query for each custom query that returns multiple results. The name of the count query must be the name of base query prefixed by “countFor”. For instance, for a custom query named “queryName”, the related count query must be named “countForQueryName”. In addition, make sure that the count query returns a long. The result of the count query is visible in the HTTP response header, in the Content-Range field for the REST API API/bdm/businessData/businessDataType?q=queryName. This header will be available for all queries returning multiple results for which there is a related count query.
UI Designer Data Management:
We have changed the variable management mechanism, and made every variable read-write. It'll avoid confusion on the way data are managed by UI Designer(some are read-only but some are not, some are always recalculated and some are not).
This means that you can retrieve data using a REST API call and manipulate the results inside a JavaScript expression variable. The user can then update the variable, which is then submitted. As a result of these modifications, all variables are now evaluated even when they are not used. You need to be aware of the consequences of this for each type of variable.
A JavaScript Expression variable is reset to the expression evaluation every time the result of the expression evaluation changes. For instance, consider an expression variable processing a selectedUser from a displayed table to have information more readable. Consider that this selectedUser can be updated via a displayed form. When the user clicks on another user in the table, the form is updated with the value of the new selectedUser. Previous selectedUser data is lost if not managed correctl
A URL or REST API variable resources are reloaded every time the URL value changes.
We have also introduced an initial naive algorithm to find the dependencies of a given variable (the other variables it relies upon). This way, we can wait for non-dependant variables to be resolved before resolving ones that have dependencies.
UI Designer enhanced home page
UI Designer Homepage has been revamped. It can manage in a more efficient/scalable way the typical volume of UI artifacts of a typical BPM Apps project :
Capability to create any type of web artefacts: Application Pages, Process Forms, Application Layout, Fragments, Custom Widget.
Artefacts are presented per type on the different tabs.
Search bar to retrieve quickly any artefact based on its name. Number of artefacts matching a search are displayed on the tabs badges.
Add favorites artefacts and retrieve them quickly in a dedicated panel.
UI Designer usability improvements
Many improvements to existing features:
Container widget (added in 7.1.3) Added a default variable, $collection, used when repeating content in container to manipulate sub-collections.
Button widget (modified in 7.1.3) Additional HTTP actions GET and DELETE, and actions to update a collection.
Artifact import New checks on import:
If the uploaded artifact does not overwrite anything, the import completes and the import report is displayed to the user.
If the uploaded artifact overwrite something: a popup is displayed to the user indicating the elements that will be overwritten by the import. The user can choose whether to continue the import and overwrite the listed elements, or cancel the whole import.
Link widget has now the capability to choose the target window.
Add an dropdown on Preview window to view a multi-language page in a specified language based on the languages defined in the localization.json file.
Capability to download an asset added in a page/form or on a custom widget.
CHANGES:
Italian, German and Portuguese translations are no more included into the product (You can find into the documentation how to add your own language pack for the Bonita Portal).
Removal of the profile pop up at Bonita Studio startup
Relocating some artifacts that were on the file system (Bonita Home) into the database:
process definition
parameters
business archive (all files contained in .bar)
Request Key generator script now asks for licensing model (instances-based or legacy by CPU).
UI Designer Datepicker widget updates to remove timezone issues.

New in Bonita 7.3.1 (Aug 27, 2016)

FEATURES AND ENHANCEMENTS:
Bonita home removal:
Starting from Bonita BPM 7.3.0, there is no more Bonita Home to store the configuration, all the configuration is in the database.
Please refer to the platform configuration page to find out how to manage configuration.
It simplifies bundle configuration and cluster deployments by removing file system dependencies (no more shared filesystem) and enables hot backup of runtime data.
Fewer files to configure
Configuration can be managed remotely (new admin tool in command line)
Deployment process is ready to be automated with scripts
Database schema creation can be reviewed by DBA
Database can be created before the first start of the engine
Improved messages in the logs explain the checks done by the Engine at startup.
Backup is easier (no need to synchronize database backup with filesystem anymore)
Backup is possible without downtime (depending on DBMS vendor capabilities)
The migration tool is impacted by the removal of the Bonita Home folder. Please see the associated release notes for further details.
User task list re-design:
Choose between 2 view modes to efficiently pick the right task and do it fast:
Master / Details: when selecting a task in the list, a detail panel displays the form to submit so you don't go back and forth between list and forms.
Wide table: a large table displays task details with the possibility to use display name for tasks that include business data. In this view, the form is displayed in a popup
Easily view large forms with the option to expand the form panel to any size
Select columns to be displayed in the list
Select the number of elements per page
Retrieve information on the case thanks to the case overview, displayed just a tab away from the form.
Allow users involved in a case to exchange comments on the case directly from the task list, just a tab away from the form.
Note: User display preferences are stored in the Browser Local Storage
NEW UI DESIGNER WIDGETS:
New widgets in UI Designer for Subscription edition:
File viewer:
It adds the capability to preview or download a file or a process document in a page or a form.
With this new widget, you can display a document in a modal dialog box or directly in the page.
The documents displayable are limited to the document supported by the end user browser (by default pdf and images on usual browsers). Documents that are not displayable are prompted to be downloaded.
Rich Text Area:
It adds the capability to edit formatted text from a page or a form.
With this new widget, you can add rich text area for end users to create text to be exported in HTML format for integration on emails, etc.
Text area can be prefilled with an HTML template.
Toolbar options exposed to end users can be customized and localized with the usual localization mechanism (localization.json file).
UI DESIGNER USABILITY IMPROVEMENTS:
Many improvements to existing features:
Generated form from contract (in the Studio) are filled into a Form Container using basic form validation.
Quick save everywhere on the editor with the usual keyboard shortcut Ctrl-S.
Custom Widgets and Fragments have now their own icons with an auto-generated image displayed on the editor palette and whiteboard. For Custom Widget, it is now possible to customize the template for better whiteboard rendering.
New icons for the different containers.
In Custom widget editor, it is now possible to add a caption and tooltip when adding or editing a widget property.
In Fragment Editor, when a data is exposed, it is shown as (exposed) in the variables panel.
Subscription Edition: On DataTable widget, when there is only one page, the pagination footer is removed.
Home Page: when clicking on Create, the selected artifact type is the same as the current selected tab.
UI DESGINER DATE PICKER IMPROVEMENTS:
Capability to edit and set manually the dates with a format validation (works within a Form Container)
Capability to add a "Today" button to select automatically and quickly the current day.
Subscription Edition: Calendar can be localized with the usual localization mechanism (localization.json file).
Other minor changes:
Tomcat has now better default log messages: clearer, less redundant, shorter log lines
BUG FIXES:
BS-15244 Error 500 and NPE are generated when a cluster is started with FINEST log level
BS-15358 Exception thrown when starting server in cluster mode
BS-15407 Deploy a bar file with a file without content in Oracle11g doesnt work
BS-15487 Error "The script is null" while testing Groovy connector
BS-15511 Live update broken: "Violation of UNIQUE KEY constraint" message is generated when changing connector implementation with dependency
BS-15526 Process Manager profile can't delete case
BS-15536 Refine an existing Resource Permission Mapping fails
BS-15548 Studio does not validate (50 char max) contract input name length after click
BS-15572 ProcessPermissionRule.groovy prevents a process manager to update a groovy expression
BS-15588 Portal un-extracted strings for translation
BS-15632 Preview of initialisation script is empty when creating a contract from a data

New in Bonita 7.3.0 (Aug 27, 2016)

[BS-8234] - Current Tenant information is lost on session timeout
[BS-12240] - Sequential multi-instantiation with empty list unexpectedly create one instance
[BS-13575] - java.lang.Error thrown at connector execution blocks the process instance and is not logged
[BS-13652] - Unique index in ref_biz_data_inst contains nullable fields
[BS-13653] - Unique index in group_ table contains nullable fields
[BS-13654] - Unique index in page table contains nullable fields
[BS-14027] - Date picker not internationalized
[BS-14279] - "item not found" error popup when starting a process fully automated without instanciation form
[BS-14579] - ProcessAPIImpl.cancelProcessInstance fails when parent Process cannot find subprocess
[BS-14629] - Unreleased Resource: Streams
[BS-14766] - jackson-annotations-2.2.3.jar redundant dependencies JBoss Bundle
[BS-14816] - Executing task lead to violation of unique constraint : idx_uq_pending_mapping
[BS-14833] - Javadoc is not clear for archived methods and InstanceId parameter
[BS-14837] - Cannot replay a gateway on Community edition with flowNode REST API
[BS-14844] - typos in wizard "create contract inputs from document"
[BS-14868] - Groovy autocompletion do not display proposals
[BS-14878] - When importing a .bos from the Studio, all "favorites" UID artefacts are kept
[BS-14879] - UsedBy property is wrong for forms and layout
[BS-14885] - Living application layout log 3 error 500 on loading
[BS-14903] - Engine creates new temporary files at each startup without cleaning old ones
[BS-14960] - Overview: started or terminated : Access denied: you do not have the rights to view this page
[BS-14976] - Overview and actor filter and sub process : started or terminated : Access denied: you do not have the rights to view this page
[BS-15003] - BO POJO Clear the list without check
[BS-15072] - Incoherent behaviour of the legacy overview form
[BS-15073] - ehcache (Hibernate Level 2 cache) has a configuration issue: all objects are cached into default cache (all together)
[BS-15085] - Create New Application raises SEVERE error
[BS-15123] - Contract data not found when used in a BDM query setting default value of business variable at Event Subprocess start
[BS-15155] - Engine API getArchivedUserTaskExecutionContext fails with documents
[BS-15172] - REST API humanTask miss parameters, standard search parameters is incomplete
[BS-15174] - Portal: blank page after log in on Windows with bonita.home located on a network drive
[BS-15195] - Process manager mapping memberships entities selection fails when using the search with blank spaces
[BS-15202] - Radio group button in connector selects two values at the same time
[BS-15213] - TextArea in a group with contingency is not editable with IE11
[BS-15219] - Published organization falls back to ACME or none after studio restart
[BS-15236] - Documentation REST bpm case comment missing
[BS-15241] - Cannot import REST API extension based on provided example
[BS-15253] - Legacy forms contingency: Show when a trigger field has changed generates a NPE
[BS-15256] - Sub Fragments not Displayed in UI Designer whiteboard
[BS-15261] - Task Assign doesn't block another user + No message for other user when task is done
[BS-15270] - Studio information collection failed when using HTTP proxy that requires authentication
[BS-15274] - Cannot display the diagram overview if a message contains the '+' (plus) sign
[BS-15275] - Event sub process creates a new BO instance instead of updating the parent one
[BS-15276] - Ambiguous Error message when Custom connector using BDM dependance bdm-polo.jar conflicts with automatic dependencies
[BS-15314] - Studio and Portal copyrights are out of date
[BS-15315] - Rest API Extension not commited
[BS-15317] - SVN lock not released when closing Diagram
[BS-15322] - NullPointerException in the Portal when deploying a Process with UI Designer selected but no forms included
[BS-15323] - Rest API Extensions not Synchronized after a commit in SVN
[BS-15325] - Find query that select subset of object attributes failed
[BS-15329] - SSO with CAS: specific URL to log in as tenant administrator is failing
[BS-15336] - SSO with CAS: JBOSS/modules/org/jasig/cas/main/module.xml contains an invalid resource element.
[BS-15337] - Organization and Environment SVN Delete only remove file in Local
[BS-15338] - Cannot remove date on datepicker once selected
[BS-15340] - Problem using saved connector configurations
[BS-15341] - Multiple Task Bars in Mobile view
[BS-15345] - Login from Portal License tab URLs not encoded - 403 Forbidden - Login fails
[BS-15355] - Cannot import a diagram exported as BPMN2 in Eclipse BPMN modeler
[BS-15357] - Studio cannot import a BPMN process
[BS-15362] - As a real hacker, execute code (XSS) in the web browser of your victim
[BS-15364] - Case fails on End Event when the Business data are archived in Performance edition
[BS-15371] - Memory leak on the engine
[BS-15379] - Publish in 7.2.x studio an organization created in 6.2.1 fails for unexplain reasons
[BS-15403] - It is no more possible to use a query to assign a bdm to a legacy form transient data
[BS-15410] - Double menu after a sequence Form V6 + Form UIDesigner
[BS-15411] - Error deploying process from Studio
[BS-15418] - Process "Enable/Disable" button randomly disabled
[BS-15444] - OutOfMemoryError: PermGen space when using BDM
[BS-15447] - Invalid JSON produce by /API/bpm/activityVariable when process variable is null
[BS-15451] - Connection with the anonymous user doesn't recreate /bonita/client/tenants/1/work/ correclty after Migration
[BS-15457] - REST API extension can't be deployed if user walter.bates is not into the Organization
[BS-15488] - Date Picker Display broken in an Application in Chrome
[BS-15494] - Studio Reset Engine doens't work
[BS-15495] - init without license result in an inconsistent state
[BS-15497] - MANIFEST.MF is not generated properly when repository name is not a valid java identifier
[BS-15512] - Task Perfomer Actor filter only works once
[BS-15525] - Task iteration multi-instanciation output result data "is multiple" shouldn't be checked by default
[BS-15546] - Missing translation in Case Overview page

New in Bonita 7.2.3 (Jul 6, 2016)

New in Bonita 7.0.2 (Aug 8, 2015)

UI designer :
The Property Panel has been enhanced. All property fields are now typed. This helps to clarify the behavior of a property and the capability of each field. There are several types of property value: Constant, dynamic value, bidirectional bond, and interpolation:
A constant is a literal, fixed value.
A dynamic value field contains either a constant (the default) or a JavaScript expression.
A bidirectional field specifies a read-write binding between the property value and a variable.
An interpolation field contains text to display in the widget including variables that are interpreted using AngularJS interpolation.
The new image widget is used to include an image in a page. The image widget can use either an external link or an image asset as the source of the image.
Assets usage have been improved. You can now disable an asset to manage libraries conflict at page level.
Migration:
There is a new 2.x migration tool for migrating from 7.0.0 or 7.0.1 to 7.0.2. See the migration tool release notes.
If you are migrating from a 6.x.y version you must first use the latest 1.x migration tool (1.23.1) to migrate to 7.0.0, and then use the 2.x tool to migrate from 7.0.0 to this version.
Limitations and known issues:
This product version does not provide German localization.
Cannot perform pagination with BDM Rest API. o Workaround: implement your own server-side pagination through a REST API extension using multiple BDM requests.
AngularJS Form validation in UI Designer does not work completely.
In the UI designer, when you rename a fragment there is no validation that the name is unique, so naming collisions are possible.
There is no out-of-the-box mechanism for displaying a confirmation message when submitting a form. o Workaround: specify a confirmation page manually in the UI Designer.
Autologin/Anonymous access to forms is not available with the new form application.
To create a form using the UI Designer, the user must to create it from the Form tab or Contract tab in Bonita BPM Studio. The New button in UI Designer creates only pages, not forms.
Process Context and Task Context are not yet configurable. They contain all the references to Business Data and Document manipulated in the process instance. Forms do not benefit from the Application Look & Feel. You cannot apply the application theme to a form using the shortcut “../theme/theme.css”. o Workaround: specify the full path of the theme in the index.html of the form.  In a form, there is no simple way to display a business object that is used in a Multi-instance Human Task.
Using Chrome, when editing an application URL, or a page URL, the cursor always jumps to the end of the line.
BS-13748: NPE in WaitingEventsInterrupter.interruptTimerEvent
BS-13555: No confirmation message when overriding page/fragments/widget during import
BS-13360: The TaskList Custom Page from Customer Portal does not work with version 7.0
 BS-12723: It is not possible anymore to skip case start form
 BS-13654: Unique index in page table contains nullable fields

Bonita Changelog

What's new in Bonita 2023.2-b2 Beta

New in Bonita 2023.1 Beta 1 (Mar 15, 2023)

New in Bonita 2022.2-u0 (Oct 4, 2022)

New in Bonita 2022.1-u0 (Mar 31, 2022)

New in Bonita 2022.1 Beta 1 (Feb 10, 2022)

New in Bonita 2021.2 Beta 2 (Oct 24, 2021)

New in Bonita 2021.1 Build 7.12.1.1 (Mar 3, 2021)

New in Bonita 7.12.1 (Feb 19, 2021)

New in Bonita 7.11.4 (Jan 19, 2021)

New in Bonita 7.11.3 (Nov 26, 2020)

New in Bonita 7.11.2 (Oct 1, 2020)

New in Bonita 7.10.5 (Jun 4, 2020)

New in Bonita 7.10.3 (Mar 6, 2020)

New in Bonita 7.8.4 (Apr 18, 2019)

New in Bonita 7.8.3 (Mar 7, 2019)

New in Bonita 7.8.2 (Feb 14, 2019)

New in Bonita 7.8.0 (Dec 7, 2018)

New in Bonita 7.7.5 (Nov 23, 2018)

New in Bonita 7.7.4 (Sep 7, 2018)

New in Bonita 7.7.3 (Aug 3, 2018)

New in Bonita 7.7.2 (Jul 13, 2018)

New in Bonita 7.7.1 (Jul 12, 2018)

New in Bonita 7.7.0 (Jun 7, 2018)

New in Bonita 7.6.3 (Mar 6, 2018)

New in Bonita 7.6.2 (Feb 1, 2018)

New in Bonita 7.6.0 (Dec 9, 2017)

New in Bonita 7.5.4 (Aug 4, 2017)

New in Bonita 7.5.2 (Jul 22, 2017)

New in Bonita 7.5.1 (Jun 8, 2017)

New in Bonita 7.5.0 (Jun 8, 2017)

New in Bonita 7.4.3 (Jun 8, 2017)

New in Bonita 7.4.2 (Mar 9, 2017)

New in Bonita 7.4.1 (Feb 1, 2017)

New in Bonita 7.3.3 (Oct 19, 2016)

New in Bonita 7.3.2 (Sep 5, 2016)

New in Bonita 7.3.1 (Aug 27, 2016)

New in Bonita 7.3.0 (Aug 27, 2016)

New in Bonita 7.2.3 (Jul 6, 2016)

New in Bonita 7.0.2 (Aug 8, 2015)

New in Bonita 7.0.0 (Jun 19, 2015)

New in Bonita 6.5.0 (Apr 3, 2015)

New in Bonita 6.4.0 (Dec 17, 2014)

New in Bonita 6.3.0 (Jun 6, 2014)

New in Bonita 6.2.6 (May 6, 2014)