Siebel Performance Management Guide > Performance Scorecard Reference >

Performance Scorecard Usability Solutions

This topic provides information and solutions to practical issues for users working with Performance Scorecard.

Edits to the Employee Objective KPI Record by Multiple Users

If multiple users (for example, an end user and an administrator) edit the Employee Objective KPI Record at the same time, the following error message is displayed:

The Selected Record has been modified by another user since it was retrieved. Please Continue. (SBL-DAT-00523)

The Employee Objective KPI view (Administration - Key Performance Indicators screen) is actually accessing the Employee Objective Record. Since Performance Scorecard uses the same record edit functionality as is employed in other Siebel applications, the second user to access the record sees the error message stating that another user has edited the record. It does not matter if the second user is the administrator or an employee; the first user to access the record always has preferential access and the ability to save the change to the database. After the first user steps off the record, the next user can edit the record.

If you get this error message, click OK, step off the record, step back on the record and perform the action.

Last Update Field in the KPI Administration Screen's Global Employee KPI View

The Last Update field provides the administrator with a timestamp of when the KPI was last refreshed or when the KPI value was manually changed. If the KPI is a manual KPI, and the user does not change the value of the KPI, the Last Update field is not updated. If the user changes the value of the KPI for a specific employee, the Last update column is updated. The Last Update value for other employees is not updated unless the values of the employees' KPIs are changed.

The following list provides a summary of this functionality:

• If the actual value of the KPI changes (global or employee specific), then the last Update time stamp is changed.
• If the employee name changes on an employee-specific KPI, then the Last Update timestamp is changed.
• If the administrator clicks Refresh for a Siebel Analytics Request, the Last Update timestamp is updated on the form applet for each employee that is listed in the Global Employee KPI (even if an employee is not part of the list that comes from Siebel Analytics).

Siebel Analytics Web Server Field in KPI Administration

The Analytics Web Server field identifies which Analytics Web Server is being accessed to calculate the KPI. This field is read-only by default. Some organizations may want the administrator to be able specify another Analytics Web Server to calculate different KPIs. In this case, the field properties must be changed to read-write using Siebel Tools. The administrator can then pick a different Analytics Web Server from this field. For more information, see Configuring the Performance Scorecard Dashboard.

Usage of Numbers and Decimals for the Update Frequency?

Only whole numbers may be entered in the Update Frequency field. Decimals and value of 0 are also not valid entries. If you want KPIs to be refreshed more frequently than one day, customization is required.

List of Values and Tracking a KPI

The preconfigured list of values are the only available Tracking frequencies. If you want to track the KPI at a different time interval than what is listed in the list of values, then customization beyond simply changing values using List of Values Administration is required. You must customize the values to actually change the frequency so that tracking occurs at a frequency different than those provided in the preconfigured List of Values.

Fewer Than Expected Employees Listed in the Global Employee KPI View

If you are expecting 100 employee rows to be loaded in the Global Employee KPI view when the KPI is refreshed to Siebel Analytics, but only 30 rows are loaded, there may be a problem with the KPI Request in Siebel Analytics. You can see how many records are being loaded for each refresh in the Data Load view. Check the KPI request in Siebel Analytics, specifically the preview, to make sure that the result set is generating the employees you expect.

Refresh Process for a KPI Takes Excessive Time

The Data Load view shows the refresh task start and end time so you can see if the Siebel Analytics Server is spending an excessive amount of time on a specific KPI Request. Check this view for the time required for a previous load of this KPI. If the previous load time duration is short, then there may be a problem with the Analytics server. Verify that the Analytics server is operating correctly.

Automatic Synchronize and Refresh Processes Do Not Occur

If a KPI that should automatically synchronize or refresh does not seem to be updating according to the specified frequency, check the Repeating Server Job to make sure that the server job is starting and running correctly. For more information, see Scheduling a Repeating Server Job for KPIs. Check the Analytics server to see if the server is functioning properly and that the KPI Request is functioning properly. Check the Data Load view to see when the most recent refresh occurred, and whether the result was successful or produced an error.