« Questions about institutional repositories | Main | Dropping anchor to the desktop »
Monday, March 05, 2007
Workflow by any other name...
Since I've spent the last several months talking about our 6.0 release, I've learned how important it is to position the information lifecycle management features correctly. They're not exactly a separate feature, but an adjunct to an existing feature, workflow.
That statement is true at the platform level, since both the "approval and routing" (non-records management) and disposition rule (records management) features are built on the same workflow engine. The statement also applies at the user experience level, within the Enterprise Document Manager 6.0 application. An approval and routing workflow of the Would you please take a look at this? variety is much the same as the Can you please archive or delete this record now? workflow. From the user's perspective, they're both to-do items. Therefore, they both appear in the user's My Tasks section of the web UI.
As we build new workflow enhancements into either part of the system, RM or non-RM, we'll continue to keep the "everything in the same to-do list" model that I'm describing.
Edited on: Tuesday, March 06, 2007 10:08 AM
Categories: Basic content services, Use cases
|