Difference between revisions of "Service Manager Settings"

From Hornbill
Jump to navigation Jump to search
 
(43 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;">
+
This document can now be found at its new location in the [https://docs.hornbill.com/servicemanager-config/advanced-tools-and-settings/application-settings/ Hornbill Document Library].
−
__NOTOC__[[Main Page|Home]] > [[Administration]] > [[Service Manager Administration |Service Manager]] > Settings
+
 
−
</div>
+
[[file:hornbill-document-library.png|Application Settings|link=https://docs.hornbill.com/servicemanager-config/advanced-tools-and-settings/application-settings/]]
−
{|style="width: 100%"
+
<!--
−
|- valign="top"
+
{{breadcrumb|[[Main Page|Home]] > [[Configuration]] > [[Service Manager Configuration]] > Settings|Administration}}
−
|style="width:73%"|
+
{{Section|
  
 
== Introduction ==
 
== Introduction ==
−
The various application settings associated with Hornbill Service Manager can be configured in Hornbill administration under '''''Home > Service Manager > Settings'''''.
+
[[file:ServiceManagerSettings.mp4|800px|border|right]]The various application settings associated with Hornbill Service Manager can be configured in Hornbill administration under '''''Configuration > Service Manager > Application Settings'''''. The page below describes some of the more commonly used settings. This is not a complete list and more settings can be viewed within Configuration.
 +
<br><br>
  
−
|style="width:5%"|
+
'''Accessing Application Settings'''
 +
::* Select the Configuration Cog on the bottom of the left hand application menu bar
 +
 
 +
::* From the Configuration Selector choose ''Service Manager''
 +
 
 +
::* Scroll the navigation panel and find the section ''Advanced Tools and Settings''
 +
 
 +
::* Select ''Application Settings''
 
|
 
|
−
|style="width:22%; border-style: solid; border-width: 1px; border-color:#e6e6e6; background-color:#f2f2f2;"|
+
{{rightBox|In This Article|
−
 
+
:* [[#Email Settings|Email Settings]]
−
== Related Articles ==
+
:* [[#Category Settings|Category Settings]]
 +
:* [[#Portal Settings|Portal Settings]]
 +
:* [[#Intelligent Capture Settings|Intelligent Capture Settings]]
 +
:* [[#Request List Settings|Request List Settings]]
 +
:* [[#Request Settings|Request Settings]]
 +
:* [[#Configuration Management Settings|Configuration Management Settings]]
 +
}}
 +
{{rightBox|Related Articles|
 
:* [[Service_Manager_Notification_Settings|Service Manager Notification Settings]]
 
:* [[Service_Manager_Notification_Settings|Service Manager Notification Settings]]
−
|}
+
}}
−
 
+
}}
−
{{#ev:youtube|sMPV58E_ar8|300|right}}
+
{{Section|
 +
==Email Settings ==
  
−
== Email Settings ==
+
===Archiving Emails ===
−
=== Archiving Emails ===
 
  
 
The Shared Mailboxes can be configured to automatically move the email into a folder of your choice.   
 
The Shared Mailboxes can be configured to automatically move the email into a folder of your choice.   
Line 31: Line 46:
 
:- This setting applies to all Shared Mailboxes that Service Manager Users have access to.
 
:- This setting applies to all Shared Mailboxes that Service Manager Users have access to.
  
−
=== Email Authorisation ===
+
===Email Authorisation ===
 
An email can be sent to a user that is assigned an authorisation task.  The user must be a full user and not a ''Basic'' user in order to receive and process the email authorisation.
 
An email can be sent to a user that is assigned an authorisation task.  The user must be a full user and not a ''Basic'' user in order to receive and process the email authorisation.
 
:* ''app.request.sendEmailToAuthorisers''
 
:* ''app.request.sendEmailToAuthorisers''
Line 37: Line 52:
 
:* ''guest.app.authorisations.email.revealOutcomes''
 
:* ''guest.app.authorisations.email.revealOutcomes''
 
:: By default, an option to ''accept'' or ''reject'' the authorization is included as part of the authorization email.  Turning this setting off will remove this option and the user will only have the option to view the authorisation.
 
:: By default, an option to ''accept'' or ''reject'' the authorization is included as part of the authorization email.  Turning this setting off will remove this option and the user will only have the option to view the authorisation.
−
 
+
|}}
 
== Category Settings ==
 
== Category Settings ==
  
Line 78: Line 93:
 
* ''guest.servicemanager.portal.additionalRequestTypes.change''
 
* ''guest.servicemanager.portal.additionalRequestTypes.change''
 
:- The default is 'Off'
 
:- The default is 'Off'
−
:- When the setting is 'Off' customers will not see Changes on the portals requests lists, nor see any configured portal visible Change Catalog Items
+
:- When the setting is 'Off' customers will not see Changes on the portal requests lists, nor see any configured portal visible Change Catalog Items
−
:- When the setting is 'On' customers will see '''All''' new and historic Change records in the request lists on the portals where they are the marked as the customer
+
:- When the setting is 'On' customers will see '''All''' new and historic Change records in the request lists on the portals where they are marked as the customer
 
:- When the setting is 'On' customers will have the option to see and use portal visible change catalog Items for their subscribed services
 
:- When the setting is 'On' customers will have the option to see and use portal visible change catalog Items for their subscribed services
  
−
== Progressive Capture Settings ==
+
* ''guest.com.hornbill.servicemanager.showRespondByDate''
 +
:- The default is `Off`
 +
:- When this setting is 'On' the Respond by date/time will be displayed in the right-hand information box of a request on the Customer Portal.
 +
 
 +
== Intelligent Capture Settings ==
  
 
* ''servicemanager.progressiveCapture.servicedetails.enableSupportVisibility''
 
* ''servicemanager.progressiveCapture.servicedetails.enableSupportVisibility''
Line 99: Line 118:
 
* ''app.itsm.progressiveCapture.customerDetails.showOnlySupportedRequests''
 
* ''app.itsm.progressiveCapture.customerDetails.showOnlySupportedRequests''
 
:- The default setting for this is 'Off'
 
:- The default setting for this is 'Off'
−
:- When the setting is 'On' the analyst viewing the Customer Details Progressive Capture form, will only see the customers request's which have been logged against services which the analyst's team's support.
+
:- This setting determines whether an agent is granted visibility to unsupported customer Requests in the 'Customer Search', 'Contact Search' or 'Co-worker Search' forms in Progressive Capture. When disabled, an agent '''will have''' visibility to unsupported customer Requests, this must be avoided for customers with multiple service desks (e.g. IT and HR).
  
 
== Request List Settings ==
 
== Request List Settings ==
Line 120: Line 139:
 
:- When the setting is off, it is only possible for Service Manager subscribers with the '''Service Desk Admin''' role to see any requests which are not assigned to any teams
 
:- When the setting is off, it is only possible for Service Manager subscribers with the '''Service Desk Admin''' role to see any requests which are not assigned to any teams
  
−
== Timeline Settings ==
+
== Request Settings ==
 +
 
 +
* ''app.request.questions.excludeConditionalQuestions''
 +
:- The default setting for this in 'OFF'
 +
:- When the setting is off, conditional progressive capture questions which were not displayed in progressive capture flows will appear in the '''Questions''' section on the request forms
 +
:- When the setting is on, conditional progressive capture questions which were not displayed in progressive capture flows will not appear in the '''Questions''' section on the request forms
 +
 
 +
== Timeline Settings ==
  
 
* ''guest.servicemanager.request.timeline.showShortPostTitle''
 
* ''guest.servicemanager.request.timeline.showShortPostTitle''
−
:- The default setting for this is 'ON'
 
 
:- When this setting is on, it will display the name of the user who posted on the timeline of the request, when viewing the timeline of the request in the Customer and Service Portals.  
 
:- When this setting is on, it will display the name of the user who posted on the timeline of the request, when viewing the timeline of the request in the Customer and Service Portals.  
 
:- When the setting is off, the name of the user who performed the post can still be viewed by hovering over the image of the user on each post.  
 
:- When the setting is off, the name of the user who performed the post can still be viewed by hovering over the image of the user on each post.  
 +
:- The default setting for this is 'ON'
  
 
* ''servicemanager.request.timeline.showShortPostTitle''
 
* ''servicemanager.request.timeline.showShortPostTitle''
−
:- The default setting for this is 'ON'
 
 
:- When this setting is on, it will display the name of the user who posted on the timeline of the request in the user app, when viewing the timeline of the request.  
 
:- When this setting is on, it will display the name of the user who posted on the timeline of the request in the user app, when viewing the timeline of the request.  
 
:- When the setting is off, the name of the user who performed the post can still be viewed by hovering over the image of the user on each post.  
 
:- When the setting is off, the name of the user who performed the post can still be viewed by hovering over the image of the user on each post.  
 +
:- The default setting for this is 'ON'
 +
 +
* ''guest.servicemanager.request.timeline.availablePostTypes.editPost''
 +
:- This setting determines the type of posts that a user is allowed to edit. By selecting additional post types, this will allow a user to edit their own post in a Timeline, provided that the post has not been liked or commented on.
 +
:- The default setting for this is 'None' i.e. the option to edit a post will be disabled.
 +
 +
== Configuration Management Settings ==
 +
{{bullet1|app.cm.explorer.diagram.expand|These are the entities that can be expanded in the Explorer. The entities with 'false' will have no icon expand/collapse.  If a new entity is added in the future in the Conf. Manager app, and this  object is not updated with the new entity name, then its value will be set to the default value, which is 'false' (i.e. the user will not be able to expand/collapse the nodes for that entity). The entities currently shown in the diagram are Asset, Colleagues, Contact, Attachment, Requests, Services.}}
 +
{{bullet2|Default Settings|
 +
"Asset" : true,
 +
"Colleagues" : false,
 +
"Contact" : false,
 +
"Attachment" : false,
 +
"Requests" : true,
 +
"Services" : true,
 +
"default" : false
 +
}}
 +
 +
{{bullet1|app.cm.explorer.diagram.level.max|The max level shown in the explorer. Min value is 2 (root plus children)}}
 +
 +
{{bullet2|Default Setting|
 +
  3
 +
}}
 +
{{bullet1|app.cm.explorer.items.dependencies|This setting holds the possible dependencies that can be set between two entities. The possible entities are Asset, Colleagues, Contact, Attachment, Requests, Services. The property "defs" hold all possible list of values.  To associate a list to two linked entities, you must add a property by following this rule: From + entity1 + To + entity2, where entity1 and entity2 can be any value chosen from Asset, Colleagues, Contact, Attachment, Requests, Services. If the two entities are the same (for example 2 assets), then you may define the list of possible values as AssetFromParentToChild and AssetFromChildToParent. For other entities works the same way. Any missing value will detault to the list in defs.default. }}
 +
 +
"defs" : {
 +
"set1" : ["Connected To", "Depends On", "Installed On"],
 +
"set2" : ["Connected To", "Depends On", "Installed On"],
 +
"default" : ["Connected To", "Depends On", "Installed On"]
 +
          }
 +
"FromAssetToRequests" : "set1",
 +
"FromRequestsToAsset" : "set2",
 +
"FromAssetToServices" : "set2",
 +
"AssetFromParentToChild" : "set2",
 +
"AssetFromChildToParent" : "set2"
  
 +
{{bullet1|app.cm.explorer.items.inPolicy|They are the entities that can be set in/out policy. The entities with 'false' will have no property inPolicy=true/false. If a new entity is added in the future in the Conf. Manager app, and this object is not updated with the new entity name, then its value will be set to the default value, which is 'true' (i.e. the user will be able to put the new items in/out of policy). The entities currently shown in the diagram are Asset, Colleagues, Contact, Attachment, Requests, Services.}}
  
−
[[Category:Administration]]
+
"Asset" : true,
 +
"Colleagues" : true,
 +
"Contact" : true,
 +
"Attachment" : true,
 +
"Requests" : true,
 +
"Services" : true,
 +
"default" : true
 +
<br>
 +
-->
 +
[[Category:HDOC]]
 +
<!-- https://docs.hornbill.com/servicemanager-config/advanced-tools-and-settings/application-settings -->

Latest revision as of 21:12, 18 March 2024

This document can now be found at its new location in the Hornbill Document Library.

Application Settings

Retrieved from "https://wiki.hornbill.com/index.php?title=Service_Manager_Settings&oldid=32022"