Jasmin, yes that's correct. I should have stated the exection environment. In Steve's Feb 25 post he stated
Here is my execute script code to convert a list of attachments to a map of attachments which you can then pass to a Render step:
I re-read that a few days ago and thought, "Oh, I wonder if he means the Render step as in the FormsService/renderPDFForm process?" So I created a map variable (sub-type document) and populated it with a few documents and then attempted to execute the renderPDFForm process with no form and the form data set to the map<document> object. That's what generated the InvalidCoercionException.
So going back to Steve's Feb 25 post, I can't understand what 'Render' step is being referenced. I know you can pass a list of documents as an attachment list in the UserServiceV2 'Assign Task' process (but you can't pass a map of documents because the 'Assign Task' Attachments UI only displays lists, nothing else).
As I mentioned in an earlier post above, I have a process that parses a map of documents and generates the DDX as an XML variable which can be passed to the AssemblerService 'Invoke DDX' process (which actually requires a map of documents as one of the inputs).
Message was edited by: Don400 (fixed a typo and made minor readability improvements)
Message was edited by: Don400 (to re-address the post and clean up associated subject references)