Sonic Forms - Deployment
Using the Admin PanelEach time a Sonic Forms Page is added to your RiSE website you need to tell it which Sonic Form to display and what options to use. Because each page has its own unique admin panel you can reuse your Sonic Forms in multiple locations and quickly swap out Sonic Forms variations whenever you need to keep your site fresh and engaging.
To configure your deployment options, you use the Sonic Forms Admin Panel. It uses a page-specific configuration file to set and retain various form parameters. To access the Admin Panel, you must be logged into your RiSE website with the SysAdmin Role. Users with this role will see the blue bar which allows you to view and hide the configuration panel settings.
Simply click anywhere on this bar to expose the Admin Panel.
Select Form and Preview
You can select any form from your form library to deploy. Use the Preview option to confirm that you are deploying the correct Sonic Form from your library on the page.
The following validation features are set at the page level:
- Page Title – Overrides the page title displayed in browsers.
- Message on Success – If the submit button does not take the user to another page, this global message is displayed to indicate the outcome of the Submit process. Default message is “Successfully updated.” If you have button-specific messages they are appended to this message if it is used.
- Message on Failure – This global message is displayed to indicate the outcome of the Submit process. Default message is “Form not saved.” You can enter your own form-specific message here if required. If you have button-specific messages they are appended to this message if it is used.
- Validation Summary – The Validation Summary displays a list of messages related to your form fields. For example - Last Name is required, Zip Code is required. Normally these messages are displayed near the bottom of a form (where a Submit button is usually deployed), however, it can also be useful to display your Validation Summary at the at the top of the page or in both locations when designing longer forms.
- US Date Format – Forces the page to use the US date format of MM/DD/YYYY regardless of the user's Windows settings.
- 12-Hour Format - Display time fields in AM/PM format; Otherwise 24-hour format is used.
- Additional Error Message (Top) – when enabled, this option displays system related error messages at the top of the page. The standard location is at the bottom of the page (see Troubleshooting for more details).
One of the most powerful features in Sonic Forms is its ability to invoke a stored procedure when a form is successfully submitted. Stored procedures can be used for any kind of data update or transformation based on the information provided by a user.
- Stored Procedure – Name of the stored procedure in your iMIS database.
- SEQN Table - (Optionally) identifies which Multi-instance Table should be the target of the Stored Procedure and passes that table's SEQN number to the stored procedure for processing.
- Default Country – Default value for the country that will be used by address fields.
- State / Province - Default value for the state or province that will be used by address fields on the form.
Form Change LoggingBy default, Sonic Forms logs all changes recorded as part of a form submission in the standard iMIS log table (Name_Log). You can disable this feature by turning it off if changes recorded by a form are not important or needed for your administrative requirements.
Create Account Features
You can optionally define the following defaults for new accounts created using Sonic Forms.
- Member Type – Any valid member type from iMIS.
- Billing Category – Any valid billing category from iMIS.
- Create Account Form - By default, Sonic Forms will create a new account and then immediately sign-in the new user when successful. If you are using a Sonic Form to allow for 3rd party accounts to be created (e.g. a Company Administrator creating accounts for their employees) then you can enable this option to allow a user to create accounts without logging them in which allows them to continue to create additional accounts or perform other activities in iMIS.
- Auto Assign Company - This option is used with the Create Account Form option to automatically assign a newly created user to the same company as the person who is creating their account. For more information see also Create Account Features.
Duplicate Check OptionsSonic Forms can help you to avoid duplicates when you are creating new accounts.
- Duplicate Account Message – An optional friendly message for duplicate accounts. Default message is “Sorry – your account is already on file - please reset your password to gain access to your account.”
- Proceed Anyway Option – Option to override duplicate checks and permit a new account to be created. Selecting this option requires that new accounts be reviewed for duplicates and merged if necessary.
- Duplicate Check –
- Simple - The Simple duplicate check validates only if the user's email is on file already.
- Advanced - The Advanced duplicate check executes a stored procedure to evaluate if the user meets your organization's policy for duplicate management. This stored procedure is called "va_CheckForDuplicateAccount" and is automatically installed when you activate Sonic Forms. See Advanced Duplicate Check for more information.
- None - do not send an email on submission.
- Notification Only - send an email which just provides a notification to the administrator.
- Notification and URL - send an email which includes a customized link to a designated page where the user's submission can be viewed. Requires login to your iMIS website.
- From: The "From" address for the email - this address must be a valid address on your SMTP server.
- To / cc / bcc - Specific email addresses to send the notification to. Multiple addresses can be added separated by a comma.
- Subject - Subject Line for the email.
- URL - Used with the "Notification and URL" option to define the target link for review of the form submission. This link can accept parameters if they are provided to the form via the URL. For example:
The "@ff@" prefix is a token indicator which defines the field name to use as taken from the URL or the form submission.