Octopus Options on Demand

SHOW ALL CONTENT

Table of contents

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.

But as each company / service has its needs, constraints and requirements, we also have several options that are available, but that can not be configured directly in Octopus.

In this article, we propose to list the hidden Octopus options that could be useful. This list will of course be updated as new options are added, so we recommand visiting this page often. 

To request one of these options, the authorized Octopus administrator must make a request to our Service Desk stating:

  • The name of the environment
    • It can be found in Tools > Display installation kit address.
  • The name of the team
  • The name of the option

 

What you need to know : 

The options presented in the table are all configurable by team, except when indicated.

Visual Support

To better explain the option in question, we sometimes add visual support:

Click the icon to see the picture

Click the icon to see the video

 

https://wiki.octopus-itsm.com/en/articles/octopus-options-demand

General Options

Description

Modify the Default Source of Requests

When a request is created directly in Octopus, by default, the source is Telephone. This choice can be modified  for another as needed.

It is also possible to leave the field empty by default, to force the Octopus user to make a choice when creating the request.

  • Option name
    • Sources.UseDefaultValue
    • To modify the default value, we add a choice.
    • To force a choice by default, we leave empty. 

Open the Internal Annoncement in Another Window

Because sometimes the messages are long or you want to keep them easily accessible, you can change the behavior of the internal annoncement to open in a separate window.

  • Option name
    • InternalAnnouncement.ShowInNewWindow

Modify the Hours of the Deployment Calendar

By default, the week view of the deployment calendar displays deployments from 7:00 to 00:00. But it is possible to change these hours as needed.

  • Option names
    • DeploymentCalendar.StartTime
    • DeploymentCalendar.EndTime

Valid Approval Responses for Email

By default, when a reply to an approval is received by email, Octopus accepts Yes, No, Oui, Non as an answer. But in some contexts we want to add other valid answers, such as OK, Alright.

In addition to the option, note the answers to add.

  • Option names
    • For positive response MailIntegration.PositiveApprovalResponses
    • For negative response MailIntegration.NegativeApprovalResponses

User Profile Modification on the Web Portal

WARNING: This option affects all teams.

By default when a user goes into his profile on the Web Portal, a number of fields can be seen and changed. 

It is possible to block the modification of certain fields. 

It is also possible to display the approval delegation fields at any time.

And to make visible and editable some other fields.

 

For more information see the Additional information in the selection of a user article.  

  • Option names
    • WebUI.EditProfile.ContactInformation.ReadOnly 
    • WebUI.EditProfile.DelegateApprovalTo.AlwaysVisible 
    • WebUI.EditProfile.Site.Visible 
    • WebUI.EditProfile.Departement.Visible
    • WebUI.EditProfile.Local.Visible 
    • WebUI.EditProfile.JobTitle.Visible 
    • WebUI.EditProfile.Pager.Visible

Add or Remove the [Web] Prefix to the Request Subject

By default when a request is created from the Web Portal, [Web] is added to the beginning of the subject.

For example: [Web] I lost my cell phone.

  But this prefix can be removed.

  • Option name
    • WebUI.Incident.BriefDescription.UsePrefix.Enabled

Download the Database - GetDBApp

It is possible to manually download a copy of the Octopus database or automate the download.

To find out more, see the GetDBApp: Downloading the Octopus database automatically article. 

  • Option name
    • CanObtainLastDBBackup

Add the Contact Field to Your Requests

Requests often drag on because the user is a difficult person to reach. Either he works on night or overnight shifts, weekends or is medical staff or travels frequently. 

Many times in these cases, there is another person who is aware of the request and could answer for the user.

Adding the Contact field allows to put this person's name in the request and indicates that this is the person to reach for the request.

  • Option name
    • Incident.Contact.Visible

 

Options Related to Assignment

Description

Resolve on Behalf of the Assigned Octopus User

By default when a person resolves a request, the resolution activity will be associated with the user who did the action.

But in some contexts, mainly for the building management department, the person who enters data into Octopus is not the person who did the work.

It is therefore possible to associate the resolution of the request with the person assigned to the request rather than the one making the data entry.

  • Option name
    • Incident.DeriveResolvedByAssignee 

Automatic Assignment by Site

This option is very often used with the Building Management service, but it can be useful in other contexts as well.

We configure where a type of request should go according to the site and then Octopus will assign the request based on that choice.

Note that the automatic assignment based to the site associates a group, but not a specific Octopus user.

  • Option name
    • SiteAssignment.Enabled

 

 

Options Related to Service Targets

Description

Enabling Service Targets for Initial Response Delay

By default, service targets (SLAs) in Octopus are intended to look at the resolution of incidents and service requests.

But for those who follow these closely it's possible to also activate the initial response SLA. 

  • Option name
    • ResponseSLA.Activated 

Once activated, the configuration is done directly in the reference data.

Exclude Lunch from the SLA

By default, if the hours of a service are from 8:00 am to 4:00 pm, there are 8 business hours, as there is generally minimum staff to provide service during the lunch break.

But for contexts where all people eat at the same time and the service is not available, we can exclude lunch hours from business hours.

  • Option names
    • BusinessHours.Lunch.IsExcluded
    • BusinessHours.Lunch.StartTime
    • BusinessHours.Lunch.EndTime

Add the start and end time for this option. 

Include Weekends to Calculate SLA

By default, business days are from Monday to Friday.

But it is possible to add Saturdays and Sundays to the work week.

  • Option name
    • BusinessHours.IncludeWeekEnd

 

Options Related to CIs

Description

Keep Links Between CIs After the Retirement

By default, when a CI is removed, its links to other CIs are cleared.

But in some contexts we need to keep the link active. This option keeps the links between CI during the retirement.

  • Option name
    • ConfigurationItem.Deactivation.DeleteCIRelationships.Enabled

Link the Request Site to the CI or the User

By default, when creating a request, the request site is associated with the CI site when there is one and if there is no CI, to the user's site.

But it is possible to associate the site of the request with the site of the user at all times.

  • Option name
    • Incident.Site.DerivationMode

 

X
Help us improve our articles








Help us improve our articles