Release notes
New values added
Low code application development: business data management from the Studio to the UI Designer
Easily create forms where business variables or documents are edited by the users (read/write)
A form that allows a user to edit business variables or documents needs to display the current values before the user modifies them.
The Studio now creates the variables needed to display the current values and links them to the same widgets than the widgets linked to the task contract: what the user needs to fill and send back to the process.
No need to create variables and manipulate the BDM REST API anymore.
In the generated forms, the property required of the widgets now reflects the property mandatory of the corresponding attributes in the BDM. All contract inputs were marked required before.
⚠️This is not the case for DatePicker and DateTimePicker types yet: they still are always required. This limitation will be fixed shortly.
For more information, read the dedicated documentation.
Easily display read-only business variables in forms
A lot of forms that require users' input or edition of business variables also need to display other business data as read-only information. This information is useful to the users to make the right inputs and/or decisions. For each form created for a task, the studio now gives the option to display all attributes that are linked to the business objects used to create the contract inputs as read-only widgets. The unneeded attributes can easily be deleted, all useful ones are ready to be displayed to the users, saving a lot of development time. For more information, read the dedicated documentation.
New embedded AngularJS filter to resolve the lazy references of a business object
This improves the management of embedded objects with lazy references. When in the need to retrieve lazy references of objects for either edit or read-only use-case, the above features create a variable using the | lazyRef filter for the object to retrieve (as well as the widget to display the variable). For more information, read the dedicated documentation.
Switch widget
Directly from whiteboard or from widget properties section, you will now be able to change your current widget by a new one without loosing the configuration you have done. Useful when switching to a new version of your widget custom or not, and as first customization steps after your form creation from studio to match your end user needs. ⚠️This feature is not available on Edge and IE 11 browsers.
Update multiple documents
Operations at the level of tasks now handle the complete update of multiple documents: add/delete/update are automatically managed by the method, using document Ids. This improvement is also implemented in Bonita Portal case overview, where only the last version of each document is visible, and each document gets two widgets: file viewer to access the document, and file upload to update it.
Render a UI Designer page and form in the end-user browser
Now you can open your preview in a browser tab, outside of current preview mechanism to allow you set new URL parameters, play with dynamic browser sizing, and to reuse same url in another browser to see how your form or page behaves in your user default browser.
A new method for Living Applications buttons: "Assign and execute"
A new action is available on the provided Button widget in the UI Designer: "Assign and submit task". This action is mandatory for ACM use-cases, where a user often manages a given case on his own, from begining to end, but can be used in many other use-cases. As a result, a user of an ACM-type Living Application can view and fill out the form of any available task in the case, and then simply click on "Submit". This is different from Bonita Portal Task List where the user needs to click on "Take" to book a task and take it out his colleagues' To Do list.
Continuous delivery of projects / Industrialization
"Theme" projects are now integrated in Bonita project (Subscription only)
From the Studio, the theme can now be created as any other part of a Living Application, from the Development Menu and from the Project Explorer "New" option. It is packaged as a Maven project, just like the REST API extensions, and is nested in the Bonita project. A theme created in the Studio can be deployed to the Portal, and managed (open, edit, delete) as any other element of the application. The theme is taken into account in Bonita Continuous Delivery, through the builder and the deployer. For more information on how to use it, go to the dedicated documentation.
View a UI Designer artifact within an application theme while developing
Once the theme is mapped to applications, it can be used to view a page, form, layout or fragment under development in the context of the target application. To do so, a new "View in application" feature has been added to the preview window in the UI Designer, to ease the style adjustments of the artifact.
In Bonita Community, use customized themes and layouts in living applications
Themes created in an IDE can now be mapped with an application descriptor to customize the look and feel of a living application. Layouts created in the UI Designer can also be updated in an application descriptor for better customization.
Use provided UI Designer widgets as a template for a custom widget
Do you need a text widget that applies an specific numeric formating to match your external system keys? Do you need a table widget with specific padding? Bonita UI Designer provides a set of standard widgets to build your form & pages, and now you can extend them to fullfill your specific needs. In the Properties panel header, there is a new widget action menu. From this menu, you can launch all the widget-related actions, such as: edit, view, save as fragment (depending on the selected widget). From this widget action menu, you can view the widget, clone it as a custom widget and modify it. It will be directly available in your palette for further uses.
Manage UI Designer assets order to guarantee user interface rendering
Apply the right order on assets affects the behaviour the page such as the order or CSS loading to override styles, or JS object declarations. Base framework assets are now visible to show you which ones are used to build your UI Designer page, such as Angular or Bootstrap and in which version, additionally a documentation link has been added to take benefit of such frameworks documentation.
From Bonita Portal to Bonita Living Applications
We are pursuing the initiative of progressively migrating Bonita Portal to our UI Designer technology and transforming it into three applications, one per provided profile. Each new page is provided as a new custom page that is responsive, that can be customized in the UI Designer, and used in any living application.
"Install/Export Organization" for the Administrator Portal
It offers the same features than the old Portal page:
-
A file updload expecting the .xml of an organization
-
An Export button to download the .xml locally and share it Additionally, it offers better validation (checks for any error in the file format with a dedicated error message).
A new Bonita Layout
Created with the UI Designer, it is responsive, it can be customized and added to any living application. It is composed of a few custom widgets. Provided as a Resource in Bonita Portal (the old one is deprecated), it can be imported and edited in Bonita UI Designer. It offers new features:
-
A "list of applications" icon: once clicked, it displays a modal window that lists the available Applications for the profiles of the loggued user, so the user can pick one and switch application.
-
The name of the loggued user: once clicked, it displays a modal window with user’s information, the language picker for the application and a logout button It is compliant with all browsers: Microsoft Edge, IE11, Mozilla Firefox and Google Chrome.
Getting to Adaptive Case Management (ACM)
Bonita Platform now embeds the underlying mechanism that allows the update of tasks statuses in the scenario of mixed diagrams (structures as well as unstructured).
This event-handler will evaluate the value of task variables that begin with "$" after any task execution.
For the purpose of ACM, the variable is the status of each task, deciding for its availability for the user at any step of case execution.
This event-handler is included in the Studio and the Runtime bundle, but is disabled by default.
To use it, it needs to be enabled in the studio Preferences or in the bundle configuration.
Improvements
Performance
Engine work execution
A work execution audit mechanism has been introduced. It can be activated to detect when a work takes too much time to be executed or it was rescheduled too many times. See Work execution audit page.
Asynchronous connector execution
The Bonita Runtime is now up to 10x more performant in a context of slow connectors, allowing more tasks to be executed and avoiding and SPOC (single point of contention).
-
Connectors are executed in an asynchrous manner. In earlier versions each work was waiting for the connector to end before processing other workload. This resulted in degraded performance if few connectors had a long execution time.
-
Worker threads are now released as soon as the execution of the connector is triggered. see connector execution page for more details. As a consequence, in a context of connectors taking a lot of time (connecting to slow third party services, high computing, …) the usual job executions are not blocking and can continue.
Timer execution
Bugs were fixed to increase stability of the integration with Quartz:
-
BS-19239 Exception during Quartz Job execution leaves the associated flownode in WAITING state and the process execution is stopped
-
BR-56 Failure in a cron timer cancels future executions A new page was added to explain how Timers are executed and how to handle time execution failures. Also details were added on how to configure Quartz for timers execution: quartz performance tuning
Cluster locks
A new configuration capability was added:
bonita.platform.cluster.lock.leaseTimeSeconds :
Specify a maximum time a lock is kept cluster-wise. It avoids having an instance of process indefinitely locked when one node does not release a lock due to errors like network issues.
It is set by default to 600 seconds. It should be kept to a high value (more than transaction timeout) or else some concurrent modifications on processes can happen.
Packaging
Bundles
Tomcat and Wildfly bundles have been renamed. The Wildfly and Tomcat version are no longer specified in their name.
Technical updates
Java 11 Compliance
Bonita now runs on Java 8 and Java 11. It is still compiled with java 8, but can now run on Java 11.
According to that, some libraries and dependencies of the product have been updated: they either presented security issues, or they did not work at runtime. The list can be found [there](#java-11-lib-update).
The others have been left as they were.
Some of those can generate warnings with Java 11, such as "WARNING: Illegal reflective access by […/]", but this has no consequence on Bonita execution, and they will be updated in the future.
If you are migrating to Bonita 7.9 and plan to run it on Java 11, some of your connectors will have to be migrated. See [Connectors dependency updates](#connector-dependency-updates)
Generally speaking, custom code and connectors might require updated versions of libraries used in Bonita. In such cases, those updated versions should be added as scripts/connector dependencies.
REST API extension project update
In order to be compatible with Java 11, you must update the following plug-ins dependencies in your pom.xml:
-
groovy-all dependency must be updated to 2.4.16
-
groovy-eclipse-batch dependency must be updated to 2.4.16-02
-
maven-compiler-plugin dependency must be updated to 3.8.0
-
groovy-eclipse-compiler dependency must be updated to 3.3.0-01
-
You need to add the plugin repository below in your pom.xml
-
<pluginRepositories>
<pluginRepository>
<id>bintray</id>
<name>Groovy Bintray</name>
<url>https://dl.bintray.com/groovy/maven</url>
<releases>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
...
</pluginRepositories>Dependency updates
Migration
For Bonita 7.9.0, the migration step tries to migrate the CMIS, Email and Webservice connectors of the processes deployed on the platform, along with their dependencies, to allow the migrated platform to run on Java 11.
The step works at best effort:
-
It will try to upgrade all the connectors it can.
-
It will not upgrade connectors that have dependencies used by other connectors. Those connectors will still work on java 8, but not in java 11, and will require a manual update.
-
A detailed report of all the changes made is displayed at the end of the migration step.
-
Beware that if one of these connectors' removed dependencies was used in one your scripts, it will still be removed/updated, and therefore your scripts might not work anymore after migration. The full list of updated and deleted dependencies can be found below.
From Bonita 7.9+, the supported version of Oracle database is 12c (12.2.x.y) To migrate to Bonita 7.9+ from an earlier version than Oracle 12c (12.2.x.y), see Migrating to Bonita 7.9+ using Oracle.
WebService connector
The following dependencies have been added, to ensure Java 11 compliance:
-
javax.xml.stream:stax-api:1.0-2
-
org.codehaus.woodstox:woodstox-core-asl:4.1.2
-
org.codehaus.woodstox:stax2-api:3.1.1
-
com.sun.istack:istack-commons-runtime:2.4
-
javax.activation:activation:1.1
-
com.sun.xml.messaging.saaj:saaj-impl:1.3.28
-
javax.xml.ws:jaxws-api:2.2.7
-
com.sun.xml.ws:jaxws-rt:2.2.7
-
javax.jws:jsr181-api:1.0-MR1
-
javax.xml.bind:jaxb-api
-
com.sun.xml.bind:jaxb-impl
CMIS connector
The following dependencies were updated to ensure Java 11 compliance:
-
org.apache.chemistry.opencmis:chemistry-opencmis-client-impl dependency has been updated from 0.13.0 to 1.1.0
-
org.apache.chemistry.opencmis:chemistry-opencmis-client-api dependency has been updated from 0.13.0 to 1.1.0
-
org.apache.chemistry.opencmis:chemistry-opencmis-commons-api dependency has been updated from 0.11.0 to 1.1.0
-
org.apache.chemistry.opencmis:chemistry-opencmis-commons-impl dependency has been updated from 0.11.0 to 1.1.0
-
org.apache.chemistry.opencmis:chemistry-opencmis-client-bindings dependency has been updated from 0.11.0 to 1.1.0
-
org.apache.cxf:cxf-rt-bindings-xml dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.cxf:cxf-rt-frontend-simple dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.cxf:cxf-rt-core dependency dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.cxf:cxf-rt-transports-http dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.cxf:cxf-rt-ws-policy dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.cxf:cxf-rt-ws-addr dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.cxf:cxf-rt-bindings-soap dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.cxf:cxf-rt-databinding-jaxb dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.cxf:cxf-rt-frontend-jaxws dependency has been updated from 2.7.7 to 3.0.12
-
org.apache.neethi:neethi dependency has been updated from 3.0.2 to 3.0.3
-
org.apache.ws.xmlschema:xmlschema-core dependency has been updated from 2.0.3 to 2.2.1
The following dependencies have been added to ensure Java 11 compliance:
-
org.apache.cxf:cxf-rt-wsdl-3.0.12
The following dependencies have been removed:
-
org.jvnet.mimepull:mimepull-1.9.4.jar
-
org.codehaus.woodstox:stax2-api-3.1.1.jar
-
org.apache.geronimo.javamail:geronimo-javamail_1.4_spec-1.7.1.jar
-
org.codehaus.woodstox:woodstox-core-asl-4.2.0.jar
-
org.apache.cxf:cxf-api-2.7.7.jar
In addition bonita-connector-cmis-
JTA transaction manager replacement
In Bonita 7.9.0, we replaced the JTA transaction manager used to handle XA transactions in Bonita Engine from Bitronix to Narayana (also known as Arjuna).
This change should not impact the way to use Bonita.
However, tuning Bonita transaction configuration is now a little different. If you wish to change the default transaction timeout,
it is now done by changing the defaultTimeout property in file server/conf/jbossts-properties.xml instead of file server/conf/bitronix-config.properties
More configuration info can be found here.
Databases supported
Oracle
From Bonita 7.9, the supported version of Oracle database is 12c (12.2.x.y)
To migrate to Bonita 7.9+ from an earlier version, you need to run the Bonita Migration Tool once with the version 7.8.4 target, so that the database and configuration is updated. Then you must upgrade your Oracle database to version 12c (12.2.x.y). Then run the migration tool again to target version 7.9+. See Migrating to Bonita 7.9+ using Oracle for more details.
PostgreSQL
From Bonita 7.9, the supported version of PostgreSQL database is 11.2.
Some PostgreSQL-specific tuning recommendations are provided for
improved database performance.
Microsoft SQL Server
Microsoft SQL Server open-source drivers are now provided by Bonita. There is no need to download and install them manually anymore.
MySQL
From Bonita 7.9, the supported version of MySQL database is 8.0 (8.0.x)
To migrate to Bonita 7.9+ from an earlier version, you need to run the Bonita Migration Tool, so that the database and configuration is updated. Then you must upgrade MySQL to version 8.0. See Migrating to Bonita 7.9+ using MySQL for more details.
|
Up to 7.9 version Bonita requires MySQL to use UTF-8 encoding, which is an alias for 'utf8mb3', now deprecated by MySQL. The link:http ://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8.html[official MySQL recommendation is to use 'utf8mb4']. 'utf8mb4' is supported on Bonita starting from version 7.10. |
Componentization and tools for developers
Embed Bonita Engine in your application
You can now easily embed a Bonita Engine and easily interact with processes within your business application.
This can be done in two different ways:
-
using standard Spring Boot starter integration
-
programmatically, calling Bonita Engine code through Java, Kotlin, Groovy, or any other language running on JVM
For more information, see how to embed Bonita Engine.
| This is a Lab feature and is subject to change without warning in any version. It is not recommended for production. |
Feature deprecations and removals
Deprecations
EJB
EJB communication protocol with the engine is now deprecated. Removal is planned for 7.10 version.
Wildfly Bundle
The Wildfly bundle has been deprecated in Bonita 7.9. If you are using the Wildfly bundle, we advise you to switch to the Tomcat bundle when migrating to 7.9. The Wildfly bundle was mainly used with the SQL server database. The Tomcat bundle is now compatible with it, and is the recommended solution.
Removals
SAP JCO2 connector (Subscription only)
The SAP JCO2 connector is no longer available. SAP JCO3 connector is more recent and can still be used.
Deploy zip
The BonitaSubscription-x.y.z-deploy.zip is no longer provided starting from Bonita 7.9. Please use the Tomcat bundle instead, or see the Custom Deployment page for more specific needs.
Analytics and Reports - For Enterprise, Performance, Efficiency, and Teamwork editions only.
In keeping with Bonitasoft’s promise to continuously deliver valuable, high quality features, we had to relinquish the Analytics and Reports page from the Bonita v2021.2 release. The default reports were based on an old Jasper software version that didn’t allow dynamic reporting, required you to have a relatively deep technical knowledge of Jasper and SQL, and most importantly, didn’t meet Bonita’s expectations in terms of security requirements. The good news is that we are working on a special dedicated project for reporting. Here’s a heads-up of what’s coming: You’ll be able to view statistics and to extract process execution reports with meaningful data for performance analysis and pinpointing areas of improvement.
Stay tuned for more news.
Bug fixes
Fixes in Documentation
-
BS-19323 Bonita documentation is not clear enough about PostgreSQL versions supported
-
BST-151 Default outgoing transition not executed when there is more than one outgoing transition from inclusive gateway
-
BST-269 Document workaround for MacOS - ssh issue
-
BST-171 Can’t share a project on github using HTTPS and double authentication factor
-
BST-341 On MacOS, Studio installer might not detect the installed JRE
Fixes in Bonita 7.9.4 (2019-10-03)
Fixes in Engine component
-
BR-143 platform-setup-sp contains both Community and Subscription versions of files
-
BR-189 NullPointerException error is shown when the description of a page/form is empty
-
BS-18473 Unable to update connector implementation with the same java class name
-
BS-19340 SAP Connector throws JCoException: (101) RFC_ERROR_PROGRAM: 'mshost' missing — RFC_INVALID_PARAMETER(19)
-
BS-19377 When a failed Receive Task is replayed, no waiting_event is generated
-
BS-19387 ConcurrentModificationException is shown in the logs and in the portal when a connector fails
-
BS-19395 Java clients are limited to only 2 remote HTTP connections to Bonita server
Fixes in Bonita 7.9.3 (2019-09-05)
Fixes in Studio component
-
BST-396 Import validation message doesn’t show up
-
BST-398 Avoid errors when the expected active organization is not in the project anymore
-
BST-417 Impossible to launch several Bonita Studio on macos
-
BST-427 Theme version is not taken into account when creating a theme. Bonita version is used instead of user choice from wizard
-
BST-434 Studio does not inform when the deployment of a REST API Extension fails
-
BST-466 Autogenerated edit form with multiple documents can’t be submited
-
BST-469 Option "On exit clean database" doesn’t work anymore
Fixes in Web/Portal component
-
BPO-105 BS-19244 The License page is not able to list the subscription end date
-
BPO-184 Translation error in Process configuration after installation
-
BPO-185 Popup Error in the Portal / Admin / Case Details
-
BPO-190 In case overview page, the BIZ data table headers are not displayed.
-
BPO-198 Performance issue with resources downloaded from internet at page load
-
BPO-202 Empty list when filtering cases in the portal using process version All
-
BPO-202 BS-19309 - Portal User Processes page - Filters dropdown contains only All processes
-
BPO-202 Monitoring pagination does not display when lowering the number of cases per page
Fixes in Bonita 7.9.2 (2019-08-01)
Fixes in Engine component
-
BS-19299 GET REST API connector raised an exception if answer body is null
Fixes in Studio component
-
BST-345 Open an invalid access control file leads to an NPE instead of displaying the
error view -
BST-349 The option to initialize a business data using a Query is not always available
Fixes in Web/Portal component
-
BPO-24 BS-18487 and BS-18488 cannot download a document from the FilePreview widget link
-
BPO-101 Rename Application Descriptor XML file using "ApplicationDescriptorFile.xml" in Portal
-
BPO-157 Migration form and color in a form
-
BPO-170 Different caseIds are displayed for a same archived case in Bonita Portal
-
BPO-179 URL parameters are not displayed in a Custom Profile
-
BPO-189 Case overview page for an archived case is not working in IE 11 (id not found)
Fixes in Bonita 7.9.1 (2019-07-04)
Fixes in Studio component
-
BST-248 Name of sub-process is lost when importing an BPMN XML file
-
BST-282 When creating an application or editing the displayName of an application, there is no limit to the number of characters
-
BST-287 In UI Designer tomcat server, there is no extended parameters
-
BST-288 Click on Configuration icon has no effect
-
BST-290 Import multiple jars at once does not work: in the project lib, the files are empty
-
BST-294 Bonita LA Builder doesn’t have the provided groovy scripts
-
BST-299 BPMN export fails if Data to send in Call Activity contains empty association
Fixes in UI Designer component
-
UID-82 When a new Fragment is created, the Palette is not updated
-
UID-83 Message toast in UI Designer is not clear when license is expired
-
UID-104 Fragment variable value isn’t clean when variable scope change
-
UID-105 When name of artifact is too long, left panel is broken
Fixes in Web/Portal component
-
BPO-72 BS-19311 Administration profile: Monitoring page generates a 26 seconds request (search process definition)
-
BPO-106 BS-19310 Administration profile: Open cases page generates twice the same requests (search)
-
BPO-146 No tooltips on the top right icons and name of the user
-
BPO-154 Clean and Improve Layout css file
-
BPO-159 "All profiles" should be the default option in the application list filter of Bonita layout
-
BPO-163 "…" of ellipsis should not be displayed on a white background
-
BPO-167 Avoid user details modal overflow
-
BPO-171 Bonita Layout mobile app title error on click
-
BPO-178 Improve the default user icon in the bonita layout
Fixes in Bonita 7.9.0 (2019-06-13)
Fixes in Engine component
-
BR-69 SQLServerException error when deleting cases with more then 2100 subprocesses
-
BS-15896 Unable to configure EntityManagerFactory
-
BS-18364 Connector Replay stays in state TO_RE_EXECUTE when executeFlowNode arrives at the same time the task is transitioning from 'initializing' to 'ready'
-
BS-18734 Deploying a BAR with two forms with the same name but a different case leads to Unique index or primary key violation CONSTRAINT_INDEX_29 BAR_RESOURCE(TENANTID, PROCESS_ID, NAME, TYPE)
-
BS-18748 Portal Organization IMPORT button has no feedback
-
BS-18874 work execution: 5 seconds SELECT * FROM flownode_instance WHERE kind = 'boundaryEvent' …
-
BS-18880 work execution: 84 seconds SELECT * FROM from flownode_instance where logicalGroup3=nn and terminal=0 order by id ASC limit 1;
-
BS-18910 message_instance x waiting_event couples: 72 seconds request duration
-
BS-19082 Long execution duration for this processAPI.searchAssignedAndPendingHumanTasks API call
-
BS-19239 Exception during Quartz Job execution leaves the associated flownode in WAITING state and the process execution is stopped
-
BS-19293 REST API extension: ClassCastException
-
BS-19295 SELECT widget sets the field of the variable holding the initial value to null when the page/form loads if it is shared by another SELECT widget
-
BS-19298 Process may end up locked forever
-
BS-19319 [BDM] Business Object Java Setter does not create aggregated instances
-
BS-19322 Contract validation fail if a complex contract input is null and has a multiple complex child contract input
-
BS-19335 Timers triggers keep being rescheduled and are not fired on time or fired randomly
-
BS-19345 Script Connector does not return stderr in connector result
Fixes in Studio component
-
BST-126 Studio must be restarted to use User-defined functions
-
BST-132 Wrong script generated in some specific cases with multiple data
-
BST-162 Generate process documentation does not work post 7.7
-
BST-201 Contract input name should never be equal to the associated business data name
-
BST-202 Application descriptor Deploy button does not trigger the saved changes and does not raise errors
-
BST-204 Default Application created in the Portal raises an error about custompage_home when imported and Deployed from Studio
-
BST-221 UI Designer allows to have 2 forms with same name when created from the Studio: this breaks LA Builder
-
BST-251 On MacOS, manage organizations wizard needs scrolling to add a membership
-
BST-271 Import .bpmn diagram fails
Fixes in UI Designer component
-
UID-29 RichTextArea readOnly property should be dynamic
-
UID-30 When a form or a page is renamed in the UID, the field 'displayName' is not updated in the json
-
UID-34 ui-bootstrap-tpls.js asset should be displayed in the Assets panel for the modal container (as for tabs container)
-
UID-38 Select widget set bound value to null
-
UID-39 when importing a javascript local asset, content is not editable
-
UID-69 Localization help section is empty in custom widget editor
-
UID-73 Widget editor: title underline not aligned
-
UID-86 Modal container: the focus should be located on the input element
-
UID-90 Deleting one asset from a custom Widget based on the default one remove all the assets
-
UID-101 INTEGER contract type is not set as mandatory in widget when creating the form