Eine deutsche Version dieses Artikels findet ihr hier.

 

In the spring of 2021, HCL announced its in-house "Domino Online Meeting Integration" (DOMI for short) and published it with the Domino version 12 release in June 2021. DOMI enables you to create online meetings from the Notes calendar and is already included in the license for the Notes version 12 client at no additional cost. If you have a client of version 11, you can manually install the extension from version 11.0.1 FP3. You can find the corresponding GitHub link here.

We took a closer look at DOMI. On the one hand, because as an HCL business partner we always want to be up to date in order to be able to support and advise you in the best possible way. On the other hand, of course, to find out whether we would like to equip our ITWU Teams integration for the Notes calendar, called "Teams@Notes", with additional functions in the future and keep going on further development. Spoiler alert: we chose to keep going on the Teams@Notes-Development because we think each solution has its merits and raison d'être.

We have been working continuously on extensions to Teams@Notes since spring 2020 and have gained a lot of experience with the underlying technology and Microsoft interfaces during this time. Accordingly, we immediately saw that the technology behind DOMI is basically the same as that of Teams@Notes. But that also means that we understand DOMI very well and would be happy to support you in setting up and extending this solution. After all, DOMI is primarily a standard solution that in its actual form offers few customization options. However, if you have in-depth Docker knowledge and are familiar with the Domino Designer, HCL offers you the opportunity to install and customize DOMI completely locally on your servers. In such an environment, the integration of additional functions, such as those we regularly integrate into Teams@Notes, would be feasible. With Teams@Notes, these extensions are available as additional functions to the basic solution or as add-ons. We are currently working at full speed on an add-on for integrating the Microsoft Planner functions for creating and delegating to-dos within MS Teams, which are automatically transferred to the to-dos in the Notes client. With our extensive knowledge of the interfaces between HCL Notes and Microsoft Office 365, your individual requirements can be implemented in no time.

 

But what are the differences between Teams@Notes and DOMI?

We found nine major differences between the two solutions when testing DOMI:

Advantages DOMI

Advantages Teams@Notes

Price:

If you are licensed by HCL to use Notes version 12 or at least Notes 11.0.1 FP3, you get DOMI for free.

Teams@Notes, on the other hand, requires an additional license. We will integrate the solution into the mail template you want, so the integration effort is included in our price.

 

Online meeting platforms:

Besides MS Teams, DOMI is also an online meeting integration for Webex, Zoom, GoToMeeting and HCL Sametime.

Teams@Notes, on the other hand, has so far been limited to MS Teams.

 

App registration:

As an interface for Notes Domino, you need a registered app for both DOMI and Teams@Notes on the Microsoft side, which for DOMI is already registered and managed by HCL.

With Teams@Notes you register the app yourself in Microsoft Azure, which is only a few simple clicks ;)

 

Entry in 3rd party calendars:

With DOMI you can also create entries in the associated calendars for some supported solutions. This works e.g. with Zoom, but unfortunately not yet for the MS Teams calendar.

Teams@Notes also does not create any entries in the MS Teams calendar, as it is intended for companies whose employees only use their Notes calendar as a single point of truth to prevent data redundancy. So-called instant meetings are used here, which do not appear in the Teams calendar by default.

 

Upgrades

With Teams@Notes, an upgrade of the mail template version or of Teams@Notes itself always requires a mail template adjustment on our side. This is done quickly and you can simply roll out the adjusted template to your employees after a short time.

To upgrade DOMI, you only need to update the Notes client and template to the desired version.

 

Integrated into the HCL Verse calendar

DOMI is now finally integrated into the HCL Verse calendar (version 3.2.1), which means it can now also be used via the web browser.

In contrast to HCL as a product manufacturer, with Teams@Notes we cannot programmatically access the Verse user interface in order to change it. So Teams@Notes is not supported here.

Setup and support:

Teams@Notes is set up centrally in one place for all users. When creating the first meeting in the Notes calendar, users only need to log in with their Teams account and can use the solution directly. With DOMI, every user has to go to the settings once and, after logging in to Teams, copy a so-called authentication token from an HCL page into the settings. This can be quite time-consuming with a larger number of users if the users have to be supervised individually during the setup.

We are involved in setting our solution up right from the start, take care of the integration into your mail template and help immediately if errors or problems occur in your environment. Thanks to our extensive experience, which we have been able to collect since the release of our solution, we know about the sticking points that you can stumble upon when setting up (e.g. which problems and settings need to be considered when using a web proxy or the necessary settings in Active Directory).

 

Authentication:

With Teams@Notes, the authentication token for logging into Teams is requested directly from Microsoft by the Notes client - it therefore remains local on your systems.

With DOMI, by default, the token is forwarded to an HCL page where the user has to copy and paste the token into their Notes client. Here we see a small but still existing security risk. It is similar with the return address for multi-factor authentication at DOMI.

Alternatively, DOMI can also be made on-premises-capable, but this requires the appropriate expertise. We would be happy to assist you here as well.

 

Meeting options:

With Teams@Notes, in contrast to DOMI, the Teams meeting options for the respective meeting can already be defined when planning a meeting. In this way, you can determine in advance who is allowed to present, for example, who has to wait in the lobby, whether the meeting should be automatically recorded, or whether all participants should start the meeting muted. Once meeting options have been set, they can be set as the default for all future Teams meetings created with Teams@Notes.

 

Multilingualism:

Currently, DOMI is only available in English. Since we can customize Teams@Notes individually to the needs of the users, we can of course also offer it in different languages. So far we have been able to create a German, English and French version for our customers.

 

Fig. 1: This is how you create an online meeting with DOMI

 

Fig. 2: This is how you create a Teams meeting with Teams@Notes

We hope that - with the help of this comparison - you were able to become aware of the advantages of both solutions and that you can now better decide which solution suits you and your company. As already mentioned, we not only answer your questions about Teams@Notes, but would be also happy to help you set up and extend DOMI. Do you have any questions or suggestions? Call us on +49 5251-288160 or send us an email to info@itwu.de.

 

Neues vom ITWU-Blog

Mit ITWU Simple Signature automatisch generierte HTML-Mailsignaturen für HCL Verse und Notes erstellen - Weiterlesen
ITWU-Projektvorstellung: Digitale Werkszeugnisse automatisch erzeugen, standardisiert und transparent - so geht smarte Qualitätssicherung! - Weiterlesen
DOMI im Verse-Kalender 3.2.1 und unsere Roadmap in Sachen Teams@Notes und MS O365-Integrationen - Weiterlesen
ITWU-Projektvorstellung: Ohne Papierkram auf Montage – ITWU zeigt euch das perfekte Tool für euren Montagearbeitsbericht, digital und doch offline-fähig!  - Weiterlesen
Der Grid-Konfigurator – Teil 2 – Wie ihr in ISIE eine Datenbank hinterlegt und eine neue Grid-Konfiguration erstellt - Weiterlesen
LotusScript-Fehler beim Hochladen aus HCL Notes ins Office 365 - Weiterlesen
Verbesserung der Benutzererfahrung auf dem Smartphone mit Nomad - Weiterlesen
 zum Archiv