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.

Comment wrap
Further Reading
Digital Solutions | November 16, 2020
Updates Regarding HCL Notes v11 on Apple Big Sur
Apple officially released macOS Big Sur, its latest operating system, on Nov 12. We are aware that customers were unable to run the HCL Notes v11/11.0.1 client on a Mac after upgrading. Various fixes have been applied to allow HCL Notes to run on Big Sur. You can read our tech note here. This has all been resolved. The fix pack is available on Flexnet.
Digital Solutions | November 5, 2020
Remotely Debugging Java Applications with Domino 11
For Domino customers on v9 or 10, you might be familiar with debugging a Java agent remotely on IBM JVM using the following server ini’s and set Port 8000 in Debug Configuration from the Designer client: JavaEnableDebug=1 JavaDebugOptions=transport=dt_socket,server=y,suspend=n,address=8000  This will work up to Domino v10 but not on Domino v11. In fact, doing so will cause it to crash! This article is going to help developers looking for a way to debug Java agents remotely on Domino v11. The pre-requisites are:  Domino v11 or above on Windows Server 2016 / 2019. HCL Domino Console. Notes, Designer and Administrator Client v11 or above. Java agent to be debugged. Any Web Browser to run Java agent.  Domino v11 uses OpenJDK. With the above ini's enabled, both the JVMs would attempt to bind to same port (8000) and the second process that attempts to bind to this port would fail and crash. To overcome this problem, the idea is to remove the Port 8000 from the Debug and attach it to some other random Port.  First, you will need to add the below ini’s to the server’s notes.ini.   JavaEnableDebug=1  JavaDebugOptions=transport=dt_socket,server=y,suspend=n  Note that we are not binding the Debug to Port 8000 by omitting address=8000, as compared to ini which was set on earlier version of Domino.  The JVM will then pick a random port. To know the random Port number, simply quit and load http or run your Java agent from web browser and check the console from HCL Domino Console Program. You will need to restart http task after adding those ini’s to make it work.  Note down this Port number somewhere as you would need it in next step. (The server console in the Administrator Client doesn’t show the Port number information.) With your Port number, you are going to bind to the Debug from the Designer client. Go to Tools menu > Debug Server-side Javascript > Manage Debug Configuration You should land on the Debug Configuration window. Here you need to mention the Port number which you noted down from the HCL Domino Console...
Sending future mails from your HCL Notes Client
Have you ever wanted to schedule future emails from your Notes Client? Well, now HCL Domino supports scheduling email messages, which allows you to do just that. So, draft your email, assign it a send date, and sit back and relax. The email will be delivered by the router at the time you specify. This feature is very useful for scheduling announcements, newsletters, or any mail which you want to be delivered at a future specified time. You need to be on Domino v10 or v11 (using the Mail10.ntf or Mail11.ntf template) to be able to schedule messages to be sent in the future. Here’s how it works. The configuration document setting “Allow users to schedule a delivery time for messages” is enabled by default, so you don’t have to change anything in that document. You would make sure that the mail policy setting has the checkbox selected to enable the delivery option, as illustrated here. If you don’t have a mail policy, then you can create a new one. If you already have a mail policy, you merely update it. After creating or updating the mail setting, you need to give the following command to update the mail policy in the user’s mail file. Tell adminp process mail policy The next step is to restart the Notes Client, so that it will pull the new policy settings from the server. Advanced users can use this command from the command prompt of their client machine to update the policy on the client's side without restarting: C:\notes\ndyncfg -2 Once the settings are pulled by the Notes Client, you will see the following option in delivery options while sending mail: “Delivery Options at the user side.” Simply select the date and time for delivery and the router will deliver it at that...
a/icon/common/search Created with Sketch.