Help with creating workflow "on the fly"

John W. Simon, Jr.

I have a form feeding my workflow. The user filling out the form has the ability to assign work to people (up to 100 different tasks). I want to get out of creating up to 100 "if this task was checked then assign to this user" steps in the workflow.What I came up with is a subworkflow called from the main workflow. This subworkflow has a start step and a "generic user" step. I have a submap callback script in the original workflow that is fired at "Determine Sub-Map To Use" that will 1) access this subworkflow, 2) copy the "generic user" step (for each task), and 3) assign it to the proper user.I have all of this working but it creates a new version of the subworkflow everytime. I thought a better way would be to create a temporary map (from the original subworkflow map), change the maprec on the temporary workflow, save the temporary map, then pass the temporary mapID as the value returned in my "Determin Sub-Map To Use" submap callback script.I am having trouble with this. It is producing an "Error finishing workflow step" and I don't know why. Does the temporary workflow get deleted between me saving in (in the submap callback script), and the system using it as the map for the subworkflow?Any other thoughts (BTW, we are using LL9.5SP1)?Thanks in advance for any help.

John W. Simon, Jr.

Just following up in case others have the same problem.Basically it was PILOT error. I was trying to return the dataid for the DAPInode as the mapID in my "Determine Sub-Map To Use" script. It clearly says in the documentation "These scripts must return either an error on failure, or the id of a map stored in WAPI that should be initiated as a submap when the step becomes ready. To store a map definition in WAPI, load the map definition from the node and then pass it to the script $WFMain.WAPIPkg.SaveSubMap".