The Manage Jurisdiction Configuration page allows Administrators to update and add configuration settings to their OAS installation. These additions are primarily used for integration requirements. Updates made in this screen will be written to the database when saved.
The following fields are listed on this page:
Jurisdiction Name (Required):Friendly name of jurisdiction OAS installs. It will be used as the title for the OAS install in the UI, emails, etc.
Jurisidiction Slug (Required): A slug is a human-readable version of a primary key, a unique identifier, in this case, for the jurisdiction.
Description: The text and the graphics that will appear in the Jurisdiction Configuration page and will display on the Jurisdiction Login selection page.
ProjectDox URL (Required): The full URL to the ProjectDox install.
ProjectDox Security Token (Required): Th security token to ProjectDox component install.
ProjectDox Components URL (Required): The full URL to the ProjectDox components install.
ProjectDox Web API URL (Required): The full URL to the ProjectDox web API install.
Integration URL: The full URL to the permitting integration web API install.
ProjectDox User Name (Required):Email of an account dedicated to communicating from OAS to ProjectDox. This account should be an SA and not change.
ProjectDox Password (Required): Password of an account dedicated to communicating from OAS to ProjectDox. This account should be an SA and not change.
Contact Name (Required): Name of the person/department that should be displayed in UI when appropriate.
Terms and Conditions (Select List): Terms and Conditions is an optional step. By this blank, an applicant user will be navigated directly to an application instead of having an extra step to agree upon terms and conditions. If a piece of custom content is selected, however, the user will be presented the Terms and Conditions page. The default value is “Terms & Conditions.”
Is Active (Checkbox): This checkbox determines if the jurisdiction OAS account is active or not. If checked, users can access the OAS application. If unchecked, users will not be able to access it.
Save Username (Checkbox): This checkbox, if checked it will save the email address in a cookie and auto-populate the login text box of the OAS login.
Permit System Provider (Select List): The configured permitting for the jurisdiction.
Binary Namespace (Required): The name of the DLLs that will be uploaded for the custom forms (if applicable). This is used so that someone can’t upload anything to the OAS bin folder. Case-sensitive.
Custom Path (Required): The folder name that holds all the custom files for the jurisdiction. This folder holds CSS, JavaScript, custom forms specific to the jurisdiction.
Payment Configuration: This information will come from Avolve development. All the configuration data associated with the selected payment provider. This contains all the settings and properties that are required by the payment provider.
You must add the Payment
URL to successfully submit an application. This will be different
for each jurisdiction and should be supplied by development or the
Business Analyst.
Password Regular Expression (Required):The regular expression that the password must conform to when a user creates or edits an account password.
Password Validation Message (Required):The message to tell the user what format the password must conform to.
CC Emails (comma-separated): Comma-separated list of email addresses that will receive emails when an error occurs in application submission.
Google ReCAPTCHA Site Key: Used to display the reCAPTCHA widget on your site. Must be obtained from your Google developer account.
Google ReCAPTCHA Secret Key: Used to display the ReCAPTCHA widget on your site. Must be obtained from your Google developer account.
Enable Login ReCAPTCHA (checkbox): Adds a ReCAPTCHA widget to the login screen.
Enable Account Create ReCAPTCHA (checkbox): Adds a ReCAPTCHA widget to the account creation screen.
Country (required): Select the country of the jurisdiction.
