Description:
This hotfix doesn't need any TRA hotfix. The patch can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/ActiveEnterprise/BusinessWorks/BW/5.4.0/hotfix-03/  to download the appropriate hotfix for your OS/platform.

1-6ME83D
The SOAP Request Reply activity lost the default prefix of the
first child of soap:Body because of problems in xsi:type resolutions.
This has been fixed.

1-6TBKTB
When an encryption policy was applied to the entire body of a SOAP
fault message, the SOAP Send Fault activity failed to process the message. This has been fixed.

1-79B2E5
When two Adapter Request Response servers subscibed to the same
subject, the first server deleted the message as soon as the message
was received whereas the second server got a Null Pointer Exception
when referring to the same message. This has been fixed.

1-7ZCWEB
The HTTP Receiver activity did not parse the post data content
according to the Content-Type of the HTTP request header. This has
been fixed.

1-83EUIB
If a custom activity's process name was same as the process
definition’s name where you included the custom activity, the input
and output for the custom activity did not appear correctly.
After making the names unique, the process and the design form were
unusable when the project was reopened. This has been fixed.

1-83OL8E
During migration of TIBCO BusinessWorks project from version 5.2 to
version 5.4, the HTTP Receiver activity received partial data
through HTTP POST. This has been fixed.  

1-851ZGF
For RPC/literal/type SOAP messaging, the namespace information for parent element was not passed to the child element. This has been fixed.

1-85QMC4
The "Mapping wizard" was creating empty tags for each optional element
even if the optional elements did not appear in the input data. To
avoid the empty tags in the output when the input did not contain the
optional element, the user had to manually create "xsl:if" statement.

A new system property "automatic_mapper_if_surround" is added to fix
this problem. Set this property to 'True' to surround all new
optional-to-optional mappings (including child elements) by an
xsl:if statement. If the system property is false or not present,
child elements will not be surrounded with the xsl:if statement.