Difference between revisions of "Service Manager Experimental Features"

From Hornbill
Jump to navigation Jump to search
Line 13: Line 13:
 
==Current Features==
 
==Current Features==
  
* app.experimental.advancedRequestTaskCompleter ('''Build 928''')
+
* app.experimental.advancedRequestTaskCompleter ('''Build 935''')
 
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.
 
: * Default is '''Off'''
 
: * Default is '''Off'''
Line 19: Line 19:
 
: * 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
  
* app.experimental.multipleRequestsAction ('''Build 928''')
+
* app.experimental.multipleRequestsAction ('''Build 935''')
 
This feature allows a user to multi-select and resolve or close requests from the request list view.
 
This feature allows a user to multi-select and resolve or close requests from the request list view.
 
: * 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'''

Revision as of 09:43, 13 March 2017

Home > Service Manager> Experimental Features

Introduction

The features listed here are subject to change. If 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

Current Features

  • app.experimental.advancedRequestTaskCompleter (Build 935)

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.

* 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
* This does not effect Authorisation Tasks, which can still only be completed by the assignee / owner
  • app.experimental.multipleRequestsAction (Build 935)

This feature allows a user to multi-select and resolve or close requests from the request list view.

* 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