I am part of a Domino migration at a large client in the financial/insurance industry and we have been moving applications from Domino 6.5.5 to version 8.5.2 FP1. I know, there are newer versions out there but you can’t always upgrade blindly – this is going to be one of the stories why IN-DEPTH testing is so important.
The client has an application that has been around since R5 days, migrated and upgraded several times – both client and server versions and never an issue.
Suddenly we get reports (during testing – thank GOD!) that when using the app with the new client (LN 8.5.2 standard) that certain document do not get created – they vanish.
To make a L O N G story short – we opened a ticket with IBM support and after digging and prodding they produced this one for us:
(from the actual ticket)
******************* SUBSEQUENT CALL RECORD TEMPLATE *******************
Created a test DB in 85 and copied customer form and data.
Found field “eml” caused the issue: SPR RDJS8APTK6.
This is a regression error that made its way back into the Lotus notes 8.5.2 code stream. It was fixed in Notes 8.5.3 but if you are on 8.5.2 (no matter the FP level) you are snorked.
What we did
Since it is hard to determine with any certainty how many other applications out there might contain a filed called “eml” the decision was made to do a company wide, mid-project change and instead of rolling out Notes 8.5.2 we will be rolling out 8.5.3 and upgrading all workstations to which 8.5.2 has been deployed previously. A huge undertaking.
Had this not been found during testing it could have been very costly for my client. As is, the change in scope will be massive and costly as well, but it beats having actual business processes interrupted and clients (actual consumers) be impacted.
So – the lessons everybody should take home from this:
- Test – always test even if it is a small point upgrade
- Test – with ALL server and client variations that you might have in your environment – do not skip anything
- Have test plans that are captured and documented across each scenario and can be compared apples-to-apples.
- DO NOT NAME ANY FIELDS, FORMS (or anything else for that matter) IN YOUR APPLICATIONS “EML” – this error could possibly be re-introduced in a future code stream – you never know.