|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 29
| 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
||EngageUG 2016 Recap
For a fourth year, DOCOVA attended the EngageUG conference in Europe. This year, David Wice accompanied me, giving customers the opportunity to put a face to the name of their new account manager. Dave transitioned from a technical role, spending years at DLI as a developer and consultant.
We started the week by meeting with a customer in Hoofddorp, near Amsterdam, where we showed the multilingual capabilities of DOCOVA SE, the SQL edition of our product. We had both Dutch and Japanese translations completed and uploaded into their instance.
We then stopped off at DOCOVA partner Silverside’s offices in Rotterdam in the afternoon. We reviewed our roadmap and how we were positioning DOCOVA to be a migration alternative for customers looking to refresh or migrate Notes/Domino applications.
From there it was on to a meeting with CFE in Belgium. CFE is a construction company in the process of migrating 400 Quickr places and 4500 users to DOCOVA. We were scheduled to do a project recap. As it turns out we arrived in Brussels minutes after the terrorist attacks. Enough said there. The last thing these people need is more press. Fortunately we had a rental car and were able to make it out of the city with no difficulty. The metro would have been a different story as police had access closed off.
After Brussels it was off to Eindhoven for the conference on Wednesday and Thursday. EngageUG is the re-branded BLUG, Belgium Lotus User Group. This is one of the many Lotus Love Ins that continue to be held at venues around the world. These events keep the spirit of Notes/Domino alive despite the fact IBM has moved in a different direction.
Eindhoven for many years was a working class company town with its economy tied to the manufacture of Philips lamps. The hotel we stayed in is actually a retrofitted factory, called the Inntel Art. There is still a strong Philips presence even though the company relocated to Amsterdam several years ago. The conference itself was held at Evoluon, a facility originally built by Philips in the 60’s as a science museum and now used as a conference centre.
Engage is Theo Heselmans. Together with his wife they do all of the logistics and deliver a quality experience for what has grown to be more than four hundred attendees. It is mind boggling to see two people create an event that rivals those put on by larger vendors with dozens of resources.
The two day event kicked off with a keynote address from IBM’s Inhi Cho Suh. She is the new head of ICS, what used to be the Lotus pillar at IBM before they dropped the Lotus branding. DOCOVA belongs to an advisory group and had a round table meeting with her representative following her keynote. It was great that new blood is at the helm, but I communicated that in my opinion the keynote was under whelming.
Inhi announced that there would be another Connect event next Feb in San Fran and at that time they would outline the roadmap better for Notes/Domino. Not exactly earth shattering news to a community that has been waiting for the latest release around Notes/Domino for more than 30 months now. The keynote was followed by a demo of IBM Connections.
The same presentation that was done at the IBM Connect conference in Orlando, complete with the attractive blonde and flippant dialog with the demo jockey. There almost no mention of Notes/Domino.
For me the conference helped to support what we already suspect. In our opinion IBM has given up on the Notes client and we expect the will eventually discontinue it. They will most likely keep the Domino server, considering the investment they have with it internally and the strength of the product.
That bodes well for us. If Domino customers are going to be forced to find a replacement for Notes to handle their many apps, that is one of the key functionalities that DOCOVA provides. We expect IBM will reveal an alternative, but that causes us little concern. We take it one step further in that we can also provide DOCOVA SE, which replaces the Domino server as well. That appears to be the direction most customers are going. Once the move is made to leave the Notes client, the momentum will continue to a new platform.
The EngageUG event is paid for by the sponsors. In return, sponsors get to do a 30 second pitch to all of the attendees after the keynote, then a 3 minute pitch during speed sponsoring later in the day when small groups swing by the booths on the showcase. For our 30 second pitch Dave played a well known blues riff while I delivered the message that if customers and partners are worried about the future of Notes/Domino they should come and see us. We got kudos from several people at IBM, which made me wonder if they actually listened to the lyrics.
In the speed sponsoring session we relayed our migration message (https://youtu.be/_iOy6Py2OKM) and the three common migration paths to DOCOVA: Refreshing existing Notes/Domino apps, migrating commercial Notes apps that have been discontinued (ie Quickr), or moving off the Notes/Domino platform entirely. The latter is facilitated by DOCOVA V5, the soon to be released version that incorporates many of the design elements common to custom Notes applications. Things like views and response documents. This new designer will eventually appear in our DOCOVA SE product, giving developers that rapid app dev capability we enjoyed with Domino but on a SQL platform. We also provided attendees with a taste from Canada.
The event ended with “The Final Drink”, and sponsor giveaways. We donated a bottle of Canadiana, AKA Crown Royal Maple, which was won by John at Cooperteam.
For DOCOVA, EngageUG was a success. We met several new potential customers and partners, but most memorable is the ability to interact with people directly.
Next year we plan to return as a sponsor and suggest you consider going as well.
Mar 28, 2016
| 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