Closed Issues

The following are the closed issues of TIBCO ActiveMatrix BusinessWorks™.

The closed issues are grouped by components:

Administration

Release 6.6.0

Key Description
AMBW-36934 The running application instance details were not visible as App Instances view could not be expanded on the Application level 2 page on Admin UI.
AMBW-36739 OSGI commands failed to execute through Admin CLI when BWAgent was configured in DBEMS mode.
AMBW-36508 A module property of type password had a garbage value when it was just selected for modifying a value, but not modified, and any other module property was modified on the Admin UI.
AMBW-36208 An AppSpace property reverted to its original value when the other AppSpace properties were added or modified.
AMBW-35617 When an application was started or stopped multiple times, there was some discrepancy in displaying application status from Admin UI, Admin CLI, and REST API.
AMBW-35415 An incorrect error was displayed during BWAgent startup.
AMBW-35413 The Applications view on the Admin UI displayed errors even when application instances were running properly.
AMBW-35239 The name of the profile was reset to default in the Admin UI when a module property value was changed.
AMBW-35236 Applications failed to start on AppSpaces with the same name across different domains.
AMBW-35106 The BWAgent configured with DB or EMS took considerable time while running backup scripts.
AMBW-35063 When the EMS server was restarted, the machine status and the BWAgent status was changed to unreachable in the Admin UI.
AMBW-35006 The BWAgent failed to register when a TIBCO Enterprise Administrator(TEA) agent had a default value as 0.0.0.0, and the BWAgent was configured with Database with TIBCO Enterprise Message Service™.
AMBW-34936 An application endpoint URL was not populated in BWAgent REST API call when BWAgent was configured with DB and EMS. However, it was populated for BWAgent was configured with ActiveSpaces.
AMBW-34935 The Admin UI displayed promoted module properties for an application as undefined%.
AMBW-34929 The Deploy application REST API method returned a huge response.
AMBW-34423 The StatisticsProvider is not yet initialized error occurred on the BWAgent console when the AppNode was in the running state and the BWAgent was started.
AMBW-33978 The browse domains REST API call with the flag full=true returned different response than that of swagger document.
AMBW-33847 The incorrect response was received during the start or stop of an application using BWAgent REST API.
AMBW-33833 An application took more time to stop than anticipated and the REST API Stop command returned a response even when the application had not stopped completely.
AMBW-33765 A REST API call now generates a URL with applications instead of apps. For example: "href": "http://SERVER:8079/bw/v1/domains/Domain_PT_01/appspaces/AS_PT_01/applications/PT_OAUTH_Token_v1-service.application/1.0"
AMBW-33690 You can now update the agentrequesttimeout property using bwagent_db.json and bwagent_ftl.json and all other timeouts are derived from it.
AMBW-33203 After EMS failover, if EMS is configured using json file, and the bwagent is restarted after restarting the failed EMS server, the bwagent can not start, and displays Duplicate member error.

In the bwagent.ini file, the active EMS server should be the first one in the URL, and then restart the BWAgent.

AMBW-32706 If a BWAgent was configured to use process monitoring via UDP, then after closing BWAgent from console, an error was displayed on Admin CLI.
AMBW-32705 Unnecessary information is not displayed in a BWAgent log as it is now moved to DEBUG level.
AMBW-32699 The BWAgent REST API now has all the fields that bwadmin exposes. The new option -description is added in a swagger UI.
AMBW-31451 After performing any action on any page of Admin UI, pagination redirected to first page.
AMBW-27163 The unregisteragent command to unregister an agent from a domain did not work.
AMBW-22169 The BWAgent considered Windows Internet Explorer browser settings for a file path when uploading an .EAR file.

Release 6.5.1

Key Description
AMBW-34241 A REST API returned an incorrect response code when you tried to stop an application that was already in a stopped state.
AMBW-34005 An application failed to start with MySQL database installed on a Linux platform.
AMBW-33804 In the show command of bwadmin, the domain name was case sensitive.
AMBW-33803 An AppNode runtime information could not be retrieved on a non-domain agent's AppNode level 2 page in a graph view.
AMBW-33800 The custom OSGi plug-in could not retrieve data about process statistics from TIBCO ActiveMatrix BusinessWorks™ 6.5.0.

Release 6.5.0

Key Description
AMBW-31242 The bwagent now closes all the EMS connections during shut down.
AMBW-31120 Support for obfuscated password for FTL has been added. Users can use the bwobfuscator.exe utility to obfuscate plain text passwords.
AMBW-30932 BWagent REST API role management failed to grant read access rights to all the browse REST APIs.
AMBW-30903 The -home option in the Create Domain command while creating a domain sets the domain home on all the machines available in the Agent network for the particular path.
AMBW-30354 Memory leak issues were observed with bwagent, and the Admin UI took time to respond when loading the Application Archives and Applications page.
AMBW-29734 The bwadmin application returned the status as started for applications that were in the impaired or degraded state.
AMBW-29730 When an application took more than 60 seconds to start, a warning message stating that the Application did not start was displayed due to timeout exception. To configure the timeout value, set the timeout property, bw.agent.technology.requestTimeout in the bwagent.ini file and restart the agent.
AMBW-29602 The -csv option used to print the table content as a comma separated value table was not handled for domains, AppSpaces, AppNodes, Applications, and Archives.
AMBW-29531 Support has been added to set the bwagent timeout for an AppNode that takes a longer time to start.

To configure the timeout value, set the timeout property bw.agent.technology.requestTimeout in the bwagent.ini file and restart the agent.

AMBW-28971 The Show App command now shows description of applications.
AMBW-28341 A new bwagent REST API for getting the component details is now available. The new API is

http://<HOST>:8079/bw/v1/domains/<Domain Name>/appspaces/<Appspace Name>/applications/<Application Name>/<Application Version>/<appnode_name>/component/ <Component_name>.

AMBW-28257 During application stop, the stop application command in the bwagent became unresponsive.
AMBW-27600 An error was generated when pushing the config.ini file through the command line.
AMBW-27521 Memory leak issue was observed when statistics were enabled.
AMBW-26162 Issues were reported when the bwagent was configured with the Microsoft SQL Server.

To configure the bwagent with MS SQL Server, set the values for Minimum Server Role and Database Role required for a user for a particular database using the following steps:

In MS SQL Server Management Server, navigate to Security > Logins > Right click on Login Properties > Server Roles .

The minimum server role required for a particular user is public.

Under User Mapping, the minimum database role membership for the selected database for a user mapped to the login should be one of the following two combinations: 1) public and db_owner OR 2) public, db_datawriter, db_datareader, and db_ddladmin.

AMBW-26160 A Null Pointer Exception was displayed under the details heading intermittently when performing any action on the Application level 2 page.
AMBW-26129 The components of an Application did not stop when the Application was stopped.
AMBW-25547 After EMS failover, the bwagent could not start and displayed duplicate member error. For a specific scenario, refer AMBW-33203 in the known issues section.
AMBW-25529 Now same application with different versions can be deployed to the same AppSpace. You can now start or stop, deploy or undeploy any application version.
AMBW-23807 Obfuscated password is now supported when securing the BWagent REST API server.
AMBW-22512 A new command bwagent.exe startagent -nt has been added. You can not register the bwagent in the TEA UI when the bwagent is started using the startagent -nt option.

Bindings

Release 6.6.0

Key Description
AMBW-37322 Invalid format for type errors were thrown on creating a REST service from a swagger document. Also, null pointer exceptions were thrown when an element of object type was created, without populating its properties value.
AMBW-36994 The Reverse Proxy Host or Port was not updated in the endpoint URL, if a Concrete WSDL was generated at run time. To get the updated host/port at design time, we have configuration fields for host and port on the Concrete WSDL Generation Wizard.
AMBW-36863 When an unbound fault was added to the header in a SOAP service, the following exception occurred after invoking the service:

Failed to process Declared Fault Message for Operation.

AMBW-36269 When you create a REST service with Swagger file, which has a non-standard OpenAPI Specification format, the design-time errors were displayed.
AMBW-36057 When a Compression check box of the HTTP Connector shared resource was selected, POST responses for REST services were not compressed.
AMBW-35898 If the WSDL definition had a schema imported from a shared module, a concrete WSDL could not be generated from URL.
AMBW-35279 The HTTP Exceptions thrown by the SOAP Invoke activity were not caught in the Catch block of the particular HTTP Exception.
AMBW-34796 The security header was not available as the undescribed header for SOAP.

Set the property bw.governance.removesecurityheader.disabled to true in the config.ini file.

AMBW-34608 An error was generated and the SOAP request failed when there was a change in the order of soapenv:actor and soapenv:mustunderstand attributes.
AMBW-34379 Applications with SOAP Reference Binding failed to start when a SOAP service had a WSDL with <?Siebel-Property-Set EscapeNames="false"?> tag.
AMBW-34172 TIBCO Business Studio™ for BusinessWorks™ could not recognize REST service response with status codes 2xx other than 200, and displayed string instead of response objects when REST service was created using Swagger file .

Release 6.5.1

Key Description
AMBW-34259 Concrete WSDL file could not be retrieved at run time during SOAP service deployment on a web browser using the URL for an AIX platform.
AMBW-34010 At times, the concrete WSDL file could not be retrieved at run time and gave the following error: No service definition available.

This issue occurred when the SOAP service was deployed from a web browser and you tried to access the concrete WSDL file by using the domain name.

AMBW-34009 The <wsdl:types> tag was empty in the concrete WSDL generated at run time from the browser.
AMBW-34008 The schema elements in the run time concrete WSDL were duplicated when the concrete WSDL was fetched from two deployed applications sharing a common schema from a shared module.
AMBW-34002 SOAP requests failed when mapping optional nil element to optional empty element.
AMBW-33646 If a concrete WSDL file was accessed using a domain name during SOAP service deployment on a web browser, the file could not be retrieved at run time and the following error was generated: No Service Definition Available.
AMBW-33573 A REST service generated an error when multiple services were deployed on the same connector in a certain order.
AMBW-33440 The concrete WSDL added an extra forward slash (/) in the address location when a module property was used for the Endpoint URI field in a SOAP service binding.
AMBW-33282 TIBCO Business Studio™ for BusinessWorks™ displayed validation errors when generating concrete WSDL at design time and run time.
AMBW-33272 The Concrete WSDL file could not be retrieved at run time for a SOAP service deployed through a web browser by using the URL.
AMBW-33135 The NoHttpResponseException was intermittently displayed when invoking a REST service.

To ensure correct request processing, on the Advanced tab of the Invoke Rest API activity, set the Request Entity Processing field value to Buffered.

Release 6.5.0

Key Description
AMBW-32812 The SOAP service sent incorrect fault response values to the client when the Set Context activity was used to set the fault response values.
AMBW-32747 When an invalid XML request was sent to a REST service, the 500 server error was displayed and the subsequent valid requests also started failing.
AMBW-32364 The Concrete WSDL file could not be retrieved at run time for a SOAP service deployed through a web browser by using the URL.
AMBW-32079 TIBCO Business Studio for BusinessWorks displayed the Null Pointer Exception when generating concrete WSDLs. The Null Pointer Exception was also displayed when the abstract WSDL's inline schema was imported with blank namespaces, or the schema had resource files with no target namespaces.
AMBW-32030 In some cases, TIBCO Business Studio for BusinessWorks displayed the error, WSDL import error when concrete WSDL files were imported to another application.
AMBW-31528 The Invoke REST Reference displayed the error, java.lang.IllegalArgumentException: prefix cannot be null when creating a QName under heavy load of concurrent REST requests, or during load testing.
AMBW-31524 When creating a concrete WSDL, TIBCO Business Studio for BusinessWorks displayed the Null Pointer Exception, when schemas imported other schemas with no target namespace for a SOAP service.
AMBW-31509 The Get Context activity could not fetch Security Context Certificate values when the Expose Security Context check box was selected in the SOAP service binding.
AMBW-31397 The information added in the Summary field in TIBCO Business Studio for BusinessWorks did not appear in the Swagger file on deployment when the top-down process workflow was used.
AMBW-31349 When creating a concrete WSDL, TIBCO Business Studio for BusinessWorks displayed the Null Pointer Exception, when schemas included other schemas with no target namespace for a SOAP service.
AMBW-30596 Support to add the SOAP Actor attribute in the Subject Provider shared resource.
AMBW-30315 If the Client Acknowledge Mode was enabled for a SOAP over JMS service and the max session value was set to more than 1, when a service run time exception occurred in the service all the JMS messages were recovered during session recovery causing multiple message delivery.
AMBW-30314 When the SOAP Service binding was configured to use JMS as the transport type, and Client Acknowledge Mode was enabled, the module property value set for the Max Sessions field was not honored at run time.

This has been fixed, and now the sessions used at run time correctly reflect the value set on the Max Sessions field.

AMBW-30276 The sequence of elements of complexType were modified when an XSD was generated using Swagger file.
AMBW-30252 Swagger 2.0 definitions that had other files in related directories could not be imported to TIBCO ActiveMatrix BusinessWorks™.
Note: When you import the swagger file, first generate the XSD schema.

Right click the swagger json file, and click Refactor > Generate XSD Schema to generate the XSD schema.

Create the service using the top-down approach, and change the schema element in the Input Editor tab of the generated Reply activity.

AMBW-30240 The Swagger UI generated two responses when the response header parameter had the same name as the request header parameter in the REST service.
AMBW-30237 TIBCO Business Studio for BusinessWorks displayed an error when the response header parameter had the same name as the request header parameter in the REST service.
AMBW-30168 If the SOAP Service binding was configured to use JMS as the transport type, and Client Acknowledge Mode was enabled, and if a JMS message caused a service run time exception to be generated in the SOAP Service process flow that contained a Throw activity, but no catch block handle, all subsequent JMS messages were also recovered during the session recovery.

The correct behavior is to recover the JMS message that is currently processing and all subsequent messages to be processed, if the max session value for the JMS Connection in the service binding is 1.

AMBW-30139 TIBCO Business Studio for BusinessWorks displayed an error : Null Pointer exception when multiple form parameters were added in a REST Reference Binding created using the Request-Type: application/x-www-form-urlencoded and the POST operation.
AMBW-30122 In the scenario where the SOAP Service Binding was configured to use JMS as the transport type, and Acknowledge Mode was enabled, the module property value set for the Max Sessions field was not honored at run time. This has been fixed, and now the sessions used at run time correctly reflects the value set on the Max Sessions field.
AMBW-29913 When a module property was renamed, the changes did not reflect on the SOAP JMS Binding for the respective fields that used this property.
AMBW-29907 ActiveMatrix BusinessWorks™ generated Unexpected EOF in attribute value error when processing the SOAP response with the log level set as ERROR for SOAP binding logger, and if the SOAP response had MTOM attachments of large size.
AMBW-29845 TIBCO Business Studio for BusinessWorks displayed the error, Failed to create DocumentBuilderFactory for parsing xml schema source when trying to retrieve concrete WSDL at run time by using the ?wsdl option for multilevel schema import.
AMBW-29732 Duplicate entries of XSD elements were generated in the concrete WSDL retrieved with ?wsdl option when multiple applications used the schema from the shared module, deployed to the same AppSpace.
AMBW-29687 When an XSD defined inside a WSDL was used in the REST service, the JSON validation error occurred when invoking the service.
AMBW-29660 When an abstract WSDL used for SOAP service binding had WSDL import artifacts, that is, the imported WSDL had inline schemas, they were not added during design time concrete WSDL generation.
AMBW-29659 Changes to the SOAPAction header on the SOAP service binding were not reflected in the Concrete WSDL if the WSDL retrieved at run time used the <request URI>/?WSDL option.
AMBW-29581 TIBCO Business Studio for BusinessWorks displayed an error when the REST Reference was used to invoke a service that had path parameters not enclosed within path separators.
AMBW-29487 The non-inline WSDL schema was not embedded in the Concrete WSDL, if the WSDL was retrieved at run time using the <request URI>/?WSDL option.
AMBW-27549 TIBCO Business Studio for BusinessWorks displayed XSD Schema validation error when validating conversion from the Swagger schema to the XSD schema.
AMBW-25279 The Refactoring option has been added for the REST service binding. Using this option, you can rename the binding and delete the binding or operation.
AMBW-22553 A NullPointerException is generated when using the Generate Concrete WSDL option to create a concrete WSDL for a SOAP Service binding.

To avoid this error, create a new SOAP Service Binding, and generate the concrete WSDL using the same option.

AMBW-22246 When the Concrete WSDL was dragged and dropped over an empty process or reference area and the Invoke Operation option was selected, ActiveMatrix BusinessWorks did not pick the binding from the Concrete WSDL.
AMBW-22027 TIBCO Business Studio for BusinessWorks displayed the Null Pointer Exception when the schema element in the Input Editor of the Reply activity for operations of the REST service was changed.

General

Release 6.6.0

Key Description
AMBW-37665 When an application was created with Docker and Cloud Foundry profile, and if the ContainerConfiguration value was selected, the Integer and Password field values were different from the String field.
AMBW-37664 When a <TIBCO_HOME> had spaces in its path, and there was a change in the logback.xml file in the Run/Debug Configuration dialog box, wrong arguments were generated in the arguments page, which did not let the internal appnode to start.
AMBW-37663 Exceptions occurred while adding input under Tests tab.
AMBW-37661 At design time, when an executable bwdesign encountered an error, it did not return non zero error code to the operating system on failure.
AMBW-37500 The Invalid comparison error is now shown in the Problems tab in addition to the Xpath builder.
AMBW-37461 TIBCO ActiveMatrix BusinessWorks™ generated Failed to parse configuration error at run time when a module property has hash (#) character in its value.
AMBW-37237 The Copy Of function added unused namespaces declared inside a source activity.

Select the copy-of target element. Open Show/Hide edit tab. Clear the copy-namespaces check box to not carry parent namespaces.

AMBW-36920 The duplicate property was created when importing properties from a property profile for a group and a nested group.
AMBW-36816 At design time, when a project with no warnings was exported from one workspace and imported into a different workspace lot of warnings were displayed.
AMBW-36776 ActiveMatrix BusinessWorks returned incorrect results when comparing the primitive type boolean values to functions true() and false() for the Parse XML activity having Validate Output check box was clear, and XPath and XSLT version was 1.0 in few cases.

To resolve this issue, select the Assume all inputs untyped check box under Windows > Preferences > Mapper dialog box and perform the Clean operation on the project.

AMBW-36552 A .EAR file was not generated when the ADB adapter was installed.
AMBW-36498 Applications failed to start on AIX platform.
AMBW-36477 The getcomponentdetail command displayed activation status as SingleNode on Admin CLI, even when a multi node application was running in a FTGroup with LB Mode.
AMBW-36421 In FTGroup mode, an AppNode became unresponsive when an application in a standby mode with an activator process was stopped.
AMBW-36318 The matches() XPath function did not work when partial regular expression was provided.
AMBW-36271 If the property bw.engine.start.all.applications.on.appnode.startup is set to true, then all the applications deployed on an AppNode are started once the AppNode starts irrespective of the last states of applications.
AMBW-36163 The XPath function format-dateTime() ignored the picture string for [MN,*-3] and generated incorrect output at runtime.
AMBW-36064 Considerable amount of time was required while building a workspace when there were multiple schemas in a workspace.
AMBW-36063 Building a workspace took a longer time when modifying REST bindings in a Components view.
AMBW-36053 TIBCO Business Studio™ for BusinessWorks™ became unresponsive in Components view intermittently when switching between REST Bindings.
AMBW-35962 Promoting a module property to an application property took an incorrect value at run time when a module property had a new line character (\n) in the value.
AMBW-35961 Fractional values were always present even though there was no fractional part in the mapping when the xsd:restriction condition was used with the base as xsd:decimal.

Add the following VM argument to omit the fractional part from the value: -Dbw.xml.decimal.omitDecimalPoint=true

AMBW-35863 Subprocess is now listed inside the main process span.
AMBW-35797 An application failed to restart as the config folder was corrupted.
AMBW-35725 A new frwk:startapp OSGI command is added to start an application gracefully.

This functionality is supported in TIBCO Business Studio for BusinessWorks only. Do the following configurations to Debugger in TIBCO Business Studio for BusinessWorks:

  1. Go to Debug Configurations > Bundles.
  2. Set Auto start for all the applications to false.
  3. If Apply button is not reflecting changes, you need to deselect one of the core bundles in target platform and then reselect it. Then changes are applied.
  4. Default Auto-start in the debug configurations has to be true.

When you start debugging, an application is loaded. To start that application, on the console, execute the following command:

startapp <ApplicationName>.application

AMBW-35430 Subprocess transition failed to process in few cases when XPath version was changed from 1.0 to 2.0.
AMBW-35417 An informative error message was not logged into the appnode.log file when a module property referred an incorrect keystore.
AMBW-35405 ActiveMatrix BusinessWorks generated a Null Pointer exception when an AppNode was shut down.
AMBW-35391 Jenkins jobs failed to build an .EAR file using the bwdesign command line utility for the projects containing SAP palette RFC activities.
AMBW-35375 A warning was displayed in a debug mode when unbounded string element had multiple values set.
AMBW-35334 Iterate group failed when using a schema with no target namespace.
AMBW-35108 During migration, the .xsd files took more time than expected to migrate.
AMBW-35058 A reference for original policy on binding broke when a policy resource was copied and renamed.
AMBW-35043 Atlassian Git did not track empty project folders, which were present in ActiveMatrix BusinessWorks, resulting in warning and error messages when a Git versioned ActiveMatrix BusinessWorks project was imported into TIBCO Business Studio™ for BusinessWorks™.
AMBW-35015 The bwdesign utility displayed Null Pointer error intermittently when exporting an .EAR file.
AMBW-34980 TIBCO ActiveMatrix BusinessWorks application took a longer time to start.
AMBW-34979 The Repeat on Error group executed even when a success condition occurred.
AMBW-34975 After migration, process memory and heap memory consumption increased substantially.
AMBW-34972 At run time, when a condition was matched, ActiveMatrix BusinessWorks wrongly evaluated the success with no matching condition as success.
AMBW-34943 A new Disable implicit-if existence checking check box is added in the Preferences > Mapper dialog box. Select the check box and clean the project to remove <xsl:if test="$Mapper/Element1"> elements from Optional to Optional mapping.
AMBW-34878 You can now export lapi OSGi command output to .CSV file.
AMBW-34869 The %DOMAIN_NAME% variable is now supported in the appnode_config.ini_template and bwappnode-an.tra_template files.
AMBW-34832 When the XSLT version was changed from 1.0 to 2.0, the empty tags were created in the activity output.
AMBW-34759 When an application had nested Repeat on Error groups, the inner group executed continuously in a loop and never exited, even though there was no error.
AMBW-34738 An application displayed all platform values of Deployment Target that were first selected and then cleared in the New BusinessWorks Application dialog box.
AMBW-34663 When module properties were added to the shared module and the application project was imported, the properties of the application were not updated after the import.

The following error was displayed: Application configuration error. A set of module properties included in the BW application are not in sync with the module properties configured for the module. Re-include module in the application.

AMBW-34565 Loop variable mapping for an iterate group was not correctly resolved.
AMBW-34505 The subprocess job status remained scheduled when a spawned subprocess completed after the main process.
AMBW-34482 The XPath function Prefix-from-QName() returned an empty value when the QName() function had an input as prefix.
AMBW-34377 The application did not start in TIBCO Business Studio for BusinessWorks and became unresponsive during an application startup with high memory usage, when specific schema was imported into a project.
AMBW-34338 Swagger files in a project were not in sync for local folders.
AMBW-34321 An error occurred when an .EAR file was generated using bwdesign utility.
AMBW-34312 Unable to open and view a .bwp process in the process editor.
AMBW-34179 The lapi OSGI command displayed all process instances instead of active process instances for all applications running at AppNode.
AMBW-34159 When a schema was imported during coercion, from a maven shared module, the schema location could not be resolved. Also, when multiple schemas, or a WSDL and a schema shared the same target namespace, errors were thrown in coercions using the schema.
AMBW-34014 An application became unresponsive when an error occurred while executing OnStartUp method of an application activator process.
AMBW-33915 The Success with Condition and Success with no matching Condition transitions were evaluated as true at the same time, when performing copy and paste operations.
AMBW-33742 The compare-dateTime() XPath function returned incorrect results when one of the parameters was the output of parse-dateTime() XPath function.
AMBW-33733 ActiveMatrix BusinessWorks returned incorrect results when comparing the primitive type boolean to functions true() and false() with a few cases. For example, the Parse XML activity.
AMBW-33618 The Export Profile utility in TIBCO Business Studio for BusinessWorks now generates the same profile as it is generated by exporting from an application archive.
AMBW-33598 Creating a complex value by combining two module properties did not work in the File Poller activity.
AMBW-33511 Support is added for suspending and resuming process instances via OSGi commands. The following two new commands are added:
  • suspendpi <input pid>
  • resumepi <input pid>
AMBW-33472 An application stopped receiving requests intermittently when using pageThreshold property in a config.ini file of an AppNode.
AMBW-33211 TIBCO Business Studio for BusinessWorks was unable to import the schemas from the external shared module libraries to the schemas inside application modules.
AMBW-33158 The bw.application.checkpoint.retainFaultedJob and bw.application.checkpoint.recoverOnRestart properties are now applicable for all applications without any configuration changes at AppSpace level.
AMBW-33103 The application did not start in TIBCO Business Studio for BusinessWorks and became unresponsive during an application startup with high memory usage, when the specific schema was imported into a project.
AMBW-33101 The Start, End, Eval, and Elapse time values were not displayed for process instance statistics and activity instance statistics.
AMBW-32852 TIBCO Business Studio for BusinessWorks displayed a warning when a schema without a namespace was present in a shared module, and was referred in an application module.
AMBW-32799 The definition of xs:key in the XSD generated an error even when the XML schema was valid.
AMBW-32656 Renaming of the schema element name did not automatically reflect in the SOAP service and reference Context parameters.
AMBW-32603 The changes performed in the Swagger file from the API Explorer view did not reflect in the process.
AMBW-32301 An element of type <Any> inside a choice block could not be coerced with the other element.
AMBW-32276 Unrelated error messages occurred when a shared resource outside a package was moved inside a package.
AMBW-31960 TIBCO Business Studio for BusinessWorks displayed incorrect icon for an operation's implementation type, when an abstract WSDL was dragged and dropped in the process editor to implement the operation.
AMBW-31928 When you use the mapper directly in the deep-equal() function, it always resulted as TRUE.
AMBW-31520 The variable %APPNODE_NAME% did not work in the bwappnode-an.tra_template file.
AMBW-31408 In a few cases, when you change the condition on transition , no job data was visible when debugging an application and generated a No namespace found error.
AMBW-31264 A component was created in a module when a direct sub-process, without any component, was copied and pasted.
AMBW-30910 Set the bw.engine.inline.subprocess.multiLogging.disable property to true in the config.ini file to avoid unnecessary logging at ERROR level.
AMBW-30573 When multiple endpoints were generated from the same Swagger file of the resource path to generate the Resource name, the full resource path was not considered.
AMBW-30432 The drop-down box in the Process Launcher pane on the Debugger view is now removed.
AMBW-30297 When a choice type was compared to an atomic or an element type in the mapping, an Invalid Comparison error occurred.
AMBW-30005 Transitions did not work as expected when validation was disabled.
AMBW-29963 Folders within a special folder could not be renamed.
AMBW-28838 TIBCO Business Studio for BusinessWorks displayed some files as modified for collaborative development even though there were no logical or structural changes made.
AMBW-28651 TIBCO Business Studio for BusinessWorks and runtime were unable to work with large schema file, threw OutOfMemory exception, and CPU usage was very high.
AMBW-26726 Changes made in logback.xml for logging parameters are applied even when AppNode is running.
AMBW-26499 TIBCO Business Studio for BusinessWorks could not resolve a schema and displayed an error, if the folder containing schema had special characters in the folder name.
AMBW-25561 On adding or removing coercion in the XPath Builder dialog box for transitions and groups, the coercion was not expanded to an appropriate level to view the coerced type.
AMBW-25449 Performance was degraded for spawned processes.
AMBW-23610 An error occurred when an application with an activator process was stopped.
AMBW-23609 The OnShutDown operation in an activator process was not executed when an AppNode was stopped.
AMBW-23422 Type or value of promoted application property was not updated when changing the type or value of the module property related to the promoted application property.
AMBW-22529 Logging was stopped when a log level of AppNode was changed while its running.
AMBW-19460 The input text is dynamically validated whenever the XPath is changed in the XPath Builder dialog box.

Release 6.5.1

Key Description
AMBW-34236 An error occurred when validating a WSDL.
AMBW-34235 A validation error occurred when an XSD schema without import location was imported.
AMBW-34233 A source process was changed and corrupted when copying a constructor and then deleting it from the target process.
AMBW-34194 An EAR failed to generate when the port type was missing in a WSDL interface.
AMBW-34113 Building a workspace took longer time than expected when modifying REST bindings in the Components view.
AMBW-34100 Complex schema elements could not be mapped when existing projects were imported without the Copy Projects into workspace option.
AMBW-34098 The format-dateTime() XPath function generated an incorrect result with the Z operator.
AMBW-34097 The format-dateTime() XPath function could not parse the picture string correctly.
AMBW-34096 TIBCO Business Studio™ for BusinessWorks™ displayed an error for anyElement and anyType element mappings when using an explicit XPath expression.
AMBW-34095 After migration, an assertion error occurred due to an external document.
AMBW-34091 The format-dateTime() XPath function returned AM instead of PM for the time between 12:00 and 12:59.
AMBW-34083 SOAP and REST endpoints were duplicated after restarting an application.
AMBW-34082 The application failed to start when it had a asterisk (*) in the XPATH, and the warning message Runtime binding is not synchronized was fixed with the Quick Fix option.
AMBW-34080 AppNode logs did not roll over.

For previously created AppNodes, replace the existing AppNode's logback.xml with {BW.HOME}/config/logback.xml.

Newly created AppNodes use the new logback.xml.

AMBW-34068 A NullPointerException occurred on a SOAP Reference Binding when refactoring an operation on a server side.
AMBW-33813 An application with JDBC Connection shared resource failed to start for the first time when an AppNode was configured in a group persistence mode with DB and EMS configuration.
AMBW-33795 Embedded policies were not enforced on the AIX platform, and the NoClassDefFoundError exception was logged in the AppNode log when you started the AppNode.
AMBW-33700 After deploying an application on TIBCO Cloud Integration™, an exception occurred at run time for the date-format function.
AMBW-33588 After migration, an incorrect validation error was displayed for a process inline schema when referring to WSDL inline schema without the schemaLocation attribute.
AMBW-33569 During migration, the Handle Variable Rename error message was displayed.
AMBW-33550 Values of the promoted application properties in different profiles were modified when a new module property was added.
AMBW-33510 The FaultDetails variable was not shown in the debugger when a Catch block was applied in the Scope group.
AMBW-33503 For a few migrated projects, building a workspace took a long time.
AMBW-33462 TIBCO Business Studio™ for BusinessWorks™ became unresponsive in Components view intermittently when switching between REST Bindings.
AMBW-33461 The application went into an impaired state when a shared resource was not placed inside a package in a shared module.
AMBW-33276 Main process was delayed as sub-processes could not be spawned.
AMBW-33246 Considerable amount was required while building a workspace when there were multiple schemas in a workspace.
AMBW-33219 An application without any dependency on JMS failed when an Enterprise Messaging Server (EMS) driver was uninstalled.
AMBW-33204 New process was created after renaming an existing process.
AMBW-33192 You could not completely remove an activity name when renaming an activity in the Properties tab with the backspace key.
AMBW-33118 The module property name could not be edited when clicking it too fast.
AMBW-33113 A validation error was generated during start of an application but not at the design time even when the type of the property inside the module descriptor did not match the type of the process property.

Release 6.5.0

Key Description
AMBW-32826 XML output that used the XmlEncoder, including the render-xml() function, the custom XPath function, and the Render XML activity produced malformed output, where > was replaced by <.

For e.g. <element> appeared as &lt;element&lt;

AMBW-32811 When multiple schemas shared the same target namespace and contained chameleon includes, the following error message was intermittently displayed: Locked. Cannot add additional Schema.
AMBW-32809 TIBCO Business Studio™ for BusinessWorks™ displayed the validation error when mapping to a choice element and the second option from the choice list was selected.
AMBW-32277 The bwagent displayed incorrect information about an AppNode's allocated and used heap memory in the Admin UI.
AMBW-32219 Design time errors were not displayed though the process file contained the wrong location for the WSDL import location.
AMBW-32073 The process color became blue when a REST Reference Binding was created using a JSON file.
AMBW-32001 The Quick Fix option did not work for reserializing design time and run time binding, and the warning Runtime binding is not synchronized was displayed.
AMBW-31913 The XSD element, DuplicateKeyException was not available in the internal fault types XSD schema. When the Checkpoint activity was created, the internal fault types XSD schema overrode the Checkpoint activity's fault type schema. The XSD element DuplicateKeyException was missing and the runtime error was displayed.
AMBW-31858 After migration, the port type pointed to incorrect WSDL locations though the serialization was correct.
AMBW-31766 Some job data was missing for a few projects when the projects were run in the debug mode.
AMBW-31651 When the XSD schema namespace ended with XML, the Eclipse Modelling Framework (EMF) generated a prefix which started with XML. This generated prefix was invalid and caused the EMF mode deserialization error.
AMBW-31646 TIBCO Business Studio for BusinessWorks could not display a schema in the currentElelment variable on the Input tab of the Iterate Group when the conditional statement's output referred to the same element defined in the schema.
AMBW-31518 Importing the XSD file from a shared module now directly adds the shared module in the dependency list.
AMBW-31401 TIBCO ActiveMatrix BusinessWorks™ failed to process the schemas and displayed the cache exception at runtime due to a chain of chameleon includes.
AMBW-31338 Closing and restarting TIBCO Business Studio for BusinessWorks caused the previously added components to disappear.
AMBW-31256 The debugger could not display the correct status of the process execution in the Process Details tab as the shared modules were released and were not dependent on the application module.
AMBW-31249 Activities in a process could not be renamed because incorrect comment syntax broke the third-party parser.
AMBW-31248 If the Set Shared Variable and the Get Shared Variable activities were used in a process, or multiple processes, of a shared module to retrieve a module shared variable, and if two applications were dependent on the same shared module, both of the applications referenced the same copy of the module shared variable.

This has been fixed, and now each application uses a separate copy of the module shared variable.

AMBW-31247 Validation warnings were displayed if there was no coercion (xsd schema) specified when mapping the any element(*).

Validation errors are now lowered to the warnings level when there is no coercion.

AMBW-31246 The Copy-of binding functionality did not carry information for the original element. The Surround with.. option was not available with the Copy-of binding functionality.
AMBW-31140 TIBCO Business Studio for BusinessWorks displayed the error, render-xml exception: node cannot be null, when running projects with custom XPath functions.
AMBW-31108 The Quick Fix option is now available when an extra parameter binding is detected after projects are imported to the workspace.
AMBW-31093 TIBCO Business Studio for BusinessWorks displayed the error, render-xml exception: node cannot be null, when running projects with custom XPath functions.
AMBW-31072 ActiveMatrix BusinessWorks™ generated VariableNotFound exception intermittently when an activity was deleted and replaced by the other activity in an application. The error was also generated when certain BPEL activity extensions were created or deleted.
AMBW-31023 A quick fix is now available to enable validation warnings or errors for transitions with conditions where the XSLT is not set.

With this quick fix, the XSLT is set using the design time expression language.

AMBW-31014 When a subprocess call failed due to any error, the subprocess created duplicate fields in the input of the subprocess call.
AMBW-30971 When module properties were added to the shared module and the application project was imported, the properties of the application were not updated after import.

The following error was displayed: Application configuration error. A set of module properties included in the BW application are not in sync with the module properties configured for the module. Re-include module in the application.

This has been fixed, and now TIBCO Business Studio for BusinessWorks includes or updates the missing properties of the application when the application is included in the workspace.

AMBW-30873 Some projects using Fault Context on the service or reference bindings failed.
AMBW-30848 The debug logs did not display the activities inside the processes, and the debugger failed to stop when an activity included a breakpoint. Due to the missing XPDLID attribute in the serialization of the activities, the projects were executed at the run time but were not displayed in the debugger.
AMBW-30815 ActiveMatrix BusinessWorks generated Failed to read Process model from resource error when starting an application.
AMBW-30814 When two ActiveMatrix BusinessWorks applications were dependent on the same shared module, one of the applications went into the impaired state.
AMBW-30775 A new option Configure Contents has been added in the Problems tab. Select this option to configure types of errors and warnings to enable CI/CD.
AMBW-30732 A radio button was displayed under the API Explorer tab in TIBCO Business Studio for BusinessWorks.
AMBW-30727 ActiveMatrix BusinessWorks did not display any error for incorrect XPath expression, and continued to execute infinitely when comparing to string types.
AMBW-30674 Application properties are now updated properly after selecting the red (X) button. The default value is updated correctly without selecting the Save button.
AMBW-30673 ActiveMatrix BusinessWorks did not evaluate XPath expression consistently in the XPath Builder and generated warnings for if-then-else statements.
AMBW-30634 TIBCO Business Studio for BusinessWorks was unresponsive after importing projects to the workspace and performing the building workspace action.
AMBW-30614 The bwdesign command line utility could not import binary shared module in the archived format.
AMBW-30589 Importing projects and updating the JDBC shared resource took a long time.
AMBW-30569 The bwenginedb command generated an error Invalid object name 'PES_PROCESS_CHECKPOINT' when running the application in the persistence mode ftgroup.
AMBW-30430 Two AppNodes were in the active state at the same time when the bwengine was configured in the ftgroup mode and TIBCO Enterprise Message Service was stopped for few minutes and restarted.
AMBW-30427 A new API getSerializedFaultData() has been added to get error or fault output from an activity audit event.
AMBW-30361 In ActiveMatrix BusinessWorks 6.x the trackingInfo element was not present under the ProcessContext element.
AMBW-30275 Schemas without namespaces were not resolved in the Iterate group.
AMBW-30191 If the schema for the Reply activity in a REST service was changed, the following error was generated at runtime: PVM-XML-106032: Cannot find XML element.
AMBW-30119 When extensions were used in the schema, then that element was duplicated and displayed validation errors.
AMBW-30114 The complex element could not be mapped to the anyelement datatype under two levels of choice of elements when one of the choices is a repeating anyelement.
AMBW-30100 Errors were displayed in TIBCO Business Studio for BusinessWorks when multiple applications used the same HTTP Connector, that was defined inside the Shared Module. The errors were displayed when the Shared Across check box was not selected.
AMBW-29997 ActiveMatrix BusinessWorks failed to process the schemas and displayed the cache exception at run time due to a chain of chameleon includes.
AMBW-29947 TIBCO Business Studio for BusinessWorks did not show any validation error even if there was an error in the XPath statement used in the activity.
AMBW-29932 TIBCO Business Studio for BusinessWorks took time to respond and was unresponsive when renaming WSDLs or schema folders.
AMBW-29919 When a type was coerced to the any element, a validation error was generated on the XPath expression over the transition.
AMBW-29916 TIBCO Business Studio for BusinessWorks displayed transition configuration error when coercions were applied on a transition.
AMBW-29882 Activities in the catch block of a group were not visible in the Output Activity list.
AMBW-29881 When projects were imported from an external location into a workspace without copying the project, projects were deleted and generated again from the application module.

The regenerated projects were created under the workspace instead of the location from where the project was created, and a copy of the same application data was created.

AMBW-29860 When schemas had cyclic includes, model group conversion displayed the following assertion error: Compositor argument cannot be null.
AMBW-29838 When the build automatically option was turned off, the operation to copy and rename a process between modules ended with corrupted entries in module.bwm.
AMBW-29737 Any data entered in the Sequence Key field on the Advanced tab of the JMS Receive Message activity generated the Variable Not Found error.
AMBW-29714 ActiveMatrix BusinessWorks generated the Invalid BWApplicationHandle error and went in the start failed state when an application was restarted on the AppNode. The AppNode was in the passive state and then turned active when the initial active node was stopped.
AMBW-29603 When an Invoke activity received a fault response that was a declared fault, the Rethrow activity and the Repeat on Error group activity did not pass the fault response to the higher level catch.
AMBW-29591 Applications that had Activator Process and Invoke activity with binding or process references displayed different and unexpected behavior when executed in the FT with group mode.
AMBW-29585 Copying and pasting a calling process retained older references and displayed an error.
AMBW-29569 ActiveMatrix BusinessWorks generated warning for activator component when the Engine Command activity invoked StopApplication command. An error was displayed after restarting an application.
AMBW-29499 Adding a Timer activity to a subprocess did not generate validation errors.
AMBW-29497 When multiple commands were run in the script, bwdesign displayed the ArrayIndexOutOfBound exception.
AMBW-29495 Validation errors were reported in TIBCO Business Studio for BusinessWorks after importing projects created on ActiveMatrix BusinessWorks 6.4.1 or earlier versions.
AMBW-29492 Users can now turn the Build Automatically option ON or OFF from the config.ini file by setting the property bw.autobuild to true or false.
AMBW-29475 Assertion XPath mappings and absolute values could not be saved for unit testing purpose.
AMBW-29440 In some cases, automatic refactoring through TIBCO Business Studio for BusinessWorks led to extra parameter bindings in refactored XSLT files, which resulted in runtime errors.

This has been fixed, and the correct input parameter bindings are now provided during the automatic refactoring process.

AMBW-29433 The Engine Command activity returned duplicate information for the GetProcessInstanceInfo command when ProcessDefinitionName was passed from the input schema.
AMBW-29360 An error was displayed when a shared resource was moved from an Application Module to Shared Module using the Move option.
AMBW-29354 In some cases, ActiveMatrix BusinessWorks generated errors at runtime when automatic refactoring led to the extra parameter bindings in refactored XSLT files through TIBCO Business Studio for BusinessWorks.
AMBW-29331 Logging a large validation exception resulted in the out of heap space condition.
AMBW-29312 Component configurations could not be seen after saving the project.
AMBW-29279 The intermittent cache error Locked. Cannot add additional Schema was displayed when multiple schemas shared the same targetnamespace and contained chameleon includes.
AMBW-29136 Files and folders were not removed when a new version of ActiveMatrix BusinessWorks was installed in the same TIBCO_HOME where a previous version was installed.
AMBW-29121 The bwdesign import command became unresponsive.
AMBW-29105 In certain scenarios, TIBCO Business Studio for BusinessWorks stopped responding when performing actions like cleaning all projects, adding a REST resource, adding SOAP or REST bindings to a resource, and automatic building of a workspace.
AMBW-29101 A runtime exception activity output data validation error occurred when the generated concrete WSDL had schemas that included other schemas with no target namespace.
AMBW-29083 Schemas without namespaces were not resolved in the Iterate Group and in the output of the Start activity in the direct sub process.
AMBW-29079 A Null pointer exception was displayed when a new process was added to an application module with an empty or missing TIBCO.xml file.
AMBW-28995 The error, TIBCO-BW-FRWK-600026: Failed to start BW Module [factset.client.contact.crmfm.nbc.module:1.0.0.qualifier], <CausedBy> null <CausedBy> java.lang.NullPointerException was displayed when module properties were referred from the Shared Module.
AMBW-28983 The Apply button was disabled in the Run Configuration and Debug Configuration dialog boxes when the initial configuration was changed.
AMBW-28549 The error, No matching ns9:property was reported when Refactor > Repair BusinessWorks Projects was used with the option, Recover Activity IDs.

This is now fixed and the error is no longer reported.

With this fix the Recover Activity IDs option in the Refactoring Wizard has been replaced with the Quick Fix option.

To apply Quick Fix, perform the following steps:
  1. Navigate to Windows > Preference > BusinessWorks > Validation and change the preference for Recover Activity ID and Recreate Activity ID from Warning to Error.
  2. Right-click on the errors related to Recover Activity Id, Recreate Activity ID, and select the Quick Fix option.
AMBW-28406 When multiple commands were run in the script, bwdesign displayed the ArrayIndexOutOfBound exception.
AMBW-27711 A process was deselected in the Run Configuration and Debug Configuration dialog boxes when it was renamed.
AMBW-27710 The Apply button was disabled when new processes were added in the current application or project, and the Select All button was selected before running the application.
AMBW-27575 The automatic_mapper_if_surround functionality was not working for nillable optional to optional elements mapping.
AMBW-27521 The memory leak issue was observed.
AMBW-27503 TIBCO Business Studio for BusinessWorks was unresponsive when projects from the GIT repository were opened.
AMBW-27431 TIBCO Business Studio for BusinessWorks displayed an error when importing projects that had empty folders. The projects were exported using the Studio Projects to Archive option.
AMBW-26925 TIBCO Business Studio for BusinessWorks could not display attributes defined under complex element in the Input Editor tab of a Mapper activity.
AMBW-26725 In a transition coercions were not saved after they were added to mappings.
AMBW-26297 When a user stopped and started a running AppNode, the NullPointerException was logged intermittently in the appnode.log file.
AMBW-26180 Copying activities from one process to another process displayed errors.
AMBW-25791 The bwdesign command line utility became unresponsive and could not create EAR files.
AMBW-25629 After migration, TIBCO Business Studio for BusinessWorks displayed the validation error for violation of UPA (Unique Particle Attribution).

Workaround: Clear the check box Check full XML Schema Conformance at XML > XML Schema Files > Validation on the Preferences dialog box to disable strict checking.

AMBW-25502 The mapping from a coercion to a variable list broke when clicked on any other activity.
AMBW-24717 When changing the color of a transition to a color other than the default black, the transition color changes but the text remains black. Sometimes the text color also changes but when the workspace was reopened, the workspace became black.
AMBW-24410 You can now export an application without a profile. At the runtime we can upload profile and run the application successfully.
AMBW-23858 ActiveMatrix BusinessWorks generated Null Pointer Exception when an AppNode was configured in FT mode, and then was restarted.
AMBW-22862 A button Navigate to schema was added to show what file or namespace is the selected Schema element of the Process Variable.
AMBW-20542 The out data validation stack trace in ActiveMatrix BusinessWorks 6.x did not specify the erroneous elements.
AMBW-20144 TIBCO Business Studio for BusinessWorks became unresponsive intermittently when a SOAP or REST binding was added to the process and a workspace was built.
AMBW-13197 Support has been added for a module property to configure DateTime property in the Timer activity.

Migration

Release 6.6.0
Key Description
AMBW-36740 The JDBC transaction group was migrated as a Scope group instead of JDBC.
AMBW-36526 After migration, some of the mappings or conditions were not migrated in the Generate Error activity.
AMBW-36476 The format-dateTime() or parse-dateTime() XPath functions in TIBCO ActiveMatrix BusinessWorks™ 5.x were migrated incorrectly.
AMBW-36462 Mapping was migrated partially for the Throw activity.
AMBW-36342 The Iterate group was migrated incorrectly and when the process was opened, the following error occurred:

Argument cannot be null.

AMBW-36297 The Activator process present in the shared module (during migration) was not visible during run time causing errors.
AMBW-36170 Not all Custom XPath functions migrated and led to errors in the project.
AMBW-36096 After migration, following error was generated while starting a soap service.

no xsd for this imported location

AMBW-35860 After migration, the XPath expression for For-Each current element value was incorrect.
AMBW-35769 After migration, the mapping errors were observed, because the target namespace was absent in the ActiveMatrix BusinessWorks™ 5.x schema file.
AMBW-35766 After migration, the union ("|") operator was converted to OR operator and could not return a value correctly.
AMBW-35753 The migration of the For-Each loop with complex XPath expression and global variables was incorrect.
AMBW-35511 The Invoke REST API activity was migrated as an empty activity.
AMBW-35395 The processes from ActiveMatrix BusinessWorks 5.x application were not migrated because of the invalid entries in the Process Name field in a call process.
AMBW-35226 While migrating ActiveMatrix BusinessWorks 5.x SOAP Client application using headers from WSDL, the migrated project automatically adds the SetContext/GetContext activities in the process.
AMBW-35223 After migrating projects with process properties mapped, the following exception occurred at run time:

[err:XPST0008] The expression refers to a variable name that is not defined in the static context.

AMBW-35170 After migration, an error was generated when the applications had inline schema with no namespace defined.
AMBW-35108 During migration, the .xsd files took more time than expected to migrate.
AMBW-34731 After migration to ActiveMatrix BusinessWorks 6.x, the system was unable to map any element with a given XPath.
AMBW-34704 After migration, a few optional elements that were not mapped were not migrated.
AMBW-34688 After migration, the local variable was not shown as repeating.
AMBW-34653 After migrating a project, the Error output schema for HttpCommunicationException, HttpClientException, and HttpServerException in the SOAP Request Reply activity was not available.
AMBW-34558 After migration, the starter process was migrated as a service subprocess.
AMBW-34519 After migration, a few DTD schema attributes were not migrated.
AMBW-34518 After migration, the subprocess was migrated as NULL.
AMBW-33997 When the ActiveMatrix BusinessWorks 5.x project was migrated to TIBCO ActiveMatrix BusinessWorks™ Container Edition, some of the shared variables were not migrated.
AMBW-33752 After migration, the global variables which were declared as a concatenation of a global variable and a literal value were not migrated properly, and the activity configuration data was lost.
AMBW-33665 After migration, an extra body element, bodyText, was displayed in the Send Mail activity, and displayed a validation error.
AMBW-33664 After migration, an .xsd file imported a .wsdl file and displayed validation errors.
AMBW-33663 After migration, one of the processes in the project was migrated as an empty process.
AMBW-33594 After migration, an error occurred because of an additional import statement.
AMBW-33473 After migration, the output of the subprocess containing a parse data activity was not shown in the main process.
AMBW-32880 After migration from ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks™ Container Edition, the conditional transition having coerced XPath was not recognized.
AMBW-32847 After migration from ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks™ Container Edition, shared variables containing an inline schema were not migrated.
AMBW-32742 After migration, validation errors were displayed since the ResultSets Use Schema check box on the JDBC Call Procedure activity was not selected.
AMBW-32372 An application migrated the File Poller activity incorrectly whenever it had the sequencing key value.
AMBW-32327 When the SOAP Request Reply activity referred a WSDL from the project library, its configuration failed to migrate correctly.
AMBW-31988 After migration, the unwanted process properties for shared resource were getting added into the process even when that shared resource was not used in the process.
AMBW-31886 After migration, an application failed to start.
AMBW-31848 After migration, the com.tibco.xml.xdata.bind.CommentBinding exception occurred in the migration report.
AMBW-31711 The inputs for the Mapper activity did not migrate properly.
AMBW-31610 In a project containing the shared modules, the global variables were not migrated to the respective module properties.
AMBW-31478 The comments at the beginning of an XPath Expression in a transition or group were ignored causing loss of information.
Note:

Transition/Group Level Comment Support: Comment at the start of an expression (on a transition/group) with design time validation error (unexpected token) present in ActiveMatrix BusinessWorks 6.6.0.

Activity Level Comment Support: Post migration, all the comments (at the start, in the middle, and at the end) in an activity are moved to a different line-set (Comment Binding) as a Comment.

AMBW-30839 After migration, the relative path in the Input tab of the Mapper activity was not working.
AMBW-30731 If the process variables had an element reference from the inline schema of WSDL then those process variables were not migrated.
AMBW-30689 After migration, the End activity displayed an error, when a SOAP Reference Binding was configured with a part name other than the default part name in the Message Part Configuration option.
AMBW-30387 The global variables were not migrated from ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks™ Container Edition.
AMBW-29836 During migration, the Handle Variable Rename error pop up was displayed.
AMBW-29688 After migration, an inline schema with namespace collision was reported.
AMBW-29428 After migration, an input schema for the Throw activity was invisible and all the mappings were unavailable.
AMBW-29002 The migration tool failed to migrate processes for the large projects.
AMBW-28446 After migration, the process properties were not created.
AMBW-27266 After migration from ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks™ Container Edition, the existing comments in the XPath expression were not migrated.
Release 6.5.1
Key Description
AMBW-34351 A main process could not pass mapped data to a subprocess.
AMBW-34187 After migration, the JMS Send Message activity could not reflect changes in a referenced schema.
AMBW-34078 After migration, the Process In-line schema namespace collision error was displayed which was incorrect.
AMBW-33959 After migration, the Rendezvous Subscriber activity could not pick up messages at run time and generated a null pointer exception.
AMBW-33880 After migration, a few exceptions were listed in the MigrationReport.log that broke some processes.
AMBW-33876 After migration, the Catch block and its associated activities executed only once.
AMBW-33856 After migration, a process migrated as empty due to some issue with its Iteration element's inline schema creation.
AMBW-33577 After migration, a few processes had duplicate WSDL or XSD entries on the Process Dependencies tab.
AMBW-33571 The mapping did not create a copy-of element for choice elements when a root element had choice elements.
AMBW-33520 When you ran a project after migrating to TIBCO ActiveMatrix BusinessWorks 6.5.0 HF-001, the Confirm activity remained in the starting status.
AMBW-33499 After migration, Generate Error activities that had choice elements with when-otherwise conditions were deleted.
AMBW-33492 After installing TIBCO ActiveMatrix BusinessWorks 6.4.2 HF-004, some projects displayed the StackOverFlow error during migration.
AMBW-33490 After migration, Parse XML and Mapper activities were migrated as Null when an input binding element schema was a part of WSDL and a resource URI had special characters.
AMBW-33488 The JMS Receiver activity was migrated as empty when JMS application properties were not mapped from design time libraries.
AMBW-33464 The </xsd:attribute name="xml:lang" type="xsd:language" use="optional"/> now migrates as </xsd:attribute ref="xml:lang" use="optional"/>.
AMBW-33443 Numbers in XPath expressions were wrongly migrated as "xsd:string(...)" instead of xsd:string().
AMBW-33437 After migration, the JMS Queue Requestor and JMS Queue Receiver activities had different target namespaces for inline schema, which resulted in some errors in the project.
AMBW-33433 An exception was generated when migrating the project due to which a process was migrated as an empty process.
AMBW-33389 After migration, the Activity input configuration error was generated on the Input tab of an End activity inside a Catch block.
AMBW-33369 After migration, XPath was missing from a Reply activity.
AMBW-33368 After migration, an error occurred at run time when the JMS Send Message and JMS Receive Message activities had inline schemas with different namespaces.
AMBW-33309 After migration, a process was migrated as an empty process.
AMBW-33308 After migration, when a process had JMS Queue Requester activity whose input and output was configured with an inline XML schema, the output inline schema replaced the input inline schema for that activity.
AMBW-33307 After migration, when a process had JMS Topic Requester activity whose input and output was configured with an inline XML schema, the output inline schema replaced the input inline schema for that activity.
AMBW-30921 A subprocess with a WSDL inline schema in the End activity could not be migrated.
Release 6.5.0
Key Description
AMBW-32993 After migration, the elements for Accumulate Output of the Iterate group were not visible.
AMBW-32816 The $Error_<activityName> was not migrated in the Catch block correctly.
AMBW-32808 A few mappers were migrated as empty activities.
AMBW-32807 The mapping repair mechanism applied to activities during migration resulted in the argument cannot be null exception. Also, when the service definition was migrated, the message that was defined in the imported WSDL was not handled correctly.
AMBW-32377 After migration, unused process properties were created in the processes.
AMBW-32374 A few processes migrated as empty scopes and the Argument cannot be null error was displayed when trying to open those processes. This issue occurred when the schemas were not available for some of the activities in those processes.
AMBW-32241 TIBCO Business Studio™ for BusinessWorks™ displayed the Null pointer exception when accessing the service context, post migration.
AMBW-32171 A few processes migrated as empty scopes.
AMBW-32169 After migration mappings in the main process were broken.
AMBW-32162 Processes representing Operations migrated as empty processes.
AMBW-32064 Migrated projects failed to start at run time due to the missing schema.
AMBW-32062 After migrating a project, run time failed with the error, cvc-complex-type.3.1: The attribute, 'ref', is not valid with respect to its attribute use. src-element.
AMBW-32041 After migrating and running the project, the subprocess output was missing from the job data.
AMBW-32035 After migration, the Output activity field for the Iterate group was not populated.
AMBW-31965 After migration, the XPath expression from the Invoke activity was not resolved.
AMBW-31961 After migration, a few processes displayed the process inline schema namespace collision error.
AMBW-31905 After migration, the output of the Invoke activity present inside the group was not available outside the group. The output was unavailable outside the group because the Global Scope check box was not selected.
AMBW-31899 After successfully validating a project, when a process was deleted and then migrated again, the project displayed errors in other processes.
AMBW-31896 Selective migration failed for the service agent process when the process was migrated using the command line.
AMBW-31880 The unresolved type validation error occurred due to the invalid namespace in the output element of Call Process activity.
AMBW-31875 The Get Context and Set Context activities migrated twice.
AMBW-31859 After migration, the output of the Invoke activity was not visible.
AMBW-31857 After migration, duplicate datasources were observed in the transition from the Invoke activity.
AMBW-31823 The service implementation process was not migrated correctly when the service agent process name included a period (.).
AMBW-31609 During migration, process loading failed with the out of memory issue leading to the Java heap space error.
AMBW-31551 Mappings in the End activity were not migrated.
AMBW-31548 Projects containing global properties within Java global instance shared resource can now be migrated.
AMBW-31355 Due to the missing name attribute in a process, the argument cannot be null error was displayed when the process was opened after migration.
AMBW-31097 Elements in the context binding were missing after migration.
AMBW-31096 The component was deleted after the project was saved because the Name attribute in the process was missing after migration.
AMBW-31095 Operation contexts were not migrated.
AMBW-31060 User defined faults were not visible in the catch all block for migrated projects.
AMBW-31048 Some processes failed to open after migration due to the missing namespace declaration within the process's definition element.
AMBW-31002 Service Agent migration failed as the corresponding context schema migrated incorrectly.
AMBW-31001 After migration, a process failed to open and displayed the argument cannot be null error.
AMBW-30983 Contents of the Schema file were empty after migration. This issue was caused due to the UTF-16LE charset present in the Schema file.
AMBW-30982 The Custom ErrorSchema was not available in the End activity of the main process block after migration.
AMBW-30977 The choice option was not visible for the Start, Render XML, Parse XML activities post migration.
AMBW-30974 The Get Context activity migrated as a null activity.
AMBW-30948 During migration, multiple schemas could not be migrated separately. A single XSD file was created for multiple processes.
AMBW-30859 The service process migrated as empty which led to the component process under the module descriptor for the service process not getting created.
AMBW-30831 When a TIBCO ActiveMatrix BusinessWorks™ 5.x project was configured using SSL, the corresponding JMS connection was not created after migration.
AMBW-30587 During migration, when a WSDL inline schema was referred as input or output for direct call processes and for service migration, the location evaluated for adding the import in a process model failed with the Null Pointer exception.

Migration failed, and the null pointer exception occured as locations with .xsd qualifiers were incompatible with the URI formation guidelines.

AMBW-30559 Few processes failed to migrate correctly and displayed the argument cannot be null error, when opened in TIBCO Business Studio for BusinessWorks.
AMBW-30406 The service agent failed to convert to the service process and binding creation failed as the service agent used the input header from the WSDL instead of the port WSDL.
AMBW-30403 Shared variables corresponding to Context Resource did not contain the required headers and the expected structure of the headers was not displayed correctly in the Output field for the Get Context activity after migration.
AMBW-30401 After migration, the Output Signatures for the Get Context and Set Context activities were not displayed correctly due to the type field for the Job Shared Variable coming blank.
AMBW-30385 Fault element was not displayed in the error variable of the Call Process activity after migration.
AMBW-30278 Input mappings for the Generate Error activity were missing after migration.
AMBW-30154 After migration, SOAP services were not implemented correctly. Once the migration process was complete, the migration log displayed the error message, The Invoke activity has its input specified as a WSDL message only, for now , and the SOAP service implementation migrated as empty.
AMBW-30146 After migration,the default host in the HTTP Client shared resource was mapped to https://localhost instead of localhost.
AMBW-30144 Processes with the Start and End activities where schemas pointed directly to a WSDL Inline Schema element were migrated incorrectly.
AMBW-30143 When a process containing activities from TIBCO ActiveSpaces was opened after migration, the following error message was generated: The argument cannot be null.
AMBW-29918 External schemas were not generated post migration when a ActiveMatrix BusinessWorks™ 5.x project contained inline schemas with WSDL references.
AMBW-29850 Migrating ActiveMatrix BusinessWorks 5.x project to ActiveMatrix BusinessWorks 6.x failed with the error java.lang.StackOverflowError.
AMBW-29849 The Encoding field on the General tab of the File Poller activity displayed a warning when projects were migrated from ActiveMatrix BusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x.
AMBW-29831 There were naming errors in the Activator process after migration because the name of the Call Process activity used in the Activator process was not according to the NC naming standard.
AMBW-29648 When an application containing data format with elements from a schema was migrated, the migration generated data format would not populate the elements resulting in errors in the application.
AMBW-29646 The Argument cannot be null error for migration scenarios has been fixed.
AMBW-29447 Though mappings were correct, the activities failed to recognize the output element. There were no input configuration errors but errors like Activity has input configuration error. No Matching response were displayed. This led to the Argument cannot be null error when trying to open the faulty processes post migration.
AMBW-29438 Within an if condition, when the value assigned for false was zero, the XML node was not rendered after migration.
AMBW-29425 The custom data type used in the input parameter of the JDBC Call Procedure activity migrated as a string.
AMBW-29277 Migration failed for some processes and displayed the Argument Cannot be Null error.
AMBW-28923 Processes did not migrate, and displayed the argument cannot be null exception when the processes were opened.
AMBW-28342 ActiveMatrix BusinessWorks 5.x subprocesses configured with dynamic override migrated as empty subprocesses.
AMBW-27626 Migration failed for the date-Time translation.
AMBW-27605 Data was not passed from the main process to the subprocess, and the process failed after migration.
AMBW-27324 Due to the stackoverflow error displayed during migration, a few processes did not migrate correctly.
AMBW-27254 The function true migrated as true() when this function was used in the XPath of an activity but did not migrate as true when the function was used on a transition.
AMBW-27107 The Activity Error Variable field was not selected after migration, and the error messages of the group activities were not reflected outside the group.
AMBW-26985 Expression fields were not migrated because the root element was not recognized by the migration tool.
AMBW-26873 After migration, the external XSDs displayed the error src-resolve: Cannot resolve the name element name' to a 'element declaration' component.
AMBW-26629 Migrated ActiveMatrix BusinessWorks 6.x projects displayed design time errors when the subprocess referred to a WSDL inline schema.
AMBW-26620 After migration, downstream mappings were broken as the SecurityContext element was not available at the output from the HTTP Receiver activity for mapping.
AMBW-26430 When a process variable was defined without a schema or inline element reference, mapping errors were displayed after migration.
AMBW-25258 After Migration, when one of the elements from the $_processContext was mapped, the mapping broke since the element was not available.
AMBW-23174 Links between the process service descriptor or WSDL and the process broke after migration.
AMBW-22999 Selecting the option Add Complex Type Variable allowed users to select only the global element. Selecting Schema type (complex types, WSDL messages) was not supported.
AMBW-20170 After migration, validation errors occurred when an XML element from an XSD schema, without a target namespace could not be resolved.

Palettes

Release 6.6.0

General Activities Palette
Key Description
AMBW-35406 When the same coercion was applied on two or more sibling elements, all the elements were incorrectly renamed to the name of the very first sibling.
AMBW-31685 No data was accumulated for the Output Activity field marked as Assign.
HTTP Palette
Key Description
AMBW-34185 An error occurred intermittently when invoking REST APIs with Send HTTP Request activity.
JAVA Palette
Key Description
AMBW-34874 For Java Invoke activity inside a loop, memory leak occurred for a process that ran for a long time thus surpassing the max heap limit.
AMBW-34177 The XML To Java activity could not generate target namespace when dependency was specified as Maven Dependency.
JDBC Palette
Key Description
AMBW-37041 The JDBC connection for DB2 database driver using sslTrustStoreLocation property in URL generated errors at run time, but Test Connection was successful.
AMBW-36702 The JDBC Call Procedure activity displayed all input and output parameters for two different procedure and function, if the procedure and function have the same name.
AMBW-35531 The number of JDBCQuery threads increased significantly during application execution.
AMBW-35360 The JDBC Query activity and SQL Direct activity gave different output for numeric data types.
AMBW-34854 JDBC connection URL for PostgreSql database driver generated errors at run time, but displayed connection successful message at design time when a connection URL had the sslmode=require property.
AMBW-34853 The SQL Direct activity did not show error message code in the Job Data view.
AMBW-34852 The JDBC Update activity timed out when inserting records in the IBM AS400 custom database driver using the jt400.jar file.
AMBW-34721 An application did not consider the currentschema parameter from the JDBC Connection URL at run time.
AMBW-34720 The Override S/A DataType check box on the Advanced tab of the JDBC Call Procedure activity now supports inout and out object type at run time.
AMBW-34360 The JDBC Update activity did not consider the Timeout(sec) value set.
AMBW-29290 Installing TIBCO ActiveMatrix BusinessWorks™ under Program Files on Windows operating system caused installation errors with JDBC driver bundles at runtime.
AMBW-29072 The Maximum open cursors exceeded error occurred in the JDBC Updateactivity while inserting records.
AMBW-28204 Execution of JDBC activities were delayed due to the SharedResource thread being in sleep state.
AMBW-18192 The column name is not valid error occurred with JDBC Query activity when aggregate functions like avg,sum, and count are used in select query.
JMS Palette
Key Description
AMBW-37270 Memory growth and memory leak occurred for JMS Send Message activity from the JMS Local Transaction group.
AMBW-36565 The configuration of the AQjmsInitialContext is not complete error occurred during test connection in JMS connection with Oracle AQ as Tibco custom JMS provider.
AMBW-34802 When a message was not acknowledged in the Get JMS Queue Message activity and the Acknowledge Mode was set as EMS Explicit Mode, a message was not processed again unless the application was restarted.
AMBW-34701 The JMS message deserialization failed when both the JMS Send Message and the JMS Receive Message activities used the same schema, and when you set the field value for int, decimal, double, and float to NULL.
AMBW-22481 The session was blocked and messages were not retried by JMS Receive Message with XML Text message type in Non-Auto Ack modes like Client ,TIBCO EMS Explicit Client, and TIBCO EMS No Acknowledge when the Confirm activity was in exception block and incoming messages were of text type.
Mail Palette
Key Description
AMBW-36118 The Receive Mail activity displayed an error message for emails with attachment for Microsoft Outlook mail server.
Parse Palette
Key Description
AMBW-34145 The Line Length value in the Field Offset section of the Data Format shared resource was not correctly updated with respect to changes in the end field value.
AMBW-32644 TIBCO Business Studio™ for BusinessWorks™ failed to parse the CSV strings, and intermediate double quotes from input string were removed.
AMBW-32623 TIBCO Business Studio for BusinessWorks failed to parse the CSV strings, and double quotes were not processed correctly.
REST and JSON Palette
Key Description
AMBW-30857 The Parse JSON activity interpreted "null" value incorrectly.
Rendezvous Palette
Key Description
AMBW-36176 Timed out error occurred on the Rendezvous Request Reply activity for reply message received within timeout value.
XML Palette
Key Description
AMBW-36021 The Parse XML activity failed to parse data for multiple comments above the root element.
AMBW-34998 The parseXML validation error was not shown in the $error_ParseXML activity, but in the generic $_error activity.
AMBW-31697 The XSLT tag omit-xml-declaration did not work as expected.
AMBW-30050 The Catch block could not handle errors from the Parse XML activity.
AMBW-28176 The Parse XML activity failed to parse an XML when it contained processing instructions such as <?Siebel-Property-Set EscapeNames="true"?>.
AMBW-25223 When the XPATH functions, like trim, pad, and so on, were used inside the filter expression, the java.lang.UnsupportedOperationException exception was thrown.
AMBW-14549 Performance degradation was observed in the Render XML activity.

Release 6.5.1

HTTP Palette
Key Description
AMBW-34208 The Send HTTP Request activity sent responses with empty fields intermittently.
AMBW-33136 An application failed at run time but no error was displayed at design time when the Host field in the HTTP Connector shared resource had a literal value as localhost and the value of the Deployment Target for an application was Tibco Cloud.
General Activities Palette
Key Description
AMBW-33483 An application job was started as soon as an Application or an AppNode was restarted when the Interval Unit value was set to DAY in the Timer activity.
JAVA Palette
Key Description
AMBW-32756 The XML To Java activity could not reload newly added Java members in a Java class.
JDBC Palette
Key Description
AMBW-34293 An Activity output data validation error was displayed when the Use Nil and Resulsets Use Schema check boxes were selected on the Advanced tab of the JDBC Call Procedure activity, and a procedure returned records with null values.
AMBW-34027 All columns of the table were displayed only when one of the tables returned as a part of an SQL procedure response was completely empty and the Use Nil check box was selected.
AMBW-33475 The SQL Direct activity returned the value as true instead of empty when you mapped the output with nillable as true and selected the Use Nil option.
AMBW-33360 The JDBC Query activity returned the value as true instead of empty when you mapped the output with nillable as true and selected the Use Nil option.
AMBW-33359 The NVARCHAR data type was converted to the VARCHAR data type when the sendStringParametersAsUnicode property was set to false in the SQL Server URL.
AMBW-33330 Excess threads were created when there were maximum number of connections to the database. The threads created by JDBC activities went into sleep state for few seconds rather than going into the standing or the waiting state.
AMBW-31914 JDBC activities could not connect to a secondary server when a DataDirect driver was used and the connection URL had hyphen (-) character in the host name.
AMBW-25957
JMS Palette
Key Description
AMBW-34053 The JMS Receive Message activity failed to reconnect after TIBCO Enterprise Message Server (EMS) failover. This issue occurred only when EMS was configured with ftgroup or group mode with governance flag enabled.
AMBW-34050 The JMS Receive Message activity generated an exception multiple times and failed to reconnect to the IBM MQ server when there was a network outage.
AMBW-34028 In some scenarios for Client Ack mode, only the first JMS message was processed successfully and subsequent messages failed to process.
AMBW-33828 When a message was sent using the JMS Send Message activity, and fetched by using a Get JMS Queue activity, the property JMSXDeliveryCount was automatically added to the Dynamic Properties output.
AMBW-33812 The JMS Send Message activity failed to reconnect to the IBM MQ 8 server when the IBM MQ 8 server was restarted.
AMBW-33438 Messages were not moved to $sys.redelivery.delay queue because they were not confirmed in the Get JMS Queue activity with client acknowledge mode.
Rendezvous Palette
Key Description
AMBW-34389 After migration, the value for one of the elements was missing in the Rendezvous Subscriber activity at runtime.

Release 6.5.0

FTP Palette
Key Description
AMBW-32911 The FTP Put activity was transferring data in ASCII format even when binary transfer mode was selected and the Overwrite Existing File option was not selected.
HTTP Palette
Key Description
AMBW-31211 The httpVersion, statusCode, and reasonPhrase data elements of the statusLine data element were not populated in the fault output of the Send HTTP Request activity when the HTTP server returned the 500 HTTP response.
AMBW-29915 When the Send HTTP Request activity's input headers type definition was changed, an error was generated due to unresolved MIME schema component.
AMBW-29138 The Send HTTP Request activity could not save the file obtained from the server response to the disk.
AMBW-27590 The HTTP request failed when the Content-disposition header in Send HTTP Request activity was unable to process multi-part MIME attachments according to the specifications for HTTP Components library.
AMBW-27506 The connections at the HTTP Client shared resource were active even after the HTTP server closed the connections. Notification was not sent to the HTTP Client shared resource after the timeout period.
AMBW-27290 When the Write To File check box was selected on the Advanced tab of the Send HTTP Request activity, and the size of the content sent by the server was large, TIBCO Business Studio™ for BusinessWorks™ displayed the out of memory error.
AMBW-24812 Contents of large MIME attachments in the HTTP Requests are now written directly to the disk without accumulating in a memory, when the Write To File check box is selected in HTTP Receiver or Wait for HTTP Request activities.
AMBW-21261 The statusLine element was empty in the Fault tab of Send HTTP Request activity when the HttpServerException was caught and the HTTP server responded with the error code 5xx.
General Activities Palette
Key Description
AMBW-30723 The second element was renamed incorrectly when the same coercion was applied on two sibling elements.
AMBW-30632 TIBCO ActiveMatrix BusinessWorks™ generated an error when the expression referred to a variable name not defined in the static context was mapped to a copy content.
JAVA Palette
Key Description
AMBW-30077 The XML To JAVA activity did not show a schema in the Input tab when it was linked to another activity.
AMBW-29456 When users refreshed the XML To Java activity before generating a schema, the schema with errors was produced, and validation errors were displayed.

This has been fixed, and the correct schema is created after refreshing the activity.

AMBW-29419 When the CustomerProfile class in a newly added Java To XML activity was selected or reloaded in one process, the Java To XML activity in other processes failed to display the output in the Output tab.
AMBW-26871 Incorrect schemas were generated when composition was used in two Java classes, and both the Java classes were used in the Java To XML activities in the same application module.
AMBW-32203

The Java To XML activity failed and displayed the Activity output data validation error due to incorrect annox generation of the arrays of type string (non-primitive) and 2D array of type class.

Note: For projects created or modified in TIBCO ActiveMatrix BusinessWorks™ 6.4.2_HF-003, go to the Navigator explorer and delete the .annoxfiles folder and the .ann.xml files from the bin folder or from the project's workspace. Also, delete the existing auto generated schemas from the schemas folder and reload the respective class to generate new schemas. If the schemas are not deleted, it leads to duplicate schemas and the project fails due to the issues with validation.
JDBC Palette
Key Description
AMBW-32891 The JDBC Call Procedure activity was not serializing the sqlState node if a JDBSQLException was generated.

This has been fixed, and the node is now successfully serialized.

AMBW-32759 ActiveMatrix BusinessWorks™ generated errors when the JDBC Connection shared resource using custom JDBC driver could not create new connection. This happened due to the TeraData database aborted the session in use.
AMBW-31516 The String index out of range: -1 error was generated with the Microsoft SQL data direct driver, when it was used with the server instance name instead of a port number in a JDBC shared resource.
AMBW-30889 ResultSets Use Schema was unable to fetch the metadata for the resultset from the stored procedure when the schema name was set to a module property in the JDBC Call Procedure activity.
AMBW-30694 The JDBC Call Procedure activity timed out when calling a stored procedure that had an object type input parameter, and if one of the fields of input parameters was empty.
AMBW-30619 If an SQL stored procedure had OUT parameters and was returning resultsets, ActiveMatrix BusinessWorks 6.x could not process the resultsets.
AMBW-30615 All whitespaces were removed from UnresolvedResultSets when the Interpret Invalid XML Chars check box on the Advanced tab of the JDBC Call Procedure activity was selected.
AMBW-30242 If there was a space in the column name in the Oracle stored procedure, the following error message was generated: Invalid column name.
AMBW-30166 When users called a stored procedure that returned multiple results, the UnresolvedResultsets variable was not populated with results from the database.
AMBW-30117 When a called stored procedure returned a select statement containing the "at symbol" (@), the UnresolvedResultsets variable was not populated with results from the database.
AMBW-29662 An invalid unwrap error occurred for certain JDBC Call Procedure scenarios.
AMBW-26926 When configuring a JDBC Connection shared resource to connect to a DB2 server, the error The encryptionMethod or autheticationMethod specified is not supported by the DB2 server you are connection to was generated if the AutheticationMethod option was used.
AMBW-24035 Activities from the JDBC Palette displayed a JDBC Timeout Exception when the query loads were too large for the connection pool to handle.
AMBW-22945 The JDBC Query output schema was not updated in the process when the iteration group was present in the same process.
JMS Palette
Key Description
AMBW-32877 The JMS Receive Message activity was unable to reconnect after restarting IBM MQ 8 server.
AMBW-32837 The JMS Receive Message activity failed to receive messages from IBM MQ 8 server if the messages contained empty properties.
AMBW-32825 The Process Property with a value as a Module Property could not be set in the Message Selector field on the Advanced tab of the JMS Receive Message activity.
AMBW-32369 The module property is now supported for the Delivery Delay (msec) field on the Advanced tab of the JMS Send Message activity.
AMBW-31933 The JMS Receive Message activity with Client Acknowledge Mode displayed incorrect receiver count on the queue in the FTgroup mode when the EMS server was restarted.
AMBW-31649 ActiveMatrix BusinessWorks failed to make SSL connection to the EMS 8.4 server as the EMS client did not support SHA256 cipher.
AMBW-31202 The dynamic property of the boolean data type was replaced with the string data type for the JMS Receive Message activity.
AMBW-29628 The JMS Send Message activity was unable to reconnect after restarting IBM MQ 8 server.
AMBW-29558 Runtime memory leak was observed when running long-time stability test for the JMS Receive Message activity.
AMBW-28017 The bwengine was unresponsive and displayed the javax.jms.IllegalStateException: Consumer is closed exception under heavy load or during load testing. The bwengine was unresponsive because the JMS Receive Message activity failed to respond.
AMBW-26750 ActiveMatrix BusinessWorks 6.x could not be connected to the JBOSS 7.x or higher version application server due to unsupported JNP protocols.
AMBW-24989 The Process Property having value as Module Property could not be set in the Message Selector field on the Advanced tab of the JMS Receive Message activity.
Parse Palette
Key Description
AMBW-32381 The out data validation stack trace in ActiveMatrix BusinessWorks 6.x did not specify the erroneous elements.
AMBW-30580 TIBCO Business Studio for BusinessWorks displayed File [null] cannot be opened using encoding method [ASCII] error when the Parse Data activity got an empty file or null data as a string input.
REST and JSON Palette
Key Description
AMBW-32937 The Use Null For Empty Value option for the Parse JSON activity and the REST Service Binding failed for specific scenarios.
AMBW-31344 The Parse JSON activity could not parse unicode characters.

This has been fixed now.

From TIBCO Business Studio for BusinessWorks, pass the following property in the VM arguments to enable unicode conversion:

-Dcom.tibco.plugin.restjson.escape.unicodeInText=true.

AMBW-30574 During the XML element to JSON conversion, the leading and trailing spaces were trimmed.
XML Palette
Key Description
AMBW-32835 Messages with duplicate prolog could not be parsed in the Parse Xml activity.

To avoid producing an XML declaration in the Transform Xml activity output, the following property must be added in the AppNode or AppSpace config.ini file:

bw.palette.xml.transform.omitXMLDeclaration=true

From TIBCO Business Studio™ for BusinessWorks™, add the VM argument

-D bw.palette.xml.transform.omitXMLDeclaration=true.

If the property is not present or has a value false, it produces an XML declaration in the Transform Xml activity output.

AMBW-30686 The Transform XML activity did not return values for elements where the XSLT file had conditions and where the input XML attribute was blank or nil.

For example <ws:Amount /> or <ws:Amount xsi:nil="true" />.

AMBW-31537 When using the XML Transform activity, the EmptyStackException error was displayed during XSLT transformation.
AMBW-29415 The Transform Xml activity now shows the XML declaration in the XML output.
AMBW-28657 The XMLParseException was generated when the Format using default namespace check box on the General tab of the Render Xml activity was selected.

Policies

Release 6.6.0

Key Description
AMBW-36553 The Authentication Failed error was displayed when a WSDL had namespaces that did not start with "http://".
AMBW-35852 TIBCO Business Studio™ for BusinessWorks™ displayed an error when a policy resource was in a shared module.
AMBW-35075 A REST service configured with LDAP basic authentication policy returned an incorrect error code when invoked with wrong credentials.
AMBW-34850 When a policy resource was in a shared module, a policy was not applied at run time and a plain request was sent.
AMBW-34795 The Timestamp was not sent intermittently in the SOAP security header.
AMBW-33977 TIBCO ActiveMatrix BusinessWorks 6.x could not generate errors for expired certificates.
AMBW-27423 The Invalid Property Exception occurred when a module property was used to search a user in base DN in LDAP resource.

Release 6.5.1

Key Description
AMBW-33460 SOAP requests were authenticated intermittently when the password in a request was empty.
AMBW-33336 The LDAP basic authentication policy did not work for Microsoft AD Server at runtime when the Admin user credentials check box was selected.

Release 6.5.0

Key Description
AMBW-32920 The security policy was not enforced when it was applied to Shared Modules in the application.
AMBW-32146 LDAP connections exceeded max connections setting.
AMBW-31978 The non standard tags in SubjectDN were not displayed correctly in the Expose Security Context field.
AMBW-29986 An application went to the Start Failed state on restart of an application when there was an unused Keystore Provider resource available in the application EAR.
AMBW-29733 New requests were not authenticated or processed once the number of requests were equal to LDAP pool size. Now any number of requests are authenticated across LDAP.
AMBW-29608 When unused Keystore Provider shared resource was present in the project, sometimes wrong keystore got wired to the SSL server resource. This resulted in the HTTP SSL server resource to fail.
AMBW-22196 The user name is now logged for the users when authentication fails.