31 Jan 12 11:26
The current OOB allows you to attach SCAN ATTRIBUTES to CATEGORY ATTRIBUTES and just start a workflow map stored in livelink where the scanned document gets added to its attachments folder.For anything further than this you are looking at development.
Some ideas and it may not help you if you are a livelink novice or scan novice and may more palatable to a experienced livelink integrator
Option 1:Explore Jscript(the programming paradigm of ESCAN) and look at the lapi example supplied with it.If you can compile that code you are half way....you may be able to get the forms api to cooperate that way.
Option2:Explore Jscript(the programming paradigm of ESCAN) and write a simple webservice and try to do a livelink webesrvice.
Option3:pass the scan attributes and let a event script populate the form attributes.
Option4:Explore 'Set document pipeline attributes' and see if PERL can be used to program against livelink or atleast create the 'COMMANDS' file for such a operation.
Escan is designed to take tonnes and tonnes of paper and batch it into a leading app(sap,livelink,tcp etc) and is not the ideal interface to show a livelink workflow screen .If before the start of a batch the operator is made to fill a lot of indexing data(which you are doing mapping scanning attributes to livelink attributes) this becomes yet another time wasting thing at the scan client.what you probably want is a intelligent tool like ICC or OCC that can take fields out of teh scanned input and do something useful with that data in livelink.
Your design requirements sound odd and at logger heads with mass scanning.theoretically this can be accomplished .
I am not sure if there are better ways so somebody else who may ahve done this could help you.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010