Configuration

Updated date: 10 January 2020
The "task" concept is applied in Octopus for service requests, changes and problems. Tasks are created to reflect the execution process ("workflow") of a service request, the steps for preparing and implementing a change and the tasks involved in analyzing a problem; in all cases, they can be...
Updated date: 28 August 2018
On startup, Octopus comme pre-loaded with different templates. However, some settings are specific to your organization and need to be configured before you can use the system in an efficient way. To ease the transition, we invite you to consider, in order, the following advices.
Updated date: 24 January 2020
Introduction By default Octopus comes with a variety of options configured to meet the needs of most environments. Many of these options can be modified directly in Octopus.
Updated date: 11 July 2019
We can make basic customizations to your Web portal (add your logo, rename center services, etc.). These basic changes are free of charge.
Updated date: 23 May 2017
When you manage a service, it is important to measure it to find out what are its strengths and weaknesses. From the information that is gathered, you can make changes to processes, give training or coaching to employees, communicate more information to the customers, etc. to improve on what the...
Updated date: 10 April 2017
In a company, it often happens that people from different departments have to work together to deliver a Service Request. Octopus enables End Users to receive Tasks and participate in the execution of a request. They are called "External Assignees". The delivery of the Service Request is more...
Updated date: 17 October 2018
It is possible to integrate and track all the changes implying the IT Department in an efficient and centralised manner by using the Octopus Changes module. This article describes the functional use of the module. 
Updated date: 18 March 2020
Related articles Activities in Octopus Introduction The activity types are used to standardize the information entered into Octopus by the Octopus users.
Updated date: 12 July 2017
ITIL recommends that an incident priority is derived from the Impact and the Urgency, based on the context of an organization. Octopus can derive automatically an incident priority by selecting the impact and urgency of a incident.
Updated date: 31 October 2018
Related Articles Custom field library Why this conversion is important for you

Pages

Subscribe to Configuration