193 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
Migrate Notes to DOCOVA Blog Series Part 7: XPages
Thu, Apr 20th 2017 70
Migrate Notes to DOCOVA Blog Series Part 6: Security
Wed, Apr 19th 2017 101
Migrate Notes to DOCOVA Blog Series Part 5: File attachments
Tue, Apr 18th 2017 91
Migrate Notes to DOCOVA Blog Series Part 4: Richtext and Doclinks
Wed, Apr 12th 2017 29
Migrate Notes to DOCOVA Blog Series Part 4: Richtext and Doclinks
Wed, Apr 12th 2017 31
Migrate Notes to DOCOVA Blog Series Part 3: @formula language
Mon, Apr 10th 2017 8
Migrate Notes to DOCOVA Blog Series Part 3: @formula language
Mon, Apr 10th 2017 24
Top 10
Migrate Notes to DOCOVA Blog Series Part 6: Security
Wed, Apr 19th 2017 101
Migrate Notes to DOCOVA Blog Series Part 5: File attachments
Tue, Apr 18th 2017 91
Migrate Notes to DOCOVA Blog Series Part 7: XPages
Thu, Apr 20th 2017 70
Is 2017 The Year IBM Announces the End of Life of Notes?
Tue, May 24th 2016 34
Migrate Notes to DOCOVA Blog Series Part 4: Richtext and Doclinks
Wed, Apr 12th 2017 31
Migrate Notes to DOCOVA Blog Series Part 4: Richtext and Doclinks
Wed, Apr 12th 2017 29
Migrate Notes to DOCOVA Blog Series Part 3: @formula language
Mon, Apr 10th 2017 24
Migrate Notes to DOCOVA Blog Series Part 2: LotusScript
Thu, Apr 6th 2017 18
Migrate Notes to DOCOVA Blog Series Part 1: What gets migrated?
Tue, Apr 4th 2017 15
DOCOVA SE General Release Announcement!
Wed, May 27th 2015 9


DOCOVA 4.5 – Client Upgrade #1
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
David Wice    

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.”



---------------------
http://www.docova.com/docova-4-5-client-upgrade-1/
Oct 28, 2015
2 hits



Recent Blog Posts
70
Migrate Notes to DOCOVA Blog Series Part 7: XPages
Thu, Apr 20th 2017 2:17p   John Ryan
Welcome to blog series part 7 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to discuss XPages. So, the simple question is: Does DOCOVA migrate and support XPages? Annnnd, the answer is: No. For DOCOVA’s development we pretty much stayed away from XPages for two reasons.  First, although we might have been able to leverage it on the Domino side, it wasn’t a good fit for the SQL edition of DOCOVA which caters to several different relational platforms.  Second, we n
101
Migrate Notes to DOCOVA Blog Series Part 6: Security
Wed, Apr 19th 2017 1:00p   John Ryan
Welcome to blog series part 6 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to talk about three things. Security, security and security. We thought the security in Notes/Domino was pretty good.  It was clear, easy to manage and provided for a lot of variable implementation.  DOCOVA’s enhanced security capabilities were made so that it is flexible enough to support the Notes/Domino approach to security. DOCOVA application access control is handled similarly to Notes
91
Migrate Notes to DOCOVA Blog Series Part 5: File attachments
Tue, Apr 18th 2017 3:33p   John Ryan
Welcome to blog series part 5 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to talk about how file attachments are migrated over to DOCOVA. When it comes to the importing of data from a Notes application to a DOCOVA application, the DOCOVA App Importer initially scans and detects all file attachments in the source nsf and keeps track of what form design elements contain an attachment. As the import of form designs occurs, if a form had an attachment, not only will the
29
Migrate Notes to DOCOVA Blog Series Part 4: Richtext and Doclinks
Wed, Apr 12th 2017 2:57p   John Ryan
Welcome to blog series part 4 of 17 on migrating Notes apps to DOCOVA.  In this blog entry I’ll talk about richtext and how it gets migrated over. So, first off, there is  no such thing as a “richtext” field in a browser as compared to what a richtext field is in a Notes client.  If you are running DOCOVA on a Domino platform rather than one of the other SQL database platforms, DOCOVA RT remains RT and is rendered to HTML by the server when the page/form is first loaded.  From that
31
Migrate Notes to DOCOVA Blog Series Part 4: Richtext and Doclinks
Wed, Apr 12th 2017 1:57p   John Ryan
Welcome to blog series part 4 of 17 on migrating Notes apps to DOCOVA.  In this blog entry I’ll talk about richtext and how it gets migrated over. So, first off, there is  no such thing as a “richtext” field in a browser as compared to what a richtext field is in a Notes client.  If you are running DOCOVA on a Domino platform rather than one of the other SQL database platforms, DOCOVA RT remains RT and is rendered to HTML by the server when the page/form is first loaded.  From that
8
Migrate Notes to DOCOVA Blog Series Part 3: @formula language
Mon, Apr 10th 2017 3:59p   John Ryan
Welcome to blog series part 3 of 17 on migrating Notes apps to DOCOVA. In this post I’m going to talk about @formula and @command language. Most Notes apps have the @formula and @command language strewn throughout them.  The @formula and @command languages were very useful in that they were an easy way to quickly accomplish simple tasks as well as tackle what were sometimes quite complex operations without being a master coder. In order to handle the conversion of @formula and @command l
24
Migrate Notes to DOCOVA Blog Series Part 3: @formula language
Mon, Apr 10th 2017 2:59p   John Ryan
Welcome to blog series part 3 of 17 on migrating Notes apps to DOCOVA. In this post I’m going to talk about @formula and @command language. Most Notes apps have the @formula and @command language strewn throughout them.  The @formula and @command languages were very useful in that they were an easy way to quickly accomplish simple tasks as well as tackle what were sometimes quite complex operations without being a master coder. In order to handle the conversion of @formula and @command l
8
Migrate Notes to DOCOVA Blog Series Part 2: LotusScript
Thu, Apr 6th 2017 1:30p   John Ryan
Welcome to blog series part 2 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to go over LotusScript. In part 3 of this series I’ll talk about @formula and @command language. When we began to embark on the journey of providing a killer platform and migration strategy to bring Notes applications to DOCOVA, we knew that the conversion of LotusScript was going to be an important part of it. Converting LotusScript to JavaScript and PHP is complex.  If anyone out there
18
Migrate Notes to DOCOVA Blog Series Part 2: LotusScript
Thu, Apr 6th 2017 1:30p   John Ryan
Welcome to blog series part 2 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to go over LotusScript. In part 3 of this series I’ll talk about @formula and @command language. When we began to embark on the journey of providing a killer platform and migration strategy to bring Notes applications to DOCOVA, we knew that the conversion of LotusScript was going to be an important part of it. Converting LotusScript to JavaScript and PHP is complex.  If anyone out there
9
Migrate Notes to DOCOVA Blog Series Part 1: What gets migrated?
Tue, Apr 4th 2017 2:11p   John Ryan
Welcome to the first installment of the Migrate Notes to DOCOVA blog series.  This is a multi-part series touching on what gets migrated when moving Notes applications to the DOCOVA collaboration platform.  It doesn’t have to be Sharepoint.  I will publish entries on a regular basis, every couple of days or so, I’m shooting for Tuesdays and Thursdays right now. You can fast-track and get all the whitepapers on our migration methodology and everything that will be discussed in thes




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition