Sounds Like and interesting Idea Matthew. Have you actually done this yourself?

Thanks,

Milton

Yeah, lots of times, both reorganizing values in a single form process, and passing values into a secondary process.

OK that works for me. Just weird that the Multi Value Variable in Business Process does not pass from one Task to another. It would Save a whole lot of Work Passing stuff back and forth from Workflow. Thanks so much for the quick reply. Still would like to know if it can be done without Workflow.   Have a great weekend!

Milton

Here's an example of what I mean in Workflow:

I have a notes table that I reuse on a lot of forms - so it's really consistent.  If I have a need to start a new process based on a prior one, I'll often copy the contents of the prior notes table and put them right into the notes table on the new process.  The "Retrieve Business Process Variables" can select the variables from the notes table on the first form (for example: notes_table.user, notes_table.date, and note_table.not) then the "Invoke Business Process" activity can load those values, unaltered, directly into the table on the new form, like this: 

notes_table.notes_user=%(RetrieveBusinessProcessVariables_notes_table\notes_user)
notes_table.notes_date=%(RetrieveBusinessProcessVariables_notes_table\notes_date)
notes_table.notes=%(RetrieveBusinessProcessVariables_notes_table\notes)

What method are you currently using to pass the values into the second form?

Are you using formulas, or default values, or Javascript, or passing them as URL parameters, etc.?

Just Passing the Table field Variable from each Column in the first table as the default Value for the Table Fields in the Table on the Second Form.

As you can see from my example above.  The second forms Table gets that Values for each Column, it  Just places them in One row with a ; between each value.

Yeah, that makes sense. 

There are definitely functions that they intended to have populate a table, like database lookups and passing multi-value tokens from Workflow.

But unfortunately, I don't think they ever intended for default values to work to populate a full table, so it just doesn't work that way.

Fair Enough, would be a great feature though if it did! It's obviously needed and we are all trying work arounds to get there. Yours seems the logical approach.

Another thing with the Workflow.  If you want wanting to just copy from one table in your instance to another table in the same instance, you can do that using the "Set Business Process Variables" activity instead of the "Invoke Business Process" process that I mentioned before.

Also, although it may not seem like it when setting up a workflow, because it seems to "link" to a specific Forms process.  If the variables are the same, you can reuse a workflow for different Forms processes.  So, if you always have table_a and table_b, and you always want to copy column_1, column_2, and column_3 from table_a into table_b - and all the fields in both tables have the same variables - and in every different process that uses those tables, the variables are always the same - then you should be able to just set-up a single Workflow that does the "Retrieve Business Process Variables" activity to pull in table_a, and then runs the "Set Business Process Variables" activity to push out the values into table_b.  It'll work from any Forms process you call it from that has those variables, regardless of whether or not you set-up the Workflow against that specific Forms process.  I hope that makes sense.

I was Just about to ask that question. Thanks for anticipating. That's exactly what i need to do.

You're welcome.  I hope this work or your needs.