Known Issues

The following known issues have been identified in this release of TIBCO ActiveMatrix BusinessWorks™.

The known issues are grouped by components:

Administration

Key Description
AMBW-41955 Summary: If an AppNode log is not present and you click the Download Log button from Admin UI, an exception is thrown.

Workaround: Start appnode and try again

AMBW-41795 Summary: When agent is started with MySQL 8.x jar, a harmless message about the driver being deprecated is displayed on bwagent and the bwadmin console.

Workaround: None

AMBW-41794 Summary: A harmless warning is shown when starting a BWAgent.

Workaround: None

AMBW-41555 Summary: The Appnodeconfig button is not available under the Appnode Data view.

Workaround: Navigate to any other page within an AppNode and then navigate to appnode config.

AMBW-37468 Summary: Harmless logs are shown at Admin Console on SUSE 12 Linux.

Workaround: None

AMBW-32929 Summary: Process monitoring statistics are not populated if checkpoint has been used in the process.

Workaround: None

AMBW-32922 Summary: On Process Monitoring page, Job filter displays results for records on the current page only.

Workaround: None

AMBW-32904 Summary: Sometimes all the transitions are not highlighted and input/output data is not seen for activities when process monitoring is enabled using UDP transport.

Workaround: Use FTL transport for process monitoring.

AMBW-32594 Summary: On the Process Monitoring page, the Datetime value in the MM/DD/YYYY format for filtering jobs does not work.

Workaround: Use the datetime value as displayed in the database

AMBW-32071 Summary: Failed to Upload Large EAR file larger than 10MB with MariaDB.

Workaround: Use any other database.

AMBW-32057 Summary: Agent Count is getting increased for AppSpace after restoring Domain.

Workaround: None

AMBW-31832 Summary: In the process diagram view of Process Monitoring, if a constructor block includes a catch block, then it is not highlighted after its execution.

Workaround: None

AMBW-31831 Summary: In Process Monitoring, sometimes, because of uid issue references are not highlighted and input or output data might not displayed.

Workaround: Remove all uid related warnings from TIBCO Business Studio™ for BusinessWorks™. Create an EAR file. Deploy the EAR file, and then enable process monitoring.

AMBW-31600 Summary: When an application is running and AppNode is restarted, the job id is duplicated and two jobs with same id is present under process monitoring.

Workaround: None

AMBW-31493 Summary: User is getting considered as Role in file based authorization.

Workaround: None

AMBW-31447 Summary: The Same .EAR file is uploaded in different folders without using the replace option in AS Enterprise Mode.

Workaround: None

AMBW-30759 Summary: Failed to get AppNode Config.ini file's property details by REST API.

Workaround: None

AMBW-30398

Summary: Unable to register BWAgent from the command line on some machines.

Workaround: None

AMBW-29846

Summary: Process diagrams are not visible on the Admin UI when the project name has a period (.) between the numbers.

Workaround: Remove the number from the process package name, regenerate the EAR file, and re-deploy it.

AMBW-29725 Summary: The Internal Server Error is displayed intermittently in logs when there is a change in the network.

Workaround: None

AMBW-29632 Summary: Process diagram is not shown in TIBCO® Enterprise Administrator when the TIBCO ActiveMatrix BusinessWorks™ process package name contains number.

For example com.tibco.bw.service.SIXXXZZZ.1.0

Workaround: None

AMBW-29235

Summary: When application components are started or stopped multiple times from the Admin UI, the TIBCO-BW-TEAAGENT-500506: Failed to get components for Application error is sometimes displayed.

Workaround: Refresh the entire page or navigate to different tab, for example, the AppNodes or AppSpaces page and then go back to the Components tab.

AMBW-28244 Summary: Admin UI shows wrong information under Installation tab after upgrade.

Workaround: None.

AMBW-27654

Summary: Identity-Truststore is not created for the SSL Client post migration.

Workaround: After migrating the SSL enabled service , it will create the SSL client resource. In SSL client resource, provide the keystore provider resource in Keystore Provider as Trust Store. Provide the Keystore only. This will import all the certificates required for SSL enabled services in ActiveMatrix BusinessWorks™ 6x.

AMBW-27440 Summary: In the DBEMS mode when you upgrade from ActiveMatrix BusinessWorks 6.3.1 to ActiveMatrix BusinessWorks 6.4.0 and restore Domain, the error, ERROR: null value in column "commandid" violates not-null constraint, is thrown.

Workaround: After upgrade, drop the old commandhistory table and run the new ActiveMatrix BusinessWorks 6.4.0 bundled script to create the commandhistory table and then restore the domain.

AMBW-26286 Summary: Unable to upload large sized EAR files (~10 MB) when the DB2 database is used for the DBEMS or DBFTL mode.

Workaround: None

AMBW-25889 Summary: From the command line, users can enable the OSGi and create a new AppNode on the same OSGi port.

Workaround: Use the Admin UI to enable the OSGi port.

Bindings

Key Description
AMBW-41957 Summary: On creating a REST Reference Binding from an external Swagger 3.0 JSON file with "https" URL in "servers" tag, the Default Confidentiality was not selected on the HTTP Client shared resource. This caused the application to fail at run time.

Workaround: Select the Default Confidentiality check box in the HTTP Client shared resource of the application.

AMBW-41082 Summary: Form Parameters are not supported in TIBCO ActiveMatrix BusinessWorks™ 6.7.0 release for OpenAPI 3.0 REST services.

Workaround: None.

AMBW-36113 Summary: A multipart message where one part points to type and the other part points to element and a message using mixed security mode is not supported.

Workaround: Change mixed security mode in a given WSDL.

AMBW-32951 Summary: A SOAP service responding with mustUnderstand attribute as true is ignored irrespective of selecting or deselecting the Ignore mustUnderstand check box on the SOAP Reference binding. This behavior does not affect the client and server communication.

Workaround: None

AMBW-32760 Summary: On creating SOAP Reference Binding with the concrete WSDL generated at run time with multilevel schema imports, the java.lang.NullPointerException is displayed when clicking the reference binding.

Workaround: None

AMBW-29098 Summary: When creating a concrete WSDL by right-clicking on the Service Descriptor folder, the following error is generated at design time: WSDL import error.

Workaround: None

AMBW-27870 Summary: On importing WSDL with RPC Encoded style, a validation error is generated at design time since the underlying schema with namespace http://schemas.xmlsoap.org/soap/encoding/ is not generated.

Workaround: To remove the validation error and create the SOAP Reference Binding, download the encoding schema with the said namespace and ensure that schema is a part of the application module or the shared module.

AMBW-27435 Summary: When module properties used from a shared module project were renamed, the changes made were not reflected at the SOAP binding level.

Workaround: Select the updated module property from the drop down in the SOAP binding.

AMBW-26806

Summary: When a REST service with a schema that uses a type which was imported from another XSD is invoked in a REST Reference Binding, it fails with the ServiceRuntimeException.

Workaround: None

AMBW-23104 Summary: When the WSDL uses multiple parts in the Request body of an operation, a design time validation error occurs on the generated SOAP reference binding. The application works fine at run time.

Workaround: None

AMBW-22981 Summary: When the REST Service which is implemented with GET Operation with Response as String, then the content-type of the response is changed from application/json to text/plain.

Workaround: Use XSD Element in Response instead of String.

AMBW-21363

Summary: REST Call failed on run-time under non-UTF8 locale environment.

Workaround: Set the default encoding of the AppNode to UTF-8 by adding "-Dfile.encoding=UTF-8" to java.extended.properties of "bw/6.3/config/bwappnode-an. tra_template".

AMBW-13607

Summary: REST Doc UI is not supported on Firefox browser.

Workaround: Use other browsers for the Doc UI.

AMBW-13572 Summary: For some use cases, REST Doc UI does not show the correct error code in case of Internal Server errors on the Server side.

Workaround: Check the raw message that contains the correct error code.

AMBW-13485 Summary: REST Doc UI does not support browsers like Internet Explorer.

Workaround: Use Chrome browsers for the Doc UI.

AMBW-8982 Summary: Changing the Resource name in the REST service Bindings tab, does not update the Resource Service Path.

Workaround: None

General

Key Description
AMBW-42131 Summary: Customization of the template for an unencrypted project template fails.

Workaround: Import the template in a workspace without customization, and then rename the project.

AMBW-42046 Summary: Encryption Setting Window shows no editable fields when opened by clicking on the Lock Icon if TIBCO Business Studio™ for BusinessWorks™ is not in full-screen mode.

Workaround: Open Encryption Settings when TIBCO Business Studio for BusinessWorks is in full-screen mode or enter into full-screen mode for Encryption setting if it is opened in a minimized view.

AMBW-41991 Summary: Eclipse command line options such as -clean does not work with TIBCO_HOME/studio/4.0/eclipse/TIBCOBusinessStudio.app/Contents/MacOS/TIBCOBusinessStudio executable on macOS platform.

Workaround: Use the following command:

TIBCO_HOME/studio/4.0/eclipse/Eclipse.app/Contents/MacOS/TIBCOBusinessStudio --launcher.ini TIBCO_HOME/studio/4.0/eclipse/TIBCOBusinessStudio.ini -clean or any other eclipse command line option

AMBW-41960 Summary: Input and Output schema not formed correctly when creating a Mesh client for a BW/Flogo OAS3 Mesh Service

Workaround: None.

AMBW-41950 Summary: In bwdesign, if we export substvar files with the same name twice in the same location, it does not overwrite the substvar file.

Workaround: Delete the previous substvar file and export substvar again.

AMBW-41948 Summary: Many to one mapping is not supported for Smart Mapper.

Workaround: None

AMBW-41846 Summary: Any operation on the module or application properties that leads to a change in their order results in a faulty difference generation. So, such operations are not supported in TIBCO ActiveMatrix BusinessWorks™ 6.7.0.

Workaround: None.

AMBW-41832 Summary: The lock icon on the encrypted profile in the difference viewer perspective is shown based on whether the workspace copy of the profile is encrypted or not. Currently, if the workspace copy of the profile is encrypted, then in the difference viewer perspective, the lock icon is shown even on the un-encrypted revisions of that profile.

Workaround: None.

AMBW-41827 Summary: The properties and profile are not showing in the application property editor on opening the editor for the first time in a new workspace.

Workaround: Close and reopen the editor, it shows all the details.

AMBW-41779 Summary: If a keystore file location or name is changed then on refresh blank property value is shown and on running the application, the File Not Found Exception is thrown.

Workaround: Restore file with a valid name at a specified location on disk and do project clean.

AMBW-41716 Summary: Any changes in the module or application properties inside groups are not supported in ActiveMatrix BusinessWorks 6.7.0 and the corresponding difference generation is faulty in such cases.

Workaround: None.

AMBW-41715 Summary: The difference viewer calculates the difference and highlights the properties, but does not highlight any corresponding fields of the properties.

Workaround: Switch to the text difference mode and see the difference in the non-UI fields.

AMBW-41499 Summary: In the substitution variables file, only five types of module properties are saved: String, Integer, Long, Boolean, and Password.

When a module property is assigned a type other than the above-mentioned types then that type is saved as a String in the substvar file in the Diff Viewer window.

Workaround: None.

AMBW-41474 Summary: If there are any changes in the Description field of a module or application property, it is not highlighted in the difference viewer.

Workaround: None.

AMBW-41307 Summary: Application property editor does not display value in case of removing encryption setting using the Clear All button and exporting profile.

Workaround: Close the application properties editor and open it again.

AMBW-41277 Summary: When you try to install a missing plugin using the Quick Fix option and you select or unselect a plugin version from the list of provided versions; the following message is displayed: Cannot complete the install because of a conflicting dependency.

However, you can still install the plugin successfully.

Workaround: None.

AMBW-41271 Summary: The application property editor doesn't get refreshed intermediately on encrypting profiles.

Workaround: None.

AMBW-41252 Summary: The New Name field in the Rename Projects section on the Create Project From Template window is not enabled on a single click.

Workaround: First click on the old name of the module or the application after which the field is enabled. .

AMBW-41155 Summary: The Password field is shown as changed while doing a Shared Resource diff, even if the password are the same.

Workaround: None.

AMBW-41238 Summary: Confirmation message is displayed with any operation on encrypted profiles.

Workaround: Click Yes.

AMBW-41035 Summary: The Authentication field is shown while doing a diff when the Confidentiality field is set for Http Connector shared resource.

Workaround: None.

AMBW-40811 Summary: Default icon shown instead of Custom icon for the Call Process and Java Invoke activities within external shared module.

Workaround: Manually browse the Custom icon field value and add respective icon to activity on importing external shared module.

AMBW-40464 Summary: ActiveMatrix BusinessWorks applications fail at run time in TIBCO Cloud Integration if they consume a Flogo endpoint that has Post/Put Operations.

Workaround: None.

AMBW-40010 Summary: null pointer exception is thrown at run time on ActiveMatrix BusinessWorks Mesh client when the organization name contains a space character.

Workaround: When importing the ASR descriptor json file to create a Mesh client, there is a second wizard page for customizing json file location (Change swagger name). In that wizard page, remove the space from the folder name.

AMBW-39899 Summary: The null pointer exception reported on clicking Binding Section in Components after the Refactoring operation.

Workaround: Post refactoring, close the Module Descriptor section and reopen it. No popup is displayed.

AMBW-39887 Summary: ActiveMatrix BusinessWorks Mesh Client applications fail at runtime in TIBCO Cloud Integration if they consume a Flogo Mesh Service that has Post or Put Operations.

Workaround: None.

AMBW-39837 Summary: The collectappnodedata command is not working on the AIX platform.

Workaround: None.

AMBW-39804 Summary: SVN compare with revision option doesn't work for any revision other than the base revision.

Workaround: None.

AMBW-38593 Summary: Condition fails to evaluate completely when you try to equate a boolean value to a string.

For example:-If an expression is $DataGen/group/bool2 != "false"', where the bool2 is true()

Workaround: Simply update "false" to false() or 0 and run the project. It runs as expected (or vice-versa if its equated to "true" value)

AMBW-38580 Summary: Transition configuration error for specific customer projects.

Workaround: When a project has the Invalid expression value: [: not a Boolean] error, complete the transition by equating it to either "true" ("1") or "false" ("0") and run the project.

AMBW-37714 Summary: Local Transaction group option is not present in the drop-down list present for the Group Type field for a group.

Workaround: User should ungroup the existing group and create a new group.

AMBW-37594 Summary: Breakpoints are not working when execution flow goes from one process to another.

Workaround: Select an activity where debugging with the breakpoint is halted. It enables the Resume button. Click the button to resume debugging.

AMBW-36990 Summary: When you delete a module shared variables or job shared variables from the Unused Resources view, then the editor for module shared variables or job shared variables does not get refreshed automatically.

Workaround: Close the module shared variables or job shared variables editor and open it again.

AMBW-35659 Summary: If you uninstall custom XPath function, then there are chances that custom XPath plugin is not deleted from the {tibco_home}\studio\4.0\eclipse\plugins folder.

Workaround: Delete all existing jar files from the {tibco_home}\studio\4.0\eclipse\plugins folder.

AMBW-35024 Template has been updated for the matches Xpath function in TIBCO Business Studio for BusinessWorks.
AMBW-34416 Summary: Failed to connect to AppNode using SSH client

Workaround: Use HTTP client. Preferred way is using curl.

AMBW-34404 Summary: Incorrect trace is generated for the invoke process with default jaeger properties.

Workaround: Set JAEGER_SAMPLER_TYPE=const, and JAEGER_SAMPLER_PARAM=1 properties in the AppNode or AppSpace config.ini file.

AMBW-34396 Summary: Clicking Help Contents shows HTTP ERROR: 500 error.

Workaround: None

AMBW-34343 Summary: An application fails to start in TIBCO Business Studio™ for BusinessWorks™ when you install the latest EMS driver.

Workaround: Restart TIBCO Business Studio for BusinessWorks.

AMBW-32761 Summary: The user will not be able to create the references for the custom operations such as Merge, Update, Trace using the drag and drop swagger file approach.

Workaround: Users can create the references for the custom operations using the REST Reference wizard.

AMBW-28941 Summary: Ungrouping nested groups created inside a Catch block of a group may not ungroup as expected.

Workaround: None

AMBW-28663 Summary: The tibco.bw.sample.policy.samlcredentialmapping.SoapHttpBinding sample fails intermittently with the error: com.tibco.governance.agent.action.ActionException.

Workaround: None

AMBW-28378 Summary: When a process property is renamed , the change is not reflected in the activity and an error is displayed.

Workaround: None

AMBW-28319 Summary: WSDL interface fails to resolve correctly if multiple WSDLs share the same target namespace and the SOAP invoke is created with an external binding reference.

Workaround: Instead of an external reference binding, use binding reference.

AMBW-28264 Summary: When groups with the On Catch, Catch All and the OnEvent faults are created inside a constructor or a proxy operation, the activities inside them are lost after ungrouping.

Workaround: None

AMBW-27253 Summary: The Identity Provider field in the WSS Consumer policy resource does not support module properties.

Workaround: None

AMBW-25219 Summary: Multiple End activities use the same variable in TIBCO ActiveMatrix BusinessWorks™.

Workaround: None

AMBW-25073 Summary: The option to test connections, for example JMS or sFTP, in a shared resource that has a profile is not supported in TIBCO Business Studio for BusinessWorks.

Workaround: Specify the server configuration details as literal value or module properties.

AMBW-24508 Summary: TIBCO-THOR-FRWK-CMN-500001:Error while renaming bundle file to final location: - error could be displayed due to low disk space.

Workaround: None

AMBW-19746 Summary: When you initialize the module shared variable of XSD type with the select value option to point the XML instance, application fails to start at run time.

Workaround: Enforce the default encoding of AppNode JVM to UTF-8 by adding -Dfile.encoding=UTF-8 in the bwappnode.tra file.

AMBW-19540

Summary: When a project contain abstract and concrete WSDL using same target namespace, a validation error is generated.

Workaround: None

AMBW-18459 Summary: The ability to reference from a standalone (external) schema to an inline schema is not supported. If your project contains such a reference, a validation error is generated.

Workaround: Externalize the WSDL-inline schema and change the import statements to reference the newly created (external) schema.

AMBW-17562 Summary: The OSGi configuration properties have been aligned between the debug environment launched from within TIBCO Business Studio for BusinessWorks and the AppNode that is launched in an installation. However, a difference in behavior of the osgi.compatibility.bootdelegation property in both the environments has been observed.

Workaround: None

AMBW-16256 Summary: The first attempt to change the data type of an Operator's input or output schema element fails and the change is not committed. Subsequent attempts complete without any failure.

Workaround: To commit the change, you must press the return key after every change.

AMBW-14861 Summary: Unable to enter an XPath expression on a transition using the XPath Builder. This issue is observed on Mac OS only.

Workaround: Enter the XPath expression directly in the Properties tab > Expression field for the transition without using the XPath Builder.

AMBW-12490 Summary: Under certain circumstances, substitution types do not resolve properly in the mapper. The mapper shows errors for them.

Workaround: Try closing and reopening the project. If that does not solve the issue, try closing and reopening Eclipse. If the errors still persist, perform a project clean (that is, go to the Project menu and click Clean...).

AMBW-11534 Summary: TIBCO Business Studio for BusinessWorks crashes occasionally on Windows 2012 R2 platform when switching workspace from File > Switch Workspace.

Workaround: Retry by switching the workspace.

Migration

Key Description
AMBW-40387 Summary: After migration, a path is not executed that leads to the difference in output.

Workaround: In TIBCO ActiveMatrix BusinessWorks™ 5.x the transition condition $Map-Data/ConditionType[last()] is treated as boolean but not in ActiveMatrix BusinessWorks™ 6.x as ActiveMatrix BusinessWorks™ 6.x has strict validations.

In order to resolve this, please update the condition as follows:

count($Map-Data/ConditionType[last()])>0

AMBW-40187 Summary: Migration of custom icon for the Call Process activity is not supported

Workaround: After migration, manually browse the custom icon field value for the Call Process activity.

AMBW-39231 Summary: While migrating a project using XPATH language for transitions option, which is set to XPATH 1.0 by default, on the Migration Wizard, the Process inline namespace schema collision issue occurs intermittently after migration is complete.

Workaround: Navigate to the faulted process and add the missing schema location field next to the namespace.

AMBW-39230 Summary: While migrating a project using the XPATH language for transitions option, which is set to XPATH 1.0 by default, the service agent process migrates as an empty process thereby throwing the Argument Cannot Be Null exception upon trying to view that process post Migration.

Workaround: Migrate that project in a different workspace, because the issue is intermittent.

AMBW-36094 Summary: Post migration, a schema cannot refer the .WSDL file in it and if you try to run the project, the Schema not found error is displayed at the run time.

Workaround: Copy the inline schema that gets created post migration of the project and paste it into the .WSDL file.

Remove the inline schema dependency from the dependencies section and in the input editor of the inline schema activity, re-map the point to the inline element. After this remove the inline schema that is empty and execute the project.

AMBW-36077 Summary: After migration, if the migrated project contains any SOAP service or client binding that uses SOAP RPC Encoded arrays, the following WSDL validation error occurs:

WSDL In-line schema SOAP encoded array type error. In-line schema in WSDL file contains SOAP encoded array type which requires a fix pattern.

Workaround: Download the SOAP Encoding schema from 'http://schemas.xmlsoap.org/soap/encoding/', and put it into the ActiveMatrix BusinessWorks project.

AMBW-35926 Summary: The migration tool does not support external schema for multi-part message in the bindings.

Workaround: Create wrapper schemas for all multi-part messages of WSDL.

AMBW-35899 Summary: Currently, only copy-of mapping is supported for context mapping of headers.

Workaround: You can either create One-to-one mapping manually or use a copy-of option for context mappings.

AMBW-33749 Summary: After migration, additional round brackets in the names of the folder for externalized schema creates issues at run time.

Workaround: Remove the special characters after migration in the folder names.

AMBW-30656 Summary: A schema cannot contain two global components with the same name.

Workaround: Modify one of the schema namespaces or element names, so that the names are unique.

AMBW-30476 Summary: After migration, the input mapping for the End activity which refers to a multi-part WSDL message displays validation errors.

Workaround: A WSDL message is not supported by a mapper. Create a new .xsd schema element with the structure similar to associated WSDL message, and then map the schema element in place of WSDL message.

AMBW-26746 Summary: The TransformXML activity from ActiveMatrix BusinessWorks 5.x did not migrate correctly if the Input/Output style of the activity was set to TREE in the ActiveMatrix BusinessWorks 5.x project.

Workaround: None

AMBW-14547 Summary: When you migrate an TIBCO ActiveMatrix BusinessWorks 5.x project containing in-built functions in the JDBC Query activity, an Invalid Column name error is thrown in the JDBC Query activity.

Workaround: Use an Alias instead of the in-built functions in the ActiveMatrix BusinessWorks 5.x project.

AMBW-14295 Summary: After migration, the output of project with REST and JSON palette activities does not match with the input of the other activities in the migrated project.

Workaround: None

AMBW-13683 Summary: Shared resource module property references in the migrated TIBCO ActiveMatrix BusinessWorks 5.x projects do not show up correctly on non-Windows platforms.

Workaround: Close and reopen the project.

AMBW-9969 Summary: ActiveMatrix BusinessWorks 5.x projects with SOAP headers configuration in SOAP activities are not properly migrated to ActiveMatrix BusinessWorks 6.x.

Workaround: SOAP functionality in ActiveMatrix BusinessWorks 6.x is achieved through SOAP Binding where its detail configuration is outside of ActiveMatrix BusinessWorks Process. The SOAP headers definition are defined at the Binding configuration and configured as generic context parameters for the Process. In the Process, you can use the Get Context activity (from Basic Palette) to retrieve and process the headers as context data. You can do this manually to complete the migrated project.

Palettes

JAVA Palette
Key Description
AMBW-13526 Summary: In Java To XML activity, the Output tab is not populated correctly, if Java class contains nested object references in different classes.

Workaround: None.

JDBC Palette
Key Description
AMBW-42049 Summary: Unable to access the stored procedure input and output parameters with MSSQL DataDirect driver if you select the procedure without selecting Schema, and Catalog or Package.

Workaround: Select the Schema, and Catalog or Package fields and then select the stored procedure

AMBW-36229 Summary: Unnecessary error logs are displayed in the log file.

Workaround: None

AMBW-23464 Summary: The Oracle DataDirect driver does not support cursor datatype.

Workaround: Use native drivers instead of DataDirect drivers.

AMBW-23260 Summary: MySQL Community Edition is not supported for Data Direct drivers

Workaround: Use native drivers instead of DataDirect drivers.

AMBW-23193 Summary: When using DataDirect drivers with a JDBC Shared Resource, that is linked to a JDBC process, the SQL Builder Wizard does not work correctly.

Workaround: Use native drivers.

AMBW-20130 Summary: The login timeout value is not effective when connecting to a Windows OS database. The JDBC Query activity fails with the error,JDBCConnectionNotFoundException at runtime without honoring the Login Timeout value specified in the JDBC Connection Shared Resource.

Workaround: None

AMBW-14624 Summary: The Set Explicit Nil check box for Objects and Collections in JDBC Call Procedure activity is disabled.

Workaround: None

AMBW-14547 Summary: When you migrate an TIBCO ActiveMatrix BusinessWorks™ 5.x project containing in-built functions in the JDBC Query activity, an invalid column name error is thrown in the JDBC Query activity.

Workaround: Use an Alias instead of the in-built functions in the ActiveMatrix BusinessWorks™ 5.x project.

AMBW-11667 Summary: Using any in-built function in JDBC Query activity without "Alias" fails to execute the application and throws an Invalid Column name error at run time.

Workaround: Use "Alias" to work with any in-built function in JDBC Query activity.

AMBW-11624 Summary: TIBCO Business Studio™ for BusinessWorks™ hangs when opening SQL Builder if the database details on the JDBC shared resource are changed from PostgreSQL to MySQL after a query has been created using SQL builder.

Workaround: None

AMBW-8855 Summary: The localized error messages of JDBC connection are not displayed correctly in TIBCO Business Studio for BusinessWorks.

Workaround: None

XML Palette
Key Description
AMBW-31813 Summary: Use of pipe(union) ('|') character in XSLT throws the following error at runtime:

com.tibco.bw.palette.xml.runtime.fault.XMLTransformException: Exception [org.genxdm.xpath.v20.err.ConcreteErrException] occurred during XSLT transformation. Exception detail [org.genxdm.xpath.v20.err.ConcreteErrException: [XPTY0004] Either the expression has a static type that is not appropriate for the context in which it occurs, or the dynamic type of the value does not match the required type.]

Workaround: Open the XSLT file and manually convert the pipe (union) ('|') operator to "or" operator and run the project

AMBW-14292 Summary: The Parse XML activity displays blank ErrorCode and ErrorMessage for activity output data validation error.

Workaround: None

Policy

Key Description
AMBW-34607 Summary: Marketo plugin container edition breaks with the recent JRE upgrade.

Workaround: Please refer Marketo plug-in documentation for more information.

AMBW-19513 Summary: If a SOAP binding is not configured with Transport, the Add New Policy icon should be disabled, the Policy field should not be displayed in the tree view, and a NULL pointer exception is generated if you try to add a policy on the binding.

Workaround: None