We recently hosted a presentation about the latest version of our turbocharged low-code application development platform, HCL Volt MX 9.2. It was well attended, and there was a lot of excitement around the latest features and capabilities. There were some great questions asked, which we’ve recapped here — along with all the answers. You can always watch the replay here and all Volt MX resources are always available in our community here.
For customers who want detailed insight on planning your upgrade, please join our webinar on September 23, 10 AM ET. >> Register for the Upgrade webinar here.
Before we recap the Q&A, make sure you check out this lively and informative overview video about this game-changing product!
New to Volt MX
What are the skill sets needed/advised to leverage Volt MX within very small teams?
What are the primary architecture considerations before deploying Volt MX?
HCL offers Volt MX as a managed service on AWS, or within your own cloud, or on-premises with containers.
Will there a training available to onboarding new developers?
Yes, we have a Developer Community and three types of training resources available:
- HCL Software Academy for training courses
- Documentation and tutorials
- Embedded training within Volt Iris. Get fully guided tutorials on how to build your first mobile or web app by clicking on the “Hikes” icon on the left navigation toolbar in Volt Iris
How can we learn more about Volt MX or be able to meet the community?
Yes, you will see a ramp-up of events for the Volt MX. Please stay tuned. In the meantime, check out our developer resources and subscribe to our newsletter to get the latest information on new content, webinars, and events.
Volt MX Customers
When will be all Temenos cloud accounts be transferred to the Volt MX cloud?
Our Volt MX CSM team will work with their respective clients on their plan to upgrade to Volt MX and the Volt MX Cloud.
Can Temenos v9 customers be upgraded to HCL Volt MX v9.2?
Yes, please contact your CSM account manager for help. Please note that we are asking customers to refrain from upgrading to Quantum v9 SP3 and remain on SP2 to ensure that your projects will be compatible when migrating to Volt MX v9.2. Sign up for our upgrade webinar here.
Where can I find a list of identified bugs and status on when it’ll be fixed?
Please see Defect Articles (DA) here. A DA is a type of knowledge article that capture and track reported defects. HCL Support regularly updates the status of these articles. Customers can use the unique DA number to track defects or subscribe to individual DAs to get notifications whenever the DA is updated.
Volt MX Features
How do animations interact with existing elements in a form?
Volt MX supports animations for a lot of widgets in the form using animation API. Refer to doc here. Here the animated widget is a regular widget. Lottie animations are displayed using a component that you can import to project from marketplace which internally uses a NativeContainer widget and uses some NFI functions. The component exposes some events to which you can configure logic to perform when event occurs.
When will HCL Volt MX App Preview arrive in Google Playstore?
The Volt MX Preview App will be available in the app stores the week of September 27.
Google launched the Android App Bundle in May 2018. Will that affect Volt MX?
Volt MX currently supports Android App Bundles, please refer to our documentation here.
Will Foundry still be available as a public docker container for on-prem hosting of it?
Foundry docker container (single node) is available for customers to download and use from HCL License and Download portal for development purposes. We will be making new Volt MX containers available for GCP, AWS and Azure in JFM 2022 as a preview. Also, we will be adding support for Volt MX in HCL SoFy in early 2022.
Are headless event driven connected workflows possible just within Foundry without a need for an app?
Yes, that’s correct. A client app is not required for workflows to be executed. The corresponding services and events used by the workflows must be defined in Foundry apps and published to the Foundry server, post that invoking the API directly via REST APIs or Foundry server-side events will move the workflow through the stages as it would, if the same were triggered from a client app. You can even have an external application raise the event invoke the workflow service in Foundry by producing or listening to events in external event distribution platforms like Kafka.
I would like to see renewed services predefined in Volt MX. For example, the ability to easily connect to M365 offerings, Zoom, Dropbox, etc.
In addition to the pre-built integration adapters in Volt MX which already support M365 using LDAP and Oauth connectors, we have lot of pluggable adapters in marketplace. In fact, we are refreshing the components and adapters available on the Marketplace.
Will Domino be the future backend repository service of Volt MX?
The strength of Volt MX is connecting to any enterprise application, process and data source. Domino is one of our many data sources we support. See the Volt MX toolkit here and learn more from this blog. We plan to strengthen that integration using Project Keep when its available in Domino as Domino REST APIs.
Disclaimer: HCL’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice and at HCL’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard HCL benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.