Parametrization - Ticket

to deliver the service, it is necessary that some parameter settings allow ticket management actions , such as the standard flow, the phase in which the service requests to be registered will be forwarded, and others standard flow, the phase in which the service requests to be registered will be forwarded, and others procedure access the functionality through the main menu parametrization > request and incident management ; set the parameter value to be configured; make the change; click on " save "; the list below presents the ticket's functionality and the objective of each one of them \# name possible values purpose additional guidance 9 group level 1 id (eg 1) e g 1 enter the identification number (id) of the 1st level of attendance group this group is the default to be used if the service is not informed if citsmart citsmart is used in multiple contracts, this group must be defined in the contract services import template this group id is set on the "group registration" screen not applicable 30 default phase id for service execution (ex 2) e g 2 define the phase in which a service request to be registered will be forwarded (1 = capture phase or 2 = execution phase) not applicable 31 send email in the execution of request/incident flows (eg y or n) y or n define whether email notifications will be sent to the requester when performing the service/incident request flows not applicable 40 does the access control of the service catalog per unit (eg y or n)? y or n define if the access control of the service catalog will be per unit if it is, a "service" button will be available on the "unit registration" screen, to link the service (s) to the unit, where they will be displayed in the service request according to the unit of the requester informed not applicable 41 does the control of employees linked to contracts (eg y or n)? y or n define if the control of employees will be done by contract if it is, the contracts will be displayed on the "group registration" screen to link them to the group, where employees belonging to the group will be linked to the contracts not applicable 42 service requests registration page (default will be used if not informed) inform the page that will be used for the registration of service requests/incidents default /pages/solicitacaoservicomulticontratos/solicitacaoservicomulticontratos load there is no negative impact if you do not enter the page, the default system page will be used /pages/solicitacaoservicomulticontratos/solicitacaoservicomulticontratos load 50 accept value 0 (zero) for quantity and cost of the activity? (eg y or n) y or n define if will be accepted the value 0 (zero) for quantity and cost of the service activity if it is, it will be allowed to execute a work order informing the value 0 00 if it is not, the system will not allow the execution of a work order without informing the amount due not applicable 57 the id of the e mail template will be sent to the destination group when escalating a request (eg 4) enter the identification number (id) of the email template this email template will be sent to the target group when escalating a service/incident request this email template id is set on the "email template" screen if you do not enter the id number of the email template, there's the possibility of not sending the correct email to the target group 58 notify the group when receiving a service request escalation (eg y or n) y or n set whether to notify the group when receiving a service request/incident escalation if it is, when escalating a service request/incident to the group, it will be notified via email if you do not enter the "s" value for the parameter, the group will not be notified upon receiving a service request/incident escalation 61 link contracts to the unit (eg y or n) y or n define whether the contracts will be linked to the unit if so, the contracts will be displayed on the "unit registration" screen to be linked to the unit not applicable 62 identifies the service id for service and incident requests this parameter must be configured if the user portal is enabled you must enter the service identifier (id) for service/incident requests from the portal this id is available in the service catalog not applicable 65 identify the source id of the service request default call enter the identification number (id) of the default source to open the service request/incident this id is set on the "source of requests" registration screen not applicable 69 validate fields cause and solution category of the service request page required (eg y or n default 'n') y or n (default n) define whether the "cause" and "solution category" fields of the service request/incident screen are mandatory if you do not enter the parameter value, the system default value will be set "n" (no) 72 smtp reading email limit loaded on service request e g 20 set the limit of emails that will be loaded on the service/incident request screen by clicking on the "upload email" button on the service/incident request screen, the number of e mails as configured in the parameter will be loaded not applicable 86 show incident service category (eg y or n default 's') y or n (default y) define whether the service category appears on the service request/incident screen if the value "y" is set, the "service category" field is displayed on the service request/incident screen if you do not enter the parameter value, the system default value will be used "y" (yes) 103 e mail template id for sending service change notification (eg 19) enter the id number of the notification for the e mail template of service change when you change the service of the contract, the email template defined in this parameter will be used to send the service change notification this notification will be sent to the user and/or group associated with the service this email template id is set on the "email template" screen if you do not enter the identifier (id) of the email template, you may not send the correct email 104 calculate the priority of the request dynamically using the registered formula (eg y or n default 'n') y or n (default n) define whether to calculate the priority of the request using the registered formula if "y" is informed, the priority of the request will be calculated dynamically using the registered formula if you do not enter the parameter value, the system default value will be used "n" (no) 105 source id that will be set by default when creating a new incident enter the identification number (id) of the default source to open the service request/incident this source id is set on the "source of requests" registration screen not applicable 113 email template id for auto escalation enter the identification number (id) of the auto escalation email template automatic escalation occurs when setting up the service level agreement, that after nn minutes (according to configuration) the system must escalate to the group or priority (as configured on the service level agreement screen) this email template id is set on the "email template" screen if you do not enter the identification number (id) of the email template, you may not send the correct email 115 unlink physical location with the unit? (eg y or n default 'n') y or n (default n) define if the linkage between the physical location with the unit will be removed if "y" is informed, the physical location link with the unit will be removed, that is, the location will not be established when informing the unit when registering a service/incident request if you do not enter the parameter value, the system default value will be set "n" (no) 119 type of requests/incidents capture (1 in execution, 2 in targeting) (default 1) 1 at execution or 2 directing (default 1) define the type of requests/incidents capture 1 = at execution or 2 = directing; if you do not enter the value of the parameter, the system default value will be used "1" = at execution 134 default group id for meeting hr requisitions enter the identification number (id) of the standard group for the fulfillment of human resources requests this id is set on the "group registration" screen not applicable 137 e mail template id to send notification of a "bad" or "regular" evaluation in a satisfaction survey inform the notification email template identification number of a "bad" or "regular" evaluation email in a satisfaction survey when a request satisfaction survey receives a negative value (regular or bad), the notification email (entered in the parameter) is sent to the determined group (configured in parameter 138), informing the evaluation data made if you do not enter the identification number (id) of the email template, you may not send the correct email 138 the id of the group receiving e mail notification of a "bad" or "regular" evaluation in a satisfaction survey enter the identification number (id) of the group that will receive the notification email of a "bad" or "regular" evaluation performed on a satisfaction survey, so that action is taken on that negative evaluation this group id is set on the "group registration" screen if you do not enter the group id number, the email will not be sent 139 deadline in days to respond to a satisfaction survey regarding service requests (eg 7) define the term (in days) to respond to the satisfaction survey regarding service requests if the satisfaction survey is not answered, the deadline in days (as defined in the parameter) will be established to be automated answered not applicable 151 use automatic approval for unanswered satisfaction surveys (eg y or n default 'n') y or n (default n) enable automatic satisfaction survey approval, if not answered not applicable 152 standard note for automatic satisfaction search (use a valid id of a degree of satisfaction) set the default note for the satisfaction survey if automatic satisfaction survey approval is enabled, the satisfaction survey automatic answer will be established, as defined in this parameter not applicable 171 days limit for reopening of services incidents/requests set the days limit for reopening the incident/service request not applicable 182 folder to save the description and the solution to the service request in the knowledge base (eg windows description response to knowledgebase) e g windows description answer to knowledgebase define the directory to store the answer description of the service/incident request to be saved in the knowledge base in the service request/incident screen, the field "save solution/response in the knowledge base" is displayed when answering a service/incident request, and if you want to save the description of the response solution in the knowledge base, simply select the field and inform the title, then, when saving and forward the flow, the description of the solution response of the request will be stored in the folder defined in the parameter not applicable 190 activate the escalation rules work? (eg y or n default 'n') y or n (default n) define whether the operation of scheduling rules is enabled if you do not enter the parameter value, the system default value will be set "y" (yes) 192 show save solution/response in the knowledge base? note it will only show when creating a new request if the situation is marked 'solved' (eg y or n default 's') y or n (default y) define if the service request/incident solution/response will be saved in the knowledge base in the service request/incident screen, the field "save solution/response in the knowledge base" will be displayed, in which you must enter the title for the solution/response in this case, when saving the information of the service/incident request, it'll be saved in the knowledge base the solution/response of the request if you do not enter the parameter value, the system default value will be set "y" (yes) 195 email template id for sending a notification about a request with the deadline to be expired (eg 1) enter the identification number (id) of the request notification email template with the deadline to be expired when creating an escalation rule, the deadline for the request is defined, where an email will be sent to the user (defined in parameter 197) notifying the deadline for the request if you do not enter the identification number (id) of the email template, you may not send the correct email 197 login of the user who will receive an e mail regarding the escalation rules of the service request that are being expired (eg consultant) define the login of the user who will receive the email about the service request escalation rules that are expiring when we create a scheduling rule, we set the deadline for the request, and the user login defined in this parameter will receive an email notifying that the request has entered the "expiring" status if you do not inform the user login, the email will not be sent 200 enable routine for reading new emails automatically? (eg y or n default 'n') y or n (default n) enable the automatic email reading routine this routine, when enabled, works as follows when sending an email to citsmart citsmart support, the automatic email will be read, if the email refers to a request, the title of the email will be checked if it contains the word 'request' and the request number, if it contains, the email will be stored as an occurrence in the request concerned if you do not enter the value for the parameter, the system default value will be set "n" (no) 215 receive a notification when closing/escalating linked requests (eg y or n default 'y') y or n (default y) enable or disable sending notifications of child requests to the executor group of parent requests by reporting the 'y' value for the parameter, the system sends parent notification requests to the executing group for notification of creation, escalation, capture, other changes, and closure of child service requests the email template linked to the child request service will be used not applicable 216 the id of e mail template creation that will be sent to the executor group of the related request enter the identification number (id) of the creation email template that will be sent to the executor group of a request related to another one this email template id is set on the "email template" screen if the identification number (id) is not correctly entered, the system will not send notification emails 217 the id of e mail action template that will be sent to the executor group of the related request inform the identification number (id) of the email template of other actions that will be sent to the executing group of a request related to another one this email template id is set on the "email template" screen if the identification number (id) is not correctly entered, the system will not send notification emails 218 id closing email template that will be sent to the executor group of the related request enter the identification number (id) of the closing email template that will be sent to the executing group of a request related to another request this email template id is set on the "email template" screen if the identification number (id) is not correctly entered, the system will not send notification emails 227 identifier of the flow element that is responsible for executing the service request define the flow element responsible for executing the service request not applicable 231 allow email sending when an incident is edited (eg y or n default 'y') y or n (default y) enable/disable sending notification of changes in the request (incident) by email to the requester when the parameter is enabled, when there is a change in the request information (incident), an email will be sent to the requester notifying about it not applicable 251 e mail template id to notify requester about the release of request occurrences enter the identification number (id) of the email template that will be used to notify the requester about the occurrence of the request this email template id is set on the "email template" screen with the identification number of the email template that will be used to notify the requestor whenever a permitted occurrence has opened the viewer of the requestor if the identification number (id) is not correctly entered, the system will not send notification e mails 260 type hierarchy of the filter unit (default 1 list without restriction, 2 units of the logged employee) e g 1 unrestricted unit; 2 unit of employee and its children units (restrictive); 3 unit of the employee together with his superior levels (restrictive) define which type of hierarchy will be used to generate the tree of units that an employee is allowed to access changing how the system will generate the tree of units allowed for a user/employee, many units may not be viewed if the hierarchy type uses access restriction 261 number of registries returned in advanced search (eg 50) define how many registries will be returned by the system in the advanced search for service request if you do not enter the value of the parameter, the system will return all registries related to the user search in the advanced search service search any value that the user enters will limit the amounts of search registries to the value of the parameter if the user search has more registries than the one defined by the parameter, the system will represent a related error message and will not return any registries to the user 264 filter by request in progress y or n if the "y" value is set for the parameter, the "in progress" option in the portal's "status" field, will be selected by default and will return a list of requests only with a request whose current task is equal to 'in progress' not applicable 274 filter the "service category" by the contract and/or service in the service request? values "y" or "n" default "s" y or n (default s) define whether the service category filter on the service request screen is by the contract service if enabled, in the request registration screen, only the service categories that are linked to the service of the contract will be available not applicable 288 url logo satisfaction survey (eg http //www citsmart com br/imagens/logo png ) e g citsmart com/ imagens/logo png inform the url of the image that will be used as a logo on the satisfaction survey screen not applicable 289 send notification to related requests as configured for the group? (y or n) y or n set whether to send e mail notifications to the executor group when creating a request related to another one not applicable 290 email template id sent when suspending a service request enter the id number of the service request suspension email template when suspending a service request, it will be used to send the suspension notification of the email template informed in this parameter this notification will be sent to the requester the email template id is set in the "email template" screen not applicable 291 e mail template id sent when reactivating a service request enter the service request reactivation email template identification number (id) reactivating a service request will be used to send the reactivation notification of the e mail template informed in this parameter this notification will be sent to the requester the email template id is set in the "email template" screen not applicable 294 requester selected when creating a related request values 0 none, 1 requester, and 2 user logged in default 0 y or n (default s) define whether, when creating a related request, the fields for completing the requester's data will be completed by the system with the data of the requester of the main request if the value for the parameter is not set, the value will be automatically set by the system "y" (yes) 295 reopen request by satisfaction survey (possible values y or n, default n) y or n (default n) enable the reopening of requests by satisfaction survey when the parameter value is "y", in the satisfaction search screen, it will display the "no attended" option in the "evaluation" field which, when selected, will display the button to reopen the service request when the parameter value is "n", the "not attended" option will not be displayed in the "evaluation" field, so the button to reopen the request will continue to be disabled and invisible to the user if the value for the parameter is not set, the value "n" will be automatically set by the system 296 name(s) of upper user approval flow (s) (separate by comma) configure the total of items that must be imported at one time from the base to solr not applicable 299 request/incident activate message exchange (values "y" or "n" default "n") y or n (default n) enable message exchange between the requester and the person responsible for the request not applicable 301 display the title of the request/incident (values "y" or "n" default "n") y or n (default n) define whether the request/incident title field is displayed not applicable 306 support level of incident management tools the quality of the incident management tool to support the activities collected through comparison with existing functionalities in the tool and itsm practices not applicable 307 maturity of the incident management process the maturity with which we perform incident management activities, this information is collected through an assessment process not applicable 343 narrow by attribution in advanced search? (values "y" or "n" default "y") y or n (default y) enables access control (security) to the advanced search feature not applicable 351 enables the creation of location occurrences through the unit during the creation of requests y or n (default n) not applicable 372 enable mandatory fulfillment when suspending request y or n (default n) if this parameter is yes, the system will show and require the completion of a text for the attendant to justify the reason for a ticket suspension not applicable 379 request management tool support level not applicable 380 maturity of the request management process table 1 parameters table