Learn about the limitations and upgrade considerations for BMC Helix Platform.
To stay informed of changes to this list, click theicon on the top of this page.
Post upgrade behavior
The following table describes certain behavior that takes place after upgrading to BMC Helix Platform version 19.08:
The DeploymentStatus response is now restructured by adding the DeploymentParsedStatus field and removing the errorMessage field. With changes to the Deployment.java file, which is included in the RX-SDK, the deploymentStatus.getErrorMessage() method will not work with the new SDK. You must update the SDK to successfully deploy the bundles.
The following table lists features that are no longer supported in BMC Helix Platform.
|19.08||BMC will no longer support creating export packages. Instead, you can use content packages.|
When an administrator upgrades to a new version of an application, the option to opt in or opt out in the test and tailoring environments is no longer available. Instead, the upgrade process automatically opts in for all the environments.
The LoginCommand and LogoutCommand APIs are removed from the BMC Helix Platform software development kit (com.bmc.arsys.rx.sdk-19.5.0.zip).
If you are using the LoginCommand and LogoutCommand APIs in your applications or libraries, ensure that you update all the instances of these APIs with the LoginRequest and LogoutRequest APIs. For more details on the REST APIs, see Platform REST API documentation.