Today was the first official day of the conference Engage 2020. This time Theo Heselmans chose the Arnhem and the place of the Royal Burgers’ Zoo. Again he chose a completely unique place, but honestly … as always. He deserves a big thank you for that. Also because he manages to attract more participants every year. This year it is almost 430 people.
The program was so busy that I had seen only some giraffes and zebras in the distance the first day. I’m sorry, I’m not here for them.
The opening keynote was conducted by Richard Jefts, which was gradually supplemented by his colleagues. Very interesting is the preparation of SoFy – Solution factory HCL software. accelerates the software rollout and deployment process. Available this summer.
Then a whirlwind of sessions started, accompanied by good refreshments in short breaks. My focus (as Admin) was on Domino / Notes, Verse, Nomad.
In Notes 11.0.1, which is, by the way, only a few days available in the beta tower, we can expect:
Set workspace background with policy
HCL Wash for Swift file
Future workspace concept (new app icons design)
New icon for Notes client
Notes V12 plans
Pick a different from when composing an email
Improve search UI
Install dictionaries with language kits
Improved performance on slow networks
TLS 1.3 support
Verse On Premises
Enable the new Calendar Event Form user interface as the default event form
Create/view meetings that are more than 24 hours long
Search using a Date Range
Add options to “Send and File”
Add admin option to require more than 2 clicks to open a link or attachment
Connections 6.5 support
Verse Web Mobile : Pull message list down to refresh the message list
Stretch Goals: Allow users to manage their Mail Rules
Verse On-Premises (VOP) is already in version 1.0.9.A. Most users are still used to accessing mail from a web browser using iNotes. Do you want to set VOP as default or give users a option between iNotes and VOP?
Upgrade your design or create a new iwaredir from the template included in the VOP 1.0.9 or 1.0.9.A package.
Notice: This version (1.0.9) of the redirector template includes only translations for English, Chinese(China), Chinese(Taiwan), French, German, Italian, Japanese, Korean, Portuguese(Brazil), and Spanish.
You also need to set the “Domino Web Server Configuration” application (domcfg.nsf). For the internet site or virtual server set login form “DWALoginForm”
Verse On-Premises as default
If you want the VOP to be the default for webmail, you can simply set “/ verse” in the “HomeURL” field of the document server or internet site. Of course, provided you use iwaredir for redirection.
The login form will open and after logging in you will open directly to the VOP. This is the setting for all users.
Verse on-Premises or iNotesas option
If you want the user to choose between iNotes and Verse, you can configure iwaredir.nsf. Open this redirector database iwaredir.nsf and on UI Setup page, select the following options which enable users to log on to Verse:
Enable Personal Options? No
Enable Login Options? Yes
Enable HCL Verse? Yes
Then set set “ /iwaredir.nsf?open” in the “HomeURL” field of the document server or internet site. After restarting the HTTP task the login form will open with the option “Verse / iNotes”
Notice: I encountered the problem that upgrading the design from the template and setting all the options did not open the options page. Just create a new iwaredir.nsf from the template.
Verse On-Premises 1.0.9 offers a new calendar event form design. This provides an improved environment for creating and managing calendar events.
The new form opens quickly and is smaller and streamlined. Controls allow users to show just the options that they want to use. This is a preview feature that is off by default. To make this feature available to users, you must add new parameters to the notes.ini Domino server.
While testing this new “feature”, I found the issue that HCL Development will fix in future releases.More on point 2.
There are two options – two parameters:
To enable the new event form for all users and prevent them from disabling it, add : VOP_GK_FEATURE_168=1
To keep the new event form off by default but allow users to enable it, add: VOP_PREVIEW_REACT_EVENT_FORM=1 Then, to enable the feature, users select the option New Calendar Event Form in Feature Preview section of Mail and Calendar Settings
If you use this setting (point 2) and the user selects a new form, the form will then appear completely blank when in use.HCL Development is implementing a fix for this issue. The fix will be included in a future release of VOP. For now you to use the workaround which has been described in point 1.
Starting with Domino V11, you can configure Domino to use an ID vault password to authenticate web users accessing the server.
If enabled uses the Domino server to authenticate users to HCL Verse, HCL iNotes with their Notes ID and passwords stored in IDVault. With this feature, users only can to remember their password in the file ID.
This feature is ignored for authentication of the following users:
Notes client users
Web-only users without Notes IDs
Users who authenticate via SAML federated identity authentication
How to configure?
Create or edit a Configuration document in the Domino directory. (Configuration – Servers – Configurations)
Open the Security tab
In the Internet Password Verification section, select one of the following options
If some web users with registered Notes IDs do not have IDs in the vault or if you are unsure if they do, use “Check vault first, then directory“. If Notes IDs are not found in the vault, Domino will use internet passwords in Domino directory Person documents to authenticate the users.
VOP 1.0.9 is available for download only a few days before the release of Domino, Notes and Sametime V11. Do you have to wait for Domino V11 or can you implement the changes already? Complete documentation LINK
There is System Requirements
Domino 9.0.1 with Feature Pack 10 or higher on Microsoft Windows (64-bit 2008, 2012) or Red Hat Linux (64-bit 6).
Domino 10.0 or higher on Microsoft Windows (64-bit 2012, 2016), Red Hat Linux (64-bit 7), or AIX (64-bit 7.2, TL1 or higher)
Domino 10.0.1 or higher on IBM i version V7R2 or V7R3.
Domino 11.0 on Microsoft Windows (64-bit 2012, 2016, 2019), Red Hat Linux (64-bit 7), or AIX (64-bit 7.2, TL1 or higher)
Mail files require a design derived from the mail9FP9.ntf template or a later version.
Can a user find out which version of Verse On-Premises is used to access their mail database in a browser? Yes, but it’s not quite user friendly. Someone would look for it somewhere in “About”, but you need to click a little more.
I have therefore created a new post in the Product Ideas Forum for which you can also vote LINK
I found it in the HCL knowledge database:
To determine which version of the Verse On-Premises is being used, you can examine the “build-number” in Verse. The “build-number” tag is an identifier that is unique to each Verse On-Premises version.
To view the “build-number” number you should:
Open Verse in your browser and right click on mouse to select the option: “Inspect”
Go to the “Console” tab and find the line that includes the word “Current Build”.
Use the table below to determine which Verse On-Premise version is currently in use.
Verse On-premises version
16838-458 *Note this is the same as 1.0.5 as the client code has not been updated*
You may not see the option to open an archive database after upgrading to Verse On-Premises 1.0.8.
If you have a “simple” solution where you have a manually created archive DB of your mail (without applying the policy), you probably won’t see this new option to open it to the VOP as described here LINK.
I solved this issue with HCL support and this is a bug on which request VERSE-57616 was created.
There will be a VOP 1.0.8a deliverable in the coming weeks that will include the fix for this issue.
The bug is due to the fact that the code was expecting there to be an Archive Settings policy document assigned to the user. If there was no archive Setting policy document assigned to the user, VOP would not show any archives. You can work around this issue by assigning an Archive Settings policy document to the user.