Configuration
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...
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...
From the 4.2.230 version, it is possible to activate two new modes on the Web Portal. The modern mode includes the tiles and the colors. Activating the modern mode requires some modification and preparation, but above all, it implicates all the teams that are visible on the Web...
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.
The event management module is used in Octopus to receive, categorize and take over events.
In Octopus, parts are considered consumables or physical items that do not require management in Configurations module.
This article describe both sections of CI Costs tab : Purchase which contain fields related to the purchase of a CI; and Costs which shows the cost breakdown that is used in the total cost of ownership (TCO) calculation.
Related Articles
Custom Field Library
User Management
Pages
