Configure Global System Settings
Global System settings/defaults control how CSM looks and behaves by default for all CSM Users. Use the System Settings window in CSM Administrator (Settings>Edit System Settings) to configure the following Global System settings:
- Global Search settings: Full Text Search, Quick Search, and Knowledge Search settings.
- Global Display settings: DPI/Scaling settings, Multiple Monitor settings, and an OOTB theme.
- Global Dashboard, Calendar, and Visualization settings: OOTB Dashboard, HUD, Calendar, and Visualization.
- Global Catalog settings: Whether or not to store primary system definitions in a local catalog file on a User's machine, to allow Users to decide whether or not use a definition catalog, and to force catalog files to be rebuilt each time a User restarts a CSM Application.
- Global Rich Text settings: How images are stored and displayed in Rich Text Fields, and a default font for Rich Text.
- Global Record Locking settings: General Record Locking settings, OOTB Record Locking settings for all Major Business Objects, and Portal Record Locking settings.
- Global Help settings: Help system settings, and whether or not to globally enable/display Process and Terminology Help for Business Objects and Fields.
- Global Advanced settings: Dashboard Widget refresh, system notifications, and web service call settings.
Good to know:
- Global and Role settings are initially configured in CSM Administrator. If a User has security rights, he can override many of the Global/Role settings (ex: Display, Task Pane & Search, Dashboards & Calendar, User Info, E-mail, Grids, etc.) and configure his own personal User settings.
- A system administrator can clear Role and User defaults (for a specific User/Role or all), resetting the defaults to the Global-defined settings (File>Clear Settings in the User Manager or Role Manager).
- Global database settings, Global security settings, and many integration settings are defined in a CSM Administrator Blueprint and cannot be overridden by a User.
- Some setting changes do not take effect until a User logs out/logs back into the CSM Desktop Client. In some cases (ex: Record locking settings), a settings change requires logging out all Users, resetting IIS, and restarting the Application Server.