Placing and using buttons on pages.
Each submittable (non-Confirmation) page has a Submit Button. When clicked, the application sends answers from that page to the database and checks the application for the next page to display (Display Condition field on the page).
Unlike other elements it is automatically given the name Submit Button (a name is required). The label of the button is set to Submit and can be changed to any value.
Besides the button that is added automatically with a Page, other buttons can be added. There are four different Button Types, Submit Page, Previous Page, Save for Later, and Custom.
Submit Page - default for Submit buttons. See description above.
Previous Page - returns you to the previously submitted page. It skips over pages that were not visited based on Display Condition.
Save for Later - submits the current page with current answers completed and ignoring any other validations. Submission is saved in Draft status.
Custom - allows you to add an Event that acts on Click of the Button. See the article on Events for possible actions.
Display - Please see this section.
Render Attributes - Please see this section.
- How to use the builder to create and maintain Forms for Request.
- Form Details and Advanced Properties
- Create and Maintain a Page Object
- How to add and maintain Section Objects on Forms for Request.
- Text and HTML
- Create and maintain Text content and HTML content elements for a Form.
- Checkbox Field
- Add and maintain a Checkbox field
- Date Time Fields
- Create and Maintain a Date/Time Element
- Dropdown Field
- Creating and maintaining list fields with both hard-coded data and dynamic sources.
- Radio Button Field
- How to create and maintain the details of a Radio Button field.
- Text Field
- Create and maintain Text fields for a Form.
- Setting the Visibility of fields and other elements.
- Checking for the presence of values/answers on submission of a Page.
- Render Attributes
- Add display attributes for fields and other elements.
- Save and Exit
- By default, the save button saves, but doesn't exit. This article reviews how to set up a button to save and exit to a desired location.
- Add a button next to submit
- There are occasions where users wish to add a button to the bottom of a request next to the "Submit" button. This is usually a Cancel button but can be any button. If the button were any place else in the Request the solution would be as simple as just adding a text question with html for a button. Since the "Submit" button is outside the div which contains the questions, the solution requires a different solution.
- Extra Submit Button
- A customer requirement was to put the Approval Section/Questions at the top of a Service Item which is no problem. However, as their Service Item contains many questions they wanted to add a second Submit button below the Approval Section/Questions in order to give the approver a better/easier experience.
- Reorder the Elements of a Service Item
- Sometimes the elements of a service item (the items in the Pages tab of the Service Item in the Service Catalog Console) can end up "out of order" because one or more element has the same id (sort order) as another element. This will prevent you from moving elements on the page properly, etc. Fixing these duplicate element numbers has always before been a manual process of updating the KS_SRV_ContentsElementHTML form's sortOrder value for the duplicate and all subsequent elements, which can be very time intensive. This service item and handler automates that process of fixing the elements' sort orders.