About configuration administration
Configuration allows you to customize a wide range of ClearView components to better meet the needs of your organization and users. Access the Configuration portion of administrative features through the Administration link on the user menu drop-down list.
As a ClearView Administrator, you can configure various elements of the application, including:
Application Settings
(Click image to enlarge)
|
Configure application-wide settings, such as database configuration and Reports Server URL settings.
Application Settings Summary
Approved QRYMAIN |
The list of query transaction numbers (comma delineated) accessed in the PledgeMaker database that the tenant can use in ClearView.
Queries can be applied to Prospect Search parameters within the Filter By field. The Filter By lookup includes a Query ID field. For users to apply queries within that field, queries must first be listed in this application-wide settings field.
|
Jasper Server Organization |
The organization name value to authenticate a given tenant into Jasper Server. |
Maximum Exported Rows |
Maximum number of rows we’ll allow the application to export from a data table. |
VAE IE8 Inline Edit |
Whether or not older versions of Internet Explorer, namely IE8, should enable the inline edit capability of VAEs.
Allowing inline editing when using a dated browser could potentially slow down performance.
|
Opportunity Next Action Required? |
The creation of a new Action record while creating an Opportunity is configurable to be either mandatory, optional, or not present on the form at all.
|
Filter Preferences for Solicitor Field |
When a user applies a Solicitor field filter to a data table, or filters by "Mine" on a dashboard panel, this setting indicates if the filtered results are associated with the prospect record's solicitor code or the transactional record's solicitor code.
|
Filter Preferences for Unit Field |
When a user applies a Unit field filter to a data table or a dashboard, this setting indicates if the filtered results are associated with the prospect record's unit code or the transactional record's unit code.
|
View Preferences for Work with Opportunities |
When a user accesses the "Work with Opportunities" data table, this setting indicates if a default filter is applied to that data table, and the configuration of that filter.
Select a default from a list that includes all standard views for that data table, as well as any modified or custom views that have been built using the Data Table Views configuration feature.
|
Opportunity VAE Fund Code Default Value |
For Opportunity records, this setting applies a default value to the Fund field.
If left blank, the user must input a fund code to this required field. When modifying Opportunity VAE configuration, fundCode cannot be included for this setting to register.
|
Opportunity Designations Required |
When creating an Opportunity, set whether or not the Designation section is required, optional or hidden.
|
Show Unit Filter on Dashboard |
This setting indicates if the Unit filter will be displayed on a Dashboard.
The Unit filter is a feature utilized by organizations that use a Unit structure. If your organization does not use Units, the unit filter will be empty.
|
Version of Jasper to use |
Set which version of JasperSoft to be used.
|
Hide Unit Levels |
This setting allows you to enter a comma-separated list of Unit Levels to be hidden from the Unit filter list.
|
Show Unit Statuses |
This setting allows you to enter a comma-separated list of Unit Statuses to be displayed in the Unit filter list.
|
Complete Action Default Status |
Set a default status to use when completing an action.
|
|
Assign Menus
(Click image to enlarge)
|
Configure what items are available from the navigation menu. Assign items by role, or make them available to the entire organization.
If a user has ever configured their own navigation menu settings, their own configuration take precedence. To receive the administrative configuration, the user can Restore Defaults through Navigation Menu Settings, and any administrative assignments will be applied to their navigation menu upon saving the default settings.
If a user is in multiple roles, and each role has been assigned a navigation menu configuration, the user gets the union of the menu items from each configuration, automatically eliminating double assignments of menu items with the same name.
|
Data Table Defaults
(Click image to enlarge)
|
Set which columns are displayed for each data table, the order in which they are displayed, and how content within each column is sorted.
|
Data Table Views
(Click image to enlarge)
|
Configure and edit custom data table views, and modify standard views according to the needs of your users. When creating a new view, the View drop-down list on any applicable data table is where an end-user will be able to access the view and apply it to data table results.
Both full-page data tables and applicable dashboard panels respect any modifications you make to standard views. For example, any changes to the standard All Closed view will also be reflected in the records included in the Opportunities Closed dashboard panel.
Data Table View Locations Summary for Custom Views
Everywhere |
The custom view will be available on all applicable data tables across the application.
|
Organization Wide |
The custom view will be available on all data tables that compile organization-wide data, as opposed to data tables that are specific to a particular prospect or opportunity record.
For example, applying an organization-wide custom view to the Action data table will appear in the View drop-down menu when accessing that data table from an actions-related panel, since that data table can include data for multiple prospect records. However, the view will not apply to Action data tables accessed from the Go To menu of a specific prospect record.
|
Opportunities |
The custom view will be available on the applicable data table associated with opportunity records.
For example, applying an opportunities custom view to the Gift data table will appear in the View drop-down menu only when accessing the gifts data table in relation to an opportunity record.
|
Prospect Records |
The custom view will be available on the applicable data table associated with prospect records.
For example, applying a prospect record custom view to the Mail data table will appear in the View drop-down menu only when accessing the mail data table in relation to a prospect record.
|
|
Go To Menu Settings
(Click image to enlarge)
|
Select what related records are accessible to your users from prospect, opportunity, gift and planned gift record pages on the Go To sidebar menu.
|
Labels
(Click image to enlarge)
|
Change or update how your labels are displayed. Labels are the text associated with a field. All labels are set to ClearView application defaults unless organizations choose to configure labels to meet their own needs.
|
Lookup Context Configuration
(Click image to enlarge)
|
Configure lookups in several locations to only display values that are most relevant to the needs of your users. Configurable lookups tables include: Appeals, Campaigns, Funds, Solicitors, Stage (status), and Address / Email / Phone types. Lookups can be configured on a global or a much more precise scale.
Applying a configuration to a Global Location affects the lookup table across the application. Configuring a more precise Location, (i.e. the Solicitor Code Lookup associated with Gift records), only affects that specific lookup table. The most granular configuration overrides any global configuration; for example, if a global lookup configuration is applied to Appeals lookups, but a more precise lookup configuration is applied to the Action record lookup for Appeals, the more specific configuration for that particular lookup prevails.
If a code needs to be used that is not included in the lookup configuration for a field, a user can still manually enter a code into any field and it will be accepted.
Configurable Lookup Locations
Configure any of these lookups to only display the codes that are currently applicable to your ClearView users:
Global - Addresses
- Global - Appeals
- Global - Campaigns
- Global - Funds
- Global - Solicitors
- Global - Status
- Action - Action Owner
- Action - Appeal Code
- Action - Fund Code
- Action - Status Code
- Additional Demographics - Solicitor Code
- Address - Type Code
- Email - Type Code
- Gift - Appeal Code
- Gift - Full Amount
- Gift - Solicitor Code
- Greetings - Solicitor Code
- Naming Opportunities - Fund
- Opportunity - Appeal
- Opportunity - Fund Code
- Opportunity - Solicitor Code
- Opportunity - Stage
- Phone - Type Code
- Prospect - Solicitor Code
- Prospect - Source
- Volunteer - Solicitor Code
|
Quick Actions Settings
(Click image to enlarge)
|
Select what capabilities are accessible to your users from prospect, opportunity and contact record pages on the Quick Actions sidebar menu.
A user will only see a link if they have the correct security privileges relative to the destination page of the link. For example, if a user does not have reporting privileges, they will not see the Donor Profile Report link, even if it is set to display.
|
Reports List
(Click image to enlarge)
|
View a list of reports from ClearView Business Intelligence and make them available to users. Each report has actions associated with it for configuration and running.
Report Library Administration (folder-based)
Administrators can now create folders and assign reports to them so that similarly used reports can be found in the same location. . All of these folders, except for Unassigned, can be renamed or deleted if other report folder names are preferable.
Use the Synchronize Reports Repository feature and easily update the ClearView reports list to match the BI repository, making accessible in ClearView the most recent public reports available.
If a report is not available, check with your ClearView instance administrator to ensure that the report was made available at the instance level.
|
Send Email Configuration
|
Set the defaults for action records created using the Send Email quick action from a prospect record.
|
System Code Mapping
|
Map your organization-specific codes to ClearView application-specific category types so that the application can associate user-made codes with application-level defaults.
|
User Options
(Click image to enlarge)
|
User Options are application settings and preferences stored in ClearView. Some are organizational settings; rules for creating track actions associated with Opportunity records, for example, are stored as user options. Others are security group preferences, such as whether or not to allow users to access the ClearView Business Intelligence Reports Repository. Some are individual user preferences; the default email address for each user, for example, is stored as a user option. User Options are only for settings and preferences, and are not used for storing any prospect-related data.
It is not possible to define new options using User Options or any other administrative feature. New options can only be created by our SofTrek Development team; contact Client Solutions for more information.
While some options can be changed using the User Option feature, other options can only be viewed. Some options must be set according to very specific rules which cannot be enforced by this general utility. Some options can be changed where they were configured; for example, user Email addresses can be changed by individual users using the Change Email feature found in Settings. Other options are sensitive or special in various ways, and can only be set by a Client Solutions representative. User Options containing confidential information cannot be viewed with this feature.
User Option is a feature intended only for the owner account. Incorrect changes can make ClearView unusable. Using this feature is not recommended without support from Client Solutions.
|
VAEs
(Click image to enlarge)
|
VAE stands for “view-add-edit” screens. Change the configuration of your VAE records, including the order of fields displayed, and add or remove fields. Easily revert to SofTrek default configurations when needed.
|
|