General and Other Settings
General Settings
| Name | Example Value | Value Type / Default value | Required | Explanation |
| Approval details | details | text attribute | Yes | The code for a text attribute from the specified Order Template, containing additional information to show in the Approvals list. Note: if the code is not from the Order Template, no data will be visible in the Self-Service Portal. |
Other Settings
Other settings determine miscellaneous other settings like user/person creation, public key settings, etc.
On average, making any changes will take less than 5 minutes to apply to the ESS2.
Following icons are common for all Self-Service Admin settings:
| Icon | Name | Explanation |
 |
Reset | Clicking the reset-icon resets the information on the field to the default value. |
 |
Clear | A field can also has the clear-icon, which removes the fields data and returns it to empty. |
 |
Help | Hovering over the help-icon shows information regarding that specific field/function. |
Note:
Changing any settings will immediately apply those changes to the ESS2!
Other settings have the following fields and options:
| Name | Example Value | Value Type / Default value | Required | Explanation |
| Create persons |
Off | On/Off | Yes |
Specifies whether a missing Person data card is automatically created upon ESS2 access.
Note that this is triggered when the end user performs their first action/interaction inside the system. |
| Create users |
Off | On/Off |
Yes | Defines if missing user is created automatically in ESS2 rest api calls. Note that if value of this property is “Off”, persons won't be created either. |
| Force data card save |
On | On/Off |
Yes |
Forces data card save after comment is added from ESS2. |
| Get help template code |
incident | incident |
Yes |
Defines the template that shall be used when creating incidents from ESS2. |
| Public key client connection timeout |
5000 | 5000 | Yes | Defines connection timeout in milliseconds used when fetching public keys from ESS2. |
| Public key read timeout |
5000 | 5000 | Yes |
Defines read timeout in milliseconds used when fetching public keys from ESS2. |
| Request folder code |
incident_management |
incident_management | Yes |
Defines the folder where data cards are created when the incident is created from the ESS2. |
| Validate person uniqueness only |
Off | On/Off | Yes |
Defines if validation of new automatically created person data card is done only for uniqueness in ESS2 rest api calls. |
| Comment max length |
10000 | 10000 | Yes |
The maximum length of comment. Maximum value is 10000 characters. |
| External URL link icon |
 |
Selected icon from the icon selection window:
|
Yes |
This setting defines default icon used for Group external link. |
| Reference Permission User | example.user | User ID (from Efecte User) | No | A user profile with appropriate permissions to enable visibility of reference attributes in the end-user portal. Reference form fields will contain no values if this is not set. Specifying a user profile will define the permissions that will be used to display all reference data types to the user of the ESS2 portal. The user is separately defined in the in ESM system settings. |
| Show Closed Cases | Off | On/Off | Yes | Enables or disables displaying closed cases in the Self-Service Portal. By default, closed cases are hidden from end users. If turned on, end users can view their closed cases. Closed requests can be accessed via “My Cases” and it is a separate page from the open cases. Remember to configure the closed cases as described in the article “Configuring "My Cases" View” |
| Closed cases cache max size | 10 | 10 | Maximum number of users for which closed cases are cached simultaneously. When this limit is reached, the least recently used entries are evicted. Please note, altering this setting will result in the immediate discard of the current cache. | |
| Closed cases cache expire after access | 120 000 | 120 000 | Defines the time period (in milliseconds) after which an entry in the closed cases cache is evicted if it remains un-accessed. Warning, altering this setting will result in the immediate discard of the current cache. |
|
| Closed cases cache expire after write |
600 000 | 600 000 | Defines the time period (in milliseconds) after which an entry in the closed cases cache is evicted post-write. This ensures that data is periodically refreshed, even when a user accesses their data frequently. Warning, altering this setting will result in the immediate discard of the current cache. |
Table of Contents