One more time you want to do
:A document attribute needs to be mapped to a workflow attribute.I would probably work like this if I was tasked to do this.I thought itemhandler could do both I could be mistaken.
Your options are
Easiest:An oscript event script step
Easier:Lapi you have to iterate the workflow dats structure and manipulate.since this is done thru lapi you have to do it behind the scenes because the user may not see it like a synchronous change as in an event script.
If you are absolutely new to oscript then you should try to learn it by doing the "addressbook" module or attend SDK training.Once you understand oscript then you can do simple event scripting.I wrote some documentation here if you want to take a look
it does not show you how to access the attachments volume because OT includes that as a freebie code.you can expand on that if you choose that route.There is excellent hand holding code within the event scripts area in livelink.
If you decide to do it with lapi,I will tell you the psuedo code.A workflow step is information in a bunch of different tables so lapi exposes that as a simple data structure.It is the same for lapi and oscript.A accessworkpackage gives you in index 1(print out the loop) the dataid of the attachments volume.At this point if you do a ListObjects on that you will get the nodes in that.You again have to find the cat/atts on those documents and when you found what you have looking for put that value in the attributes recarray which is at index 3.Finally after you do all this you call UpdateWorkPackage which will reflect the changes.
Let me know if this is very challenging or not understandable.I can't promise much but I may be able to do some research if I know what exactly you are trying to accomplish.
I would strongly urge you to see if XMLworkflowextensions
could work for you as well.
Good luck
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 and probably certfiable