Release Notes


Current version


-Octopus Section-

Deployment Calendar | Configure Visible Information

You can now choose what information is displayed in the deployment calendar. The Octopus administrator has access to a configuration button at the top right.

See the Deployment Calendar Configuration section of the Deployment Calendar Wiki for more information. 


CI | Many New Options for the Change CI Action

The Change CI action can now modify the Main Contact, the Site and the Local of one or more CIs at a time. 

See the Change CI section of the Service Asset and Configuration Management Wiki for more information. 


Detailed Description | Access the Original Description of the Request

If an Octopus user modifies a request using the form, you can now consult the original version with the Initial Description link. 

This link is available only if there has been a modification. 

You can also use two new columns in lists and advanced search:

  • Initial Description
  • Form Modification Date

See the Where to Find the Original Description of a Request section of the Custom Field Library Wiki for more information. 

-Octopus 5 Section-

Forms| Supports the custom forms

Incident / SR creation is done using the forms from the SR and incident types.

Visual explanation


Lists | Grouping in lists

The configuration and grouping of your lists are reflected in Octopus 5.

Note: The modification to sorting or grouping of lists must still be done through the Windows application for the moment.

Visual explanation

 Watch little video

Search | Quick search for incidents, SR, CI and users

Quick Search now works to search for Incident, SR, CI, and User data.

This feature will be improved in future releases to search for other data. But already one of the advantages is that the search is done on several modules at once.

Visual explanation

 Watch little video


Navigation History | New Concept

Octopus 5 now offers the ability to see your navigation history. The last 50 items that have been accessed are visible when you select the button.

In the advanced search of the Windows version of Octopus you can also see the last 300 elements that have been opened by various Octopus users in Octopus 5.

Visual explanation

 Watch little video



Bug fixes and performance improvement

This version does not contain any new visible features.



Bug fixes and performance improvement

This version does not contain any new visible features.


4.2.270 to 4.2.320

Internal announcement | New permission Modify internal announcement

A new permission called Modify internal announcement allows you to control who can change the announcement.

We invite you to review which role should have this permission. Consult the Role Management article for more information. 


Internal announcement | Ability to open the internal announcement in a separate window

If your internal announcements are often very long, you can opt to display them in a separate window.

Contact us if you wish to enable the InternalAnnouncement.ShowInNewWindow option. 


Incident / SR | We can now change the default source

When a request is created from Octopus, the default source is Telephone. This source can now be modified.

To change your default source, contact us and mention the Sources.UseDefaultValue option and your default source choice.

New Feature | Launch of the Custom Fields Library


It is now possible to use the fields from your forms in searches and lists. This will allow you to exploit the data entered by users when creating requests using forms.

This new option, however, modifies the behaviour of the Detailed description field in requests. The Custom fields library and changes to the Detailed description field will be deployed with version 4.2.290.

For existing customers, an article helps you prepare for the Conversion to custom fields.

See the Custom field library article for the complete information on how to use the library.  


Octopus | Adding the summer logo

Here is the summer logo that was voted during the Journée des utilisateurs on May 28th.


SR | Automated resolution after notification

You can now create SR types that send a notification as soon as the request is created and resolve automatically.

To do this, make sure that the SR type contains only a Notification task with the recipients and that the automatic resolution option is enabled on this type.

See the Using Notification Tasks section of the Task Management article for more information on this type of task.

Wiki | New field Show All Content

A new field has been added at the top of each Wiki page.

When you click the field, it automatically opens all the accordions contained in the page and makes it easier to print.

When you click the  field, it automatically opens all the collapsed sections contained in the page and makes it easier to read and print.


Help menu | We can now copy the address of the page 

Several reference pages are available under the Octopus Help menu. Most of these pages are also available in an Internet browser.

To get the link of the page, right-click and copy current page's address to send it to another person or look it up out of Octopus. 

For more information, see the How to copy the address of an Octopus reference page into a browser page. 

User info | User list with additional information

In version 4.2.160 we introduced the possibility of adding information beside the name of a user in the Web Portal and in Octopus. 

We have now added another field:

  • [User.EmployeeNumber] - Employee Number

For the other choices and to learn more about this option, see the Additional information in the selection of a user page. 


Deployment Calendar | Complete history now available

We can now consult the deployment calendar past the last three months. 

Deployment Calendar | The weekly view can show a 24 hour range

By default, the week view of the deployment calendar shows the deployments from 7:00 to 00:00. As most deployments are done out of this range a new option allows to modify the start time of the range, for example to 00:00 in order to see 24 hours at a time. 

Contact us if you want to modify your time range and mention the DeploymentCalendar.StartTime option.

See the Change Management and Deployment calendar Wikis to find out more about these elements in Octopus.  

Tasks | Behaviour for contributors outside of the SR module is now different

Members of a group assigned to a task in a module where they have no access are now considered as contributors and they will have more control over the task. 

For example, if the Technician group does not have access to the Change module, but has been assigned a task from a change, the behaviour will now be different. 


Previous behavior New behavior

The person assigned to the task

  • Can see the task
  • Can add an activity
  • Can modify the status and complete the task
  • Can reassign the task
  • Can do other modifications based on his permissions


Other members of the group

  • Can see the task

All members of the group

  • Can see the task

  • Can add an activity

  • Can modify the status and complete the task

  • Can reassign the task

  • Can do other modifications based on their permissions



Web Portal | New look



A new look for the Web Portal and WebTech is now available.


Important notes

  • To minimize the impact of this new look on your users it needs to be activated manually.
  • The new look also affects smart devices. 
  • The new look is only compatible with newer versions of browsers. In the old browsers (IE9) the old look is presented.
  • The application features stay the same. 
  • Activating the new look will affect all teams that use Octopus in your organization.

Our recommendations

How to activate?

From the Tools > Options > Modern Web Portal and activate the option. To be able to do this action, you must have the Modify common team data permission in one of the Octopus teams. 

Warning; this action affects the Web Portal for all teams. 

Web Portal | New experience using tiles to create requests



Your users can now benefit from a brand new request creation experience that accompanies the user in discovering the services offered and in selecting the type of request he wants to submit.


Important notes

  • Activating this experience will affect all the teams that use Octopus in your organization. 
  • The experience also affects smart devices. 
  • Preparation needs to the be done before activating this experience. You will need to prepare images and descriptions for each team (service) as well as the categories for incidents and service requests. You will probably opt to reorganize your incident templates and SR types. 

Our recommendations

  • Start by reading the Web Portal - Setting up the modern mode Wiki.
  • Make sure to plan things.
  • If you have more than one team in Octopus, make sure everything is ready before going into production.
  • Communicate the changes to everyone who will be impacted.
  • Run some tests!

How to activate?

Contact us to activate the tiles! And mention the option WebUI.CreateRequestWizard.Enabled.

Teams | Configuration of the basic characteristics of the teams

You can now configure the basic characteristics of a team such as the name, the image that will be used in tiles, instructions, etc.

To configure these options, go to Options >  Reference data management > Teams.

You must have the Modify common team data permission to modify this information.


Survey | Option to force the user to add a comment

We can now force a user who is not satisfied to add a comment to explain why. The comment could even be mandatory at all times. 

Go to Tools > Option > Satisfaction survey to activate this option. 

For more information, see the Octopus Satisfaction Survey Overview article. 


Major incidents | Synchronizing the status of child requests

The parent-child relationship between a major incident and the child incidents created by the users now synchronize changes to the parent status to the child requests.

If, for example, the parent request is suspended, the child requests will automatically be suspended.

For more information on the parent-child relationship or to find out more about the different types of relations between requests, see the Request Relationships article.

Web Portal | Option to view cancelled requests

There is now an option to view cancelled requests in the list of recent requests and in the history on the Web Portal.

Go to Tools > Option > Visibility of cancelled requests via the Web Portal to activate this option.

Find out more with the Web Portal Operation Wiki. 

Planned Requests | Improved control to the subject of the generated requests

We have improved the control to the subject of the generated requests using the variables available for the subject:

  • Name of the template
  • CI Type 
  • CI Model
  • CI Name
    • Will be Mutiple CI if more then one CI is covered by the request. 
  • Planned Date

By default the subject is composed of the following variables Name of the template - CI Name - Planned Date

Contact us if you want to modify this configuration. 

See the Planned Request Management Wiki to find out more about this solution. 


Bug fixes and performance improvement

This version does not contain any new visible features.


SR | Automated SR creation from MailIntegration

You can now automate the creation of SRs from an external system capable of forwarding emails (will be supported in Octopus soon). The operation is simple:

1. Configure the external system to send an email with content that matches the expected format to a new email address.

2. Set up a new task with MailIntegration to process messages from this mailbox.

This feature allows you to create SRs by specifying the custom fields of the template, which will trigger the right tasks based on the specified SR type.

Contact us for more information on the possibilities and configuration of this option. An article with more information will be available soon.

Web Portal | Maximum levels of sub-sites

It is now possible to specify the maximum number of sub-site levels that the requester can specify in a request. This is convenient to avoid going too far in the site structure.

For example, if the locals are at level 4 of your structure and you do not want the requester to specify the location with in such detail, specify a maximum of 3 levels.

When you configure the form, just add a maximum number of levels to the Site type field.

MailIntegration | Approval with the email response from an Outlook delegate

MailIntegration now recognizes delegates in the emails received.

If someone uses this feature from their email to approve a request on behalf of someone else, the system will recognize the situation and process the approval accordingly.

The message will say "Name the delegate" on behalf of "Name of the person who received the approval".

Marjor incidents | Quicker classification of child requests

When a major incident occurs, it is often tedious to classify all the incidents that users create to report the same situation.

The parent-child relationship feature between the major incident and the multiple incidents created by the users allows the automatic child classification.

When linking a parent incident to one or more child incidents, the parent's classification information is automatically assigned to the child requests.

The copied fields are:

  • Priority
  • Impact
  • Urgency
  • Category / Subcategory
  • Service
  • CI in cause

Services | Requests history linked to a service

In a typical service catalogue, you create Service type CIs and associate each SR type with the Service to which it belongs.

The requests tab of a Service CI now also includes requests of SR types that points to this service.

You can quickly answer the question, "What are all the requests I received for my Email Service?”


Bug fixes and performance improvements

This version does not contain any new visible features.


MailIntegration | Approval by email possible with an approver pool type group

The option of a single approver who receives a request for approval with MailIntegration deployed has allowed to approve or deny with simply a "yes" or "no" answer to the email for a long time. 

This option now also works when an approval request was first sent to a pool of approvers meeting these conditions:

  • The task has been assigned in Direct mode to an approvers pool type group.
  • The task has not yet been assigned to a specific approver. 
  • The action of approving or denying the request will automatically assign the task to the respondent.


Communication | Now easier to communicate with a task assignee


When sending an activity by email, the list of quick choices allows to communicate easily with the person responsible for the request. 

The task assignee has now been added to the available choices in the list to facilitate the communication. 

Visual explanation


Permissions | Adjustment of the permissions to modify the Show requests from all the groups that are normally filtered by groups field.


We have adjusted the permissions required to allow an Octopus user to modify the Show requests from all the groups that are normally filtered by groups field. 

An Octopus user must now have one of the following permissions to modify this field:

  • Administer Octopus
  • Create and modify an Octopus user

See the Permissions section of the Role Management Wiki, to see the complete list of Octopus permissions.



SR | Configuration by type of request for the Automatic resolution option


There has been a global option called Automatic service request (SR) resolution for a long time that allows to automatically resolve an SR as soon as the last task is completed or cancelled. 

It is now possible to configure this option per SR type, from the Advanced tab. 

Visual explanation


Web Portal | User lists with additional information

It is now possible to configure the information displayed in the user lists on the Web Portal.

The available fields are:

  • [user.logon] - Windows Username
  • [user.department] - Last department level
  • [] - Last site level
  • [user.jobtitle] - Title
  • [user.departmentfullname] - Complete department name, including sub-departments
  • [user.fullphone] - Phone number with extension

Communicate with us to find out more on this option. 

Visual explanation


MailIntegration | Assign a template to incidents created with MailIntegration

Incidents created from emails that are processed by MailIntegration have no template. 

A new action called Select the template allows to select an incident template and fill out the form linked to it.

Visual explanation


Reports and statistics | Improved settings of some graphs

The filtering parameters offered for these graphs have been standardized:

  • Request types by month
  • Request type breakdown
  • Planned requests breakdown

  • Planned request cumulative realization
  • Average response and resolution delay

To find out more on these reports, see the Reports and Statistics Module Wiki.  


CMDB | The order of the attributes of a CI is now configurable

You can now control the display order of the CI attributes. This allows you to group them without having to assign a prefix to each attribute.


DataImporter | Import the order for the attributes of a CI type

You can now manage the display order of the CI attributes directly from the import.
The  DataImporter - Import attributes for CI types Wiki article describes how this is done from version 4.2.150 and on. 


Reports and statistics | New report - Average response and resolution delay

The new Average response and resolution delay report will be a usefull tool to achieve and maintain good service targets.
The Reports and Statistics Module Wiki article will be updated with this new information shortly.


Incident/SR | Modification to the request status when an Octopus user is deactivated

When an Octopus user (technician) is deactivated, the requests assigned to his name that are In process will be changed to Assigned in addition to removing his name from the assignment section. 


This behaviour could result in multiple requests that were previously In process without an assignee name to be found in the New and To take assignment lists and will have to be assigned to another person.


Web forms | Action to duplicate a field in a form

It is common for a form to contain a number of fields that are very similar to each other.

You can now use the Duplicate action to quickly create a copy of a field within the same form.

To do this, select the field to be duplicated and use the button on the right of the delete button.

By default, the new field will be placed under the field with a checkbox or at the end of the form, if no box were checked. 

ADSIReader | Improvement to the AD: Last Logon Date field

ADSIReader now handles better the AD: Last Logon Date when used in a context with multiple domain controllers.

Planned requests | Planned request breakdown

To be harmonized with the new graphs, the Number series has been added to the Planned request breakdown graph.


Reports and Statistics | New report - Request type breakdown

A new graph called Request type breakdown introduces our first pie chart, which offers a global visibility of the time entered through the activities or the number of completed requests for a given period of time.

For more information about reports in Octopus, see the Reports and Statistics Module Wiki, more specifically the part about Request type breakdown.


Reports and Statistics | Now all on the same page

The reports and statistics are now accessible from the Reports and statistics button of the main tool bar, which provides a better overview of the tools to analyze your data.

The documentation for this module has also been revised to reflect this change, see the Reports and Statistics Module Wiki page.

Reports and Statistics | New report - Request types by month

A new graph named Request types per month offers a better visibility of the time entered through the activities or the number of completed requests for more efficient resource management. This report will be very useful for the planned requests management.

For more information on this new report, see the Request types by month section of the Reports and Statistics Module Wiki. 


Octopus forms | Horizontal radio buttons

You can now improve the appearance of your forms by using radio buttons horizontally

This way, you can fit more fields or questions per page.

To find out more, look at the table in the Available field types section of the Create customized forms in Octopus Wiki, as well as the Site section. 

Octopus forms | Minimum site level required

By adding a Site field to a form, you can now specify the minimum level required when the requester completes the request.

For example, if your site structure is like this:

  • Building at 1550 Metcalfe
    • 1st Floor
      • Office 100
      • Office 110
      • Office 120
    • 2nd Floor
      • Office 200
      • Office 210
      • Office 220

You can add a Site type field to your form called "Floor or Office affected" and indicate that the minimum level is 2. This way the requester will need to specify a floor or more in the request.

For more information on this new option, see the Site section from the Create customized forms in Octopus Wiki.

Incident templates and SR types are now available based on the request's site

This modification affects only customers that filter incident templates and SR types according to the site. 

When a requester selects a site or a user from a different site, the system will load the list of requests available for the new site or the other user's site. 

This change is subtle, but allows to support new scenarios even when there are request restrictions by site:

  • A requester "visiting" another site can submit a request specific to this site. 
  • A requester can submit a request for a user from another site. 

For more information, see the How Octopus handles site restriction? section of the Site Management Wiki. 

DataImporter | CI imports now supports the RetirementDate field

For more information on CI imports, consult our DataImporter - Import CIs Wiki. 

Tasks | Can be assigned in a batch

You can now select multiple tasks in a list and use the Assign action to assign them in a single step.

See the How to assign in a batch? FAQ for more information. 


Approval tasks | Configuration of acceptable responses by email

It is now possible to control the valid responses to approve or reject an approval request response received by email. For example, it is possible to configure "OK" as a valid approval response.

Contact us if you want to change the standard response configuration (yes, no, yes, no).

DataImporter | User imports supports the DelegatesApprovalsTo field

To find out more on user imports, see the DataImporter - Import Users Wiki.

Permissions | Finer control over permitted operations for suppliers and contracts

Octopus now offers more control over the permissions related to suppliers, contacts, and contracts.

The permissions are:

  • Create and modify a supplier.
  • Delete and merge a supplier.
  • Create and modify a contact.
  • Delete a contact.
  • Create and modify a service contract.
  • Delete a service contract.
  • Create and modify a lease contract.
  • Delete a lease contract.

See the Permissions section of the Role Management Wiki, to see the complete list of Octopus permissions.

Planned requests | Graph to compare the Planned versus the Completed

The new Planned request cumulative realization graph allows comparing what was Planned versus what was Completed.

In addition, the graph can be viewed by Effort or by Number of requests.

To find out more about planned requests, see the Planned Request Management article or more precisely the section on the Planned request cumulative realization graph. 


Tasks | Reminders in tasks

In addition to incidents and SR, you can now create reminders with tasks. For more information, see the Reminders Management Wiki.


Web forms | Procedure type form

You can now create procedure type forms in incident templates and SR types without the submit button in the form.

Here is an example of what you would use it for:

  • Problem: Let's say you have an IT team and a Telephony team and your users keep submitting telephony requests to the wrong team, using the Any other issue template.
  • Solution: From the IT team you create a template called Telephony problem and you write this text in the template:

"This type of request is managed by the Telephony team, please select this service in the previous dropdown list".

This way, the users will know which procedure to follow.

This works automatically. If a template contains only Header or Comment type fields, without any field that could be entered by the user, then the form will not show the Submit button and will automatically go into a Procedure type.

DataImporter | CI import allows adding the responsible Group

You can now import the responsible Group for a CI. Consult the DataImporter - Import CIs Wiki for the complete documentation about importing CIs.  

DataImporter | Incident/SR update

You can now update incidents/SR with DataImporter. Consult the DataImporter - Import Requests Wiki for the complete documentation about importing incidents/SR. 


Notifications by list | New option My pending notifications 

We have added a new option to allow you to review the list notifications that you did not have time to consult. To access it, go to File > My pending notifications. We also added a button to confirm that one or more notifications have been read. This will give you better control over your list notifications.

To find out more, consult the Notifications Wiki. 

Sites and departments| New note field

A Note field has been added to the department and site reference data to add information, such as who is responsible for a department or who to contact in case of site emergency.

The Note field can be added as a list column to consult the information or use it as a search criteria.


Planned requests | Improvement of the distribution of planned efforts

We added a new column to the planned maintenance workload graph called Completed (planned) that allows to see the efforts that had been planned once the planned request had been completed. 

To find out more about planned requests in Octopus, see our Planned Request Management article, more precisely the Planned efforts breakdown section.


DataImporter | Improvements to the import of attachments

DataImporter now allows to import attachments for users, service and lease contracts, planned requests as well as suppliers / manufacturers. In addition, the attachments can be sent to the proper folders on your network as well as on our servers if required.  

The DataImporter documentation will be revised soon to include these new instructions. Contact us for more information on these types of imports. 


Role Management | New permission Approve a task 

The Approve a task permission was created to allow an Octopus user to manually approve an approval task in the name of another user. An Octopus user without this permission cannot approve a task assigned to another person, but can still approve one assigned to himself. 

See the Role Management Wiki for more information or consult the list of permissions.


Bug fixes and performance improvement

This version does not contain any new visible features.


Multiteam collaboration | Now available

The multiteam collaboration is finally here!

The multiteam collaboration allows to share tasks of many request types with one or more teams (IT, Biomedical engineering, Building maintenance, etc.). With this feature, request duplications will be reduced and provide the end user a simplified experience when their request affects multiple teams.

With this collaboration between teams, the terms Owning team and Collaborating team will now be part of the Octopus vocabulary. The owning team owns the whole service request and delegates tasks to the collaborating team(s). The collaborating team(s) will therefore be assigned one or more tasks to be processed. 

To find out more about the possibilities offered by the multiteam collaboration:

Planned requests | Distribution of planned efforts

A new graph now offers the possibility to visualize your planned maintenance workload. This allows to quickly see the busy periods and effectively reassign maintenances towards periods with more free time. 

To find out more about planned requests in Octopus, see our Planned Request Management article, more precisely the Planned efforts breakdown section. 

Departments | No sub-department limit

As with sites, departments are no longer limited to two levels. You can now add as many sub-levels as required to properly represent your organizational structure. 

DataImporter | Improvement to the import of CI types

DataImporter now allows importing relationships, attributes, categories and the icon of a CI type. The information related to this type of import will soon be added to the DataImporter article. 

For more information on these new import types, communicate with our Service Desk.  

Incident | Site derivation is now based on the user

The site related to the request (Incident/SR) is now based on the user instead of the requester. This is required to properly reflect the location where the work is done, which is in fact the user's site. 

However, requests filtered by site stay linked to the requester's site as well as the restrictions by user group, since these restrictions are a form of permission related to the authorized requester. 

Web Portal | Allows to add an activity to a specific task

Some service requests have a workflow that involves a close collaboration with the requester. In such cases, the requester knows the workflow well and must provide additional information required for the execution of some tasks. 

In an SR type, you can now check the Allow adding specific activities to a task option. Once this option has been activated, and the task is Visible on the Web Portal, when a user adds an activity from the Web Portal, he can select the task in which to add his activity. 

The Allow adding specific activities to a task option is available from the Web Portal tab of the SR type from which you want to collaborate with the requester. 

You can access it from Tools > Reference Data Management > Service request > Types

On the Web Portal, the requester can select to add the message to the service request, or to a specific task in the workflow. 

User module | Group change history in the user file

All changes related to adding or removing an Octopus user from a group will now be recorded in the user's history. 

Notification task | Recipient can be selected between two supervisors

A new type of recipient is available in the notification tasks either the Querent's supervisor or the User's supervisor

Please note that for service requests in process, the two options will be available only if the requester and the user are different. 

Production release 4.1


Bug fixes and performance improvement

This version does not contain any new visible features.


Incident/SR | Configure initial response targets directly in Octopus

It is now possible to configure your initial response time targets directly into the configuration windows of Octopus, without having to contact our Service Desk. 

You can configure the SR targets by SR types and the incident targets by priority, if the initial response targets have been activated. 

Simply contact us if this option interest you and you have not yet activated the initial response targets.

See the Initial response targets Wiki to find out how to configure them.


Description | Visual enhancement of the description field created from an Octopus form

In response to a suggestion, we adjusted the space between the various sections of the Octopus forms in the Detailed Description field of the application and in the Description field on the Web Portal to make the information easier to read and manipulate.

Visual explanation



Bug fixes and performance improvements

This version does not contain any new visible features.


Change | Create an incident / SR from this change

A new action has been added to the Change module to quickly create an SR or an incident from the change. This is especially helpful in the context of a project, where you must create internal service requests to complete portions of the project.

To find out more on this subject, see the Change Management Wiki.

Search | New operators Does not begin with and Does not end with

These new operators allow you to create lists with even more flexibility and better targeting of the desired records.

DataImporter | Use of the Email field as a key when importing users

DataImporter can now recognize and update user files in Octopus using the Email field as the identification key. Use the new "UserByEmail" method in the XML file configuration for DataImporter to use this option.


Configuration | Service desk by sub-site

For the longest time, it has been possible to designate to which service desk are the requests being sent to,  based on a user's site. It is now possible to do this configuration with sub-sites as well.


Support in external mode | New, more flexible option for site selection

Usually, the external support mode does not offer to users the possibility to modify their site on the Web Portal or to search CIs in a site other than their own. 

A new option now allows users to modify their sub-site and search CIs in other sub-sites contained in the same root site. 

To find out more on this support mode, see the Support in external mode Wiki page.  


User search | More information available to identify the user

To identify the user more efficiently, the Windows username is now displayed along with Department and Site when searching for a user's name during the creation of a request. In addition, it is possible to remove the department or site from the visible information, or to change the order of the fields.

Contact us to activate this option.

User file | Local field is now larger

The Local field of the user file has been enlarged to make it easier to view.

Barcode reader | The scanning mode can be deactivated

It is now possible to deactivate the barcode scanning mode. Contact us if you need to have this option disabled.

For more information on the barcode reader, see Using a barcode reader section of the Service Asset and Configuration Management Wiki. 

Send by email and Copy to clipboard buttons | Additional information

The Requester and User fields have been added to the text content when using the Send by email and Copy to clipboard buttons on the right side of the requests. 

For more information on these options, see Useful buttons sections of the Incident Creation and Creation of a service request Wiki pages. 


Bug fixes and performance improvement

This version does not contain any new visible features.


Bug fixes and performance improvement

This version does not contain any new visible features.


Users| Permission to Reset Octopus password

You can now control with more details modifications to Octopus accounts with two additional permissions:

  • Reset Octopus password.
  • Create and modify an Octopus account.

Web Portal | New option to see other users' requests

A plug-in now exists that allows members of a same user group to see each other's request on the Web Portal. These visibility rights are granted per team, in the Reference data management. 

Contact us for more information on this option.


Web Portal | New profile fields available

It is now possible to allow users to modify the Local, Title and Pager fields from their Web Portal profile.


Visual explanation


Contact us to activate this option.

Event Management | CI detection

In addition to the CI Name, The CI detection rules can now identify the CI by Serial Number, Inventory Number or any of the CI custom attributes.


Visual explanation



CI | Barcode reader

You can now use a barcode reader to quickly load a CI file. 

How to use:

Click in the quick search zone of any module to give it a target and scan the barcode.

If the barcode corresponds to the serial number of a CI, the CI file will automatically load. If the barcode is not recognized, Octopus will offer to create the CI or link it to an existing CI.

For more information on this option, see the Using a barcode reader section of the Service Asset and Configuration Management Wiki. 

Tasks| Modification to the reopening rule

A task can be reopened only if the parent request (SR, Change, Problem) is in an Open status. Tasks with the Can be completed after the request's resolution option are not subject to this rule as they do not affect the parent request. 


Lists | Site details available in lists and searches

In lists that offer the Site column, it is now possible to view detailed information about sites, such as the address or hours of operation. It is also possible to search based on these fields.

Visual explanation



Search | Added periods

Searching by date is now more flexible with the addition of the following periods:

  • Tomorrow
  • Next 2 days
  • Next 5 days
  • Next 10 days
  • Next 30 days
  • Next 60 days
  • Next 90 days
  • Last 60 days
  • Last 60 days

Note that the Next type periods include the current date (today).

Task | Added Completed by field

You can now search and produce reports by exploiting the Completed by field in task type records.


Bug fixes and performance improvement

This version does not contain any new visible features.


Bug fixes and performance improvement

This version does not contain any new visible features.


Bug fixes and performance improvement

This version does not contain any new visible features.


Bug fixes and performance improvement

This version does not contain any new visible features.


Bug fixes and performance improvement

This version does not contain any new visible features.


DataImporter | Import Changes

DataImporter now allows importing changes along with all related data (tasks, activities, attachments, costs).

A new element will soon be available in the Data Source Specifications section of the DataImporter Wiki page.

Incident / SR | Reorganization of Actions in Incident module

The order of available actions for incident/SR has been revised to give more emphasis to the most frequently used actions.

Visual explanation

New type of task |External Command

A new tool allows to automate the external workflows with Octopus by using the External Command task. 

An article will be available soon with more information on how to use it.


Bug fixes and performance improvement

This version does not contain any new visible features.


Site configuration | Requests restriction by sub-site

Requests restriction used to be only available with sites. It was possible to limit some sites to specific requests, based on an applied selection of SR and incidents.

From now on, the restriction will also be available to sub-sites, which will allow a better control on multiple levels.  For example, a main site could have access to specific requests, but a user from on of its sub-site could have a different selection applied, based on the sub-site's available requests.


Visual explanation


Document Tab in CI | Content in HTML format

Continuing our constant effort to give a better control over our application, we have continued to implement the HTML format in most sections of Octopus, this time through the Document tab in a CI file.  More options and improved formatting will provide a better user experience.  

Take note that once the field has been converted to HTML (option given through the Document tab on first selection), you will not be able to revert back to the old mode, the change being permanent.

Visual explanation

Windows Username field | Support of multiple accounts for the same user 

In answer to a request made several times by many of you, Octopus will now support the notion of multiple Windows accounts for the same Octopus user.

The "Windows Username" field used to identify the Windows account of the Octopus user can now have several Windows username, by separating each of them with a semi-colon ( ; ). This way, it will no longer be necessary to have several Octopus user files for the same employee.

Task evolution | New columns for SR and tasks progression

A new field is now available to follow up on the progress of tasks, incidents and SRs. The % elapsed time field can be added as a column in lists and advanced searches. 

The column takes the following into account: 

  • Hours of operation and Holidays.
  • Incident / SR
    • Opening Date.
    • Due Date.
    • Suspension.
  • Task
    • Actual Start Date (activation date).
    • Due Date.

Note that the % value of the elapsed time of the task will be void if the task is:

  • Canceled.
  • Inactive.
  • Does not have a Due Date.
What you need to know: 

For reasons of processing time, the update to this version will not calculate the % of time elapsed for incidents / SR and tasks that are already closed. The update time would be greatly impacted. Therefore, only new incidents / SR and tasks will be presented with a value.

Adding this field as a column in a list can help follow the service level targets of groups that miss their due date, especially if you subscribe to the list. To find out how the subscription to lists work, consult the Custom notifications Wiki. 



Notification task | New recipient - Supervisor

The Supervisor of the requester can now be added as a recipient in a notification task. Upon activation, Octopus will use the information in the requester's file to send the email to the right person. 

If no supervisor can be found, an error will be recorded in the task that will be visible in the request. 

See the Task Management Wiki to find out more about the different task types and how to use them.  

Satisfaction survey | Can be filed directly in the closing window

This new option allows to present the user with the satisfaction survey directly in the closing window to avoid having to close the request and then complete the survey, forcing two steps from the resolution email.

Note that because the action is triggered from within the resolution email addressed to the user, the connection connecting to the portal is done without validation.

Visual explanation

For more information on the satisfaction survey, consult the Octopus Satisfaction Survey Overview Wiki.  

For more information or to activate this option, communicate with our Service Desk.  


Changes | Option to modify the fields name in the Documentation tab

It is now possible to modify the name of the fields or remove one or more default fields from the Documentation tab in the Changes Module.  

Default fields:

  • Description.
  • Impacts.
  • Impacts of not implementing this change.
  • Summary of costs and resources.
  • Risk assessment.

  • Contingency plan.

  • Planned downtime.

  • Communication plan.

  • Authorizations.

For more information or to activate this option in your environment, communicate with our Service Desk.

CI | Option to force the serial number to be unique

Requested by many, a new option can be enabled to force the CIs serial numbers to be unique. An error message will be received when creating or modifying a CI with a serial number that already exist, even if it is of a different CI type. This validation will affect the following methods of creating or updating CIs: 

  • Manual creation or update directly in Octopus.
  • Import with DataImporter.
  • WMIUpdater.

No validation will be done on CIs that already exist when activating the option, but it will be done when updating.  

To activate this option, go to the Tools > Options menu and modify the option called Serial number of a CI must be unique.  

Tasks | Estimated effort field has been increased

To facilitate the planning of major projects, the number of possible digits in the Estimated Effort and Remaining Effort fields of tasks have been increased from 00:00 to 0000:00

Satisfaction survey | Allows the modification of the satisfaction level selected by the user

Option that allows to change the satisfaction level and comment added by the user in the satisfaction survey. The Modify satisfaction data permission is required to use this option. Once the permission has been granted, a new action called Modify satisfaction data will be available to the Octopus user. 

When changing the satisfaction data, a window will present to the Octopus user the choices selected by the user at the top, and at the bottom the ones for modification. 

Two new columns have been added to show the initial satisfaction data:

  • Initial Satisfaction Rating.
  • Initial Satisfaction Comment.

For more information on the satisfaction survey, consult the Octopus Satisfaction Survey Overview Wiki page.

Visual explanation

Web Portal | Search field for open requests

To facilitate tracking of opened requests, users with a large number of requests now have access from the Web Portal to a search window. It is accessible at the top of the page and allows to search opened requests by number, subject or description. 


Advanced search | CTRL+ A allows to select or unselect all 

In the advanced search window, use the CTRL + A keys combination on the keyboard to select all or unselect all from a multiple choice window.

For other Octopus shortcuts, visit the Octopus Shortcut Keys page. 

Forms | Can filter CI by type 

We can now filter the CI types that will be presented to the user when filling out the form. 

This option will help the user in his search, as it will only present CIs that are relevant to his problem or request. For example, you can limit the search to only desktops and laptops for a request concerning an email issue submitted by the user.

To find out more about how to use this new option, see the Form Customization in Octopus Wiki. 

Personalized notification | New option 

It is now possible to receive personalized notifications based on an Octopus list. 

Two situations can trigger the notifications from a list: 

  • A new element was added to the list. 
  • A value from the list has been modified.
    • This notification is based on the columns present in the list.

The scope of this new option is big because it will allow to automatically monitor elements that are important for the proper function of services.

To add a notification to a list:

  1. Right click in the list and select Subscription
  2. Select the notification method. 
  3. Validate if a notification needs to be sent out when changes are made to values in the list.
  4. Confirm with OK.

The notification will be sent in the following format: 

  • The notification subject will contain the name of the first column of the list.
  • The notification will contain every column of the list
Visual explanation

For more details, see the Custom notifications Wiki page.


Bug fixes and performance improvement

This version does not contain any new visible features.


IMPORTANT REMINDER | Windows XP SP3 and more

From version 4.1.200, the Octopus application as well as the Web Portal requires Windows XP SP3 or more recent.

CI | Select a category at creation

The CI creation form now includes a field to select the CI category. 

Visual explanation

Timesheets | Consult the calendar of another assignee

It is now possible to see the timesheet of another Octopus user in a calendar format. 

Use the dropdown list on the top right of the calendar to change user.

Visual explanation


To consult the timesheet of another person the Octopus user must have the following permission:
  • Access the dashboard, statistics and reports.

Users | New option that allows to keep the links to CIs when deactivating

There is now an option to instruct Octopus that it should not remove the CI linked to the user when deactivating the user. Contact us to activate this option.

Users | DataImporter can import the Shared account field

When importing users, it is now possible to indicate if a user is for a Shared account

To find out how to import users, refer to the DataImporter - Import Users article.


Department | The number field was added to identify the department

In certain environments, a department can be associated with a name and a number, which means that over time, the name could change, while the department number remains the same.

The Number field was added to the reference data of the Departments node and can be used as follows:

  • Synchronizing with an external source, such as an HR software using DataImporter.
  • Used in advanced searches.
  • Added to lists as a column. 

This will simplify your searches and reports by keeping the department number as a constant in your data.

Department | Import using DataImporter

We have added the possibility of importing departments using DataImporter, to facilitate initial configuration, department updates and synchronization from a source different than AD.

If you use DataImporter to synchronize users or CIs with a source that associates the name of a department to its number, you can easily update the departments when the names change in the source. In addition, you avoid having to merge the new department created when synchronizing with the new name.

You only have to add the department number in the Octopus reference data before changing the name of the department in the source and when synchronizing, Octopus will link with the department number and update the department with the new name.

To find out how to import the departments, your can refer to the DataImporter - Import departments article.

Tabs | Display tabs on multiple lines

If you are of those who have too many tabs open and must navigate from one end of the list to the other with the arrows, this option is for you!

In the Octopus tab of a user file, check the Multi-line Tabs box and the tabs will appear as follows: 

Procedures | Available in HTML

Improve your procedures with the new HTML editor now available in this option.

The following items can be added to your procedures to facilitate consultation by technicians:

  • Numbering
  • Bullets
  • Bold, underline, italic
  • Images
  • Hyperlinks

The procedure will appear in HTML format in the window and will be copied in plain text if it is added in an activity.


Effort management | Behaviour modification

Following effort management implementation, some changes have been made to optimize it.

  • To ease the selection of unused efforts, hold the CTRL key and click to add an activity, the Unused effort details window will appear, allowing you to choose which effort record to include in the activity. When you'll press OK, the Add activity window will appear, already showing the correct time and effort.
  • To access request details, double-click the timer to directly open the Unused effort details window.
  • When an activity type is selected from the Unused effort details window, the text associated with the selected type will be proposed only if the note has not been manually modified.
  • When creating an activity from unused efforts, the activity details will contain the union of all selected efforts.

Refer to the Effort Management article to find out more.

Forms | Destination for combo box

Octopus can push the value selected in a combo box straight to the incident category.

  • Values presented to the user must be present in the category already configured within reference data.
  • If the value selected by the user does not exist or is ambiguous, the category will be left empty in the incident.

For more details, refer to the Incident Creation and Form Customization articles.

Web Portal | Team names when creating requests

When users create a new request, the Service field will be displayed only if the Web Portal is enabled and the user has access to at least one request type.

Refer to Web Portal Operation to find out more.

Permissions | Security strengthened for Modify my Profile permission

The security surrounding the Modify my profile permission has been strengthened as follows:

  • A user with this permission can only modify his own roles tied to the end user license.
  • A user with this permission can only modify his own user group membership.

This way, a user is unable to modify his tech roles or groups to increase his rights.

To modify roles related to standard license or assignation group, a user must have the Create and modify an Octopus account permission.

Refer to the Role Management article for more details on permissions within Octopus.


Forms | Destination for text fields

Octopus can push the content entered in a field of Text or Large text types directly into fields in the request.

  • Text fields can be pushed to the Subject field or to the Detailed description field of the request. 
  • If you already had fields named Subject or Description in your forms, they used to get pushed directly into the corresponding fields of your request. 
    • Your forms were automatically updated to the new way. 
    • The old way is not longer in effect. So you can rename these fields accordingly in your forms. 
  • The alternate subject and the Subject destination option are mutually exclusive.
    • If you use the alternate subject option, the destination option will not be available.
    • If you have configured a field with the subject destination, the alternate subject cannot be edited. 
    • The alternate subject overrides the destination option.

Incidents / SR | Access to the custom fields of the form in the alternate subject

It is now possible to access the fields of a form in the alternate subject with the F3 key. 

Attached files | Paste in text or rich text format

Octopus now supports the copy/paste in text and in rich text, creating a .txt or .rtf file type when pasting. 

To use this feature, go into the Attached files tab and use the arrow under the Paste button to choose the type. 

Effort management | Behaviour modifications

Following the implementation of effort management, some modifications were done for ease of use. 

  • When the timer is set to start automatically, the effort of an activity of under one minute will be rounded up to 00:01. 
  • The application will alert the user when the sum of the efforts is more than 99h59, this way he can take action to prevent the loss of efforts:
    • If the sum was for a selection of multiple efforts, you can change the selection to choose efforts that will add up to less then the maximum time. 
    • If it was only one effort that had more than 99h59, you can create other efforts to distribute the amount of time. 

For more information, see the Effort Management article.

Administration tools | Improved logging tools

The log file created following the use of administration tools was improved in order to detail the parameter that were used. The analysis of the parameters will only be presented in the log file, not in the command window. 

  • One section presents the supported arguments.
  • Another section presents the unsupported arguments. 

To find out more on the log files, refer to the following administration tools articles:

Bilingual environment | Open Octopus in two languages with the same Octopus account

When an Octopus user uses the forms to create requests, the questions and answers in the form will be in the Octopus user's language, that is not always the same one as the user's.

To prevent this, we have created a parameter that can be added to the Octopus shortcut that indicates in which language to start Octopus. 

This way, an Octopus user can have two shortcuts, for example one in English, the other in French and work with two Octopus windows at a time in order to fill in the forms in the user's language. 

  • Right click the shortcut and add the /language parameter with the according language code, at the end of the target field.  
    • /language:fr
    • /language:en
    • /language:pt

What you need to know
  • The language selected does not affect the language of the splash screen. 
  • Using this parameter does not affect the language set in your user file, except if you make modifications to your profile. The active language will be the one saved. 
  • This option is only for the Octopus application started from Windows. 

Permissions | Enhanced security to the Modify common team data permission

The security surrounding the Modify common team data permission has been strengthened as follows:

  • If a user does not have this permission he cannot add it to a role. 
  • If a user does not have this permission he cannot give himself a role with this permission. 

This way, an administrator limited to the configuration of one team cannot give himself additional rights, overriding his access. 

Reference data | Precision in error messages when deleting

Precisions have been added to certain error messages when it is not permitted to delete data. These messages will guide the administrator to deactivate correctly data that cannot be deleted. 


Effort | Effort management

Managing the effort in activities will now be easier thanks to the new effort timer!

The effort timer, in addition to being displayed in every window where it can be used, can also be configured to start and stop automatically. Since the timer counts time toward a single request at once, it will switch over to track the time accordingly for each request.

When you add an activity, the sum of the efforts tracked is proposed. In addition, you can manually select each effort to consume, adjust time spent on request, type or annotate efforts, or remove them altogether.

Visual explanation

For more detail, refer to the Effort Management article. (coming soon)

Effort | Time sheet and effort calendar

In relation to effort management, Octopus offers two ways to display efforts:

  • Effort calendar; a new graphical display.
    • Offers a view of activities with effort, of efforts registered and periods where efforts are missing.
    • Presents the calendar for the current technician, and is browsable by time periods.
    • Available under the Fie > Timesheet (calendar).
Visual explanation
  • Timesheet in report format.
    • Offers the same timesheet as before.
    • Allows for selecting the time period to report on.
    • Available, from now on, under the File > Timesheet (report).
What you need to know:

It is possible to see the timesheet of other technicians, when you have the Access the dashboard, statistics, and reports permission: File > Reports > Activity timesheet menu.


Database | Modified file format for transfer

The file format for the database obtained by using the Tools > Get Database... menu or the GetDB administration tool has been modified.

Instead of providing a .bak file contained in a zip file, the format, from now on, will be switched to an SQL compressed .bak file. This has no impact on the size of the data to be transferred, but reduces the amount of steps in case of a restore.

We invite you to read the article on GetDB for more details.

Requests | Support for alternative subject for manually created requests

Manually created requests from a incident template or SR type will have their alternate subject resolved when configured. The specifics of which are:

  • If an alternate subject is configured, the subject line in the request creation dialog will state The subject will be generated when saved.
  • If an alternate subject references custom fields contained in the form, the form will become mandatory.
  • It is possible to let the user input the subject by adding a custom field named Subject. If this field exist, the alternative subject will be ignored.

Refer to the Alternate subject article for more details.

Requests | Changes to tasks and fields conditions

Changes have been made to the field display and task creation conditions:

  • Completion of the form is mandatory only if conditions exist on answers from the form, directly in the form or in a task condition, as opposed to the fields related to the request itself.
  • Task creation conditions or field display conditions in the custom form allows using a comma to separate multiple valid elements (OR logical) instead of having to use the @OR operator. e.g.:
    • React to two different values from a list
      [AccessDistant.TypedAccess] = VPN, Citrix
    • React to two different values, one of which contains a white space
      [AccessDistant.TypedAccess] = "VPN", "Citrix", "VPN & Citrix"

Quick Search | Adding quick search for interrequest relationships

Quick search (where the repeated request number part of the current team can be omitted) now works as part of request relationship.

Web Portal | Approvals presented to users

Requests containing initial approval tasks will display all required approvals, instead of being limited to the first task. This way:

  • If multiple tasks require the choice of an approver, they will be shown in the approval section.
  • If approval tasks are conditional on form fields, the approval section will update automatically.
  • If an approval task is not created due to its conditions, it could cancel the dependent tasks by using the Cancel dependent tasks upon cancelation option, not to be confused with the cancelation of dependent tasks upon refusal.
Visual explanation

For more information, use the reference document for Automated Approvals.

Database | Support for Microsoft SQL 2014

Octopus now officially supports hosting it's database, for local installations, on Microsoft SQL Server 2014.

Do not hesitate to contact us if you want to migrate your database to the latest SQL version.


Custom Forms | Add comments to forms

A new field type allows to insert free-text blocks in your forms. The comment fields can be tied to a display condition, relating to the values entered in another field.

For more details, refer to the Form Customization in Octopus article.

Reference Data | Site reorganization

You can drag and drop sites to restructure their hierarchy.

IMPORTANT: If you have configurations tied to a primary site (SLAs or request restrictions) that you are moving into a sub-site, it could change the effective configuration or force an SLA recalculation, an operation that could take a while.

Web Portal | EncodedQueryString authentication mode can redirect generic account to an authentication page

Alternative authentication mode for unknown users can recognize shared Windows account flagged as a Shared account in Octopus. When a user connects to the Web Portal using a Shared account he will be prompted for credentials (mode 2: username, password) instead of being denied access to the Portal for using a Shared account.

For more details, refer to the article covering the Web Portal Authentication Mode.

Contact us to have this option enabled.

ADSIReader | Assigning the site from an AD field now supports sub-sites

Configuring the mapping file to an AD attribute to be extracted as the user's site now allows for interpreting the vertical bar as sub-site separator in the following fashion:

Site | Sub-site | Sub-site

For more details, refer to the ADSIReader - Integration to Active Directory article.

WebTech | Visual indicator for activities sent by email

In the WebTech activity log, activities sent by email will now display the recipient name or names.

For more details, consult the Web Portal for Building Maintenance Worker wiki article.


Web Forms | New configuration panel

You will definitely start enjoy configuring your Web forms!

The configuration screen is combined with the preview screen to see modifications in the form as you work. Moreover, the custom fields section can be resized, details for each field can be expanded for your convenience. Enhancing your Web forms will now be child's play.

For more details, refer to the Form Customization in Octopus - AFTER 4.1.130 article. (available soon) 

Visual explanation

General | New HTML editor

No more reasons for not enhance your email templates and other messages in Octopus to improve your communication with users, thanks to the new HTML editor.

Easy to use, the new editor makes editing without any HTML knowledge a breeze, as simple as using Word.

The new editor is available as part of the following functionalities:

  • Web Portal announcement.
  • Internal announcement.
  • Instructions for an incident template or SR type.
  • Field instructions for incident template or SR type custom forms.
  • Email template editor.
Visual explanation

General | Open a tab from a list of tasks or related CI

In the Task or CI tab of a request, the Open list in tab option from the contextual menu will open the same list in a standalone tab. For example, this option could be used to ease the management of changes containing large amounts of tasks.

Problem | Closing rules

The problem module has been improved to enforce closing rules. A problem request can only be closed if all the contained tasks are either completed, canceled or marked as Can be completed after request completion.

Permissions | Finer grained management of user modification permissions

The Modify a user and Create and modify an Octopus account permissions have been unlinked so the user modification permission is not a prerequisite of the creation and modification of Octopus account permission.

This way, the Octopus account options can be modified by users without giving them the permission to modify the user's general information. This is to better reflect the reality of teams importing their users from an external system like Active Directory or companies using multiple teams.

WebTech | Sending activities to supplier contacts

As in the Windows application, WebTech allows to add an active contact from a supplier as an activity recipient.

For more information on using WebTech, refer to the Web Portal for building maintenance workers article.

Reminders | Viewing and modifying other assignees reminders

Viewing request-related reminders created by other assignees is now possible :

  • The View the reminders of other assignees permission allows to see and search other assignees reminders.
    • The owner's name has been added to the reminder.
    • Lists can be created showing other assignees reminders.
  • Full control can be allowed by using the Modify the reminders of other assignees and Delete reminders of other assignees permissions.

For more information, refer to the Reminders Management | Octopus Module article.

Web Forms | Enhancement of conditions (display and tasks)

More conditions are available as part of custom Forms:

  • Conditions can be used  to target request fields (site, querent, user, template).
    • For example, a field can have as display condition :
      @Incident.Querent.Site = Montreal
  • Conditions comparing text strings (in addition to combo box matching).
    • For example, a field can have as display condition:
      @Incident.Querent.Site.ShortName = "Mtl"
  • Conditions comparing text containing a comma can be quote-delimited to isolate its values.
    • For example, a field can have as display condition:
      @Incident.Site = "Quebec, Canada", "Ontario, Canada"

Activity log | Planned removal of the classic mode

The display of the activity log has automatically been switched to the modern (chat-bubble) version, in preparation of the removal of the classic mode.

If the modern activity log does not correspond to your needs, you can switch back to classic mode by going into your profile. However, if you decide to revert to the old mode, it is important to contact us to notify us of your decision. Removal of the classic mode is upcoming and before removing it altogether, we want to hear your thoughts and try to improve the modern view to offer you the best experience possible.

Visual explanation

Classic activity log

Modern activity log

Emails | Planned removal of plain text format

The email format has automatically been switched to HTML, in preparation of the removal of plain text format.

If the HTML format does not correspond to your needs, you can switch back to the plain text format by going into your options. However, if you decide to revert to the old mode, it is important to contact us to notify us of your decision. The removal of the plain text is upcoming and before removing it altogether, we want to hear your thoughts and try to improve the HTML format to offer you the best experience possible.


General | Confirmation when closing a window

Octopus now asks for cancelation confirmation when closing a window where information was entered, either by pressing the escape key or clicking the Cancel button.

Multi-team | Quick search using the short number

In organizations where multiple teams use Octopus, a request number range is assigned to each (1000 to 999 999 range, 1 000 000 to 1 999 999 range, 2 000 000 to 2 999 999 range, etc.). Quick search can search for a request from it's short number (7854) instead of its full request number (3007854).

Supplier & Contact : Disabling supplier or contacts

Unused suppliers and contact can be deactivated. They will disappear from the various lists once they are deactivated.

Incidents/SRs | Options allowing more control on assignment upon resolution and reopening

New options are available allowing more control on assignment upon resolution and reopening:

  • Deactivate the automated reassignation to the Service Center upon resolution. By default, resolved incidents/SR are automatically reassigned to Service Center group. By deactivating this option, the request will stay assigned to the resolution group. In both cases, the assignee will be removed.
  • Activate the automated reassignation to the resolution assignee upon reopen. By default, reopened incidents/SR are not reassigned to an assignee. By activating this option, the request will be reassigned to the resolution assignee, if it is still part of the current assignation group..
Contact us to activate these options.


Web Portal | Options to control proposed languages on the Web Portal

The Web Portal offers three different languages: French, English, and Portuguese. An option is available to hide languages you do not want to offer your users.

Contact us to modify this option.


Bug fixes and performance improvement

This version does not contain any new visible features.


KPI Report | Average effort presented in report

The average effort calculation has been modified in the KPI report. The average resolution delay used to be presenting data based on the Resolution Delay column. As of now, the new calculation uses the Resolution Delay (without suspension) column.

If you use KPI report periodically to track your team's performance, you will have to generate new historical data to maintain your comparison indicators. However, new modifications will take place in the next version.

Incidents | Can be marked as confidential

As it is already the case for Service Requests, incidents can now be marked confidential. For more information, please refer to the confidential requests article.

Mail Integration | Deactivate incident creation

The creation of Incidents through MailIntegration can now be deactivated, sending back a rejection message to the user. This way, MailIntegration can be used to communicate with users from within an established request, without allowing new incidents to be created.

To find out how to deactivate the incident creation and which tag to use, refer to the Configuration File (XML) section of the MailIntegration article. 


Activities | Add work for multiple assignees with a single activity

When an Octopus user adds an activity, he can use the Team Work button to select all Octopus users that contributed to the work.

This will record the effort for each Octopus user, affecting the total effort as well as each Octopus user's timesheet.

The Create an activity on behalf of another assignee is required to use this feature.

For more information, visit the Activities in Octopus article.

Visual Explanation

Categories | Categories deactivation

Categories and subcategories can be deactivated by using the Active check box.

Incidents and reports showing these deactivated categories will continue showing them until changed.

If modified after a category has been deactivated, the inactive values will not be part of the list anymore.

Web Forms | Enhancement for value lists

Value lists can now be modified straight from the Web Form configuration dialog, without requiring to be defined first.

Analyze the impact of modifying a value list by looking at the Usages tab, presenting all Web Forms referencing to the list.

Import value lists with DataImporter, which can be used to feed values from external data. Refer to the DataImporter-Import Value Lists article to know more.

Visual Explanation
  • Modifying a value list
  • Creating a new value list
  • Value list usage


Custom Web Forms | Simplifying combo boxes

Creating custom Web Forms has been simplified by the introduction of the value lists concept for combo boxes and radio buttons. The visual representation has not been modified.

When creating a custom Web Form, the French Values and English Values have been replaced by the Source column, referring the value list. Modifying value lists can be done in reference data management, under General > Value Lists.

To know more, please refer to the Value List article.

NOTE: Data contained in your Web Forms have automatically been converted to value lists. To know more, refer to the Migrating Value Lists section of the Value List article.

ADSIReader | Reactivating disabled users

It is possible to reactivate Octopus users in Octopus based on their Active Directory account status using the /ReactivateUsers switch. For more details, visit the ADSIReader article.

Lists | Display attachments count including activities

The new column Attachments count including activities displays the count of attached files contained in a request and it's activities, excluding files attached to tasks.


Web Portal | Improvement on managing multiple time zones environment

The Web portal can process and display date and time values entered by the end user according to each user's respective time zone (for example, through a reservation or with the opening time of a request). 

To use the time zone function, you can assign a default time zone through the Options menu, a time zone to each of your sites in the Reference Data Management or even a time zone per user, specified in their profile. 

Please refer to the Time Zones article to learn more about this new feature.


NOTE:  If you have users in multiple time zones, it is better to assign time zones for the required sites.

Web Portal | Link to the authentication page for the Query String mode

An option allows displaying a link Access the Web Portal that redirects to the authentication page located on your Intranet when the error message that the portal cannot be access directly gets displayed. Furthermore, the link will also work when an assignee accesses the Web portal through the Tools > Launch the Web Portal menu. Contact us to activate this option.

Export to Excel | Better displaying of the time fields type

Exporting to Excel with Time fields (resolution delay, response delay, breach, etc.) will present complete data which can be manipulated using formulas and calculations in Excel instead of getting rounded up 15 minutes blocks like it used to be.

Inter request relationships | Relationship note

Adding notes to the relationships between requests - the same way it can be done for a relationship between two CIs or between a user and a CI. We have also added the possibility to reverse the existing relationship.
Visual explanation


ADSIReader | Specify a field correspondence file

It is possible to specify an access path to an ADSIReader fields correspondence file using the parameter /MappingsFilePath. For additional information, please see the ADSIReader article.

MailIntegration | Ignore email inserted logo

It is possible to configure MailIntegration to ignore specified attached files. Please refer to MailIntegration article to learn more about this feature.


User account creation within the registration on the Web Portal

Usually, a user must already exist in Octopus to be able to register. But in certain environments, for services to the population, for example, you will want the user to be able to create his account from the Web Portal. So we have modified Octopus to allow the creation of the user account directly from the Web Portal. For more information, see the Web Portal Operation wiki. 


Bug fixes and performance improvement following prerelease

This version does not contain any new visible features.

4.1.34 - Prerelease Version

Click here for more information on the prerelease program.

Version 4.1 introduces important modifications to Octopus: several improvements to Changes module, the addition of a deployment calendar and the ability to graphically view the CMDB and incident/SR tasks .

NOTE: If you already use tasks within your service requests or your changes, please see the modifications related to the task management, it will change the way you actually use them.

Change | Redesign of Changes module

Several interesting improvements have been made to Changes module: 

  • Change categorization
  • Statuses and transitions
  • Change templates
  • Modification to Change tasks

See Change Management - Octopus Module for more information.

It is also possible to refer to Change Management - ITIL Process on which Octopus was based to improve Changes module.

Change | Addition of a deployment calendar

To ease delivery of changes and minimize impacts on infrastructures and users, the deployment calendar is a very useful tool. It visualizes the planned deployments and shows if one or more services will be interrupted or degraded.

See Deployment calendar for more information.

CMDB | CMDB graphical view

Ability to get a graphical view of CI relationships.

A complete wiki article will follow soon.

Task | Task Management graphical view

Graphical view of tasks instead of the previous Edit view.

For more details on the tasks, see the Task Management article. 


Help us improve our articles

Help us improve our articles