👁️General Settings

This page can be found in the SSP Admin panel

System wide settings of the Service Catalog are configured in the General Settings page of the SSP admin page (/Common/admin/settings.aspx). Make sure these settings are checked and correct for your setup.

General behavior

All settings on this page are global settings that determine which functionality is available to service templates.

• If a setting is disabled here, the related functionality will never be available in any template.

• If a setting is enabled here, each individual template can still decide whether to use this functionality.

• Template-level configuration can only offer options that are enabled at this global level.

---

Settings Overview

Setting	Help text
Locations parameter	Selects the parameter set that defines available locations. This parameter must contain at least the fields Code, Name, City, Region, and Division. Locations are used to associate services with physical or organizational locations.
Assignment & routing types parameter	Defines the available assignment and routing types that can be used when assigning services or requests. The selected parameter must include at least Code and Label.
Target types parameter	Specifies the parameter that defines different target types. The parameter must include at least Code and Label.
Target priorities parameter	Defines the available priority levels for targets. The selected parameter must include at least Code and Label.
Time zones parameter	Selects the parameter that defines supported time zones. The parameter must include at least Code and Label and is used for time-based calculations and display.
Notes closure codes parameter	Defines the closure codes that can be used when closing notes. The parameter must include Code and Label and supports language-dependent labels.
Default trigger setting for data to send to workflow	Defines how much service data is included when a workflow trigger is fired. Minimal: Only the service GUID is sent. The workflow must explicitly retrieve any additional data it requires. Basic: The service GUID and all configured data parts are sent to the workflow. Extended: The complete service object is sent, including all data parts and related information.
Do permission check on uploaded documents?	Determines whether user permissions are validated when documents are uploaded. When enabled, only users with sufficient rights can upload documents.
Use search indexes	Enables the use of search indexes to improve search performance and response times when working with services and related data.
Use outages	Enables outage registration for services. An outage records a start and end time indicating when a service was unavailable. Outage data can be used in dashboards to show how often a service was unavailable and to provide overviews of services that are currently not available.
Use relations	Determines whether services can be related to other services. No: No relationships between services are supported. Hierarchical: Relationships have a defined parent–child structure. Flat list: Services can be related without defining hierarchy.
Use knowledge articles	Enables the use of knowledge articles within the service catalog. A knowledge article is a specific type of service. When hierarchical relations are enabled, a knowledge article can only be linked as a child service. If there is no clear purpose for knowledge articles, it is recommended to disable this setting.
Use subscriptions	Enables subscription management for services. Subscriptions link persons to services to indicate that a person receives the service. This also affects Request Forms behavior: • Subscribed persons do not see Add forms. • Subscribed persons see Update and Delete forms. • Non-subscribed persons only see Add forms.
Use "changed since publication"	Enables a warning message when editing a service that has been changed since its last publication. If any service parts or components were modified, a notification indicates that a new publication is required.
Edit service: use unique id	Enables a system-generated unique identifier for services. The unique ID is automatically generated and cannot be modified.
Edit service: use tags	Enables the use of freely entered tags on services. Previously used tags are suggested while typing to promote consistency. Tags are primarily used for categorization and search.
Edit service: tags always in lowercase	Ensures consistency by automatically converting all entered tags to lowercase.
Edit service: use icon	Allows an icon to be uploaded for a service for visual identification purposes.
Edit service: use banner	Enables a banner field on the service edit screen, allowing a banner image to be uploaded per service.
Edit service: show current state	Displays the current publication state of the service (Published, Unpublished, or Retired) on the edit screen.
Edit service: show contract tab	Displays the Contract tab on the service edit screen. This tab defines which organizational units deliver and receive the service. The structure shown is derived from Admin → Adapters → Person Data.
Edit service: show targets tab	Displays the Targets tab on the service edit screen. This tab is used to configure SLA targets such as response and delivery times per priority.
Edit service: show support groups tab	Determines whether support groups can be configured in templates.
Edit service: show requests tab	Displays the Requests tab containing the list of request forms linked to the service. If disabled, no request forms can be linked.
Edit service: show notes tab	Enables the use of notes within templates. If disabled, templates cannot offer note functionality.
Edit service: show publication history tab	Displays the Publication History tab showing all previous publication requests. The amount of visible metadata depends on the configuration.
Edit service: "View ticket" buttons link to	Controls the availability of the View ticket button for publication workflows, allowing users to open the related workflow or ticket.
Edit service: show documents tab	Enables document linking in templates, allowing documents to be associated with services.
Auto lock service when unpublished	Automatically makes a service read-only when it is Unpublished. Additional settings can define which fields remain editable during a lock.