Join us on May 14-15, 2019 at Forrester Digital Transformation & Innovation 2019 in Chicago, USA.
Figure 1: Multi Paged Form element
Figure 2: Multi Paged Form Properties
|Number of Pages||Number of pages to be presented in Integer.|
|AJAX Rendering?||Renders page only when clicked. This option improves loading times if end user does not use all the forms and number of pages is large.|
Figure 3: Multi Paged Form Properties - Page
Page name displayed in the form of breadcrumb or tab, depending on its setting in the UI.
Determines if the page is editable.
|DIsplay field as Label when readonly?||Displays the value of the element as plain text when element is set to "Readonly".|
|Parent Form Field to keep Child Form ID|
ID of the field in the parent form to store the page's primary key. Page data will be loaded based on the record ID retrieved from this field.
|Child Form Field to keep Parent Form ID|
ID of the field in the page form to store the parent form's primary key.
|Validate when change page|
Performs validation upon changing pages if checked.
Important Note about Parent Form Field to keep Child Form ID
This field must be specified if the individual form is not storing into the same table as the parent form.
Field specified does not need to be first created in the parent form.
Figure 4: Multi Paged Form Properties - Advanced Options
|Partially store form when page changed?||Partially store form when user navigates between pages.|
Store main form data when partial storing is enabled?
Store main form data when partial storing is enabled.
This option is available when "Partially store form when page changed?" is enabled.
Determines if the multi-paged form will be displayed in wizard or tabs.
|Previous Button Label||Previous Button Label.|
|Next Button Label||Next Button Label.|
|Only enable submit button on last page?|
If checked, all of the pages' forms must be completed before form submission or task completion.
Custom CSS implementation.