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.
In Octopus, parts are considered consumables or physical items that do not require management in Configurations module.
The event management module is used in Octopus to receive, categorize and take over events.
Related Articles Custom Field Library User Management
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.
Small videos on the Custom Field Library This page offers small capsules that illustrate the use of the Field Library in Octopus.
It is possible to mark a request as confidential. It affects the Type of SR or the Incident template as follows : Octopus's automatic notifications are sent only to the requester, only the Requester can see the request on the Web Portal and external assignees...
The multiteam collaboration has been created to improve the work between teams and facilitate the delivery of requests with a common goal. The multiteam simplifies the creation of requests with the possibility to share tasks that affect multiple services in the company. Hence the multiteam...
The possibility to have customized lists provides a huge flexibility, opens new horizons and allows to better exploit the numerous Octopus functionality. You will be able to: Add new lists / modify existing lists, allocate the lists in the desired module, customize the display by...