Changes in Functionality
The following functionality and features have been changed in this release of TIBCO BusinessWorks Container Edition.
Release 2.10.0
Binding | |
---|---|
Support for displaying "faultcode", "faultstring" and details in the default Fault Schema | Now you can choose between the schema options "message" or "faultfactor, faultstring, and faultcode" for the input when using Reply with Undeclared fault. |
Support for customizing the error message for uncontrolled errors | Now, an error occurs without a stack trace in the browser window when ?wsdl is eliminated from the end of the endpoint URL. |
General | |
---|---|
Support added for Tibco Developer Hub icon on the welcome screen. |
A new TIbco Developer Hub icon is added on the TIBCO Business Studio for BusinessWorks welcome screen. |
Support for enhancing error logs | You can now use the property -Dbw.pvm.dataexch.omitXSLT=true to eliminate the XSLT stylesheet from the error logs. |
Support added for a detailed view of data validation errors in XML |
Now you can view detailed validation error outputs, including a detailed hierarchy of schema elements. |
Maven Plug-in | |
---|---|
Enhancements in the Shared Module Unit Testcases sample | In the "SharedModuleUnitTestcases" sample, the following parameters are implemented now:
|
Support for execution of test cases | This release adds support for execution of test cases, when one of the test cases errors out in the same process. |
Palettes | |
---|---|
Support added for module property for JDBC Call procedure/Function name. |
This release adds support for module property for JDBC Call procedure/Function name. For more information, see "Enabling the module property in JDBC Call Procedure/Function for JDBC Call Procedure Activity" in the TIBCO BusinessWorks™ Container Edition Bindings and Palette Reference. |
Upgraded the MSSQL jar to 12.x. |
The MSSQL database jar is upgraded to version 12.x. |
Support for Content Type validation in HTTP Receivers | Content Type validation is now provided for HTTP Receivers with the help of a system-based property.
Support is added to Content Type validation in HTTP for the following flags:
|
Support for Microsoft Graph API in the Receive Mail activity | Support has been added for the Microsoft Graph API in the Receive Mail activity using IMAP OAuth protocol. |
Support for Microsoft Graph API in the Send Mail activity | Support has been added for the Microsoft Graph API in the Send Mail activity using IMAP OAuth protocol. |
Support for chunked streaming in HTTP Palette | Support has been added for chunked streaming to send large files using the Jetty client in the HTTP Palette. |
Runtime | |
---|---|
Support added for Activator process for shared modules. |
Earlier, the activator process was supported only for application module. Now, the activator process is supported for shared modules. For more information, see "Creating an Activator Process" in the TIBCO BusinessWorks™ Container Edition Application Development. |
Unit Testing | |
---|---|
Support for execution of test cases. |
This release adds support for execution of test cases, when one of the test cases errors out in the same process. |
Release 2.9.2
Design Time | |
---|---|
Support for "/"character in the |
Earlier, the Now, the |
Release 2.9.1
General | |
---|---|
Support for micro and nano seconds in the parsedate function. |
This release adds support for micro and nano seconds in parsedate function. Set property |
Support for scope variable option. |
Earlier, the scope level variable is not shown in the reset variable option. Scope variable is now present in reset variable list for while loop. |
Release 2.9.0
General | |
---|---|
Base docker image is updated to debian:bookworm-slim |
Earlier, the Now, the base docker image is updated to |
Support for default enabling of Smart Mapper | The Smart Mapper and recording the user mapping selections are now enabled by default. |
Design Time | |
---|---|
Provision to generate an EAR using the BWDesign utility command |
Earlier, the Now, the For more information, see "Using BWDesign Utility " in the TIBCO BusinessWorks™ Container Edition Application Development. |
The |
The manifest-bwce.json file is generated for Container applications on creating an EAR. |
The Clear all blank lines checkbox in the Preferences -> XML -> XML Files -> Editor -> is by default enabled. |
Earlier, the Clear all blank lines checkbox in the Preferences -> XML -> XML Files -> Editor -> is not enabled. Now, the Clear all blank lines checkbox in the Preferences -> XML -> XML Files -> Editor -> is by default enabled when the workspace is closed. |
The Java compiler version is set to Java 11 for a BusinessWorks project. |
Earlier, the Java Compiler version for a BusinessWorks Project created with Java configuration was set to 1.4. Now, the Java Compiler version for a BusinessWorks Project created with Java configuration is set to Java 11. |
Provision to export profiles with EAR using BWDesign utility | Support is added to export profiles with EAR using the BWDesign utility via a -pf option. |
Maven Plug-in | |
---|---|
Support for validation checks of Gold input files | Validation checks are now implemented when you rename or move the Gold input file within a workspace. |
Support for OpenJDK is added. |
You can now configure OpenJDK instead of tibcojre for deploying applications using Maven in Docker. |
Support for deploying an application with different versions | You can now deploy the same application with different versions in TIBCO Enterprise Administrator using the Maven plug-in. |
Support for validation checks of Input XML files | Validation errors are now thrown when you rename or move the Input XML file on Process starter activities within a workspace. |
Support for Dependency Exclusions is added |
This release adds support for Dependency Exclusions on top level POM. For more information, see Dependency Exclusions in the TIBCO BusinessWorks™ Container Edition Maven Plug-in. |
Monitoring | |
---|---|
Support for TIBCO BusinessWorks Container Edition Monitoring to make connections with non default port of Oracle database. |
This release adds support for TIBCO BusinessWorks Container Edition Monitoring to make connections with non default port of the Oracle database. |
Palette | |
---|---|
Support for Basic Authentication in the HTTP responses | A new tag HttpOnly has been added when using Basic Authentication for the Set-Cookie attribute in HTTP responses. Also, a secure tag is added when using SSL. |
Runtime | |
---|---|
Support for disabling or enabling the input and output data storage using REST APIs |
When using Stats collection, the input and output data storage can now be disabled or enabled for audit events using REST APIs. |
Release 2.8.3
General | |
---|---|
Support for Oracle JRE 11.0.19 |
Earlier, Oracle JRE 11.0.18 was supported. Now, Oracle JRE 11.0.19 is shipped with this release. |
Enhanced error description for OAuth Shared Resource Test Connection. |
The error description is enhanced now for OAuth Shared Resource Test Connection faults. |
Release 2.8.2
General | |
---|---|
The "Transformation failed for element" type error shows a complete XPath to the element. |
Earlier, the simplified stack trace variable showed only the Now, if an exception occurs while processing an element's content, the |
Ability to process XML elements of complex type with simple content for Render JSON activity: |
Earlier, the Render JSON activity used to fail with the error Now, support is added for processing XML elements of complex type with simple content in Render JSON activity. |
Support for Oracle JRE 11.0.18 |
Earlier, Oracle JRE 11.0.16.0.1 was supported. Now, Oracle JRE 11.0.18 is shipped with this release. |
Auto-complete fixable after selecting recommended elements via existing internal QF for Smart Mapper. | For Smart Mapper, after selecting a recommended element which is a convertible type of the current target element, you can use the existing internal QF that automatically casts it. This can help you to avoid an extra click. |
Design Time | |
---|---|
Provision of creating test suite/test files for newly created folders. |
Users can now create test suite/test files for newly created folders under the 'Tests' folder. |
Provision of module property picker for input XML files. |
Users are now provided with a module property picker to provide test input XML files on process starter activities. |
Palette | |
---|---|
Enabling basic authentication for HTTP Receiver activity sub-paths. | The basic authentication for the HTTP Receiver activity having sub-paths can be enabled by selecting the Apply Policy to Subpaths checkbox in the Advance tab. |
Change in the cardinality of Allow header in Send HTTP Request activity. | The Send HTTP Request activity fails with an "Activity output data validation" error when invoking a service responding with a repeated Allow header element.
The cardinality for Allow header field is now set to Repeating (*) in the Output Editor of Send HTTP Request activity. |
Support for OAuth 2.0 with HTTP Client shared resources. |
OAuth 2.0 is now supported with HTTP Client shared resources for REST reference binding, Invoke REST API, and Send HTTP Request. |
Runtime | |
---|---|
Support for DSR command via Admin CLI. | In TIBCO Business Studio for BusinessWorks, input options are present within the same DSR command scope. Whereas in Command Line, each input option of the DSR command now works as an individual command. |
Release 2.8.1
General | |
---|---|
Support is added for auto tokenize property value on export profile. |
Earlier, on the application property editor in TIBCO Business Studio for BusinessWorks, for applications with deployment target as Container the Tokenize option is checked and non editable. So on exporting the profile as property file the property values are auto-tokenized. Now, the Tokenize option is editable and not selected by default. Hence the property value do not get auto-tokenized on profile export. You can manually check the Tokenize option to auto-tokenize property value on profile export. |
Default heap size for TIBCO Business Studio for BusinessWorks is increased to 4 GB. |
Earlier, the default heap size of TIBCO Business Studio for BusinessWorks was 2 GB. Now, the heap size is increased to 4 GB for TIBCO Business Studio for BusinessWorks. |
Runtime | |
---|---|
Upgrade OpenTelemetry jars with the latest compatible jars. |
For a better user experience, the OpenTelemetry jars are upgraded with the latest compatible released jars. |
Release 2.8.0
General | |
---|---|
Disabling the Persistent option in TIBCO BusinessWorks Container Edition |
Earlier, the Persistent option for a Module Shared Variable was enabled when the deployment target option was set to Container and the TIBCO Business Studio for BusinessWorks threw an error message. Now, the Persistent option for a Module Shared Variable is disabled when the deployment target option is set to Container. |
New default value for the Activation option in TIBCO BusinessWorks Container Edition is set to Single AppNode. |
Earlier, for all the Deployment Targets (BW6 AppSpace, Container, Cloud) the Activation option was set to Multiple Appnode. Now, the Activation option is now visible for TIBCO BusinessWorks Container Edition and the default value is set to Single AppNode. |
Support is added for the Use Process Data check box for the FTP Put and FTP Get activity in TIBCO BusinessWorks Container Edition |
Earlier, the visibility of the Use Process Data check box was not enabled for the FTP Put and FTP Get activity in TIBCO BusinessWorks Container Edition. Now, the visibility of the Use Process Data check box is enabled for the FTP Put and FTP Get activity when the deployment target is set to Container and Tibco Cloud. |
Support is added for multiple XSD schemas with duplicate target namespaces.
|
When the user has multiple XSD schemas with duplicate target namespaces, TIBCO Business Studio™ for BusinessWorks™ application fails to validate them; whereas, when an application EAR is deployed, it throws an error. Now, a Preference is added in TIBCO Business Studio for BusinessWorks application wherein either an Error, a Warning, or an Ignore option is provided in this scenario. |
Enabling Memory Saving Mode by default |
The Memory Saving Mode is enabled now by default in Design time and Runtime. |
Palette | |
---|---|
Upgrade to PostgreSQL 6.0 driver. |
With this release, PostgreSQL has been upgraded to the latest 6.0 version driver. |
Release 2.7.3
Palette | |
---|---|
Support is added for custom line separator. |
Earlier, a dropdown was added to select a line separator with predefined options in Data Format shared resource. Now, a new option for custom line separator in Data Format shared resource is added. |
Runtime | |
---|---|
New Data type added for Client Secret field. |
Earlier, the data type for the Client Secret field in the OAuth Shared Resource was String. Now, the data type is updated to Password. |
Release 2.7.2
Bindings | |
---|---|
Support is added for Authorize button on Swagger UI |
Earlier, for invoking REST services configured with Basic Authentication Policy from Swagger UI, you had to provide the Username and Password in the provided input fields and click the Explore button. Now, you can use the Authorize button and provide the log-in details. |
General | |
---|---|
Updated spring framework libraries for Eclipse. |
The spring framework libraries for Eclipse are updated to address the vulnerability issues. |
Upgrade the JDK compiler compliance version to the one greater than 1.5. |
The minimum JDK compiler compliance required is 1.5. If the project that you are importing with Java nature has JDK compiler compliance less than 1.5, you can choose to upgrade the JDK compiler compliance version to the one greater than 1.5. |
Monitoring | |
---|---|
Support is added for two separate Docker files to start TIBCO BusinessWorks Container Edition Monitoring. |
Earlier, to use Oracle for TIBCO BusinessWorks Container Edition Monitoring, only one single monitoring Dockerfile was present. Now, two Dockerfiles are used to start TIBCO BusinessWorks Container Edition Monitoring. To use MSSQL Server, Postgresql or Mysql DBs, use the Dockerfile To use Oracle DB: Dockerfile_Oracle. Before using, rename this file as 'Dockerfile'. |
Palette | |
---|---|
Improved error message for SOAP Client using HTTP and HTTPS |
Earlier, while invoking a service using HTTPS, the error message returned by invoke was not very useful to identify the problem. Now, an improved error message occurs for SOAP Client using HTTP and HTTPS. |
Runtime | |
---|---|
Password Digest option is provided in SOAP Reference. | The users have the option to choose the password type as Password Digest when using the UserNameToken for security in SOAP Reference. |
Release 2.7.1
Palette | |
---|---|
Support is added for discontinuing the extra mime part in the Send HTTP Request activity. |
When sending a multipart/mixed request with Send HTTP Request activity, TIBCO BusinessWorks Container Edition is adding an extra mime part with an unspecified boundary at runtime. Now TIBCO BusinessWorks Container Edition supports the behavior to avoid adding any extra headers by setting the com.tibco.net.mime.mpwob=true in VM arguments. As a workaround, if whitespace is prepended to the main Content-Type, then the extra headers are removed. |
Release 2.7.0
General | |
---|---|
Resilience4j for Circuit Breaker |
Earlier, Hystrix Libraries were supported for Circuit Breaker. Now, Resilience4j is supported for Circuit Breaker. |
Change in the default setting of the Always run in background check box. |
Earlier, the Always run in background check box located at Window > Preferences > General was clear by default. Now, the Always run in background check box is by default selected. Clear the check box to view progress bars for some events. |
Palette | |
---|---|
A new JMS Fetch Timeout field is added. |
A new JMS Fetch Timeout field is added on the Advanced tab of the Get JMS Queue Message activity. Additionally, the behavior of the timeout field on the Input tab is changed. For more information, see "Get JMS Queue Message" in TIBCO BusinessWorks™ Container Edition Binding and Palette Reference. |
Support is added for OpenTelemetry to collect traces. |
Earlier, you could collect traces by using OpenTracing. Now, you can collect traces by using OpenTelemetry. For more information, see "OpenTelemetry" in TIBCO BusinessWorks™ Container Edition Administration. |
For more information about Changes in Functionality before TIBCO BusinessWorks Container Edition 2.7.0 release, see Changes in Functionality