What's New in Lotus Workflow 7.0?
What new features and functionality are introduced in Lotus Workflow 7.0?
New capabilities of Lotus Workflow 7 include:
- Expose basic Workflow services as Web Services; based on Domino 7 core Web services hosting feature.
- Initiate workflow
- Request status
- View activity lists
- Performance improvements for name look-up in Workflow Architect
- Improved error reporting
- Enhanced logging for Architect
- Supports attachments in the Document Manager integration from the browser
Additional information on the new features and functionality for Lotus Workflow 7.0 can be found in the product's release notes (readme file). For your convenience, that information is repeated below.
Support Workflow services as Web services
In Lotus Workflow 7 some common activities are exposed as Web services allowing the customers to integrate Lotus Workflow applications into emerging platforms such as WebSphere and Microsoft.Net. This support also paves the way for Lotus Workflow to be used in conjunction with MQSeries Workflow and WebSphere Services Choreographer (Dragonfly), since both IBM Workflow environments provide and leverage Web services.
As a service provide, Workflow provides the following services:
- LWFInitiateJob -- to initiate a job in Workflow
- LWFQueryJobStatus -- to get the status of a job in Workflow
- LWFQueryWorklist -- to get the work list of a user
These services use the support provided by Domino 7 for Web services.
Support attachments in the Domino Document Manager integration from the browser
Lotus Workflow 7 allows Workflow Web browser users to make changes to a document and any attachment checked out from the Domino Document Manager. In the earlier versions of Workflow, the attachment was lost during check-in.
Performance improvement on a name lookup in Architect
A new WORKFLOW.INI variable, QuickLoad, provides significant performance improvement for name lookups in Lotus Workflow Architect 7. If you enable QuickLoad, the system does not check for duplicate entries. This improves processing time, especially if the duplicate names are from different Domino Directories. Instead, if there are duplicate entries, both names are presented and the user can choose the correct one.
To enable this feature, add QuickLoad=1 to the WORKFLOW.INI file on the machine where Workflow Architect and the databases you want to access are installed. If QuickLoad is set to 0 or is not present in the WORKFLOW.INI file, this feature is not used.
Install Usability Improvement for Workflow Viewer
Lotus Workflow 7 provides a new installer to install Workflow WinViewer. The viewer files are not copied automatically to the Workflow/Viewer directory (or to a user specified directory) as with previous releases. Instead an Install Shield Wizard runs and users must install the Lotus Workflow WinViewer.
After the setup has run, "Lotus Workflow WinViewer" is added to the list of programs in the Add/Remove Programs window. To remove the viewer from the system, uninstall it using Add/Remove Programs, rather than deleting the viewer files as with previous releases.
Serviceability Improvement - Debug Print
Lotus Workflow 7 provides a Debug Print utility for the Workflow Engine and the Workflow Architect. For Workflow Engine, Debug Print logs all of the actions performed by the Engine, such as creating a new job or completing an activity. The log includes the name of the application database, the user and/or server, date and time, and the function and/or subfunction. For the Workflow Architect, Debug Print logs details of communication between the Architect and external agencies such as the Sametime server or the LDAP server. Log information includes the time, section (i.e. Preferences or Sametime), the function, the debug/error, and the message. Developers can use this log to try to pinpoint whether the bug is.