Category Archives: Quickr

Sticking with Quickr a While? Some Suggestions

QuickrLogoTinyAs you contemplate the document-management-collaboration-teamspace-workflow-process world in the coming months and years, it’s likely that many of you will want to wring everything you can out of your investment over the past 14 years (that’s right, 1999) in Lotus Quickr and its previous married and maiden names.

I’ve heard from companies who are planning to migrate to Connections Content Manager 4.5 (coming soon to a server near…me), and some that plan to migrate in and out to everything from PDFs (we do that) to Sharepoint (uh, huh) to IBM ECMs and other collaborative platforms like Liferay.

But for many, sticking with Quickr Domino for the foreseeable future is a very valid choice. Your users know it well and don’t need training, or use the Quickr Connectors religiously, or you have a customization in place that conforms to paragraph 17 section 42 subsection d of the corporate style guide. Whatever the reason, if you intend to maintain a Quickr Domino server I have a few technical and business suggestions to bring and keep you up to date.

Internet Sites Documents

Starting with an earlier fixpack of Quickr 8.5.1 (currently 37), Quickr officially began to support Domino’s Internet Site Documents. Prior to this, we all used the Web Configuration document and standard MSSO / LtpaToken combination. And if you did, it’s not likely you switched because things are working. Switch. Two reasons — if you are still on Domino 8.5.1 (see below) you can add a custom header to provide better support for IE9 by putting it into compatibility mode. But more importantly, when using Internet Site documents, you have the option to have the server automatically compress (gzip) files from the file system as they are fed to the browser, cutting down traffic. And Quickr traffic, and these files, number in the hundreds. Multiply this by hundreds or thousands of users and this represents a significant savings and performance boost.

Domino – Upversion

Starting with Quickr 8.5.1 Fixpack 34, the team separated the Dojo installation to the point where Quickr no longer depended on the Domino Dojo version 1.3.2 being in a specific directory. Don’t get this wrong – Quickr still uses Dojo 1.3.2, but it installs its own copy. This has made the Quickr server more independent from the Domino version, meaning…it’s more likely we’ll see Quickr supported on Domino 9 when the time comes. (That is not an official or even informed statement, it’s just technically more feasible.) So, upgrade Domino to 8.5.3 (FP1, HF618 specifically) and when doing so, be sure you understand that there are two fixpack code streams now – and install the Quickr fixpack for Domino 8.5.3 going forward.

Fixpacks – Do Them

Quickr fixpacks are released every month. I suggest a maintenance release schedule of every two months, one month behind IBM, unless there is a specific fix for you or a showstopper bug (to you!) in a fixpack. Applying fixpacks is easy, despite the best efforts of the documentation to be confusing. Once you’ve done a few of them it becomes second nature and can take little to no downtime. Be sure to read the fix lists and consult the sample qpconfig xml document for new parameters and options, and once in a while even some features.

RTQM

With each fixpack comes an updated release document, and while you may be tempted to skip it, there are often hidden gems, like the time that all the notification templates were updated, or XSRF security was added. Have a look through this document, then, as I suggested above, compare your existing qpconfig.xml configuration file to the newly deposited qpconfig_sample.xml file. You may in fact find undocumented new settings (I know of one for sure, because I put it there!).

Collaboration Space Lifecycle

Quickr places that are designed for project work are temporal in nature (I love throwing ST:TNG terms into my blog), but more often than not at the end of their usefulness they sit on the server taking up space, processor, indexing time, and resources. Just like the more granular corporate document management lifecycles and retention policies, the lifecycle of Quickr places and their documents, collaborations and bastions of tacit knowledge should be planned as well. We have tools to export to PDFs, which may or may not work for you, and there are other storage options out there…

Tools and Apps and Workflows, Oh My!

Once you’ve settled on an updated Quickr instance, it’s time to add in some moderate helper tools, optimizations and easily pluggable customizations to enhance the user experience. Sitemaps, widgets to do pretty much anything, custom notification templates (branding), themes, views and HTML forms are all part of the more mature, high-ROI Quickr environments I’ve worked with for 14 years. It doesn’t take a rocket scientist to deduce that you get more out of software when a) people like using it and b) it helps get their job done faster and better. So consider some of the free and paid add-ons out there. A few are in my post below (well those are more full-blown apps). One was even done for a rocket scientist. Honest.

 

Lotus Quickr is only Mostly Dead

So you’ve heard by now that Lotus Quickr is dead. Doornail, zombie, Betamax, rotary dial, dead. Somebody came back from what used to be called Lotusphere, said there were no sessions, saw a tweet and now has you scrambling for an answer to the pressing, urgent, mission critical need to provide a replacement. Dead, I say!

MiracleMax“Whoo-hoo-hoo, look who knows so much. It just so happens that your friend here is only MOSTLY dead. There’s a big difference between mostly dead and all dead. Mostly dead is slightly alive. With all dead, well, with all dead there’s usually only one thing you can do.”
-Miracle Max, The Princess Bride

A side effect of thundering silence, which is what we heard about Quickr for a year, is a desire for new direction. I recognize that, and of course counsel clients to be best of my ability when they are making strategic, tactical, or weekly conference call decisions.

So, I shall put my powers of deductive reasoning to work here and provide you with my view of the situation and perhaps, some direction.

Quickr is far from “dead.” In the IBM software world, “dead” takes place over a period of years and takes the shape of changes to the official product lifecycle status. First we’ll see a version reduction (there are two, some could argue three, versions) with the older versions being withdrawn first. In our case, Quickr for Domino has version 8.2, and two slightly different versions of 8.5.1 – one that runs on Domino 8.5.1 and one that runs on Domino 8.5.3. By “withdrawn” I mean that the lifecycle status will change to what they used to call (and I still do) “EOL” or “End of Life” then eventually “EOS” or “End of Support.” When a product hits EOL, it is removed form IBM’s offerings and no longer sold, a letter is published about its withdrawal from marketing, and maintenance is no longer extended. EOS comes later, as customers can actually buy a product until the EOL date and expect support. Even after EOS, companies can purchase extended support contracts to keep themselves covered for longer term use.

SecondOpinion

OK, here’s one:

“First of all, I want to make it very clear, that Quickr is going to be continued to be supported for a very long time. So, there is no immediate action required on the customer side to do something right now. You can all continue to use Quickr.”
-Rene Schimmer, IBM (Ask the Product Managers, IBM Connect 2013)

But really, all that is just the mechanics of availability. What about you thousands of Quickr customers? Well IBM has laid out a roadmap, and that is a partial migration to IBM Connections Content Manager 4.5, to be released next month, and a utility to migrate Quickr for Domino or J2EE libraries to it. Problem solved! Well, for some of you.

When you start classifying your current use of Quickr, the answer you’re after gets a bit more complex.

Customizations
You see, many companies (I claim 50%) have some sort of a) non-library, b) custom, c) workflow, or d) extranet use for Quickr. Or a combination. Here’s a sample from memory: Quickr is used for law firm caseloads, extranets, group calendars, marketing campaign tracking, oil exploration scientific taxonomies, network procedure tracking, drug approvals, multi-phase editing cycles, leave approvals, insurance certificate delivery, employee timesheets, global trademark legal processes, quality assurance reporting, global feedback management, training delivery systems, on-demand surveys, trade ministry envoy support, and presidential speech delivery.

Let’s say you have some level of customization, but at the end of this article believe you should still migrate to Connections Content Manager. You’ll need some services to get your Quickr server data in order, or migrate the customization work and data. That effort might be an item of value for you, or it might not. It will take individual analysis to come up with the best strategy.

Size Matters
There are indeed customers who may fit the use profile but do not have Connections today, are running Quickr on a single Domino server or cluster, who in order to migrate need multiple high powered servers, a services engagement for installation and configuration, and a need to acquire or hire WebSphere skills. If you’re a small shop or operate on a smaller budget, this could be a challenge.

Extranets
As a replacement strategy IBM is offering a solution that does not YET have an extranet or external user story. Quickr Domino is very often used for these purposes. In fact this was the original marketing message for QuickPlace in 1999. Also, when Quickr customers use local users, the additional burden of converting to an LDAP solution comes into play.

Conclusions
The best advice I can give a Quickr customer is more like a meme: STAY CALM and CHOOSE WISELY. It’s a bit obvious. IBM has said that Quickr Domino will be around and supported for many years to come. It’s just not going to get new features. It will receive what they’re calling “currency updates” which means support for new browsers and operating systems on the client end…at least what can be supported based on the architecture. For those who choose to follow the migration roadmap, I propose an analysis of the current environment, feature comparisons and a readiness check for your Quickr environment.

So to migrate or not to migrate? Start asking these questions.

  1. If you have no customizations but use Quickr for document storage only, plus for migration
  2. If you already have IBM Connections, plus for migration
  3. If you don’t have IBM Connections but do have WebSphere skills, small plus for migration
  4. If you have customizations that are functional or business process oriented, plus for Quickr stability
  5. If you have an extranet, plus for Quickr
  6. If you have a small installation and no IBM Connections, plus for Quickr
  7. If you want some stability for several years while you work it out, plus for Quickr
  8. Keep in mind there are a few other options besides the roadmap — other products for collaborative document management
  9. More than likely, you have mixed answers

A final thought – being up to date on Quickr will be key to that “stable” environment, if sticking with Quickr is your choice. And once you’re there, there is no harm in investing in add-on products, MODERATE customizations and additional support services to enhance your business processes and client experience. Quickr is quite flexible today, and the stability of several years of support for the same version means your risk associated with ISVs and customization is actually lower now than at any time in the past. Think about that as you make your choices for 2013, 14, 15, 16…

Quickr Fix 36 – Oh yeah, a couple of my fixes are in…

QuickrLogoTinyI haven’t really been posting too much technical yet on the new blog but this is one of my pastimes, reading through fixes. Especially ones that include “my” fixes, like the one in red below. Hard to believe this one wasn’t noticed before now — comments not being secured like their documents are. So anyone could see “RE: Should we fire Joe?” or perhaps “RE: Is Susan pulling her weight?” in the What’s New page. If Joe or Susan were admins, there’d be hell to pay.

Another fix of mine (I enjoyed this one, as I opened a PMR, gave the solution, writing my own undocumented qpconfig.xml node) has to do with the Preview capability in Quickr. You may know that Quickr, like Notes and iNotes, uses the KeyView viewer technology to preview certain types of files. Well, in some cases you don’t even want to try to invoke that viewer, you don’t even want to show the link “Preview” next to the file attachment. After staring at the corresponding widget for  while, I dug a bit in the DOM and discovered an element called “filetypes_not_supported” with an array of six values. But they had some spaces where they shouldn’t be, and only the first one of these “.zip” was actually hiding the Preview link. The rest were showing it.

I dug a bit further and found a corresponding area of qpconfig.xml where, if this setting could be controlled, I would expect it to be. I added the setting without the spaces, and voila, fixed the core code. And now as of Fixpack 35, there is a somewhat documented node in qpconfig.xml:

<filetypes_not_supported>.zip,.z,.exe,.bin,.nsf,.ntf</filetypes_not_supported>

Now why did I care? Well, I had written a few widgets to invoke the Adobe Acrobat embedded viewer instead of KeyView. The KeyView one is quite bad on some PDFs, especially ones with images. Because of this, we didn’t want the Preview link EVER to show up next to a PDF, regardless of the form. That’s what started this little hunt in the first place.

QuickTime LogoRecently, I expanded on the PDF viewer widget and turned it into more of a utility viewer-enabler widget for files of other MIME types that have native browser viewers. A client had asked me if I could build a QuickTime version (four kinds of files) for their training needs, so their videos would stream from the site. Good news, we could do that and now due to the fix above we can avoid the Preview link and hence user confusion.

Go forth and fix, people. I have two more “By the way, I already fixed it” PMRs going in this week, so watch out for those next time…I sure hope the support folks don’t mind me doing that. 🙂

FP 8.5.1.36

GAKI8YXCW4

LO72042

An email delivered to a place that contains no paragraph break may not wrap or scroll in the rich text editor.
HMON8YJRFH

LO71856

When sending a Link from a page that has been edited, the subject line in the email may contain the word “test”.
DAMC8UMGNB

LO69635

When email groups have subgroups that contain the same user, that user may receive notifications multiple times.
DTRR92QM8H

LO73028

Comments to a Page that is private may display in the What’s New page.
MMOI6C8UHQ Request a way for Local Users of a place to not see places that are available to all logged in users to display in My Places.

(see fix MMOI6C8UHQ  in “Additional Information for special fixes” section)

RTIN92RJ74

LO73041

When using ActiveX, and editing a Page, the ActiveX attachment box appears on top of the of the notification dialog when sending a notification.
HMON92ES4H

LO72785

Popup Date fields display the previous day after upgrading from Quickr 8.2 to 8.5.1.
DWHN92GKHL

LO72884

Attachment links in custom forms disappear when using Internet Explorer 8 in compatibility mode.
TMAI92J69B

LO72896

Cannot create a new Room in FireFox when in the What’s New page.
TJOR8SVQEC

HMON936KKF

LO73241

LO68478

Pages upgraded from Quickr 8.2 to 8.5.1 display the modified date in the future.
DWHN8WTF6X

LO70889

Changes made to a subfolder in a PlaceType does not get pushed down to the child Places.
PPOR8ZTLPG

PPOR922LBL

LO72642

LO72519

When a Task’s title contains certain special characters, those special characters are removed from the notification.
TJOR8WGNVG

LO70682

Daily and weekly Newsletters may show the incorrect last modified date and time.