Monday, July 1, 2019

Can We Get To Work Now?

As you may have heard, the divorce from IBM of the Lotus Portfolio of products has come to a conclusion and HCL has come out the winner,

The value of the deal ensures a decent rate of return to HCL within 3 years(maybe earlier) based solely on Support and Services, otherwise known as renewals.

The efforts to stop the leaving and increase the renewals only adds gravy to the deal for HCL.

But many of us want to see a new land, we want to not just see people hang on, but new customers come out of the cold. This could be the start of a renewal for the product line, sure, few companies have done it, Apple being the biggest turn around, and we have to do it without Steve Jobs. Not sure if that is the vision, but it is a goal which I think should be on everyone's mind.

We have to see the world, not like it was, not like we wish it was, but as it is and how we can once again be useful to people. Yet, once again, daily, we will have to prove that a venerable product, it  never went away in 30 years while so many disappeared, still runs and can run many companies worlds.

Sure, Salesforce now does workflow and automation, taking our niche potentially, or at least trying to if you believe a $200 million software project in Salesforce is required to replace, and not fully, a Domino application. The limitations and costs of Salesforce are not enough to convince someone to drop Salesforce, to push on those is working the competitive tactics of old.

Embrace and extend maybe is the answer, but that would end up a Business Partner play, aside from HCL getting the APIs to place nicely.

Microsoft of course still worries about us, funny how old flames die hard but the old ways, do not work the same and a better play in the competitive space is needed.

Google/Alphabet still sucks at calendaring and while the focus from HCL may not be messaging, messaging still is what runs a lot of businesses.

Workflow and automation demand a solid, stable, secure platform that can be relied upon to work no matter what you throw at it and no matter how little you babysit it. Do you ever hear Exchange admins say they love Exchange? No, not really, but there are 100s if not 1,000s of people out there that will say they love Domino.

Back to HCL Software and the future, while the dust settles and this 3 Billion dollar(Lotus bits)  startup creates logic where there was none, have some patience.

We would all like to see new commercials and marketing, but in a modern world, that doesn't cut it enough. If we really want this to succeed, we need to embrace the social media side, not just pay lip service to it.

We need to ingrain into people that MongoDB is only decades behind Domino in getting field level encryption in a NoSQL flat database.

And people treat that like news?

IBM would never let us go after this, but my hope is HCL will because if we don't bring the issues to the front, there is no press and no customers begging to come back.

Do we need new templates? Yes, and we need to find a way to make them flexible enough so customers can adopt them easily enough. I have some ideas in this space for another blog post.

Do we need to revise old ones? It wouldn't hurt, and these will help keep customers renewing. I gave my input already on the Rooms and Resources.

I have argued that to try to convince people to code with Domino is a hard sell, kids in college have never seen or heard of it. More importantly, the workforce is not what it was in the dawn of the PC industry.

Many employees are niche driven and not code happy, or even interested.

In the earlier days, those of us that wanted to find a better way or figure something out had to read anything we can find, play with everything, dig into stuff that even now I think about some of it was amazing.

But I don't see that spark in employees. The need to know more is gone, maybe because love of company went away over the last 20 years. If HCL can figure out how to light that spark again, we may be on top something.

I mentor startups and they listen to me explain long dead products that did what they plan to do and what went wrong so they can try to make a better way...while scratching their head why they never heard of these solutions.

HCL has the chance to do everything we have been begging IBM to do with the products for years. Now we just need to get on with it and be aware that the future is being built literally every minute as of officially 17 hours ago Grenwich Mean Time.

Thursday, June 20, 2019

SnTT - Rooms and Resources Accidentally Delete a Resource and the Reservations

Last week I gave a session where I outlined a bunch of things I would like to see in the new Rooms and Resources database template should it get updated.

Yes some things were just more defined views, but other things that would make it more useful to admins, and users, were also included.

Well yesterday I learned the hard way about some things I knew, but I guess had not quite gotten to fix yet. Let me explain.

One of my clients has some very full RnR databases, 1 per region. Sometimes, against my preference, names or very similar names, are used in different places.

Tasked with clearing some old rooms, I set out to do just that and get on with my day.

And, of course, as you may have guessed, I deleted an active room.

Very active room.

400 reservations active.

As I saw when the pop up asked me if I wanted to notify people. I said no to that, knowing I can fix this. Well a few hours later, here is what really happened.


Domino problems are caused by admins, truth (except for developer agents that run amok).

I say, no problem, go to trash and undelete it. No Trash View in this R9 template. Note to HCL, please add one. Go into developer mode figuring it would be in the hidden view.


Call client developer and ask what they think, SOL. Soft deletion was not turned on.

Damn. Thought we had enabled it after last issue, but maybe the template got written over in an update or a restore and maybe we had only set soft deletions in the database itself and not the template.

In any event, I was blocked this route.

Call restore team, can you provide me with a backup from the prior 24-48 hours ASAP?
Yes, no problem they said.

Great, restore completes and I go to try to get back the data shows me what I see now, not what I should have seen for a day ago.


Call restore team, ask how it is possible. Well replication was on, ok, try again, turn it off this time.

And get notification, go open it up, same problem!

Well now I am confused. Got the team together to figure it out, and it seems they do incremental backup sand logs.

I said I don't want logs just data.

And 3rd time lucky, I open it up and it is the old data. Perfect, I start to copy a doc to test that pasting it back in will work.

BAH! No dice, this database doe snot allow pasting of documents.


Call back the developer, ask how I, as the admin, can not do this. Well, she knew why and where to look to fix it. And now I will let you know because someone out there will read this after pulling their hair out.

Open the database in the Designer client and go to the views section.

Find the view you need to paste into, you will need 2 of them.
The first is the resources view itself because you need to copy back the deleted resource.
The second is the view of Reservations, by Resource so you can paste back all of the reservations you killed accidentally.

Once you have the view open, locate the Querypaste section as shown in the graphic below and REM out all of the code there and save it.

Once you do this and reopen the database you should be able to paste everything back in.

Then run a Fixup and Updall to get everything cleaned up and reindexed and then test making a reservation that honors used and open times.

You learn something new every day, even after all these years.

EDIT: Adrian asked me on twitter about Adminp and Busytime. I forgot to discuss it, so here is what we did and what you should check.

Adminp at the customer is set to run on a set schedule, so it did not worry me, but you should go into the database and clear the delete request otherwise you will lose the setting in the names.nsf for the resource.

Busytime, I did not rebuild it because my tests showed it was working. Presumably because the dates/times had been in the database already and did not update but if you run into problems, you should follow the technote and clear the old busytime and let a new one start.