These settings control how Acoustic™ Tealeaf cxView is configured.
These cxView settings control creation of user accounts, password policies, and default user settings.
Setting | Description | Default |
---|---|---|
Automatic User Creation |
If NT Authentication is enabled, this option allows new users to have Portal accounts automatically created on first login. | Enabled |
Automatic User Creation Settings Prompt |
Enables first-time users to specify their user settings immediately upon login. | Disabled |
Event Selector Dimensions |
The initial size for the Event Selector. | 2x1 |
Login Page Language (Global) |
The language used on the global login page. After the user logs in, the user's preferred language is known. | English (US) |
Minimum Password Length |
Minimum password length for user passwords. Portal passwords can have a maximum length of 32 characters. | 3 |
New User Default Page |
The default start page to assign to automatically created users. | Default Dashboard |
New User Default Time Zone (used in Search |
The default timezone to assign automatically created users. This setting is used for display in search. By default, this value is set to the Tealeaf system time zone. | System time zone |
Previous Password History (Count) |
Number of unique passwords a user must have before reusing a password. | Disabled |
Previous Password History (Days) |
Number of days that must pass before a user can reuse a password. | Disabled |
Require Strong Passwords |
Require passwords to meet the 'strong password' requirements. Strong password requirements:
|
Disabled |
User Default Group |
The user group to assign to automatically created users, one for each role: cxImpact, cxReveal, or cxView. | cxView User |
Use these settings to configure schedule retention, dashboard distribution, and scorecard data retention.
Setting | Description | Default |
---|---|---|
Data Trimming |
When Enabled , scorecard data is trimmed according to the configured trim settings.
Note: This setting does not affect data trimming for base cxImpact data, which is stored and managed independently of scorecard data.
|
Enabled |
Schedule History - Days Retain |
The number of days to retain the history of scheduled scorecard runs. | 30 |
Scorecard Data - Days Retain |
The number of days to keep Day scorecard calculations. | 365 |
Scorecard Data - Months Retain |
The number of months to keep Month scorecard calculations. | 24 |
Scorecard Data - Weeks Retain |
The number of weeks to keep Week scorecard calculations. | 104 |
Scorecard Email - Attach HTML |
Attach the scorecard HTML as an attachment to the e-mail. | Disabled |
Scorecard Update Frequency |
Frequency in minutes when scorecards are updated with data from the database. Default value is 60 minutes. You may also set the frequency to 5 minutes, which is the rate at which the Data Collector gathers data from the Processing Servers and aggregates and inserts it into the reporting database.
Leave this value at 60. Updating scorecards every five minutes can impact performance. |
60 |
Temporary Directory |
The temp directory for any scheduled reports that generate PDFs, relative to the directory in which the Tealeaf Data Service is running.
|
. |
- Login to the Portal as an administrator.
- From the Portal menu, navigate to Portal Management.
- In the left panel, click cxView Settings.
- Select the category that applies.
Migrating reports, scorecards, and dashboards
Use this workflow to migrate reports, scorecards, and dashboards from one system to another.
- Create Report Builder reports with all of the events that you want to migrate.
- These reports must contain events that are used by any dashboards or scorecards that you want to migrate.
- These reports do not have to be actively used in your Tealeaf environment; the purpose of creating these reports is to bundle up sets of events, which are migrated with the report.
- Export all Report Builder report templates that you want to migrate or that contain events you want to migrate.
- Import them into the destination system.
- Verify that the events and related event objects are properly imported.
- In the source system, you can choose to export scorecards and dashboards. Follow the Export Template Steps.
Note: In general, re-create scorecards and dashboards in the destination system. However, in some cases, it can be problematic to do so. Issues can occur during the import of these items, which do not affect the events that are already imported through Report Builder reports.
- Import them into the destination system.
Forcing scorecard recalculation
You can also apply previously calculated data to redefined scorecards. You must have administrator permissions to perform this task.
For example, if you switch a scorecard definition to use a new event, you can force a recalculation of all scorecards by using the available historical data.
The number of days that you extend the scorecard calculation range in the past is directly correlated to how long the recalculation takes. Depending on the length of time and number of scorecards in the system, this recalculation can impact system performance.
If possible, you should conduct lengthy recalculations during off-peak periods.
- From the Portal menu, navigate to Portal Management.
- Click CX Settings.
- Click the Data Retention link.
- Review the value for Reporting Data (daily)-Days Retain.
- This setting determines the maximum amount of reporting data that is retained in the database. Typically, this value is set to 365.
- If the Tealeaf system was installed after the date indicated by this setting, you must calculate elapsed days since the first installation. Use the smaller of the Reporting Data (daily)-Days Retain value or the elapsed number of days since installation.
- Using Excel, you can calculate the following date: Today
This date is used in the following steps to configure the date from which the next scorecard recalculation begins.
- In the Portal menu, select Configure > Scorecards.
- In the left panel, click the Data Management entry.
- Click the Aggregation Dates link.
- For the Last Interval for Scorecards (SID=5/Day) entry, click the edit icon.
- Click the Date field. From the Calendar tool, select the previously calculated date.
- Click Save.
If the Data Collector's next run is at the top of the subsequent hour, all scorecards in the system are recalculated from the specified date to the current hour.