This is typically implemented as a LiveCycle orchestration:
- Form 1 is completed and submitted to a LiveCycle orchestration on the server
- The orchestration saves the submitted data to the database and then uses it to pre-populate Form 2
- Form 2 is sent to the user
Common options for these steps include:
- Submission by email using a LiveCycle email end-point or secure, seamless submission by HTTPS to a web component (e.g. servlet or ASP.NET page) that calls the orchestration as a web service using the LiveCycle SOAP end-point
- Form Pre-population is performed using Forms Data Integration (FDI) or LiveCycle Forms
- Form is sent to user either by email or streamed back in same session if using HTTPS
Avoka Technologies provides a pre-built web component Process Invoker that makes it easy to implement the HTTPS submission option.
Of course, if the forms are filled out by the same user, you could merge them into one form and collect all the data on the client side before submitting to the server. You can even use show/hide to give the user the experience of filling out multiple forms if that is desired.
Ben Walsh
www.avoka.com