Layton ServiceDesk - General Settings - Request Settings

From Layton Support
(Difference between revisions)
Jump to: navigation, search
m (Minor formatting changes)
m (Minor text changes)
 
(14 intermediate revisions by one user not shown)
Line 1: Line 1:
<p align="right">[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk™]] [[User Guide for Layton ServiceDesk™|<u>Back to Contents</u>]]</p>
+
<p align="right">[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk]] [[User Guide for Layton ServiceDesk|<u>Back to Contents</u>]]</p>
  
 
=Overview=
 
=Overview=
Line 7: Line 7:
  
 
=Ownership & Assignment=
 
=Ownership & Assignment=
 +
[[File:Lsd admin req stg02.png|center|link=]]
 
==Ownership==
 
==Ownership==
 
===Owned By Default===
 
===Owned By Default===
This specifies the default value for the Request ''Owned By'' field when a new request is logged or a new End User Request is logged.
+
This specifies the default value for the Request ''Owned By'' field when a new request is logged by the Analyst in the web interface.
  
 
Decide who and how Request Ownership will operate and what or whether a default should be used. The normal practice would probably use the Help Desk first line Analysts as always owning a Request, even when the Request is assigned on to a Support Analyst or Group. However, this is totally configurable and you can decide to manually set or transfer ownership at any time, even after a default owner has been specified.
 
Decide who and how Request Ownership will operate and what or whether a default should be used. The normal practice would probably use the Help Desk first line Analysts as always owning a Request, even when the Request is assigned on to a Support Analyst or Group. However, this is totally configurable and you can decide to manually set or transfer ownership at any time, even after a default owner has been specified.
Line 28: Line 29:
 
|-
 
|-
 
|Use Specified
 
|Use Specified
|Ownership defaults to the Analyst Specified. The specified Analyst can be selected by clicking the select button next to the '''[[Layton_ServiceDesk™_-_General_Settings_-_Request_Settings#Owned_By_Specified|Owned By Specified]]''' field.
+
|Ownership defaults to the Analyst Specified. The specified Analyst can be selected by clicking the select button next to the '''[[Layton_ServiceDesk_-_General_Settings_-_Request_Settings#Owned_By_Specified|Owned By Specified]]''' field.
 
|}
 
|}
 
</center>
 
</center>
  
 
===Owned By Specified===
 
===Owned By Specified===
When '''[[Layton_ServiceDesk™_-_General_Settings_-_Request_Settings#Owned_By_Default|Owned By Default]]''' is set to ''Use Specified'', use this field to select the default analyst. This will default all requests to ownership by the selected analyst. You can still modify each request's ownership if desired.
+
When '''[[Layton_ServiceDesk_-_General_Settings_-_Request_Settings#Owned_By_Default|Owned By Default]]''' is set to ''Use Specified'', use this field to select the default analyst. This will default all requests to ownership by the selected analyst. You can still modify each request's ownership if desired.
  
 
==Assignment==
 
==Assignment==
Line 52: Line 53:
 
|-
 
|-
 
|Use Specified
 
|Use Specified
|Assignment defaults to the Analyst Specified. The specified Analyst can be selected by clicking the select button next to the '''[[Layton_ServiceDesk™_-_General_Settings_-_Request_Settings#Assigned_to_Specified|Assigned To Specified]]''' field.
+
|Assignment defaults to the Analyst Specified. The specified Analyst can be selected by clicking the select button next to the '''[[Layton_ServiceDesk_-_General_Settings_-_Request_Settings#Assigned_to_Specified|Assigned To Specified]]''' field.
 
|}
 
|}
 
</center>
 
</center>
  
 
===Assigned to Specified===
 
===Assigned to Specified===
When '''[[Layton_ServiceDesk™_-_General_Settings_-_Request_Settings#Assigned_To_Default|Assigned To Default]]''' is set to ''Use Specified'', use this field to select the default analyst. This will default all requests to assignment to the selected analyst. You can still modify each request's assignment if desired.
+
When '''[[Layton_ServiceDesk_-_General_Settings_-_Request_Settings#Assigned_To_Default|Assigned To Default]]''' is set to ''Use Specified'', use this field to select the default analyst. This will default all requests to assignment to the selected analyst. You can still modify each request's assignment if desired.
  
=Default Status =
+
=Status, Priority=
This defines the default Status for newly created Requests. Requests Statuses are defined in '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Request_Statuses|Administration > Libraries > Request Statuses]]'''. For more information see the Request Statuses section.
+
==Default Status==
 +
This defines the default Status for newly created Requests. Requests Statuses are defined in '''[[Layton_ServiceDesk_-_Settings_-_Libraries_-_Request_Statuses|Administration > Libraries > Request Statuses]]'''. For more information see the Request Statuses section.
  
=Default Priority/SLA =
+
==Default Priority/SLA==
This defines the default Priority for newly created requests when created by an Analyst or the End User in the web interface. If the Priority field is not present on the form (common in many configurations), the Priority will be set to ''(None)'' on Request creation regardless of the setting.
+
This defines the default Priority for newly created requests when created by an Analyst or the End User in the web interface. Note that this will not set the Priority for Requests created from emails. See '''[[Layton ServiceDesk - Workflows - Set Default Priority for All Requests|this workflow]]''' for a configuration that will set the default Priority for new Requests created by any method.
  
Requests Priorities are defined in '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Priority|Administration > Libraries > Priority / SLA]]'''. For more information see the Priority / SLA section.
+
If the Priority field is not present on the form (common in many configurations), the Priority will be set to ''(None)'' on Request creation regardless of the setting.
  
=Default Urgency =
+
Requests Priorities are defined in '''[[Layton_ServiceDesk_-_Settings_-_Libraries_-_Priority|Administration > Libraries > Priority / SLA]]'''. For more information see the Priority / SLA section.
This defines the default Urgency for newly created requests. Urgencies are defined in '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Urgency|Administration > Libraries > Urgency]]'''. For more information please see the Urgency section.
+
  
=Default Impact =
+
==Default Urgency==
This defines the default Impact for newly created requests. Impacts are defined in '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Impact|Administration > Libraries > Impact]]'''. For more information please see the Impact section.
+
This defines the default Urgency for newly created requests. Urgencies are defined in '''[[Layton_ServiceDesk_-_Settings_-_Libraries_-_Urgency|Administration > Libraries > Urgency]]'''. For more information please see the Urgency section.
 +
 
 +
==Default Impact==
 +
This defines the default Impact for newly created requests. Impacts are defined in '''[[Layton_ServiceDesk_-_Settings_-_Libraries_-_Impact|Administration > Libraries > Impact]]'''. For more information please see the Impact section.
  
 
=Default IT Services =
 
=Default IT Services =
This defines the default Service for newly created requests. Services are defined in '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Services|Administration > Libraries > Services]]'''. For more information see the Services section.
+
This defines the default Service for newly created requests. Services are defined in '''[[Layton_ServiceDesk_-_Settings_-_Libraries_-_Services|Administration > Libraries > Services]]'''. For more information see the Services section.
  
 
=Default Request Class=
 
=Default Request Class=
This defines the default request class for email requests. Incoming email requests will be automatically placed in this request class. To configure request classes, go to '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Request_Classes|Administration > Libraries > Request Classes]]'''
+
This defines the default request class for email requests. Incoming email requests will be automatically placed in this request class. To configure request classes, go to '''[[Layton_ServiceDesk_-_Settings_-_Libraries_-_Request_Classes|Administration > Libraries > Request Classes]]'''
  
=Allow Spawning=
+
=Spawning=
This option determines whether Request Spawning will be allowed. For more please see '''[[Layton ServiceDesk™ - Logging A New Request#Spawn Request|Spawn Request]]'''. If turned off the Spawn Request icon will not be displayed on the Analyst Request From.
+
==Allow Spawning==
 +
This option determines whether Request Spawning will be allowed. For more please see '''[[Layton ServiceDesk - Logging A New Request#Spawn Request|Spawn Request]]'''. If turned off the Spawn Request icon will not be displayed on the Analyst Request From.
  
=Spawn Closure=
+
==Spawn Closure==
 
Spawn closure determines how Spawned or Linked Requests are handled when the parent Request is closed. The options are:
 
Spawn closure determines how Spawned or Linked Requests are handled when the parent Request is closed. The options are:
 
<center>
 
<center>
Line 101: Line 106:
 
|}
 
|}
 
</center>
 
</center>
 +
 
=Show ''Copy Request'' Button=
 
=Show ''Copy Request'' Button=
Allows the ''Copy Request to New'' button [[File:Lsd btn copy req to new 24.png|link=]] to appear on the request form. This feature was designed to copy and duplicate a request entirely, including the comments, tasks, and attachments. If set to ''Offi'', the ''Copy Request to New'' button will be completely hidden from the Analyst Request forms.
+
Allows the ''Copy Request to New'' button [[File:Lsd btn copy req to new 24.png|link=]] to appear on the request form. This feature was designed to copy and duplicate a request entirely, including the comments, tasks, and attachments. If set to ''Off'', the ''Copy Request to New'' button will be hidden from the Analyst Request forms.
  
 
=End User Auto Refresh Interval=
 
=End User Auto Refresh Interval=
Line 110: Line 116:
 
Determines how the HD Mins (sys_hdmins) and 24 HR Mins (sys_24hrmins) fields are displayed on the request forms. The HD Mins field will display the amount of time that a request has been open, taking into account the Working Hours and any closed periods or suspensions. The 24 HR Mins shows the amount of time that a request has been open on a full 24 hour basis. The display options are Hrs & Mins (1hr 30m) or Decimal (1.5).
 
Determines how the HD Mins (sys_hdmins) and 24 HR Mins (sys_24hrmins) fields are displayed on the request forms. The HD Mins field will display the amount of time that a request has been open, taking into account the Working Hours and any closed periods or suspensions. The 24 HR Mins shows the amount of time that a request has been open on a full 24 hour basis. The display options are Hrs & Mins (1hr 30m) or Decimal (1.5).
  
=Pop Up Solution=
+
=Pop Up=
This field is used to determine if Layton ServiceDesk will prompt an Analyst when a request is being logged that there is a possible solution to the Request Type that they have selected. For more information on Solution Pop Ups please see the '''[[Layton ServiceDesk™ - Solution Base#Solution_Pop-Ups|Solution Pop-Ups section]]'''. The options are:
+
==Pop Up Solution==
 +
This field is used to determine if Layton ServiceDesk will prompt an Analyst when a request is being logged that there is a possible solution to the Request Type that they have selected. For more information on Solution Pop Ups please see the '''[[Layton ServiceDesk - Solution Base#Solution_Pop-Ups|Solution Pop-Ups section]]'''. The options are:
 
<center>
 
<center>
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
Line 129: Line 136:
 
|}
 
|}
 
</center>
 
</center>
 +
==PopUp If Priority Change==
 +
A pop up can be generated if the Priority changes.
 +
 
=Mark Request as Responded When=
 
=Mark Request as Responded When=
 
This setting determines when a request is considered to have been responded to. For more information on Request Response please see the Priority / SLA section.
 
This setting determines when a request is considered to have been responded to. For more information on Request Response please see the Priority / SLA section.
 
If this is set to "On Assignment", when a request is assigned to an Analyst it is marked as responded. If this is set to "On First Public Comment" the request will only be marked as responded when an Analyst adds a Public Comment. A Public Comment is a comment that the End User can view and a copy of the comment will be emailed to them.
 
If this is set to "On Assignment", when a request is assigned to an Analyst it is marked as responded. If this is set to "On First Public Comment" the request will only be marked as responded when an Analyst adds a Public Comment. A Public Comment is a comment that the End User can view and a copy of the comment will be emailed to them.
 +
 +
=Color Options=
 +
These settings will determine the color indicator that will be applied to any Requests, Tasks (Actions) or Problems that have reached that particular level of escalation. The system provides up to three levels of escalation before expiry. You can select a color against any level (or none) and as a Request, Task or Problem reaches each level the color in the list views will change color to that specified. The escalation and expiry parameters are set against a Priority or Service Level Agreement. See the Priority and Service Level Agreements section for further details.
 +
<center>
 +
{| class="wikitable" border="1"
 +
|-
 +
! style="background:#009999; width: 200px; color: #FFFFFF"|Setting
 +
! style="background:#009999; width: 50px; color: #FFFFFF"|Color
 +
! style="background:#009999; width: 100px; color: #FFFFFF"|Code
 +
! style="background:#009999; width: 650px; color: #FFFFFF"|Description
 +
|-
 +
|Response Missed Request Color
 +
|[[File:Lsd admin req stg col01.png|center|link=]]
 +
|#FF1493
 +
|Requests that have not been responded to in time.
 +
|-
 +
|Escalated 1 Request Color
 +
|[[File:Lsd admin req stg col02.png|center|link=]]
 +
|#99FF99
 +
|Requests that have been escalated to level 1.
 +
|-
 +
|Escalated 2 Request Color
 +
|[[File:Lsd admin req stg col03.png|center|link=]]
 +
|#FFFF99
 +
|Requests that have been escalated to level 2.
 +
|-
 +
|Escalated 3 Request Color
 +
|[[File:Lsd admin req stg col04.png|center|link=]]
 +
|FFCC66
 +
|Requests that have been escalated to level 3.
 +
|-
 +
|Expired Request Color
 +
|[[File:Lsd admin req stg col05.png|center|link=]]
 +
|#FF6666
 +
|Requests that have expired.
 +
|}
 +
</center>
 +
==Color Whole Row==
 +
This setting determines if the escalation color settings as described above will be applied to the whole row in the list view or just applied to the Priority cell.
 +
 +
=Currency=
 +
Determines the currency symbol used in the Request Cost sheets and reports.
  
 
=Enable Request Class Tabs=
 
=Enable Request Class Tabs=
 
If Request Classes are being used this setting determines if the list views for the different Request Classes are displayed in different tabs or if they will be displayed in a single list. Figure 55 and Figure 56 below show the result of the two settings (Please note that Request Class Tabs are only applicable to the Analyst’s request list views not End Users). For more information on Request Classes please see the Request Classes section.
 
If Request Classes are being used this setting determines if the list views for the different Request Classes are displayed in different tabs or if they will be displayed in a single list. Figure 55 and Figure 56 below show the result of the two settings (Please note that Request Class Tabs are only applicable to the Analyst’s request list views not End Users). For more information on Request Classes please see the Request Classes section.
  
Request Class Tabs turned on:
+
==Request Class Tabs Disabled==
 +
[[File:Fig56.png|center|link=]]
  
 +
==Request Class Tabs Enabled==
 
[[File:Fig55.png|center|link=]]
 
[[File:Fig55.png|center|link=]]
  
Request Class Tabs turned off:
+
=Display Company Separately=
 
+
[[File:Fig56.png|center|link=]]
+
  
=Color Options=
+
=Change Closed Request status on User Comment to=
*Response Missed Request Color
+
If an End User sends a comment email to Layton ServiceDesk for a closed Request, the status can be changed to one of type '''[[Layton ServiceDesk - Settings - Libraries - Request Statuses#Continue|Continue]]''' or '''[[Layton ServiceDesk - Settings - Libraries - Request Statuses#Suspend|Suspend]]'''. Select the desired status in the menu.
*Escalated 1 Request Color
+
<p align="right">[[Layton ServiceDesk - General Settings - Problem Settings |<u>Next article in this series: ''Problem Settings''</u>]] [[File:Btn forward.png|link=Layton ServiceDesk - General Settings - Problem Settings]]</p>
*Escalated 2 Request Color
+
<p align="right">[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk]] [[User Guide for Layton ServiceDesk|<u>Back to Contents</u>]]</p>
*Escalated 3 Request Color
+
*Expired Request Color
+
 
+
These settings will determine the color indicator that will be applied to any Requests, Tasks (Actions) or Problems that have reached that particular level of escalation. The system provides up to three levels of escalation before expiry. You can select a color against any level (or none) and as a Request, Task or Problem reaches each level the color in the list views will change color to that specified. The escalation and expiry parameters are set against a Priority or Service Level Agreement. See the Priority and Service Level Agreements section for further details.
+
 
+
=Color Whole Row=
+
This setting determines if the escalation color settings as described above will be applied to the whole row in the list view or just applied to the Priority cell.  
+
 
+
=Currency=
+
Determines the currency symbol used in the Request Cost sheets and reports.
+
<p align="right">[[Layton ServiceDesk™ - General Settings - Problem Settings |<u>Next article in this series: ''Problem Settings''</u>]] [[File:Btn forward.png|link=Layton ServiceDesk™ - General Settings - Problem Settings]]</p>
+
<p align="right">[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk™]] [[User Guide for Layton ServiceDesk™|<u>Back to Contents</u>]]</p>
+

Latest revision as of 04:59, 26 July 2018

Btn back up.png Back to Contents

Contents

[edit] Overview

This section contains settings that will determine the default values when a new Request is logged, such as the assignment & ownership, default Status, Priority and other fields along with the escalation colors and a number of other configuration settings.

ink=

[edit] Ownership & Assignment

Lsd admin req stg02.png

[edit] Ownership

[edit] Owned By Default

This specifies the default value for the Request Owned By field when a new request is logged by the Analyst in the web interface.

Decide who and how Request Ownership will operate and what or whether a default should be used. The normal practice would probably use the Help Desk first line Analysts as always owning a Request, even when the Request is assigned on to a Support Analyst or Group. However, this is totally configurable and you can decide to manually set or transfer ownership at any time, even after a default owner has been specified.

Alternatively you may decide not to use Request Ownership and therefore the Analyst Request form will not include "Owned By" and the default "Owned By Default" will be set to "off".

Setting Description
Off Ownership not automatically set
Logged in Analyst (default setting) Ownership defaults to Analyst logging the Request
Use Specified Ownership defaults to the Analyst Specified. The specified Analyst can be selected by clicking the select button next to the Owned By Specified field.

[edit] Owned By Specified

When Owned By Default is set to Use Specified, use this field to select the default analyst. This will default all requests to ownership by the selected analyst. You can still modify each request's ownership if desired.

[edit] Assignment

[edit] Assigned To Default

Specifies the default value for the request "Assigned To" field when a new Request is logged or a new End User Request is logged. There are three options:

Setting Description
Off Assignment not automatically set
Logged in Analyst (default setting) Assignment defaults to Analyst logging the Request
Use Specified Assignment defaults to the Analyst Specified. The specified Analyst can be selected by clicking the select button next to the Assigned To Specified field.

[edit] Assigned to Specified

When Assigned To Default is set to Use Specified, use this field to select the default analyst. This will default all requests to assignment to the selected analyst. You can still modify each request's assignment if desired.

[edit] Status, Priority

[edit] Default Status

This defines the default Status for newly created Requests. Requests Statuses are defined in Administration > Libraries > Request Statuses. For more information see the Request Statuses section.

[edit] Default Priority/SLA

This defines the default Priority for newly created requests when created by an Analyst or the End User in the web interface. Note that this will not set the Priority for Requests created from emails. See this workflow for a configuration that will set the default Priority for new Requests created by any method.

If the Priority field is not present on the form (common in many configurations), the Priority will be set to (None) on Request creation regardless of the setting.

Requests Priorities are defined in Administration > Libraries > Priority / SLA. For more information see the Priority / SLA section.

[edit] Default Urgency

This defines the default Urgency for newly created requests. Urgencies are defined in Administration > Libraries > Urgency. For more information please see the Urgency section.

[edit] Default Impact

This defines the default Impact for newly created requests. Impacts are defined in Administration > Libraries > Impact. For more information please see the Impact section.

[edit] Default IT Services

This defines the default Service for newly created requests. Services are defined in Administration > Libraries > Services. For more information see the Services section.

[edit] Default Request Class

This defines the default request class for email requests. Incoming email requests will be automatically placed in this request class. To configure request classes, go to Administration > Libraries > Request Classes

[edit] Spawning

[edit] Allow Spawning

This option determines whether Request Spawning will be allowed. For more please see Spawn Request. If turned off the Spawn Request icon will not be displayed on the Analyst Request From.

[edit] Spawn Closure

Spawn closure determines how Spawned or Linked Requests are handled when the parent Request is closed. The options are:

Setting Resulting Action
Allow (Only after Children are closed) The parent Request can only be closed once any Spawned or Linked child requests are closed.
Allow (Close Children) When the parent Request is closed any Spawned or Linked Child requests will be automatically closed.
Allow (Do not close Children) If the parent request is closed any Spawned or Linked child requests will be left open.

[edit] Show Copy Request Button

Allows the Copy Request to New button Lsd btn copy req to new 24.png to appear on the request form. This feature was designed to copy and duplicate a request entirely, including the comments, tasks, and attachments. If set to Off, the Copy Request to New button will be hidden from the Analyst Request forms.

[edit] End User Auto Refresh Interval

This sets the amount of time between each auto-refresh for the end users.

[edit] Statistics Duration Display

Determines how the HD Mins (sys_hdmins) and 24 HR Mins (sys_24hrmins) fields are displayed on the request forms. The HD Mins field will display the amount of time that a request has been open, taking into account the Working Hours and any closed periods or suspensions. The 24 HR Mins shows the amount of time that a request has been open on a full 24 hour basis. The display options are Hrs & Mins (1hr 30m) or Decimal (1.5).

[edit] Pop Up

[edit] Pop Up Solution

This field is used to determine if Layton ServiceDesk will prompt an Analyst when a request is being logged that there is a possible solution to the Request Type that they have selected. For more information on Solution Pop Ups please see the Solution Pop-Ups section. The options are:

Setting Description
None Turns off the Solutions Pop Ups, irrespective of whether individual Solutions have the Solution Pop up field set to Yes.
Specified Only Will only pop up Solutions linked to the Request Type that have the Solution Pop Up field set to Yes.
All Will pop up all Solutions linked to the Request Type, irrespective of whether the individual Solutions have the Solution Pop Up field set to Yes or No.

[edit] PopUp If Priority Change

A pop up can be generated if the Priority changes.

[edit] Mark Request as Responded When

This setting determines when a request is considered to have been responded to. For more information on Request Response please see the Priority / SLA section. If this is set to "On Assignment", when a request is assigned to an Analyst it is marked as responded. If this is set to "On First Public Comment" the request will only be marked as responded when an Analyst adds a Public Comment. A Public Comment is a comment that the End User can view and a copy of the comment will be emailed to them.

[edit] Color Options

These settings will determine the color indicator that will be applied to any Requests, Tasks (Actions) or Problems that have reached that particular level of escalation. The system provides up to three levels of escalation before expiry. You can select a color against any level (or none) and as a Request, Task or Problem reaches each level the color in the list views will change color to that specified. The escalation and expiry parameters are set against a Priority or Service Level Agreement. See the Priority and Service Level Agreements section for further details.

Setting Color Code Description
Response Missed Request Color
Lsd admin req stg col01.png
#FF1493 Requests that have not been responded to in time.
Escalated 1 Request Color
Lsd admin req stg col02.png
#99FF99 Requests that have been escalated to level 1.
Escalated 2 Request Color
Lsd admin req stg col03.png
#FFFF99 Requests that have been escalated to level 2.
Escalated 3 Request Color
Lsd admin req stg col04.png
FFCC66 Requests that have been escalated to level 3.
Expired Request Color
Lsd admin req stg col05.png
#FF6666 Requests that have expired.

[edit] Color Whole Row

This setting determines if the escalation color settings as described above will be applied to the whole row in the list view or just applied to the Priority cell.

[edit] Currency

Determines the currency symbol used in the Request Cost sheets and reports.

[edit] Enable Request Class Tabs

If Request Classes are being used this setting determines if the list views for the different Request Classes are displayed in different tabs or if they will be displayed in a single list. Figure 55 and Figure 56 below show the result of the two settings (Please note that Request Class Tabs are only applicable to the Analyst’s request list views not End Users). For more information on Request Classes please see the Request Classes section.

[edit] Request Class Tabs Disabled

Fig56.png

[edit] Request Class Tabs Enabled

Fig55.png

[edit] Display Company Separately

[edit] Change Closed Request status on User Comment to

If an End User sends a comment email to Layton ServiceDesk for a closed Request, the status can be changed to one of type Continue or Suspend. Select the desired status in the menu.

Next article in this series: Problem Settings Btn forward.png

Btn back up.png Back to Contents

Personal tools
Namespaces

Variants
Actions
Main Page
Online User Guides
General Support
Release Notes
Toolbox