User-Specific Settings

Use

This function enables you to make specific system settings for specific users. This means that user-specific default values are stored for specific fields, and, consequently, that all of the data that the same user reports on can be compared against each other.

Example Example

You always work in plan version XY and organizational unit 123. If you make the appropriate settings, this data will be proposed automatically by the system at the relevant points.

End of the example.

User-specific settings can be

  • Permanent (that is, they apply to all terminal sessions)

  • Temporary (that is, they only apply to the current terminal session; in this case, any permanent settings are overwritten temporarily)

All user-specific settings apply until they are changed by the user. Any changes (specifying a different plan version, for example) are stored temporarily as user-specific settings.

Example Example

Examples of where user-specific settings can be used:

End of the example.

  • You always work with the same settings and objects (plan version, for example, or organizational unit, etc.) - in this case, you would make permanent user-specific settings.

  • You nearly always work with the same settings and objects (plan version, for example, or organizational unit, etc.) - in this case, you would make permanent user-specific settings. You are going to use different settings and objects for a specific terminal session - in this case, you would make temporary user-specific settings. During a terminal session, you can switch back from your temporary settings to your permanent settings. The next time you log on, your permanent settings will be proposed.

  • Every time you log on, you use different settings and objects. For one particular session, though, you are going to use specific settings. In this case, you would store temporary settings, not permanent settings.

You can change all user-specific settings, regardless of whether they are temporary or permanent. The last value you define is always proposed. The next time you log on, your permanent default settings will be proposed.

Features

In your user-specific settings, you can define default values for the following settings and objects:

Parameter

Standard Setting

Plan version

Integration plan version

Evaluation period (reporting period)

Start date: current system date

End date: highest system date (12/31/9999)

Include alternative qualifications

Alternative qualifications are disregarded

Include essential requirements

Essential requirements are disregarded

Disregard depreciation meter

Depreciation meter values are taken into account

Organizational unit

 

Display vacant positions only

All positions are included

Appraisal model

 

Object type of appraiser

User (if allowed)

Object type of appraisee

User (if allowed)

Note Note

If you take essential requirements into account, the system distinguishes between essential requirements and optional requirements in career and succession planning. In this case, the system does not select objects that do not meet the essential requirements. (This setting does not affect the Find Objects for Qualifications search function.)

If you specify a default organizational unit, you must also specify a plan version.

If an integration plan version is defined in the system, and if a chief position is defined for a user (person) in the organizational plan, the appropriate organizational unit is defaulted for this user.

These settings for alternative qualifications, essential requirements, depreciation meter values, and vacant positions can be made or changed only in the User-Specific Settings .

End of the note.

You can make more settings using the User Parameters in Personnel Development .