Configuration https://docs.octopus-itsm.com/en/taxonomy/term/86/all en Fédération d'identité - Microsoft Entra ID https://docs.octopus-itsm.com/en/articles/federation-didentite-microsoft-entra-id <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Active synchronization of your users between your domain and OctopusIntroduction</h1> <p>Octopus can connect to Microsoft Entra ID (formerly Azure AD) to facilitate access to the application.</p> <p>Using an identity federator provides an integrated login experience to your Octopus environment. Your users and technicians won't need to create a new password to use Octopus applications.<br /><br />  </p> <p>Octopus can connect to a federated identity manager to ease access to the <u>application in a hosted environment</u>.</p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Fri, 08 Mar 2024 20:13:18 +0000 crheault 1184 at https://docs.octopus-itsm.com How to Use Field Configuration https://docs.octopus-itsm.com/en/articles/how-use-field-configuration <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1 class="rteindent1">Related Articles</h1> <ul><li><a href="https://wiki.octopus-itsm.com/en/articles/custom-field-library"><strong>Custom Field Library</strong></a></li> <li><a href="https://wiki.octopus-itsm.com/en/articles/user-management"><strong>User Management</strong></a></li> <li><a href="https://wiki.octopus-itsm.com/en/articles/lease-and-service-contracts-management"><strong>Lease and service contracts management</strong></a></li> <li><a href="https://wiki.octopus-itsm.com/en/articles/advanced-search-0"><strong>Advanced Search</strong></a></li></ul></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Tue, 11 Aug 2020 12:41:47 +0000 Nasselin 1079 at https://docs.octopus-itsm.com Groups and User Groups Management https://docs.octopus-itsm.com/en/articles/groups-and-user-groups-management <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <p><span style="color: rgb(61, 60, 60); font-family: Bitter, serif; font-size: 24px;">Related articles</span></p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Thu, 28 May 2020 14:12:48 +0000 Nasselin 1064 at https://docs.octopus-itsm.com How the Automated Addition of Attached Files to CIs Work? https://docs.octopus-itsm.com/en/articles/how-automated-addition-attached-files-cis-work <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Related articles</h1> <ul><li><a href="https://wiki.octopus-itsm.com/en/articles/service-asset-and-configuration-management-octopus-module"><strong>Service Asset and Configuration Management - Octopus Module</strong></a></li> </ul><h1>Introduction</h1> <p>Whether it is to add a procedure or for any other type of document, it is possible from the CI type configuration to ensure that each time a new CI of this type is created one or several documents are automatically added to the new CI.</p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Mon, 23 Mar 2020 11:20:32 +0000 Nasselin 1050 at https://docs.octopus-itsm.com Activity Type Management https://docs.octopus-itsm.com/en/articles/activity-type-management <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Related articles</h1> <ul><li><a href="https://wiki.octopus-itsm.com/en/articles/activities-octopus"><strong>Activities in Octopus</strong></a></li> </ul><h1>Introduction</h1> <p>The activity types are used to standardize the information entered into Octopus by the Octopus users.</p> <p>They are used to create message templates that can be sent to users or internal activities to help with data entry in Octopus or on the mobile.</p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Tue, 17 Mar 2020 13:44:21 +0000 Nasselin 1045 at https://docs.octopus-itsm.com Identity Federation https://docs.octopus-itsm.com/en/articles/identity-federation <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Introduction</h1> <p>Octopus can connect to a federated identity manager to ease access to the application in a hosted environment.</p> <p>Single sign-on can be used independently for the following components, depending on what your federation provider supports:</p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Tue, 24 Dec 2019 17:15:52 +0000 dloranger 1039 at https://docs.octopus-itsm.com CI Attribute Management https://docs.octopus-itsm.com/en/articles/ci-attribute-management <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <p>The information contained in a CI record is very important for the&nbsp;<strong>Configuration Management</strong>&nbsp;and to control the&nbsp;inventory&nbsp;of a business.</p> <p>In Octopus each CI type allows adding attributes, that represent additional information important to manage&nbsp;this type of equipment.</p> <p>In this article, we will explain in detail how attributes work and what their possibilities.&nbsp;</p> </div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Wed, 18 Dec 2019 12:32:02 +0000 Nasselin 1038 at https://docs.octopus-itsm.com Personal Email | Activation and Use https://docs.octopus-itsm.com/en/articles/personal-email-activation-and-use <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Related Articles</h1> <ul><li><a href="https://wiki.octopus-itsm.com/en/articles/user-management"><strong>User Management</strong></a></li> </ul><h1>Introduction </h1> <p>By default, only one field is available for a user's email in Octopus, the <strong>Professionnal Email </strong>field.</p> <p>But in some environments, some users or employees may not have professional email and may need to receive Octopus communications.</p> <p>The <strong>Personal Email</strong> field can be used for this purpose.</p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Wed, 28 Aug 2019 17:53:37 +0000 Nasselin 1025 at https://docs.octopus-itsm.com Incident Templates and SR Types - Available Options for Requester/Users https://docs.octopus-itsm.com/en/articles/incident-templates-and-sr-types-available-options-requesterusers <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Related Article</h1> <ul><li><a href="https://wiki.octopus-itsm.com/en/articles/basic-configuration-incident"><strong>Basic Configuration - Incident</strong></a></li> <li><a href="https://wiki.octopus-itsm.com/en/articles/basic-configuration-service-requests"><strong>Basic Configuration - Service Requests</strong></a></li> <li><a href="https://wiki.octopus-itsm.com/en/articles/create-customized-forms-octopus"><strong>Create customized forms in Octopus</strong></a></li> </ul><h1>Introduction</h1> </div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Wed, 07 Aug 2019 12:10:40 +0000 Nasselin 1021 at https://docs.octopus-itsm.com Octopus Options on Demand https://docs.octopus-itsm.com/en/articles/octopus-options-demand <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Introduction</h1> <p>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.</p> <p>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.</p> <p>In this article, we propose&nbsp;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.&nbsp;</p> <p>To request one of these options, the <u>authorized Octopus administrator</u> must make a request to our <a href="https://servicedesk.octopus-itsm.com/"><strong>Service Desk</strong></a> with the <strong>Configuration / Data Modification&nbsp;</strong>template.&nbsp;</p> <p>We will need the following information :&nbsp;</p> <ul> <li>The name of the environment <ul> <li>It can be found in&nbsp;<strong>Tools &gt; Display installation kit address</strong>.</li> </ul> </li> <li>The name and/or number of the team</li> <li>The name of the option</li> </ul> <p>&nbsp;</p> <div class="textbox" style="border:5px solid #ebebeb;padding:17px 55px 35px 27px;width:55%;"><span style="color:#800000;"><strong><u>What you need to know</u>:&nbsp;</strong></span><br /> <br /> The options presented in the table are all configurable by team, except when indicated.</div> <h1>Visual Support</h1> <p>To better explain the option in question, we sometimes add visual support:</p> <table id="tableau1_perso"> <tbody> <tr> <td> <p class="rtecenter">Click the icon to see the picture</p> <p class="rtecenter"><img alt="" src="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/eye%20dark%20grey.png" style="width: 70px; height: 39px;" /></p> </td> <td> <p class="rtecenter">Click the icon to see the video</p> <p class="rtecenter"><img alt="" src="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/Film%20dark%20grey.png" style="width: 50px; height: 59px;" /></p> </td> </tr> </tbody> </table> <p>&nbsp;</p> <table border="1" cellpadding="1" cellspacing="1" style="width:500px;" summary="Texe summary"> <caption> <h1 class="rteleft">General Options</h1> </caption> <thead> <tr> <th colspan="2" scope="col"><span style="font-size:18px;">Description</span></th> </tr> </thead> <tbody> <tr> <td colspan="2"> <h2>Modify the Default Source of Requests</h2> <p>When a request is created directly in Octopus, by default, the source is Telephone. This choice can be modified&nbsp; for another as needed.</p> <p>It is also possible to leave the field empty by default, to force the Octopus user to make a choice when creating the request.</p> <ul> <li>Option name <ul> <li><strong>Sources.UseDefaultValue</strong></li> <li>To modify the default value, we add a choice.</li> <li>To force a choice by default, we leave empty.&nbsp;</li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Open the Internal Annoncement in Another Window</h2> <p>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.</p> <p class="rteindent1"><a href="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/AnnonceInterneDansFenetre_EN.png" target="_blank"><img alt="" src="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/eye%20dark%20grey.png" style="width: 45px; height: 25px;" /></a></p> <ul> <li>Option name <ul> <li><strong>InternalAnnouncement.ShowInNewWindow</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Attached files hosted by Octopus</h2> <p>Option that allows you to access the team's attached files from the Web.&nbsp;</p> <p><span style="color:#FF0000;">Warning!</span> This option does not work with local environments.&nbsp;</p> <p>As this option has its own separate process, to enable this option, the authorized Octopus administrator must complete a I need to... &gt; Hosted files.</p> <ul> <li>Option name <ul> <li><strong>Attachment.Storage.Enabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>External support</h2> <p>For many companies, the services offered are intended not only for internal employees, but also for external people.&nbsp;</p> <p><span style="color:#000000;">To learn how this option works, see <a href="https://wiki.octopus-itsm.com/en/articles/support-external-mode" target="_blank">external support article</a></span><br /> &nbsp;</p> <ul> <li>Option name (will affect all teams) <ul> <li><strong>ExternalSupportMode.Enabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Display&nbsp;tiles on the Web portal</h2> <p>To make easier the organization of requests on the Web portal, it is possible to use tiles with an image to represent the categories of request and the team whenever there is moreone on the portal.&nbsp;&nbsp;<br /> &nbsp;</p> <p><span style="color:#000000;">See the article : Web portal - <a href="https://wiki.octopus-itsm.com/en/articles/web-portal-setting-modern-mode" target="_blank">Setting up the modern mode</a> for details and how it work.&nbsp;</span></p> <p>&nbsp;</p> <ul> <li>Option name <ul> <li><strong>Attachment.Storage.Enabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Add a #ProviderReq. field for requests</h2> <p>Allows you to add the Supplier Request Number field to an Incident or Service Request.&nbsp;</p> <p>This is a text field.&nbsp;</p> <p class="rteindent1">&nbsp;</p> <ul> <li>Option name <ul> <li><strong>Incident.SupplierIncidentID.Enabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Modify the Hours of the Deployment Calendar</h2> <p>By default, the week view of the deployment calendar&nbsp;displays deployments from 7:00 to 00:00. But it is possible to change these hours as needed.</p> <ul> <li>Option names <ul> <li><strong>DeploymentCalendar.StartTime</strong></li> <li><strong>DeploymentCalendar.EndTime</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Valid Approval Responses for Email</h2> <p>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 <strong>OK</strong>, <strong>Alright</strong>.</p> <p>In addition to the option, note the answers to add.</p> <ul> <li>Option names <ul> <li>For positive response&nbsp;<strong>MailIntegration.PositiveApprovalResponses</strong></li> <li>For negative response&nbsp;<strong>MailIntegration.NegativeApprovalResponses</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Download the Database -&nbsp;GetDBApp</h2> <p>It is possible to manually download a copy of the Octopus database or automate the download.</p> <p>To find out more, see the <strong><a href="https://wiki.octopus-itsm.com/en/articles/getdbapp-downloading-octopus-database-automatically">GetDBApp: Downloading the Octopus database automatically</a>&nbsp;</strong>article.&nbsp;</p> <ul> <li>Option name <ul> <li><strong>CanObtainLastDBBackup</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Add the Contact Field to Your Requests</h2> <p>Requests often drag on because the user is a difficult person to reach. Either he&nbsp;works on night or overnight shifts, weekends or is medical staff or travels frequently.&nbsp;</p> <p>Many times in these cases, there is another person who is aware of the request and could answer for the user.</p> <p>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.</p> <p class="rteindent1"><a href="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/ChampContact_EN.png" target="_blank"><img alt="" src="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/eye%20dark%20grey.png" style="width: 45px; height: 25px;" /></a></p> <ul> <li>Option name <ul> <li><strong>Incident.Contact.Visible</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Adding the content of the internal procedure in the Detailed description field</h2> <p>By default, when a query is created and it has an internal procedure, the Procedure link must be used to consult it.</p> <p>An option is available to display the procedure in the Detailed description field as well as being visible through the Procedure link.<br /> <br /> *&nbsp;If the request comes from the web portal or no form is mandatory, the internal procedure is not copied, but the form description is retained.</p> <p class="rteindent1">&nbsp;</p> <ul> <li>Option name <ul> <li><strong>Incident.CopyInternalProcedureToFullDescription.Enabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Parent-Child Incident - keep the CI involved in the child incident</h2> <p>By default, when a child request is linked to a parent request, the child's CI is replaced by the parent's CI.</p> <p>In some contexts, we sometimes want to keep track of the child CI and therefore not have it replaced by the parent CI. An option is available to avoid this synchronization.&nbsp;</p> <p class="rteindent1">&nbsp;</p> <ul> <li>Option name <ul> <li><strong>Incident.ChildRequestPreserveCI</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Create from ... for incident/SR</h2> <p>An option is provided to facilitate the creation of a query from another one to avoid re-entering information by copying some information from the source query.&nbsp;</p> <p>However, the copy does not include attachments or tasks, other than those already included in an SR type.&nbsp;</p> <p>The choice of fields to be copied must be made to implement this option <a href="https://wiki.octopus-itsm.com/sites/all/files/Gestion des changements ITIL/Create%20from%20-%20choices%20for%20options.xlsx">from this Excel file</a>.</p> <p class="rteindent1">&nbsp;</p> <ul> <li>Option name <ul> <li><strong>ESI.Octopus.PlugIns.CreateIncidentFrom</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Additional information when choosing a user</h2> <p>When searching for a user in Octopus, some information helps to distinguish between different people. For example, the name of their site, department, their Windows username, etc.&nbsp;</p> <p>Some information is there by default, but it is possible to add, remove or change the order in which they appear.&nbsp;</p> <p>To find out how these options work, <a href="https://wiki.octopus-itsm.com/en/articles/additional-information-selection-user">see the article Additional information when choosing a user</a>.&nbsp;</p> <p class="rteindent1">&nbsp;</p> <ul> <li>Option name <ul> <li><strong>WebUI.UserDropdown.InfoFormat (portail Web)</strong></li> <li><strong>WinUI.UserDropdown.InfoFormat (client Windows)</strong><br /> &nbsp;</li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Access management</h2> <p>GDA in Octopus is much more than a simple option. It is a project in itself that requires the support of an Octopus specialist to set it up.&nbsp;</p> <p>For more information on what can be done with Access Management in Octopus, <a href="https://wiki.octopus-itsm.com/en/articles/automated-access-management-solution-reference-document">see the article Automated Access Management Solution - Reference Document</a>.&nbsp;</p> <p class="rteindent1">Any request for Access Management is subject to an evaluation in order to prepare a submission for the project. It is therefore necessary to already have a plan in mind of what is to be implemented and to have planned to make a budget request.&nbsp;</p> <ul> <li>Option name <ul> <li><strong>GDA</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Use of multiple criteria to establish impact and urgency</h2> <p>By default, the Impact and Emergency fields are drop-down lists.</p> <p>But it is possible to establish the impact and/or urgency from several pre-established criteria.</p> <p><span style="color:#FF0000;">Attention:</span> for the implementation, this may require assist&nbsp;from an Octopus specialist</p> <p>&nbsp;</p> <ul> <li>Option name&nbsp; <ul> <li><strong>ESI.Octopus.PlugIns.PriorityDerivation&nbsp;</strong></li> </ul> </li> </ul> <p>Une fois l'option activée, la configuration se fait directement dans les données de références.&nbsp;</p> </td> </tr> <tr> <td colspan="2"> <h2>Control assignment to resolution and reopening</h2> <p>Although it is recommended to reassign a resolved request to the Service Center, in some cases and especially in non-IT teams, it may be interesting to return the incident or the resolved service request to the resolution group.</p> <p>Two options are available to control assignment upon resolution and reopening<br /> &nbsp;</p> <ul> <li>Disable automatic reassignment to service center upon resolution. By default, resolved incidents/SRs are automatically assigned to Service Center. By disabling the option, the assignment remains to the same group, that is, to the group that resolved the request. In both cases, the assignee will be removed from the field.<br /> &nbsp;</li> <li>Upon reopening, enable automatic reassignment to the assignee who resolved it. By default, reopened incidents/SRs are not reassigned to the assignee. By enabling this option, the request will be reassigned to the person who resolved it, if the assignee is part of the assignment group. (Generally, this option will be used in combination with the previous one.)</li> </ul> <p><br /> .&nbsp;</p> <ul> <li>Option name&nbsp; <ul> <li><strong>Incident.ServiceDeskResolutionAssignement.Enabled</strong></li> <li><strong>Incident.Reopen.AssignToResolutionAssignee.Enabled</strong><br /> <br /> &nbsp;</li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Maintain relationships between users and CIs after users are deactivated</h2> <p>By default, when a user is disabled, their relationship with CI's is removed.</p> <p>But in some contexts we need to keep the relationships. This option preserves the relationship between CIs when the user is disabled.</p> <p>&nbsp;</p> <ul> <li>Option name <ul> <li><strong>User.Deactivation.DeleteCIRelationships.Enabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Software managed or not by default</h2> <p>When used with a WMIUpdater synchronization, Octopus considers that the softwares found by WMIUpdater is either managed or unmanaged.</p> <p>By default, they are managed and added to the list of software in the Configurations module. And every new CI found at the next WMIUpdater sync will be added to this list.</p> <p>There is an option to reverse this behavior and make softwares detected by WMI considered unmanaged.</p> <p>&nbsp;</p> <ul> <li>Option name <ul> <li><strong>WMI.Software.IsManagedByDefault</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Search by the name of the Manufacturer and the Model of a CI&nbsp;</h2> <p>Particularly useful in Facilities Management or GBM teams, this option allows you to add the possibility to search by the name of the Manufacturer and the Model of a CI.</p> <p>&nbsp;</p> <ul> <li>Option name <ul> <li><strong>CIQuickSearch - ManufacturerModel</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Choosing a status other than Retired when a CI is no longer detected by ADSI</h2> <p>When ADSI synchronization is used to scan computers, the system automatically sets PCs that are no longer present in AD to the Retired status. In some contexts, the process may require that the status of the CI be different when it is no longer in AD.&nbsp;</p> <p>There is an option to designate a status other than Retired, such as Recycled for example.</p> <p>&nbsp;</p> <ul> <li>Option name <ul> <li><strong>ADSIUpdater.RetiringCIStatusID</strong><br /> Specify the <u>name of the status to use</u>, when enabling this option</li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Delay reminder deadlines for approvals</h2> <p>There are two types of reminders for approvals:&nbsp;</p> <ul> <li>Reminder to the approver, when already assigned</li> <li>Required approver reminder, sent to the approver group to prompt a person to take charge of the approval.</li> </ul> <p>&nbsp;</p> <p>In both cases, the recall is sent <strong>48 hours</strong> after the first notification of approval and continues every 48 hours thereafter, until the approval is completed.</p> <p>To make a change to both options, specify the name of the option to be changed and the desired time frame.</p> <p class="rteindent1">&nbsp;</p> <ul> <li>Option name <ul> <li><strong>ApprovalAssignedReminder.Interval - </strong>(Reminder for approver)</li> <li><strong>&nbsp;ApproverRequiredReminder.Interval&nbsp; -&nbsp;</strong>(Approver reminder required for group)<br /> <br /> &nbsp; <p><strong>For more information on what can be done with Access Management in Octopus,&nbsp;see the article Automated Access Management Solution - Reference Document.&nbsp;</strong></p> </li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Resolution of variables in a task from a form</h2> <p>Allows you to specify whether variables of type Expression are resolved at the creation of a request.<br /> By default, they are resolved at the creation of the query.&nbsp;</p> <p>It is also possible that they are resolved on activation of the task.</p> <ul> <li>Option name <ul> <li> <p><strong>Incident.CreateTasksForNewSRFromTemplate.ShouldResolveFieldExpressions</strong></p> </li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Add a Note Section to Printed Requests</h2> <p>Sometimes in building management teams, workers must print requests and work on paper.</p> <p>An option (plugin) is available to add a section at the bottom of the printed request, where the worker can enter his notes.</p> <p>In addition, there is a second option which adds the CI note, when it exists, to the printed&nbsp; request.</p> <p class="rteindent1"><a href="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/FacilitiesManagement.IncidentReportExtension_EN.png" target="_blank"><img alt="" src="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/eye%20dark%20grey.png" style="width: 45px; height: 25px;" /></a></p> <ul> <li>Option name <ul> <li><strong>FacilitiesManagement.IncidentReportExtension</strong></li> <li><strong>IncidentReport.PrintCINote.Plugin</strong> <ul> <li>To have the CI note printed</li> </ul> </li> </ul> </li> </ul> </td> </tr> </tbody> </table> <p>&nbsp;</p> <table border="1" cellpadding="1" cellspacing="1" style="width:500px;" summary="Texe summary"> <caption> <h1 class="rteleft">Options Related to the Web Portal</h1> </caption> <thead> <tr> <th colspan="2" scope="col"><span style="font-size:18px;">Description</span></th> </tr> </thead> <tbody> <tr> <td colspan="2"> <h2>User Profile Modification on the Web Portal</h2> <p><span style="color:#800000;"><strong>WARNING:</strong></span>&nbsp;This option affects all teams.</p> <p>By default when a user goes into his profile on the Web Portal,&nbsp;a number of fields can be seen and changed.&nbsp;</p> <p>It is possible to block the modification of certain fields.&nbsp;</p> <p>It is also possible to display the approval delegation fields at any time.</p> <p>And to make visible and editable some other fields.</p> <p class="rteindent1"><a href="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/ProfilUtilisateur_EN.png" target="_blank"><img alt="" src="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/eye%20dark%20grey.png" style="width: 45px; height: 25px;" /></a></p> <p>&nbsp;</p> <p>For more information see the <strong><a href="https://wiki.octopus-itsm.com/en/articles/additional-information-selection-user">Additional information in the selection of a user</a>&nbsp;</strong>article. &nbsp;</p> <ul> <li>Option names <ul> <li><strong>WebUI.EditProfile.ContactInformation.ReadOnly&nbsp;</strong></li> <li><strong>WebUI.EditProfile.DelegateApprovalTo.AlwaysVisible&nbsp;</strong></li> <li><strong>WebUI.EditProfile.Site.Visible&nbsp;</strong></li> <li><strong>WebUI.EditProfile.Departement.Visible</strong></li> <li><strong>WebUI.EditProfile.Local.Visible&nbsp;</strong></li> <li><strong>WebUI.EditProfile.JobTitle.Visible&nbsp;</strong></li> <li><strong>WebUI.EditProfile.Pager.Visible</strong></li> <li><strong>WebUI.EditProfile.ProfessionalEmail.Visible</strong></li> <li><strong>WebUI.EditProfile.PersonalEmail.ReadOnly</strong></li> <li><strong>WebUI.EditProfile.BusinessPhone.Visible</strong></li> <li><strong>WebUI.EditProfile.DelegateApprovalTo.ReadOnly</strong></li> <li><strong>WebUI.EditProfile.UnavailabilityDates.Visible</strong></li> </ul> </li> </ul> </td> </tr> <tr> <td colspan="2"> <h2>Activation of tiles on the portal</h2> <p>To facilitate the organization of requests on the portal it is possible to use tiles with an image to represent the categories of requests and teams, when there is more than one on the portal.&nbsp;</p> <p><a href="https://wiki.octopus-itsm.com/en/articles/web-portal-setting-modern-mode">See the article Web Portal</a> - Setting up the modern mode for details of how it works.&nbsp;</p> <p>&nbsp;&nbsp;</p> <ul> <li>Option name <ul> <li>​<strong>WebUI.Incident.BriefDescription.UsePrefix.Enabled<br /> &nbsp;</strong></li> </ul> </li> </ul> <hr /> <h2>Add or Remove the [Web] Prefix to the Request Subject</h2> <p>In certain environments when a request&nbsp;is created from the Web Portal, [Web] is added to the beginning of the subject.</p> <p>For example: [Web] I lost my cell phone.</p> <p>&nbsp; But this prefix can be removed.</p> <ul> <li>Option name <ul> <li><strong>WebUI.Incident.BriefDescription.UsePrefix.Enabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Link CI's to user</h2> <p>Prevents displaying the option to link CI to user upon an&nbsp;incident creation is created.&nbsp;</p> <ul> <li>Option name <ul> <li><strong>Incident.showLinkCIMessage</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Resolution date display</h2> <p>It is now possible to display the resolution date in request list and&nbsp;requests form on the Web portal.</p> <ul> <li>Option name <ul> <li><strong>WebUI.RequestList.ResolutionDateVisible</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Register to this service</h2> <p>It is possible to invite external collaborators or suppliers to&nbsp;Register for the service&nbsp;in order to create their account and then allow them to access the web portal and make service requests or communicate essential information to an Octopus team.<br /> <br /> For more details, <a href="https://wiki.octopus-itsm.com/en/articles/register-service">click here</a></p> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Report an incident anonymously&nbsp;</h2> <p>The web portal can be the gateway for reporting incidents anonymously, or for users who do not have an Octopus account and whose identity is not required.<br /> <br /> For more details, <a href="https://wiki.octopus-itsm.com/en/articles/report-incident-anonymously-web-portal">click here</a></p> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>External authentication available in hybrid mode&nbsp;(ADFS or Azure AD / Username and password)</h2> <p>It is now possible to invite external collaborators or suppliers to make service requests or communicate essential information to an Octopus team.<br /> <br /> The Web portal must be configured with SSO authentication to allow&nbsp;the hybrid login mode.<br /> This mode enables certain "external" users who are not present in the customer's identity federator (ADFS or Azure AD) to authenticate on the web portal with a username and password.</p> <ul> <li>Option name <ul> <li><strong>Claims.IsExternalLoginAllowed</strong></li> </ul> </li> </ul> <p><br /> ​For more information on Identity Federation,&nbsp;<a href="https://wiki.octopus-itsm.com/fr/articles/federation-didentite-microsoft-entra-id">see the article here</a><br /> <br /> &nbsp;</p> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Filters for displaying CIs on the portal</h2> <p>When a user has to select a CI from on the Web portal, by default, they are presented with the CI(s) associated with it. But it is possible to present the choices in different ways.&nbsp;&nbsp;</p> <ul> <li><strong>User CI</strong> <ul> <li>Defaut option</li> </ul> </li> <li><strong>Site CI</strong> <ul> <li>If&nbsp;site selection is mandatory, the CIs of the selected site are displayed</li> <li>If site selection is not mandatory, the CIs of the user's&nbsp;site are displayed</li> </ul> </li> <li><strong>Departement CI</strong> <ul> <li>Corresponds to the exact deparltement level of the user</li> <li>Do not consider parent or child departements</li> </ul> </li> </ul> <p>To change the default seclection, request the next option indicating the desired option. &nbsp;</p> <ul> <li>Option name <ul> <li><strong>WebUI.CreateRequest.CIList.Source</strong></li> </ul> </li> </ul> </td> </tr> </tbody> </table> <table border="1" cellpadding="1" cellspacing="1" style="width:500px;" summary="Texe summary"> <caption> <h1 class="rteleft">Options liées à l'assignation</h1> </caption> <thead> <tr> <th colspan="2" scope="col"><span style="font-size:22px;">Description</span></th> </tr> </thead> <tbody> <tr> <td colspan="2"> <h2>Displays the Due Date field in the web portal</h2> <p>It is now possible to display the resolution date in request list and&nbsp;requests form on the Web portal.</p> <ul> <li>Option name <ul> <li><strong>WebUI.RequestList.ResolutionDateVisible</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Displays the priority in the web portal</h2> <p>It is possible to display the priority in the request list and in the request on the web portal.&nbsp;</p> <ul> <li>Option name <ul> <li><strong>WebUI.RequestList.PriorityVisible</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Modify the number of CIs displayed in the search results</h2> <p>When you create a new incident and perform a search on the CI, you can specify to display X number of CIs.&nbsp;<br /> *&nbsp;Caution: A too large a number can affect the page display delay, so we suggest limiting the number, e.g. 25.</p> <ul> <li>Option name <ul> <li><strong>WebUI.CreateRequest.FindCI.MaxResult</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Display the name of the assigned<br /> <br /> Control whether or not assignee of the request is visible in the Web portal and add the column <strong>Assigned to</strong>.&nbsp;</h2> <ul> <li>Option name <ul> <li><strong>WebUI.Incident.Assignee.Visible&nbsp;&nbsp;</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Send e-mail upon request creation via&nbsp;Web Portal</h2> <p>This option sends the creation confirmation to the requester even if the incident/SR was submitted via the Web portal. However, if the requester&nbsp;is a technician for the team where the request was created, this option will have no effect.<br /> &nbsp;</p> <p>For <a href="https://wiki.octopus-itsm.com/en/articles/what-confidential-request" target="_blank">confidential requests</a>, only the requester will receive a confirmation email.<br /> &nbsp;</p> <ul> <li>Option name <ul> <li><strong>Notification.IncidentCreated.CreateEvenIfCurrentUser</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Deactivate the Automated Site Derivation</h2> <p>When a request is submitted from the Web Portal and the site is mandatory for a&nbsp;service, the requester&nbsp;must confirm the site before selecting a request.</p> <p>If the requester leaves the site presented to him by default, in this case his own, and continues his request&nbsp;but adds a user from another site, the system will automatically derive the site of the request to the site of the user who was added.</p> <p>An option allows to keep the site initially selected&nbsp;when&nbsp;a site is mandatory for a service.</p> <p class="rteindent1"><a href="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/D%C3%A9sactivation%20de%20la%20d%C3%A9rivation%20de%20site_EN.mp4" target="_blank"><img alt="" src="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/Film%20dark%20grey.png" style="width: 30px; height: 35px;" /></a></p> <ul> <li>Option name <ul> <li><strong>Incident.WebUI.SiteDerivationDisabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Reopen a request on Web portal</h2> <p>Allow the reopening of a request on the web portal.&nbsp;</p> <p class="rteindent1">&nbsp;</p> <ul> <li>Option name <ul> <li><strong>WebUI.ReopenRequest.Enabled</strong></li> </ul> </li> </ul> </td> </tr> <tr> </tr> <tr> </tr> <tr> </tr> <tr> <td colspan="2"> <h2>Discreet Section for Confidential Requests</h2> <p>A confidential request will always only be visible to the requester from the Web portal. But in some context, we want to add even more discretion to these requests.</p> <p>The following option adds a section at the bottom of the screen for confidential requests from all teams which is collapsed by default.</p> <p class="rteindent1"><a href="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/RequeteConfidentielleCachee_EN.png" target="_blank"><img alt="" src="https://wiki.octopus-itsm.com/sites/all/files/Options Octopus sur demande/eye%20dark%20grey.png" style="width: 45px; height: 25px;" /></a>&nbsp;</p> <ul> <li>Option name <ul> <li><strong>WebUI.Filter.Confidential.Visible</strong></li> </ul> </li> </ul> </td> </tr> </tbody> </table> </div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Mon, 22 Jul 2019 11:17:59 +0000 Nasselin 1019 at https://docs.octopus-itsm.com Custom Field Library - Explainer Videos https://docs.octopus-itsm.com/en/articles/custom-field-library-explainer-videos <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Small videos on the Custom Field Library</h1> <p>This page offers small capsules that illustrate the use of the Field Library in Octopus.</p> <p>To see the solution in detail, read the <a href="https://wiki.octopus-itsm.com/en/articles/custom-field-library"><strong>Custom Field Library</strong></a> article.</p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Wed, 04 Jul 2018 15:43:25 +0000 Nasselin 965 at https://docs.octopus-itsm.com Custom Field Library https://docs.octopus-itsm.com/en/articles/custom-field-library <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Related Articles</h1> <ul><li><a href="https://wiki.octopus-itsm.com/en/articles/conversion-custom-fields-starting-42270"><strong>Conversion to custom fields - starting with 4.2.270</strong></a></li> <li><a href="https://wiki.octopus-itsm.com/en/articles/custom-field-library-explainer-video"><strong>Custom Field Library - <span style="color:#800000;">Explainer Video</span></strong></a></li> <li><a href="https://wiki.octopus-itsm.com/en/articles/create-customized-forms-octopus"><strong>Create customized forms in Octopus</strong></a></li></ul></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Mon, 07 May 2018 11:15:47 +0000 Nasselin 957 at https://docs.octopus-itsm.com Configurations Module | Cost management https://docs.octopus-itsm.com/en/articles/configurations-module-cost-management <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Related Articles</h1> <p><strong><a href="https://wiki.octopus-itsm.com/fr/node/954">Gestion des contrats de maintenances et de locations</a></strong></p> <p><strong><a href="https://wiki.octopus-itsm.com/en/articles/ci-cost-management">CI cost management</a></strong></p> <h1>Introduction</h1> <p>Cost management is an important concept in Octopus as it helps decision-making in relations to operation and maintenance costs.</p> <p>This wiki explains the concept of costs in Octopus and how to use the various information related to costs.</p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Thu, 19 Apr 2018 13:00:28 +0000 emak 955 at https://docs.octopus-itsm.com Conversion to Custom Fields - starting with 4.2.270 https://docs.octopus-itsm.com/en/articles/conversion-custom-fields-starting-42270 <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Related Articles</h1> <ul><li><a href="https://wiki.octopus-itsm.com/en/articles/custom-field-library"><strong>Custom field library</strong></a></li> </ul><h1>Why this conversion is important for you</h1> <p>Version 4.2.270 will introduce the custom field library in Octopus. This option will offer a new way of using form fields in the application. </p></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Mon, 02 Apr 2018 13:56:06 +0000 octopus-Sandra 953 at https://docs.octopus-itsm.com Automated SR creation from an email https://docs.octopus-itsm.com/en/articles/automated-sr-creation-email <div class="field field--name-body field--type-text-with-summary field--label-hidden"><div class="field__items"><div class="field__item even" property="content:encoded"> <h1>Related Articles</h1> <ul><li><strong><a href="https://docs.octopus-itsm.com/en/articles/mailintegration-create-incidents-or-events-emails">MailIntegration - Create Incidents or Events from Emails</a></strong></li> <li><strong><a href="https://docs.octopus-itsm.com/en/articles/mailintegration-testing-pop3-connection">MailIntegration - Testing the POP3 connection</a></strong></li> <li><strong><a href="https://docs.octopus-itsm.com/en/articles/creation-service-request">Creation of a service request</a></strong></li></ul></div></div></div><div class="form-item form-type-item"> <label>Language </label> English </div> Tue, 13 Mar 2018 15:46:27 +0000 Nasselin 941 at https://docs.octopus-itsm.com