InsideLotus - Lotus, Portal and Social Collaborative Software
TedStanton 0600014754 442 Views
There's a new article on developerWorks that features an interview with the main architects/team leads for Workplace Designer. This might be the first inside look at the product since Lotusphere 2005.
It's exciting to see the product come out of development and I think folks will be excited to try it...but, you'll have to wait a few more weeks for that.
Sr. Product Manager, IBM Workplace Application Development Tools
As product manager for all things in IBM Workplace application development, I thought I would provide a handy guide to everyone attending Lotusphere who wants to learn more about the IBM Workplace development options. While not an exhaustive list, I wanted to highlight some of the sessions that would be most interesting to developers. Even if you are mainly interested in Lotus Domino development, you'll find these sessions enlightening. Plus, you'll still have time to attend all the great Domino sessions being offered!
A full list of Lotusphere sessions, dates and times is posted, if you haven't seen it yet.
P.S. Don't forget the hands-on lab sessions, too!
Sunday: JMP 109 - In-depth Introduction to the IBM Workplace Client; Speaker: Carl (Pooter) Kraenzel
Start Lotusphere 2005 with this Jumpstart as Pooter takes you on a whirlwind tour of all things IBM Workplace Client. This will be an excellent introduction and prelude to the rest of the conference.
11 AM and 5 PM. AD102 - Introducing...IBM Workplace Designer! Speakers: Martha Hoyt and Maureen Leland. A Must See for All Developers. Guaranteed to make you want to try out IBM Workplace. Who better to do it than the folks who brought you that other famous Designer product.
3:45 PM. AD 304 - WebSphere Portal and Portlet Application Development; Speakers Beverly Dewitt and George Decandio
At some point, you will want to make a portlet. Thankfully, we're making this easier and easier by building in the tools into the IDE.
6:15 PM. BOF207 End the day with a BoF on IBM Workplace Application Development. I've coerced most of the developers who will be at Lotusphere to come and discuss the options with anyone who comes. Tell us what you think so far and how you can envision using all this great stuff.
10 AM. AD402 Overview of the IBM Workplace Contextual Collaboration Architecture; Speakers: Sami Shalabi and Mustansir (Miki) Banatwala
Sami and Miki always have an interesting perspective on things. As you may know, these are the guys who brought you QuickPlace. IBM Workplace goes pretty far beyond that product and this is where you'll find out more about how it all works.
1:30 pm AD305 - WebSphere Portal and Lotus Workplace: Portlet Programming Model and Techniques; Speaker: Stefan Hepper
Hear from one of the portal architects directly in this session. Portlets are an important concept for you to understand as you build IBM Workplace apps.
4:15 PM. AD405 - Introduction to Developing Applications on IBM Workplace Client Technologies; Speakers: Niklaus Heidloff and Srinivas Rao
If you are interested in developing for the IBM Workplace Client, this is the session you want to go to (after the jumpstart, of course). With the 2.5 API Toolkit, we'll also introduce apis for the client platform, and these are the guys who did it.
7 AM. BOF215 Workplace Opportunities for Domino Developers; Speakers: Alex El Homsi and David Hughes (Trilog Group)
It wouldn't be Lotusphere without an early morning BoF to go to! If you want to hear the perspective of a third party, then this is a good place to start to figure it all out and what it means to you, as a Domino developer.
10 AM. ID302 - IBM Workplace Rich Client Platform Architecture; Speakers: Rick Wilson and Bob Balfe.
As developers, we have to understand the architecture of the platform. This session will be a good follow-on to the jumpstart.
10 AM. AD407. The Power of SIP - What Can You Do With It? Speakers: Uri Segev and Amir Perlman.
If you want to find out about the power behind the new SIP server, this is the one for you. Like Sametime bots, the developers who understand SIP, and how to extend it, will be the ones ahead of the game, writing very cool, standards-based applications.
11:15 AM. AD401 - Customization of IBM Workplace Using Workplace Builder Tools; Speakers; Tom Doak and me.
Whenever you build a workplace application you will be using the application template editor in workplace builder. This is also in IBM Workplace Services Express, which I failed to mention in the abstract. In any case, this year we'll show lots of demos with a minimum of conceptual understanding slides.
1:30 PM. AD403 - Introduction to Developing Applications for the IBM Workplace Server
3 PM. AD404 - Using the IBM Workplace Component and Application Infrastructure Services APIs; Speakers: Hardy Groeger and Michael Herzberg
2 developers give you a look at how to use the new 2.5 API Toolkit to build components or access the workplace services. This is the session you've been looking for. AD403 is the introduction and overview of all the api's in the toolkits, while AD404 goes into some detail around actually building something.
1:30 PM. AD501 - Introduction to J2EE Application Development Using Rational Application Developer (formerly Webphere Studio); Speakers Beverly Dewitt and George Decandio.
Uh oh, we have a conflict...so, you'll have to chooose. I'd say if you are ready to start with Java, JSP, JSF, and Rational App Developer soon, then this session is a must. All of our tools and api toolkits will work seamlessly with this toolset, so it's important for you to know what capabilities it provides. If you haven't had the introduction to the api toolkit and are trying to figure out its capabilities, then I'd go to that one instead.
10 AM. AD307 - A "Portal Makeover": Advanced Theme Development; Speaker: Angela Self.
If you need to change the look and feel of your portal or workplace (and who doesn't?), then you need to attend this session.
11:15 AM. AD406 - Leveraging Your Lotus Domino Data in Lotus Workplace / Workplace Client Technology; Speakers: Jeff Eisen and Mike O'Brien.
Notes gurus show you the way to a blended experience of Notes + IBM Workplace Client. Cool![Read More]
TedStanton 0600014754 407 Views
Lotus GM, Mike Rhodin, recently spoke with c/Net News about our social networking efforts. No specific dates or product plans were mentioned. Some of those tools coming from IBM Community Tools have made their way into Sametime 7.5 and some are coming in future releases. I can't really distinguish between what's been discussed publicly and what hasn't been, so I'll just leave it at that. There were some demos at Lotusphere last year, however, in this realm, like the polling feature (instant poll).
While there are add-on's to Sametime being written both for IBM internal use (like our directory lookup plugin for Bluepages) and external product plans, there are other projects, more in the Web 2.0 style, like Dogear, for social bookmarking, and Activities, for managing ad hoc collaborative tasks. (In fact, I "dogeared" this article. :) )
The guiding idea behind the effort is to help people tap into thecollective knowledge of their co-workers, in much the way consumersocial networking sites like MySpace and Facebook connect people online.
Where have we hear that before? Well, the article takes the question head-on, which is good. The question is
"The reason knowledge management failed is quite simple: Knowledgeinherently resides in minds. Putting it into a system that can bemanaged is inherently flawed," he (Rhodin) said.
"Traditional content management and collaboration applications usuallyfocus on the creation of a document or presentation, Rhodin said,whereas many technologies and practices associated withsocial-networking sites focus on people and connections between people."
I think both styles of collaboration will co-exist and actually intersect at appropriate places in the UI. That's why we are building simple interfaces into these services.
What do you think? Do you use social networking software now? In your organization? or consumer sites? Can you see this taking off in your organization? What are the barriers, if any?
IBM Warms to Social Networking
User Experience Design Manager
Throughout that last 2 or 3 years, you have probably seen a shift in focus on user experience and simplification from the Lotus portfolio of products. I think it first started with the 6.5.1 product releases. This is when Lotus aligned many of the products in the portfolio and provided seamless integration between the products. I was fortunate enough to work on an IBM Redbook about installing, configuring, and integrating Release 6.5.1 of IBM Lotus Domino and the Extended Products. They are no longer extended products, but instead enterprise ready software solutions that fits into our Lotus product strategy. This brings me to the point of this blog which is tight integration between Lotus products. Click on the image below to hear from the Lotus VP of Development and view a live demo from our Lotus Executive Evangelist.
By the way, Happy belated Birthday to developerWorks.
In the tradition of the Designer family of products, we made it extremely simple to add AJAX type-ahead to an input edit control. Simply check the box, and tell us what the choices should be and you're done. For more dynamic lists, compute the values on the fly - for instance, do a view lookup and show column values for the choices. Or, point to an external URL that contains the list.
Pretty cool - why bother coding it yourself when we've done all the heavy lifting!
TedStanton 0600014754 463 Views
The folks over at Teamstudio are at it again. This time with a free utility to help you with your LotusScript coding efforts, called Teamstudio Script Browser. It lets you browse ALL of your script in the database all at once, find out where code is referenced by other code, and browse to it in Domino Designer.
I'm sure the Domino developer community will be quite grateful for this useful tool. (And be sure to check out their other Domino development tools, which have always been first class!)
Sr. Product Manager, IBM Workplace Application Development
Warning, this could be addictive! I've been checking out some interesting web design sites and studios lately because I have a new, expanded role in Lotus as the manager (with Charlie Hill as creative director, essentially) of the Massachusetts Design Studio (but we're thinking of a better name to reflect our mission). (We also have a sister/brother organization in Raleigh, aka NC Design Studio, but that's for another post some other time.)
(we've moved - new Inside Lotus blog)
TedStanton 0600014754 350 Views
We're working on a few things around here related to Workplace Designer.
1. I wrote an article for The View...24 pages worth! You have to be a subscriber to read it, or it should be in your mailboxes already. I love doing these articles because they have such good editors over there.
2. A redpaper is almost done and I should be seeing a draft tomorrow. The team built a great component and really took the tool through its paces. Thanks to John Bergland, Redbook project leader, and the team: Adam Egressy from Ad Hoc Systems; Nick Orrick from IBM Austin; and Marc Weinzetl from IBM Deutschland. You'll be able to download the code with the paper when it's posted.
3. Samples, samples, samples. We are busy writing sample components, doing code reviews, and soon we'll start posting them to developerWorks.
(There's also a Domino app dev Redpiece in progress that started this week. More on that later...)
Sr. Product Manager - Workplace Tools[Read More]
In the April/May edition of the IBM WebSphere Developer Technical Journal, there is an interesting article about WebSphere Portal & TV. The article is authored by two IBMers from the European Business Solution Center. The Internet Protocol Televison (IP-TV) uses a broadband connection to deliver digital television services. I spend about three hours of my day inside customer Portals and IBM own intranet and extranet Portals. Ironicly, I spend about another three hours watching TV. While creating IP-TV may not be practical for internal deployment or easily configurable without additional HW/SW, it is possible with WebSphere Portal and solutions are rapidly growing in EMEA and APAC.
The Article includes an IP-TV Portal demo and dives into how WebSphere Portal in an IP-TV environment can be used to create a "home dashboard" portal for communication and entertainment on a TV set.
IBM Premium Service Manager/IT Specialist
Workplace, Portal, and Collaboration Software[Read More]
One of the many competitive advantages that Lotus Connections has over other vendors is our relationships with a wide variety of partners and our commitment to build first class solutions. We’ve already made some great announcements around integration with Microsoft Office, RIM, SocialText, Confluence, NewsGator and more. While many of the niche social software vendors concentrate all of their development effort on a browser UI, many of them aren’t able to take a step back to and understand a browser interface only is limiting. The truth is, I have never met a company where every employee was able to access all their applications from a browser only. There are some division’s with-in organizations that can succeed with just a shared computer and browser.
Your probably asking where am I going with this. I can’t stress enough the importance of integrating Connections with existing applications in your enterprise. Today IBM and iEnterprises announced the integration of iEnterprises' customer relationship management (CRM) software, iExtensions CRM, with Lotus Connections.
Just one place you can read all about it.
TedStanton 0600014754 620 Views
The 'Coltrane' release of Lotus Freelance Graphics, the 1998 version bundled with Lotus SmartSuite, was famously held up for a month when it was found out that one of the clip art images had a tiny 20 pixel image of Taiwanese currency (rather than mainland Chinese currency). Or was it the other way round? An eagle-eyed QA engineer had discerned the offending image. Needless to say, this was something that would cause offense and/or affect purchasing decisions in the involved markets.
I was a little canary in that Freelance mineshaft (or was it a minefield?) when a couple of months earlier in the project I had discovered a seriously outdated map of Africa when integrating new clip art into the product. I wrote one of the sprs of which I am most proud titled something like: "Upper Volta should be Burkina Faso". The spr also made a brief mention of the fact that as far as I could tell there were similar problems in our maps with the names of the states from the former Soviet Republic which had changed earlier in the decade. I believe that my spr was deferred to a later release; it was too late in the product cycle and we'd have had to go back to the company we licensed the art from and so forth. As it turned out however, with the advent of China/Taiwan flag issue, the entire suite was delayed as the test team had to painstakingly go over all the clip art and other areas of the product vetting for similar outrages that could endanger sales.
Incidentally the acronym, spr, stands for "Software Problem Report" in Lotus's parlance. After a decade of indoctrination, I still tend to use spr rather than the more clinical, "defect", which is the favoured term at IBM, or bug which is the more widely-used term generally. You can still tell whether someone has the 'old Lotus' DNA rather than the 'new Lotus/IBM' variety by the terminology they reflexively use. For a dissection of recent linguistic trends in technology see this earlier post.
As a further aside, the Lotus spr database is actually one of the most successful and useful applications of Notes technology ever and in a similar manner, the Bugzilla project is actually one of the best things to have sprung out of the Mozilla effort. Certainly it was more useful than the Gecko suite until the M7 milestone was reached years ago. There must be some kind of software law at work here, something analogous to Zawinski's Law on software expanding until it can support email (and now feed technology) and so I'll coin it as Koranteng's First Law of Software Systems:
A software platform reaches its tipping point once it can serve as a bug reporting system.Intuitively this makes sense, once developers can view, file and retrieve bug reports using their own products, they will be more likely to use them and their confidence in their mission will improve dramatically.
Back to my topic though... I'm sure that the artists who created the clip art in that design firm had no subversive intent; they probably used outdated stock art as their source material. Still sometimes you wonder at these things and, in this vein, I'm reminded of the Nobel Prize-winning Portuguese author, Jose Saramago's wonderful novel, The History of the Siege of Lisbon, in which a copy editor proof-reading a historical novel defiantly changes a crucial word in the text changing the outcome of a famous historical battle from a miserable defeat to victory. A masterful alternate history of Portugal then develops and its culture is fully reimagined. I'm sure that bored developers sometimes slip similar things into their products, and not just serendipitous Easter Eggs.
More seriously though, the Freelance incident (or similar incidents relating to any new release of dictionaries or thesauruses from Microsoft) go beyond the cultural sensitivity of which this post is concerned into the rarefied realm of political sensitivity. The same thing goes when choosing product names: you don't want mere mention of your product to cause snickering or offense. A misconceived name or culturally-insensitive feature can be a black eye that will chasten even the most high-flying company. More worrying is that this can translate to a serious financial impact (well beyond a month's lost revenue for the suite) if proper attention isn't paid.
Internationalization however is a mostly thankless, and oft-neglected task even as I've outlined its importance. From a developers standpoint, you first think about it mostly in terms of dealing with resource bundles and having to put all your resource strings into seperate files for different languages. This is a pain because you probably started with a little prototype of a user interface and now you're being asked to find all those hard-coded strings and to "do the right thing". Plus it typically becomes an issue only late in the game when the real interesting work is over and you're ready to think about the next big thing. Instead, you're grudgingly forced to worry about handling different writing systems, dealing with bi-directional text, or that old favorite: the various "special characters" in the wide variety of programming languages, file formats, protocols or operating systems in your software. Those best at this task are akin to forensic investigators and must possess considerable patience and attention to detail.
If, for example, your software mangles names with accents, you'd have real trouble selling in France. Similarly with ampersands and apostrophes - which have significance in SGML and its derivatives (HTML, XML etc). And don't get me started about wider character sets and encoding issues... As an ironic case in point, while developing Lotus K-station, one of our best business partners was somewhat stymied in his development and extraordinary evangelism of our product because, in its earliest release, it couldn't handle the ampersand in his company's name. Luckily for us, he temporarily renamed his organization in his LDAP directory; Sun & Son became Sun and Son until we worked out the quirks. To this day, I always make sure to test whatever product I work on with that organization name. It's surprising though, how often this kind of problem recurs.
In this internet era, most technology, and certainly all software development, has to have global concerns in mind. It is said that the sun doesn't set on an IBM project and I work with a very diverse set of colleagues the world over. Presumably the benefit of such a widely dispersed and diverse workforce should be to mitigate the likelihood of issues in this area. As my current project has been going through translation and localization testing of late, I've been thinking a lot about how we handle internationalization.
The old Lotus process was a more decentralized one, each product group had an internationalization team seconded to it. Members of such teams were domain experts and knew the product inside-out in addition to being localization gurus. This had many benefits, the team was involved from the very beginning in the product development cycle and could give crucial design feedback very early and iteratively. Your first prototype was immediately critiqued from their standpoint. The obvious downside of decentralization was the lack of uniform standards - chaos that our translation teams couldn't bear. Some products were very easy to localize, others were, to put it politely, far less so.
As we transitioned to the more centralized IBM globalization process, we got the benefits of uniform standards and greater resources. More languages could be supported in the initial release and you could at least point developers to documentation about the processes to follow instead of ad-hoc stumbling about. Still this was at the expense of the loss of domain expertise, sensitivity and a much slower feeback loop. Some of the test teams would be barely getting up to speed with the product by the end of the testing phase. Localization concerns would sometimes surface too late in the game and would cause much unnecessary reworking and product delays. These things are tweaked, as all processes are, and in recent years, I've seen a push towards re-enabling more domain expertise in the internationalization teams which has been very useful for our product development.
I'll lay out a brief example then, that I think is illustrative of the kinds of things we're dealing with here I hope it can tease out the technical, design and business issues that can arise...
I embarked over the past couple of weekends on a mass digitization project and scanned, retouched and uploaded 2000 or so old photos from shoeboxes under my bed. The technology involved in this exercise was scanner hardware and image aquisition software, the bundled Adobe Photoshop Elements for color adjustment and red-eye correction and a couple of online photo-sharing services: Yahoo Photos and Flickr (I started the day Yahoo's acquisition of Flickr was announced).
The first thing I very quickly noticed: somehow all the photos that I uploaded to Yahoo Photos turned out darker than on Flickr (the services both resize uploaded photos). The photo-resizing algorithm used by Yahoo Photos was giving worse results. This was noticeable to me because a large number of photos featured darker-skinned people such as myself. The originals were fine and where there were lighter skin tones everything looked good, but with darker skintones, the resized photos were not so good. This meant that if I didn't believe in the virtues of Save Lots of Copies Everywhere (SLOCE), I would have leant towards Flickr and stopped using Yahoo Photos.
Secondly, I don't have Flash installed on my Mozilla browsers and so my experience of the Flickr website was very different from that of my family and friends who started looking at the photos with Flash on Internet Explorer. There were immediate complaints about the first bunch of photos. It turns out that images that are rendered in the Flash plugin have a slightly darker tinge than the images rendered directly by the browser itself. This is not normally noticeable but again this exacerbates contrast issues when darker skintones are in evidence as in this case. This was made worse when users tried the slideshow feature because the background of a Flickr screenshow (also implemented in Flash) is black worsening the contrast further.
Thirdly, when retouching photos, the Quick Fix or Auto Correct options in Photoshop seemed tailored for lighter skintones so I was constantly having to do manual tweaking of my photos. Now this is not a big deal for a few photos and indeed it's fun to fiddle with photos but after a couple of hundred images, it gets tiresome. I found mysef longing for "smarter" recognition by the software or for at least, a nice 'dark skin' option that I could set in a preferences dialog. In short I started considering using different software instead of Adobe's.
Now I mention these nitpicks on otherwise excellent and useful products because of the design issues they raise. Technology is simply a tool in aid of people and as human beings we live in different society and cultures. We find that different cultures adapt technologies in different ways to suit local preoccupations and concerns. And I certainly had my own localized concerns these past weeks.
Even when the technical 'fixes' are easy there are design issues and economic tradoffs that also arise. True, Macromedia could implement better JPEG rendering in Flash but that comes at a certain expense - a good renderer is a hard thing to write (even if they could license the photo-rendering from the Mozilla folks). Also what they have appears to be good enough for most people (except me obviously). When do you decide that your product is good enough and stop pandering to the Long Tail? Can you afford to do that? Or are you missing out on a vast market opportunity?
Yahoo Photos could certainly implement a better photo-resizing algorithm although presumably there's a performance penalty to be paid if you use a more color-accurate algorithm (or perhaps a larger resultant image size). At the kind of intenet scale that the Yahoo service operates on with tens of millions of users and photos, this could potentially seriously affect the scalability of their platform. Conversely, if all Yahoo users switched en-masse to Flickr which uses the more expensive algorithms, would that platform be able to handle it? Or would it generate a case of teething problems and turn users off because of poor response times?
Similarly Photoshop could implement a slight variant of their various Quick Fix and AutoCorrect features that were more attuned to my kind of skin colour (indeed I assume that photographers in Africa have written macros or filters that do such a thing). How best though, to phrase a global preference in an options dialog in Photoshop? "Adjust for darker skintones"? Documentation writers would have a field day finding the right verbiage for such an option. Also what about usability? If you add all these preferences to your product what will your user interface look like? Try typing about:config in a Mozilla browser to get a sense of the kind of complexity that modern software developers have to cope with.
If there was a huge market for these products and services in Africa the issues I faced could be a real problem for the companies in question (although this is unlikely given the low internet penetration rates and the likely widespread software piracy). There would be demand not just for local language versions (say a Swahili language version in Kenya) but also for tweaks that would make these services more closely attuned to the prevailing culture and, in this case, ethnic backgrounds. Thus photographers in Africa over the past 150 years have had to deal with brighter sunshine, higher contrast as well as darker skintones when processing their photos as photography has gone through its various evolutions and has now moved into the digital realm. The people who install photo laboratory hardware in Ghana where I come from, always have to recalibrate their equipment to deal with the kind of skin tones that are present in the local market. The factory defaults simply won't do. I've had better results developing film in Ghana than in the US because I often forget to tell the labs here that they should "watch for skintones". I'd expect then that software that were truly local (and all web software should be local or adjustable to fit local concerns) might sometimes need not just run-of-the-mill language changes or even writing system changes but also, as seems needed here, algorithmic adaptations.
As software designers, we try to engineer simplicity and refrain from overwhelming users in their interaction with our services and products. Software is not the user's main focus, it's rather its use that is most important for the user, for the business and for society as a whole. Yet there very real concerns in the application of technology in different cultures. So the next time you see a vaguely-worded so-called "Turkish option" somewhere in your application's configuration dialogs, know that someone somewhere was likely adapting their product for a local market. Join me though in saluting the developers, testers, product managers and designers who collectively worked together to come to that solution. I'd hazard that the tweaking of the product was to fix a deal-breaker in some market.
Finally, for what it's worth, I find endlessly fascinating this notion that cultural sensitivity in technology sometimes necessitates algorithmic adaptation. Maybe though, iterative adaptation in response to local environments - evolution in short, is the name of the game. Perhaps that's simply the way things should be.
Workplace Forms Development, Lotus Software[Read More]
TedStanton 0600014754 427 Views
I came down to Orlando on Thursday night to help prepare for the Opening General Session (OGS). You wouldn't believe how much work goes into this 2 hour presentation. Most of us were up until 1 or 2 a.m. working on stuff - scripts and demos, which started out too long and had to be trimmed to their essence (but still very good). Then back at it at 8 a.m. I hear that it was nice outside. :(
I went to the House of Blues for dinner with the Activities team and a few others. (Good ribs.) Then, a stop by ESPN to meet and greet with Turtle, Gary, Colleen, Carl, Bonnie, the Bob, and probably a few others I can't remember.
On Sunday, the Jumpstarts began. I hear that the 8 a.m. Workplace Designer jumpstart was over-flowing. The WP Designer Doc API session by Philippe Riand had a good crowd, too. The second Designer intro jumpstart was also well attended in a bigger room. We already gave away 400 of the Document API posters.
(The Domino Object Model posters will be in the the product showcase on a table kind of toward the back. Remember - there are 2 of them.)
The party begins soon, and I hope I can go for a little bit. Maureen Leland and I start the first session at 11 a.m. on the main stage, so they better be done with the OGS by then. :)
We're off to a good start!
Sr. Product Manager, IBM Workplace App Dev[Read More]
If you've installed Notes 8 and played around with it, you've noticed a few design changes (one or two). In the calendar, we thought it would be useful to give you good default colors so that the calendar would look like it was professionally designed, instead of letting our color-challenged users pick them. Problem is that if you installed over an existing Notes mail file, the calendar will use your existing color choices. The tell-tale sign is black text for entries, which to me looks a bit harsh because we are using a bold font for the titles. If you want to try the new colors, do the following:
1. In the Action Bar of the mail file, choose More...Preferences...
2. Choose the Calendar & To Do tab.
3. Choose the Colors tab.
4. Click the Restore Default Colors button (see picture below)
5. Click OK.
Manager, Product Design
Technorati: notes8beta[Read More]
As many of you already know, I am a Premium Service Manager for Lotus. For a while, my group has been working on a customer Portal. A couple of months ago I posted a blog about the Portal. I am now pleased to announce we have developed a demo. The demonstration gives you a tour of each page of the portal -- highlighting the key points and benefits. Find out why some of our Premium Support customers have said, "I love this portal...it has everything I need!" and "This portal is a giant step forward for the customer."
So please take some time to view our new 11-minute demonstration of the IBM Workplace for Customer Support portal, available here: