New Features
- MyST Studio now supports Oracle BI Publisher 12.2.1
- MyST Studio now supports managing Custom Actions (WLST and Jython Interpreters)
Improvements
- Release Pipeline, Continuous Delivery Profile and Artifact usability improvements and fixes
- You can now redeploy all artifacts against a Platform Instance. That’s useful in cases where you re-provision your platform.
- You can now define in your Release Pipeline if platform updates should be skipped. This is useful if you want to use MyST for deployments only
- Usability improvement: Properties under platform blueprint related to patching, which are not commonly used, are now shown only in the advanced view.
- You can now define which order the Application Blueprints within a Stream will be deployed
- AWS On-Demand provisioning now supports Mumbai, Ohio and Seoul Regions
- MYST Studio installer provides clearer instructions on the post-install actions
- SOA Extensions deployment are now supported for SOA 12.2.1
- The MyST License details are now visible in MyST Studio
- When configuring the MyST Studio Jenkins plugin, you can now save the settings even if MyST Studio is unreachable
- MyST Studio Jenkins plugin now also supports building artifacts from a Jenkins slave
- The MyST Jenkins plugin now resolves the Maven properties before reporting them to MyST Studio. You can now have property references such as ${project.artifactId}
- Improvements on Weblogic Workmanager support
Bug Fixes
- Fixed: Updating wsm-pm target used to cause a NullPointerException
- Fixed: The NGINX routing rules was not redirecting HTTPS traffic for specific URL patterns
- Fixed: In some circumstances MyST execution was hanging when the target nodes had Kerberos enabled
.png)
