How to create multiple screens in a workflow.

Hi All,

I am having a requirement that I need to create Multi-screen form in my workflow.

The scenario:

1. In the initial form Name, Age and Gender with "Next" and "Cancel" buttons.

2. When I click "Next" button in the coming screen, I am having few more form fields(inputs) with "Next" and "Cancel" buttons.

3. Now when I click "Next" button coming screen will show the summary of all the details given in previous two screens.

Please anyone help me on doing this.

Thanks in advance!!

Find more posts tagged with

Comments

David Smith

Your screen name is ironic. You'd likely have to get creative with cgitasks at the start of your workflow rather than being able to implement a multi-paged instantiation form. I don't think you can do that.

Adam Stoller

You didn't indicate if this is for WFT or WFM - I'm going to assume WFM.

The WFM instantion form limits the number of "items" that can appear on a "page" in the window (I don't remember the default limitation), such that you could do something like what you want by ensuring that the first two "pages" have the maximum number of items on them to force pagination (for FormsPublisher DCTs you can define the items-per-page on a DCT-by-DCT basis in the templating.cfg, not sure if/where you can do this for WFM)

Alternatively, you could try using the <tab> element within the custom instantiation form to create multiple pages that way and could use callout buttons to try force focus from one page to the next, etc. via FormAPI - which you would also use to present the resulant summary information on the last page. However, (A) you wouldn't be able to [easily / in a supported manner] remove the OOTB buttons for instantiating the workflow from the window; and (B) you'd have to play around with required fields and such to prevent the OOTB buttons for instantiating the workflow until the user has completed the second and perahps third pages in your scenario.

Or - you could do what Smitty suggested and perform the information gathering in a custom CGI task at the beginning of the workflow (this strategy would work with WFT too)