Migration
This topic lists the closed issues related to Migration.
Release 6.10.0
| Key | Description |
|---|---|
| AMBW-49083 | The Migration utility fails with an error while migrating a project containing DTD. |
| AMBW-48400 | The HTTP Client Name field is blank in the SOAP Binding post migration. |
| AMBW-48367 | The SOAP endpoint URI field displays the value from the concrete WSDL instead of the value in the global variable. |
| AMBW-33063 | The schema location value is missing in the WSDL Inline Schema post migration from the import statement. |
Release 6.9.1
| Key | Description |
|---|---|
| AMBW-48159 | The RV publisher activity does not honor special keyword characters like "_plus_" and "_sp_" in the element name post Migration. |
| AMBW-47732 |
GV mapped to the JDBC activity timeout and Maximum rows are not showing up in ActiveMatrix BusinessWorks 5.x to 6.x migrated code. The "Timeout (secs)" and "Maximum rows" fields in the JDBC Call Procedure activity do not display the mapped module property value post migration but display the default literal values. |
| AMBW-32780 | The REST Dispatch and Reply activity in ActiveMatrix BusinessWorks 5.x is migrated to the Invoke Rest API activity instead of the REST Service Binding. |
Release 6.8.1
| Key | Description |
|---|---|
| AMBW-44538 | After migration, the element inside the Catch all > error_variables are not resolved correctly when a process with more than one fault element is configured in the End activity. |
Release 6.8.0
| Key | Description |
|---|---|
| AMBW-43791 | After migration, the mapper input is empty when the schema is referenced from data format shared resource. |
| AMBW-43501 |
The migration tool migrates processes with the REST-Dispatch-and-Reply activity to a REST resource. In TIBCO ActiveMatrix BusinessWorks™ 5.x, the service processing logic is delegated to a subprocess as per operation. Normally the subprocess is migrated. To supplement this, a call process is created to invoke that subprocess in the REST resource. You may need to fix the mapping for the newly created call process manually. This could fix the mapping itself, or the input and output schemas for the called subprocess. Note: The REST Service descriptor supports both internal and external WADL references. However, we do not support multiple resources pointing to the same resource path and having the same HTTP method.
|
| AMBW-42280 | After migration, the Mapper activity is migrated as an empty activity. |
| AMBW-41353 | After migration, if the variable list XPath expression of an Iterate group is linked to multiple schemas then the iterator schema is not resolved. |
| AMBW-33641 | Getting "Coercion error: Can't find substitution for ""." at design time after migrating a project. |
Release 6.7.0
| Key | Description |
|---|---|
| AMBW-41319 | After migration, the
$error_<activityname> was not migrated and failed to fetch error details from the
Local Transaction group.
|
| AMBW-41022 | After migration, the subprocess containing the
padfront() function failed at runtime.
|
| AMBW-40178 | After migration, multiple errors occurred for DTD to XSD conversion. |
| AMBW-40068 | After migration, the SOAP Request Reply activity could not migrate successfully. |
| AMBW-40067 | After migration, transitions to Invoke activities were not present in a process. |
| AMBW-38737 | After migration, the
faultDetails mapping was incorrect.
|
| AMBW-37700 | After migration from the SAP adapter configurations to TIBCO ActiveMatrix BusinessWorks™ Plug-in for SAP, the mappings were not migrated. |
| AMBW-37114 | After migration, the pipe character ('|") was converted to the "or" condition which resulted in incorrect activity output. |
| AMBW-31022 | The transition condition now has the migration support of adding the XPath 1.0 tag. |