Liquid Office has changed its name to Autonomy Process Automation (APA). The version number is at 7.1 and 7.2 is due out soon. It has a new feature than makes hooking a workflow process to an existing HTML form very easy to do.
In the past I have blogged about exporting Autonomy Cardiff’s TeleForm forms into LiquidOffice using the File Exchange Format. And then populating those LiquidOffice forms with OCR’d metadata from TeleForm data using LiquidOffice’s virtual submit feature. So in this dance, TeleForm is the lead.
And a lead dancer’s job is to make the other dancer look good, right?
Time for a swap – let’s let LiquidOffice lead.
Here we’ll leverage the TeleForm LiquidOffice SOAP connect agent. Price: FREE with TeleForm. Using this method offers a helpful twist: you can attach data and documents to an active LiquidOffice process if you wish. That is not achievable with the virtual submission method.
Though described in the help files as a “complex subject”, there’s some scenarios that comply with the KISS approach (my favorite). Time to jump in but, warning, danger, disclaimer: this blog assumes you’ve spent some quality time with LiquidOffice and TeleForm.
The term “Data Strategy” and can be used to understand strategic requirements for enterprise metadata concepts and best practices. Why is this important for an ECM solution? The simple answer is why contribute to the disarray of an organizations data management when implementing an ECM solution.
The key to a successful ECM system is the ability for users to easily and quickly find information within the repository. If specific information cannot be easily and quickly found, users may not be enthusiastic about using the system.
The biggest stumbling block in the way of finding specific or relevant information is when the search returns too many documents that the user will have to physically look through before finding the specific document or set of documents that exactly meet their requirements.