Difference between revisions of "Request Details Form Designer"
Jump to navigation
Jump to search
| (10 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | This document can now be found at its new location in the [https://docs.hornbill.com/service-portfolio/requests/request-details-form-designer Hornbill Document Library]. | ||
| + | |||
| + | [[file:hornbill-document-library.png|Request Details Form Designer|link=https://docs.hornbill.com/service-portfolio/requests/request-details-form-designer]] | ||
| + | <!-- | ||
| + | |||
<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__ | __NOTOC__ | ||
| Line 10: | Line 15: | ||
|style="width:73%"| | |style="width:73%"| | ||
== Introduction == | == Introduction == | ||
| − | On each request form the ''Details'' section can be configured using the ''Request Details Form Designer'' to manage the available fields within this section. | + | On each request form the ''Details'' section can be configured using the ''Request Details Form Designer'' to manage the available fields within this section. This includes the ability to manage the existing default fields, plus allowing you to expose custom fields. |
| + | <br> | ||
| + | ===Who can use the form designer?=== | ||
| + | To access the form designer, the logged in user needs one of the following roles associated to their account: | ||
| + | :* '''Form Designer''' | ||
| + | :* '''Admin Role''' | ||
| + | |||
|style="width:5%"| | |style="width:5%"| | ||
| Line 25: | Line 36: | ||
:* [[Release Requests]] | :* [[Release Requests]] | ||
|} | |} | ||
| − | |||
| − | |||
== Using the Request Details Form Designer == | == Using the Request Details Form Designer == | ||
| − | + | {{#ev:youtube|9KmvUJsPPXU|400|right}} | |
| − | In Service Manager it is possible to manage the request details forms for each request type per service and where requests are not linked to services. | + | The form designer can then be accessed wherever the '''"Design"''' button is displayed. In Service Manager, it is possible to manage the request details forms for each request type per service and where requests are not linked to services. |
* '''Where services are not linked to a request type (Inc, Problem etc)''' you can open the form designer on any such request and edit and make changes there. These changes will apply to any other requests of that type (Inc, Problem etc) where a service is not linked. | * '''Where services are not linked to a request type (Inc, Problem etc)''' you can open the form designer on any such request and edit and make changes there. These changes will apply to any other requests of that type (Inc, Problem etc) where a service is not linked. | ||
| − | * | + | * However it is sometimes a requirement to have different custom fields on the Incident (or any other request type) form depending on the service against which the Incident or other request type has being raised (especially where multiple support teams are using the Incident forms but for their own services with different requirements). |
:* In this case each service owner's or those with the '''form designer''' role can use the form designer from within the '''[[Services_Request_Configuration|Service > Request Configuration > Request Type]]''' view to manage the request details form for requests raised against that service. | :* In this case each service owner's or those with the '''form designer''' role can use the form designer from within the '''[[Services_Request_Configuration|Service > Request Configuration > Request Type]]''' view to manage the request details form for requests raised against that service. | ||
| − | :* Or they can open up any request logged against | + | :* Or they can open up any request logged against that service and make the changes from the form designer on the request. |
| − | Which ever route is taken these changes when | + | Which ever route is taken these changes when made will apply to any requests of that type logged against that service. |
This means that you can manage any request form per service, allowing you to control the default fields and add custom fields to the Incident, Problem, Change, Service Requests and Release for each service, then any tickets raised against that service will use the request details form as configured against the service for the request type. | This means that you can manage any request form per service, allowing you to control the default fields and add custom fields to the Incident, Problem, Change, Service Requests and Release for each service, then any tickets raised against that service will use the request details form as configured against the service for the request type. | ||
| Line 77: | Line 86: | ||
:* '''Available Fields''' | :* '''Available Fields''' | ||
| − | :: There are 30 available custom fields. | + | :: There are 30 available custom fields which you can choose from per request type per service. |
| − | ::: Fields Custom A-M are of type varchar and limited to 255 characters | + | ::: Fields Custom A-M are of type varchar and limited to 255 characters - any values entered into these fields will be truncated after 255 characters |
::: Fields Custom P-T are of type text with no character limit | ::: Fields Custom P-T are of type text with no character limit | ||
::: Fields Custom 21-25 are of type datetime | ::: Fields Custom 21-25 are of type datetime | ||
::: Fields Custom 26-30 are of type Integer | ::: Fields Custom 26-30 are of type Integer | ||
| + | ::: Fields Custom 31-40 are of type text with no character limit | ||
| + | |||
| + | : Once you have used a custom field it will not be visible in the list of '''available fields''' | ||
| + | : To remove and repurpose a custom field, firstly remove the custom field from the form and it will then appear again in the list of '''available fields''' | ||
:* '''Display Label''' | :* '''Display Label''' | ||
:: Add a ''Display Label'' which will be visible to the users when viewing or editing this form. | :: Add a ''Display Label'' which will be visible to the users when viewing or editing this form. | ||
| + | :: To add different language translations for the '''Display Label''' on custom fields switch the UI into the required language and provide the values for that specific language, this can be repeated for any subsequently required languages. | ||
:* '''Control Type''' | :* '''Control Type''' | ||
:: A number of ''Control Types'' can be used. These include Single Line Text Field, Multi-line Text Area, Drop Down List Box, Radio Option List, Check List Box, 5 Star Rating, Single Check Box, Date Selector, Date Time Selector | :: A number of ''Control Types'' can be used. These include Single Line Text Field, Multi-line Text Area, Drop Down List Box, Radio Option List, Check List Box, 5 Star Rating, Single Check Box, Date Selector, Date Time Selector | ||
| Line 112: | Line 126: | ||
[[Category:Service Manager]][[Category:Videos]] | [[Category:Service Manager]][[Category:Videos]] | ||
| + | --> | ||
| + | [[Category:HDOC]] | ||
Revision as of 00:01, 30 April 2024
This document can now be found at its new location in the Hornbill Document Library.
