Do you have an old Domino app that just doesn’t look good or is clunky and old? Or one that you’re embarrassed to show new employees because it looks like it was built in the mid-1990s (and maybe it was)? With the newest version of Domino, it’s easy to modernize — and means you don’t have to contemplate migrating away from the platform, which can take years, have ballooning costs, and often doesn’t add new, better functionality or business value.

We are hearing from customers that they are able to easily modernize old apps and bring their original investments into the future. The HCL Lab Services team recently modernized an old, internal issue-tracking app to show you what a modernized Domino app experience could be. It’s easy to give an app not only a better look and feel — a face lift — but also to make it easily work on mobile devices.

This app has most of the features you’d typically find in an enterprise Domino app — workflow, access control, and security functionality. Accessed by thousands of employees every day to track business-critical businesses and approval systems, the app was designed to assist HCL in tracking issues found in various build systems, as well as assign and route those issues to key subject-matter experts.  But it wasn’t exactly pretty.

Even though this was built in 2006 (14 years ago!) on Domino v7, it was a rock-solid app. Even though it was totally stable and reliable, it was ugly and awkward and, because it was used by so many people, it desperately needed to be modernized to today’s app standards.

The Development process was as follows:

    1. We started designing what we wanted the app to look like and created a UI prototype using Adobe XD.
    2. To build the new app, we used Domino v10 and installed the following tools:
      • Node.js
      • Bootstrap 3.x
      • Domino App Dev Pack 1.0.2
      • WebStorm
      • jQuery 3.4.x
      • jQuery Datatables plug-in
    1. We used WebStorm for our web development and created standard CRUD (create, read, update, delete) components for the new web UI.
    2. We integrated security functionality with the new Node app and integrated with Azure AD so users are able to login with their Office 365 login without managing multiple logins.
    3. Once everything was built, we performed acceptance testing to ensure that everything works and is ready to be live.

We had a  web designer and developer on this project. Step 1 was accomplished by our designer in 3 days and it took our developer 3 weeks to build the app. See these stunning after shots:

We brought this app mobile and it works on an iPad!

In less than a month, we were able to transform a complex, business-critical app by modernizing it in just a few days. We want to help you accelerate your app-modernization with Domino and preserve your historical app investment. You can unlock the great value from the Domino platform simply by modernizing. Contact us today!

 

Comment wrap
Further Reading
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...
Digital Solutions | October 14, 2020
New October Release: Domino Early Access Program
Last month, we introduced the HCL Domino V12 Early Access Program, where we provided customers the chance to test new product features early in the development cycle. Today, our engaged development team has provided a new code drop named "October 2020", now available for download on Flexnet to all current customers.  We are looking for YOUR feedback on the features provided below, please:  Start testing the Early Access Code - details on how to get started can be found here  Vote for the ideas referenced or leave a comment Join the discussion and provide feedback in our forum here. What’s Provided in this Release     Time-based one-time password (TOTP) authentication   When users log on to a Domino Web server, you can now require that they provide time-based one-time passwords in addition to their user names and passwords. These one-time passwords are generated by authenticator apps like Authy, Google Authenticator or similar.   DAOS Version 2   DAOS Version 2 (DAOSV2) is a new version of DAOS that provides a more reliable way of tracking DAOS objects on a server.    Certificate management improvements   A number of enhancements and improvements related to certificate management are provided:   Disable TLS 1.0 by default now   Support for PEM-file format, in additon to *.kyr file format  (Note: This feature is intended as a test bed for future work supporting PEM-formatted keys and certificates)   Support for using CertMgr to import third-party CA keys and certificates - based on this idea (Thanks Martin!)  Support for replacing keys generated by the Let's Encrypt CA    Domino directory enhancements   There are a number of improvements around the Domino directory design (pubnames.ntf) to improve usability for administrators. Some of which were long standing requests. If you like what you see, please vote for the idea(s)s referenced below:  Mail-In Databases and Resources view - based on your input from this idea (Thanks Michael!)The Mail-In Databases and Resources view now displays the internet addresses of mail-in databases that have them and also includes a Go to...
a/icon/common/search Created with Sketch.