Configuration
This article contains the basic model of the reference data of the section General.
Related Articles
Conversion to custom fields - starting with 4.2.270
The Access Management Solution provides a frame of rules and principles that lead to sound management of accesses to informational assets. It helps to formalize, in Octopus, the accesses granted or revoked, either as part of the arrival of a new employee, a departure, or simply in a request to add...
In the past, the access level of an Octopus user was determined by the selection of permissions from a list of all the permissions available. The modification of the permissions had to be done manually for each Octopus user.
From version 3.8 and beyond, we are introducing the notion of...
During the configuration of the Web portal, some incident templates and SR types can be made visible so that users can generate their request using a web form. The forms created with Octopus can be customized in many ways: the objective is to gather the required information to...
The use of activity types helps minimize data entry for messages sent regularly to users or to help Octopus users enter information in certain situations.
The information contained in a CI record is very important for the Configuration Management and to control the inventory of a business.
In Octopus each CI type allows adding attributes, that represent additional information important to manage this type of equipment.
In...
From the point where the advanced configuration of tasks is used in service requests, it will become mandatory that users submit their requests from the Web portal. Once this technique is used, requests created from an Octopus user, cannot generate the information required as it will...
When creating a new Octopus database, it comes with pre-established configurations to facilitate the integration experience of a request management tool based on ITIL key concepts. This article describes the content of these configurations.
Pages
