There are some fields(text,dialogue list,radio buttons) in 1st tab(Preliminary) and the same fields are in 2nd tab(Final).
If I enter the field values in 1st tab and click on “Move” action button, the same field values should be populated to respective fields in 2nd tab(so user need not to re-enter the values).
Why do you have the same editable fields listed twice? Can the second tab display the first tab values via computed-for-display field? If there are any edits necessary, the user could navigate back to the 1st tab?
The fields are like quisitionairre…need to pass/copy/display the 1st tab field values to respective fields in 2nd tab…edits may not require for 2nd tab.
user doesnt/cannot go back to 1st tab…he has to create another document…there are lots of validation/computations involved before routing to 2nd tab.
This is like ROUTING type of application.
routing from 1st tab(preliminary) to 2nd tab(final) and from here he moves to close-out tab(3rd tab).Am I confusing U!?
So if the user can not go back to the 1st tab and the user can not make edits to the fields on the second tab that are retrieved from the 1st tab, I’d reccomend making the fields on the 2nd tab computed-for-display with the field values set to the fields on the 1st tab. Hope this helps.
I might add that you could use workspace.picklistcollection to open the first form with the editable fields and then as John mentions, use computed for display fields to show the values entered.