We’re proud to announce the HCL Domino Early Access Program, a new program that gives our customers and business partners a chance to test new product features early in the development cycle. This program provides a preview of features and functionality that may be shipped with a future version of HCL Domino and gives us the ability to incorporate your valuable feedback. At this stage, we are providing early access to features that contribute to HCL Domino v12.  The Early Access Program aims to get feedback on specific features, with a more formal traditional beta program planned at a later stage to receive feedback on the overall release quality and language packaging.  The Early Access Program is feature-driven and iterative, meaning new iterations and code drops will be made available as soon as it is declared ready for testing by our development team. New code drops can be provided in just a few weeks after the previous one, on short notice, without sticking to a fixed release cycle.   Based on your feedback we may proceed, improve or adjust the feature, or in some cases withdraw the feature from the code stream. The following graphic illustrates this concept: Each code drop is provided in the form of a Docker image which enables us to ship new iterations faster and to minimize the time to upgrade from one code drop to the next. You can expect us to deliver code drops at a fast pace as we want participants to have exclusive access to our latest product feature set. Please note that only the newest code drop will be available for you to download. How to Participate HCL Ambassadors who have registered Domino v11.0.1 Beta Preview will automatically be added to Domino Early Access Program. Customers and partners with a current Notes/Domino entitlement will also have access to the Early Access Program as of today. There is no need to register separately to participate. For overall...

Last week, our team of global support advisors hosted a webinar on best practices for upgrading to Domino v11. If you missed the webinar, feel free to watch the replay here. In this session, we covered several topics on how to prepare for a successful upgrade including: Baseline monitoring: Know your current workloads   Evaluating your environment: Should you upgrade in-place, or do you need new hardware? Deployment sequence: See the order of steps to upgrade your environment  Preparing your environment: What to do before your upgrade  Application upgrades: Learn how to handle your custom apps    We received a lot of questions during the webinar and you can find the Q&A recap below.    Want to learn more about what’s new in Domino v11 before planning your upgrade? Download this deep dive to see newest features. For our technical folks, check out this support article which provides a guide on how to plan your upgrade and a step-by-step guide for Domino install, setup, and upgrade tasks.   Q: Regarding Notes.ini, are there any tools we can use to check the values used in our Notes.ini to identify redundant ones?    A: DCT would be a good place to start, however there is no such tool available for the same. DCT will not detect duplicates. It is a best practice to start with a new notes.ini file.  Q: Can we get a list of Notes.ini obsolete parameters?  A: We are working on a consolidated article and will be publishing it soon.  Q: Is there a URL for recommend new Notes.ini settings to help weed out old Notes.ini settings?  A: Starting with a new Notes.ini file is the best way to ensure your file does not contain outdated settings.   Q: Can we have a mix of both Domino 9 for applications and Domino 11 for email servers?  A: Yes, you can upgrade your mail servers to version 11 now, and the application servers can remain at Domino 9.0.1. As mentioned, make sure that you are not mixing Domino versions in a cluster. Use a test pilot to see how well your Domino 9.0.1 applications work in the Notes 11 client.  Q: Is...

Low code is a software development platform that gives non-coders and coders alike the chance to develop applications through visual interfaces instead of traditional hand-coded programming.   In plain English, it’s the power to create processes without the technical experience or hand coding background application development once needed.  (It’s like suddenly being able to sing, dance, and generally dominate like Beyoncé without having to undergo 25+ years of endless practice and constant performing.)    Comparing application development to pop stardom may not be the most common way to highlight the potential benefits of low code. But by not requiring a background in coding expertise, low code allows a wider audience to create applications, making for a faster and potentially more innovative environment that companies can benefit from. (It’s like turning lemonade into even better lemonade. Ok that’s the final reference to Queen B, promise). But we’re just getting started diving into the upside of low code. Develop Business Software at Incredible Speeds Low code development should be fast.    Unlike the laborious line-by-line hand coding process that is traditionally associated with software programming, low code can go from concept to reality in a flash.  Low code allows developers to execute apps up to 60-70% faster than handwritten code, bypassing the time-consuming steps of repeatedly writing, testing and debugging code until it works correctly.  Low-code development can give designers drag-and-drop features through a visual user interface, making it easy to build intuitively while cutting down on complicated obstacles that only expert coders can spot and fix.  By making the process more visual and less repetitive, low code brings a newfound velocity to a typically slow undertaking.   Increase Enterprise Productivity  When you increase the speed of app building, and you save designers and developers time, you open new space up for productivity throughout the entire enterprise. But it’s not only the efficiencies that companies benefit from.  Those closest to a problem can fix it without a drawn-out drama that drains weeks of time and energy from the IT department. Solving...