Foundry V9 SP5 (Curie) Release
Maintenance window: Monday, December 5, 2022 00:01 to 04:00Impacted Cloud services:
Foundry Integration Server
New Volt MX Microservices connector for simplified Developer experience
Enhanced functionality for Microapps
Support for authentication into Foundry Console using AD SAML
Improved Service Monitoring
Advanced Workflow capabilities with Parallel paths
Added Looping support for workflows
Improved security for caching using Redis
Added support for WebSockets to the Volt MX Foundry Cloud
Added support to reconfigure the scheme for Swagger 2.0 services
Added the Foundry Workflow Adapter in Integration Services
Enhancements to Workflow Audit history
Middleware Integration with Volt MX Metering Service Client Library
Updates to Server Events APIs
Cloud Management Console
Developer Portal Members will now be able to see the list of other registered users
Enable additional Server Side Validations for Email Hyperlink Injection attacks
Added Content Security Policy in response header to protect against clickjacking attacks
Fixed Unable to load WSDL file error for SOAP Services
Enhanced extensibility for Integration and Object Services
Implemented calling stored procedures by ordinal position of parameters
Added support for Oracle CLOB and NCLOB data types
Fixed a timestamp parsing issue in stored procedures and functions
Composite app publish status refresh issues fixed
Publish time out increased from default 20 seconds to 60 seconds to allow bigger customer apps to be publishable
Supporting Modularity of Foundry Apps
Added OpenAPI Specification support for Object Verb Mapping
Added support for Custom Front-End URLs in Object Services
Added the Integration Service trigger type to Workflow services
Added support to view linked Java Pre and Post Processors for a Foundry App
Added a Version Upgrade mechanism to MFCLI
Updates to Engagement Adapter
For some customers, snapshot creation of extended services failed during Publish. This has been fixed
Fixed SAML provider configuration validation issue
Fixed issue where headers could not be added or saved for locked services
Fixed issue where custom operations could not be deleted for locked operations
Foundry Identity
Improved security against clickjacking attacks.
jQuery upgrade from 3.5.0 to 3.6.0
Improved support for OAuth connections using private key JWT
Added support to use PKCE in JavaScript SDK
Added support to replace Identity Service references
Fixed issue where Custom identity provider’s Claims token obtained in refresh flow was not working for Foundry integration services
Engagement
Improved support for Events notifications
Enhancements to Email API to send emails without audience member creation
Support the engagement application creation without the certificate configuration
Enhancements to the engagement adapter to support API key
Deprecated support for Blackberry
AppFactory
Cucumber Support for Foundry Testing in AppFactory
Foundry Build Process from AppFactory Command Line
IOS & Android Cross App Testing support
Target Test Data from environments
Support for Istanbul testing code coverage for Volt MX built apps using the Volt MX Testing Framework. Ensure every line of your code is tested, every time you test
Group failed tests together and re-run those test as part of AppFactory’s testing process with the Volt MX Testing Framework
Web based cross app testing backported to 9.2 to allow testers to instrument test scenarios that take the test case outside the Volt MX Testing Framework, like OAuth
Micro app test case support for combining base micro app test cases to a larger test case within a composite app
Command Line support for create new AppFactory projects and building Iris based apps within AppFactory from the command line
Apple API key support for signing iOS based apps
Regenerate Foundry object models for Iris based apps every time you build with AppFactory
Added support for Microservices
Added support for Cross Application Testing
Added OAuth support for testing deployed web apps
Impact Level : minor
Minor downtime is possible for the impacted Cloud services while this maintenance is being performed. The scheduled maintenance is designed to mitigate disruptions to service availability and performance for the impacted Cloud services. However, it is possible for the impacted Cloud services to be unavailable and/or performance degraded for a short period of time during the maintenance window. Note that no changes are being applied for other Cloud services outside of the list of impacted services above and no service availability or performance disruption is expected for other Cloud services.