Domino die-hards – this blog is for you! As you know, Domino Volt is our new low-code capability that makes it easy for anyone to develop powerful and secure apps. It’s built on Domino which means you get scalability, reliability, and security built into the platform.
We’ve seen continued interested from our Domino customers about how Domino powers the Domino Volt platform. For our dedicated technical folks, I’ve put together this video to give you a peak of what’s “under the hood.” Check out a summary of the topics I cover in this video and I’ve included timestamps if you would like to fast forward to a specific topic.
0:10: What is the architecture of Domino Volt?
Domino Volt runs on a Domino server. Domino Volt adds a browser-based design environment to Domino that lets you build apps in a visual manner. Domino Volt runs on Domino’s Java runtime and uses Domino’s database, security, directory, and messaging.
3:55: Where are Domino Volt apps stored?
All app designs are initially stored and managed in VoltBuilder.nsf as you edit your apps. Deployed apps will have their own NSF which contains all the generated design elements and all document data for the app.
4:40: How does Domino Volt work with Domino’s security model?
Domino Volt has built in roles and access, as well as the option to create your own. They are automatically mapped in Domino. We use Domino Access Control as the first layer of access to the application. There is also document level security using Domino authors and readers field.
5:40: How can we use Domino data in our Domino Volt apps?
Your Domino Volt apps are Domino data! In GA, the best way to look up information in another Domino database is through Domino Access Services (DAS). Note that the DAS approach is best used for databases on a different server to avoid thread contention. We’re also currently working on building tighter integration and access to your Domino Data in the upcoming release.
6:53: What can I do with my Domino Volt apps on Domino Designer?
Domino Volt builds a true NSF with forms, subforms, views, and other design elements. The generated subform are always completely regenerated, so any changes made there would be lost on an application redeploy. Form and view changes should be safe to make, within reason (e.g: don’t delete Volt columns or subforms, etc.). However, it would be a much better practice to add a new view or other design elements than to modify Domino Volt generated ones.
13:08: Watch a demo of how to run an agent on the database.
A Domino Designer user can add power to a Domino Volt application by adding an agent to their Domino Volt app. In the demo example, I show an agent added to the demo database that executes when a document is modified or created in the Domino Volt application. In this example, I submit a training request for Captain to take a leadership course – something he wasn’t too happy about as you can hear in the video, above. This is Captain:
The agent extracts some data from the document being added or modified and creates a new document in another database. The possibilities are endless!
Domino is the heart of Domino Volt and for our technical users, there’s plenty of ways you can use Domino Volt to add value to your applications. Have more questions about how Domino power the Domino Volt? Leave a question in the comments below! Have you used Designer with your Domino Volt apps? Tell us about it. Finally, if you haven’t seen Domino Volt in action, schedule a demo today!
What also might interest you is a webinar about how Domino Volt is primed for handling challenges for organizations adjusting to the “new normal” or working within a pandemic.
The post Domino Powers Domino Volt: Why This Matters appeared first on HCL SW Blogs.