Difference between revisions of "Service Manager Experimental Features"
Jump to navigation
Jump to search
| (14 intermediate revisions by 5 users not shown) | |||
| Line 15: | Line 15: | ||
:* [[Document Manager Experimental Features]] | :* [[Document Manager Experimental Features]] | ||
:* [[System Experimental Features]] | :* [[System Experimental Features]] | ||
| + | :* [[Activities]] | ||
|} | |} | ||
| + | |||
== Complete Someone Else's Task on a Request == | == Complete Someone Else's Task on a Request == | ||
This feature allows a user to complete tasks that are assigned to another person. Supporting teams of a service that is associated to a request will be respected otherwise if a request is not associated to a service, then the user can complete tasks that are assigned to the user's team(s) members. | This feature allows a user to complete tasks that are assigned to another person. Supporting teams of a service that is associated to a request will be respected otherwise if a request is not associated to a service, then the user can complete tasks that are assigned to the user's team(s) members. | ||
| Line 21: | Line 23: | ||
'''app.experimental.advancedRequestTaskCompleter''' | '''app.experimental.advancedRequestTaskCompleter''' | ||
:* Default is '''Off''' | :* Default is '''Off''' | ||
| − | :* If enabled a user would require one of the following roles in order to use this feature - Incident Management Full Access, Change Management Full Access, Problem Management Full Access, Service Request Full Access | + | :* If enabled a user would require one of the following roles in order to use this feature - Incident Management Full Access, Change Management Full Access, Problem Management Full Access, Release Management Full Access, Service Request Full Access |
| + | :* To complete an Activity that is assigned to another person, the logged on User must be a member of a Supporting Team of the Service that is associated to the request. If the request is not associated to a Service but is assigned to a team, then the logged on User must be a member of the team that the request is assigned to. | ||
| + | :* The ''Quick Complete'' check icon that lets you complete an Activity without opening the Activity is not currently available to users that are not the owner or the assignee of the activity. In order to complete another person's activity on a request, the activity must be opened and the ''Complete'' button used. | ||
:* This does not effect Authorisation Tasks, which can still only be completed by the assignee / owner | :* This does not effect Authorisation Tasks, which can still only be completed by the assignee / owner | ||
| + | :* This only works with tasks that are assigned to a user, it does not work if tasks are assigned to a team or role | ||
| − | == | + | == Request List [[Multi-Select Actions]] == |
This feature allows a user to multi-select and resolve or close requests from the request list view. Available as of Build 934 | This feature allows a user to multi-select and resolve or close requests from the request list view. Available as of Build 934 | ||
| − | '''app.experimental.multipleRequestsAction | + | '''app.experimental.multipleRequestsAction''' |
:* Default is '''Off''' | :* Default is '''Off''' | ||
:* If enabled a user will see a new '''Actions''' button on the request list toolbar when selecting one or multiple requests, allowing the '''Resolving''' of the selected requests, or the '''Closing''' of the selected requests if the requests are already in a resolved status. | :* If enabled a user will see a new '''Actions''' button on the request list toolbar when selecting one or multiple requests, allowing the '''Resolving''' of the selected requests, or the '''Closing''' of the selected requests if the requests are already in a resolved status. | ||
:* Existing multi-select behaviour is retained, in as much that you can only apply the multi-select actions to requests of the same '''Type''' and those logged against the same '''Service''' | :* Existing multi-select behaviour is retained, in as much that you can only apply the multi-select actions to requests of the same '''Type''' and those logged against the same '''Service''' | ||
| + | |||
| + | == [[Knowledge Centre]] == | ||
| + | This feature allows agents and customers to be presented with relevant knowledge when using progressive capture in the user app and the customer and service portal (selectively) | ||
| + | |||
| + | '''guest.app.experimental.hornbillKnowledgeCentre''' | ||
| + | :* Default is '''Off''' | ||
| + | :* If enabled you will also need to enable which interfaces will see the knowledge centre in progressive capture, this is controlled by the following system settings: | ||
| + | '''guest.app.knowledge.customer''' | ||
| + | :* Default is '''Off''' | ||
| + | :* If enabled, shows the relevant knowledge when a user log a new request in the Customer portal | ||
| + | '''guest.app.knowledge.service''' | ||
| + | :* Default is '''Off''' | ||
| + | :* If enabled, shows the relevant knowledge when a user log a new request in the Service portal | ||
| + | '''guest.app.knowledge.user''' | ||
| + | :* Default is '''Off''' | ||
| + | :* If enabled, shows the relevant knowledge when a user log a new request in the user app | ||
[[Category:Service Manager]] | [[Category:Service Manager]] | ||
Revision as of 15:51, 27 October 2021
Home > Service Manager> Experimental Features
IntroductionThe features listed here are subject to change. If they are promoted to live as supported features they will be documented in the appropriate location on the wiki and removed from the experimental list, equally if the feature is removed this will be documented here. These features can be enabled from the admin console, under Service Manager and Settings |
Related Articles |
Complete Someone Else's Task on a Request
This feature allows a user to complete tasks that are assigned to another person. Supporting teams of a service that is associated to a request will be respected otherwise if a request is not associated to a service, then the user can complete tasks that are assigned to the user's team(s) members.
app.experimental.advancedRequestTaskCompleter
- Default is Off
- If enabled a user would require one of the following roles in order to use this feature - Incident Management Full Access, Change Management Full Access, Problem Management Full Access, Release Management Full Access, Service Request Full Access
- To complete an Activity that is assigned to another person, the logged on User must be a member of a Supporting Team of the Service that is associated to the request. If the request is not associated to a Service but is assigned to a team, then the logged on User must be a member of the team that the request is assigned to.
- The Quick Complete check icon that lets you complete an Activity without opening the Activity is not currently available to users that are not the owner or the assignee of the activity. In order to complete another person's activity on a request, the activity must be opened and the Complete button used.
- This does not effect Authorisation Tasks, which can still only be completed by the assignee / owner
- This only works with tasks that are assigned to a user, it does not work if tasks are assigned to a team or role
Request List Multi-Select Actions
This feature allows a user to multi-select and resolve or close requests from the request list view. Available as of Build 934
app.experimental.multipleRequestsAction
- Default is Off
- If enabled a user will see a new Actions button on the request list toolbar when selecting one or multiple requests, allowing the Resolving of the selected requests, or the Closing of the selected requests if the requests are already in a resolved status.
- Existing multi-select behaviour is retained, in as much that you can only apply the multi-select actions to requests of the same Type and those logged against the same Service
Knowledge Centre
This feature allows agents and customers to be presented with relevant knowledge when using progressive capture in the user app and the customer and service portal (selectively)
guest.app.experimental.hornbillKnowledgeCentre
- Default is Off
- If enabled you will also need to enable which interfaces will see the knowledge centre in progressive capture, this is controlled by the following system settings:
guest.app.knowledge.customer
- Default is Off
- If enabled, shows the relevant knowledge when a user log a new request in the Customer portal
guest.app.knowledge.service
- Default is Off
- If enabled, shows the relevant knowledge when a user log a new request in the Service portal
guest.app.knowledge.user
- Default is Off
- If enabled, shows the relevant knowledge when a user log a new request in the user app