Buttons

Updated on

Button Form Parts are action oriented buttons that allow you to drive the form submission process. Buttons can be used to:
 
  • Drive navigation – send the user to another page
  • Submit updates to iMIS – update information in iMIS
  • Invoke procedures – run a stored procedure to perform database functions
 
These basic button features can be combined into combinations. For example, a single button can update iMIS, run a procedure and then send you to a new page.



Here is a summary of the options available for Sonic Form buttons:

By changing a button’s characteristics you can draw more or less attention to the button as part of your design. For example, you may wish to change your “Delete Record” button to have a red background.
  1. Button Text - the label which describes the purpose of the button. The button style and formatting will be picked up from your RiSE template.
  2. Mouse over text – the button will be rendered with additional “alt” text which is displayed when the cursor is held over the button. This can provide additional information to your user about exactly what the button will do if selected.
  3. CSS Class – By default, buttons have the standard iMIS class of “ButtonText” which will pickup the default button style defined for your iMIS website. Using this feature, you  can override this class to:
     
    • Change a button to a hyperlink
    • Change the font or background colour of the button
    • Change the shape or size of the button
By changing a button’s characteristics you can draw more or less attention to the button as part of your design. For example, you may wish to change your “Delete Record” button to have a red background. For more information on using this feature see Formatting Buttons with CSS.
  1. Target URL - this is an optional value which defines where the form should send the user IF the button is processed without error. If error message(s) are shown then Sonic Forms will leave the user on the original page. Here are some examples of Target URLs:
    • NextPage.aspx - Go to the page "NextPage.aspx" which is located in the same content folder as the Sonic Form. No parameters are specified.
    • NextPage.aspx?ID=@ff@ID&SEQN=@ff@SEQN - Go to the next page and pass the ID and SEQN from this Sonic Form into the target page. The "@ff@" coding defines a token value to Sonic Forms.
    • http://myotherwebsite.com/folder/TargetPage.html - Go to a fully qualified URL including a full path designation - no parameters are included.
    • See Linking Forms with Parameters for more information.
  2. Button Options
    • Submit form with validation - This option is the standard (default) use case where all fields are validated on the form and submitted to iMIS.
    • Submit form without validation (save) - This option allows the user to submit partial information and is ideal for a "Save my Work" button on longer forms. All fields that can be saved are accepted and update, however, fields which do not validate are ignored.
    • Do not submit data (cancel/close) – This option is normally used with a Cancel or Close button to allow the user to back out of any changes before they are submitted.
  3. Open New Window on Submit - This option will force a supported browser to open a new window upon a successful submit. A good use case would be a button to "Review Previous Year" which would open a different record.
  4. Global Stored Procedure Options
    • Run global stored procedure - Runs the global stored procedure specified on the Sonic Forms Admin Panel.
    • Do not run global stored procedure - Supresses the processing of the global stored procedure. This is often used with the "Ignore Validation" option when clicking on "Save my Work". It is also useful when designing forms where a user needs to leave a form temporarily (e.g. to complete a membership application) and wishes to return before finalizing a submission.
  5. Show Stored Procedure Message - This option will display a custom error or success message from either the global, targeted stored procedure. For example, the results of a calculation could be displayed. If this is not enabled then the general success or failure message is displayed.
  6. Run targeted stored procedure - This option specifies a stored procedure which can be run when this specific button is selected. For example, on a membership sign-up form a group of buttons could be setup for different member types as follows:
     
    • Join as Regular Member
    • Join as an Executive Member
    • Join as a Corporate Member
Each button in this case would run a separate procedure to set up the correct member type.
Note that when you are developing a form at least one “Submit” button is needed for testing.