|
|
| (5 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| | + | 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]. |
| | + | |
| | + | [[file:hornbill-document-library.png|Experimental Features|link=https://docs.hornbill.com/servicemanager-config/advanced-tools-and-settings/application-settings]] |
| | + | <!-- |
| | + | |
| | <div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | | <div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> |
| | __NOTOC__[[Main Page|Home]] > [[Service Manager]]> Experimental Features | | __NOTOC__[[Main Page|Home]] > [[Service Manager]]> Experimental Features |
| Line 17: |
Line 22: |
| | :* [[Activities]] | | :* [[Activities]] |
| | |} | | |} |
| − |
| |
| − | == 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
| |
| − |
| |
| − | == Resolve Multiple Request from the Request List ==
| |
| − | 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]] == | | == [[Knowledge Centre]] == |
| Line 42: |
Line 29: |
| | :* Default is '''Off''' | | :* 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: | | :* 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''' | | '''guest.app.knowledge.customer''' |
| | :* Default is '''Off''' | | :* Default is '''Off''' |
| Line 52: |
Line 38: |
| | :* Default is '''Off''' | | :* Default is '''Off''' |
| | :* If enabled, shows the relevant knowledge when a user log a new request in the user app | | :* If enabled, shows the relevant knowledge when a user log a new request in the user app |
| − | | + | --> |
| − | == In-App Reporting ==
| + | [[Category:HDOC]] |
| − | | |
| − | This feature allows users who are assigned the '''Service Manger In-App Reporting''' Role to run a series of default reports, create their own reports based on the default reports provided as well as:
| |
| − | | |
| − | * Print The Reports
| |
| − | * Download Report PDF
| |
| − | * Schedule Reports to be published to Document Manager
| |
| − | | |
| − | This can be enabled through '''app.experimental.inAppReporting''' application setting. By default, the Reports module is disabled.
| |
| − | | |
| − | You can access Service Manager's Reports module via the '''Reports''' sub-menu option.
| |
| − | | |
| − | [[File:smReportsMenuOption.jpg]]
| |
| − | | |
| − | Each user with the '''Service Manager In-App Reporting''' role will only see request data which they are entitled to view, based on requests logged against services which their teams support.
| |
| − | | |
| − | Users are able to create and edit their own reports using a simple clause builder and or by reusing '''views''' which they have already created from the request list view.
| |
| − | :* Default Reports attributes are not editable
| |
| − | | |
| − | Users can mark reports as favourites to view them on their reports landing page alongside, the reports they recently viewed and their list of saved reports.
| |
| − | | |
| − | '''In-App Reporting''' is available as an experimental feature and the following enhancements are already planned to evolve it's capabilities:
| |
| − | | |
| − | * Use of Custom fields
| |
| − | * Ability to sort, order and choose columns for report outputs
| |
| − | * Expanding on the list of default reports provided
| |
| − | | |
| − | [[Category:Service Manager]] | |
