|Latest 7 Posts
| MWLUG 2017 – We Believe!|
Thu, Sep 7th 2017 9
| Why we DO migrate code.|
Tue, Jun 27th 2017 6
| Migrate Notes to DOCOVA Blog Series Part 17: Input translation and input validation formulas|
Thu, May 25th 2017 7
| Migrate Notes to DOCOVA Blog Series Part 16: Form events|
Tue, May 23rd 2017 3
| Migrate Notes to DOCOVA Blog Series Part 15: Private on first use folders|
Thu, May 18th 2017 2
| Migrate Notes to DOCOVA Blog Series Part 14: Column sorting and categorizing|
Tue, May 16th 2017 4
| Migrate Notes to DOCOVA Blog Series Part 13: Shared columns and fields|
Thu, May 11th 2017 4
| Is 2017 The Year IBM Announces the End of Life of Notes?|
Tue, May 24th 2016 28
| ICAA – Did IBM Release a Free Version of the Notes Client?|
Sun, Oct 30th 2016 13
Mon, Nov 7th 2016 12
| MWLUG 2016 Recap|
Sat, Aug 20th 2016 10
| IBM Announces a Change is Coming to the Notes & Domino Life Cycle Policy|
Fri, Aug 12th 2016 9
| MWLUG 2017 – We Believe!|
Thu, Sep 7th 2017 9
| EngageUG – Ghent Belgium|
Tue, Apr 7th 2015 8
| DOCOVA University Updated|
Fri, Nov 7th 2014 8
| DOCOVA V4.1 Overview Webinar|
Fri, May 30th 2014 8
| DOCOVA V4.5 – Feature Quick Tour|
Sun, Sep 27th 2015 7
||DOCOVA 4.5 – Client Upgrade #1
Brotherhood Mutual has provided insurance solutions for America’s churches and related ministries for more than 90 years. They have been a DOCOVA Cloud customer since 2013 and recently became the first client to upgrade to DOCOVA 4.5.
Brotherhood Mutual’s DOCOVA instance is hosted on DOCOVA’s Cloud solution. They have eight users that access the system and use it to store the various forms used by their business. Since their instance is on DOCOVA’s Cloud, the DOCOVA server upgrade would need to be performed by DLI.tools, and, since Brotherhood Mutual’s PC environment is locked down, the client upgrade would need to be performed by Brotherhood Mutual’s IT staff. (as opposed to users doing their own install via the install link in the About page)
Prior to the upgrade DLI.tools reviewed the document types in use and checked the one custom subform that was used for design elements that needed to be upgraded. There were a couple date fields that were easily upgraded. Elapsed time for this update was about five minutes.
The server upgrade was performed using the DOCOVA Upgrade Utility. This automated process walks the operator through the upgrade process. The longest part of the upgrade was waiting for the backups to be created; the actual upgrade itself took around 10 minutes. The server upgrade was started at 9am and completed by 10:45am. One false error was observed when the DOCOVA browser client was accessed using a DOCOVA Cloud admin id, which was that the Dashboard was not loading properly. The issue turned out to be the user limit restriction set in the Cloud configuration. Authorized users could access the system fine.
Next Brotherhood Mutual’s IT staff upgraded client PCs and ran into an issue running the installation program. Using a standard or domain admin account, the install would fail with an error when updating the hosts file. In order for the install to complete, the user running the installation needed to be an admin on the local PC. This was not a DOCOVA issue, but standard Windows security.
Another issue that came up was disabling Compatibility Mode for the DOCOVA site in Microsoft Internet Explorer®. DOCOVA was working fine in Chrome™ and Firefox®, but not in Internet Explorer®. We checked the Compatibility settings in Internet Explorer® since in order for DOCOVA to work prior to version 4.5, Compatibility Mode had to be enabled. With 4.5, it needed to be disabled. We looked at the Compatibility settings and it appeared to be disabled, however DOCOVA was still displaying as if Compatibility mode were enabled. This was finally traced to a global Internet Explorer® policy that had been pushed out to all users, which was overriding the user settings. Once the policy was updated, all was well.
…until the next day when the main user tried to save a document to DOCOVA from within Microsoft Word® using the DOCOVA Explorer add-in. The save would not work and any DOCOVA Explorer navigation was throwing JS errors. This was finally traced to an issue with the DOCOVA Explorer installer not setting a registry entry correctly. An update was provided the next day and the issue was resolved.
DOCOVA 4.5 has been running for over two weeks now without any issues and the improved interface has been well received by Brotherhood Mutual’s users.
“We really appreciate that the most recent version of DOCOVA has the same great features and is just as easy to use,” says Lana Wright, Network Engineer. “Our users tell us that being able to access the system in various web browsers has been incredibly helpful.”
Oct 28, 2015
| Recent Blog Posts
MWLUG 2017 – We Believe!|
Thu, Sep 7th 2017 5:22p Gary Walsh
They call Toronto “Leaf Nation”, because so many of the population are passionate about the hockey team, the “Toronto Maple Leafs”. No matter where the team sits in the standings, they “believe”. The Notes and Domino community has been like that too over the last decade or so. Regardless of how the technology is trending, they believe it is the best.
MWLUG 2017 in Virginia this past August, like most of the Lotus User Group type events, was a gathering
Why we DO migrate code.|
Tue, Jun 27th 2017 1:28p John Ryan
I decided to write a blog entry on the issue of migrating Notes application code when migrating Notes applications to DOCOVA. When I say “code”, I mean the LotusScript and @formula language that is contained in Notes applications.
Now, I’ve seen some blogs and vendor web pages that espouse how you should NOT attempt to migrate the code. These vendors typically want to convince you that you should re-develop your Notes applications on their platforms. I get it. That repr
Migrate Notes to DOCOVA Blog Series Part 17: Input translation and input validation formulas|
Thu, May 25th 2017 1:51p John Ryan
Welcome to blog series part 17 of 17 on migrating Notes apps to DOCOVA. The subject of this blog is Input translation and input validation formulas (formulae if you prefer).
Right. So, one day I hear this argument coming from down the hall here at DOCOVA. The dev team embroiled in some discussion. Oh the controversy. Fisticuffs? Naw. Heated? Maybe that would be a bit of a stretch. The debate? How should input translation and input validation formulas be handled in DOCOVA?
Migrate Notes to DOCOVA Blog Series Part 16: Form events|
Tue, May 23rd 2017 1:24p John Ryan
Welcome to blog series part 16 of 17 on migrating Notes apps to DOCOVA. In this entry I’m going to talk about form events.
Okay, so the talk about form events usually starts of with the question:
Does DOCOVA have document events like onLoad, onUnload, QueryOpen, QuerySave and WebQueryOpen?
Yes. DOCOVA supports both typical browser events like onLoad and onUnload but has also been extended to handle similar events that were found in Notes forms like QueryOpen, QuerySave, PostSave and so
Migrate Notes to DOCOVA Blog Series Part 15: Private on first use folders|
Thu, May 18th 2017 1:38p John Ryan
Welcome to blog series part 15 of 17 on migrating Notes apps to DOCOVA.. In this entry I’m going to talk about good ‘ol Private on first use folders.
This is another one of those “interesting” Notes application design constructs. In my journeys I don’t think I’ve ever come across this same sort of construct in any other application environment. Anywhere. Ever. Sure, a private folder, but “…on first use” is the kicker. Interestingl
Migrate Notes to DOCOVA Blog Series Part 14: Column sorting and categorizing|
Tue, May 16th 2017 12:18p John Ryan
Welcome to blog series part 14 of 17 on migrating Notes apps to DOCOVA.. In this entry I’m going to talk about view column sorting and categorizing.
All view sorting and categorizing functionality is supported in DOCOVA. Additionally, other properties like “Show multiple values as separate entries” and showing response docs in a hierarchy are also supported.
I mean, as you get more in depth with DOCOVA, you’ll learn the breadth of the view object model and all the cool stuff
Migrate Notes to DOCOVA Blog Series Part 13: Shared columns and fields|
Thu, May 11th 2017 1:52p John Ryan
Welcome to blog series part 13 of 17 on migrating Notes apps to DOCOVA. This entry is dedicated to shared columns and fields. It’s short and sweet.
DOCOVA does not support the concept of shared columns and fields between applications at this time.
Say what? I know, right? DOCOVA is so over the top, so chalk full of functionality…it’s crazy, alas at the time of writing this blog entry, it doesn’t support shared columns and fields. Well, that’s the reason ri
Migrate Notes to DOCOVA Blog Series Part 12: Multi-value fields|
Tue, May 9th 2017 12:01p John Ryan
Welcome to blog series part 12 of 17 on migrating Notes apps to DOCOVA. In this entry it’s all about multi-value fields.
Notes had the concept of multi-value fields on forms. All fields were basically treated as arrays of values. For example when addressing field values in LotusScript, you might write some code like;
Dim myval = doc.myfield(0) (where doc is a NotesDocument)
Although it’s a bit of an odd duck, DOCOVA supports the same type of addressing when it comes to form
Migrate Notes to DOCOVA Blog Series Part 11: Pass-thru HTML and Generate HTML for all fields|
Thu, May 4th 2017 1:02p John Ryan
Welcome to blog series part 11 of 17 on migrating Notes apps to DOCOVA. In this entry I’m going to talk about “Pass-thru HTML and Generate HTML for all fields”.
Migrate Notes to DOCOVA Blog Series Part 10: Refresh fields on keyword change|
Tue, May 2nd 2017 12:11p John Ryan
Welcome to blog series part 10 of 17 on migrating Notes apps to DOCOVA. In this entry it’s all about “Refresh fields on keyword change”.
Ya, let’s take a moment to just love this one. Have you ever used it in your Notes apps? Refresh fields on keyword change was a bit of an odd beast, no? The purpose of this operation was to enable field options (or values) to be recalculated based on the change of a selection field.
For example, if you had one keyword field on a