Download Release Notes | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe
On this page:
What's New?
Highlights
The following links provide Module-wise summary of key features introduced in Tahoe SP1 Release.
Platform
License Expiry Notification
Enables an administrator to configure the license expiry notification, send notifications to desired set of selected users, and set the expiry reminder to alert the user(s) about the license expiry.
Offboarding User Policy
Provision an analyst to address pending and progressive dependent items (Incident, Service Request, Change Request, and Problem Record List) associated with the offboarded analyst.
An Offboarded Users link to list the dependent records associated with offboarded user account specific to the configured Domain, Tenant, and Workgroup.
API Discovery
To discover multiple type of devices, SummitAI now offers API based discovery. Based on the API configuration, the Servers, Networks, Links, Printers, and Laptop devices in the organization can be identified or define to establish connection with the configured APIs.
Service Management
Business Rule Designer
Schedulers are introduced in Business Rule Designer that enables you to schedule incidents for automating different tasks such as Updating Fields, Sending Notifications in a scheduler manner. Few examples of this could be auto resolving incidents that are pending since more than 2 months, sending notifications to Workgroup Owner if a VIP ticket is left unattended for more than 3 hours, or auto-cancel old incidents. This way, all the low value activities traditionally done by technicians can be offloaded to Business Rule Designer, thereby enabling the technicians to focus on high value activities.
- Incident Closing Mode is introduced in Business Rule Designer that enable you to close the incidents automatically or manually as per business requirements. Automation of incident closure helps the Administrator to define the closure mode based on the variety of criteria. The key piece to this auto closure feature is the ability to automatically close the incidents based on the following:
- Business Days - Business days will not include Holidays and Weekends
- Calendar Days - Calendar days will include Holidays and Weekends
Call Management
When a Call is resolved, the technicians are now prompted to select the Closure Code. Consequently, the technicians can update the Closure Code as Successful, Unsuccessful, Deferred etc. As a result, the Service Desk can build visibility with Reports that help them to objectively measure the service quality and also identify and execute opportunities that enhance Customer Satisfaction (CSAT), as a part of continual service improvement.
Introduced a list of relevant Knowledge Articles as recommended solution when the Analyst is typing in the user’s query in the Call Record. This enables the Analysts to instantly resolve the user’s queries, thereby improving the overall customer experience. Hence, we have integrated Knowledge Management and Call Management.
Change Management
You can now set rules that would automatically close the Implemented Change Requests after a specific period. Defining the Closure Mode (Auto / Manual) is important because it -
Eliminates the need for technicians to manually close the Change Requests
Enables the Service Desk to operationalize the business process laid out by the organization
Eliminates any potential human errors - miss out closure of CRs etc.
Better control over Notifications can now be established by configuring when the Analysts should receive the notifications during the life cycle of the Change Request. Administrators can decide if the Analysts should be notified after every Approval or Update or should be notified only after the CR is assigned to them.
Problem Management
Operational Level Agreements can now be defined for the Work Orders created from Problem Records, similar to Incident and Service Requests. As a result, it ensures that the internal SLAs between teams are met and thereby ensure on-time delivery of service. OLAs act as a foundation of good practise and common agreement.
The Approvers can now approve, review or reject the Problem Records directly over email. The details of the Problem Record can be embedded in the email, thereby eliminating the need for Approvers to traverse back and forth between mail and SummitAI Web Application for approvals.
You can now customize the Work Order Forms of Problem Record by adding custom attributes defined at the Problem Record level. This allows the Analysts to capture the details at the Work Order level by filling in the custom attributes, thereby enabling better tracking.
Service Request
- Introduced a restriction to prohibit the Requestor to select the same user as an Approver for User Group Approval in SR workflow, while configuring Service Request at Tenant level. Hence, enhanced the approval process by restricting the Requestor as one of the Approver. Hence, it will be helpful to avoid misuse or manipulation of the authorized access.
For example, User1 is the Requestor and User Group Approval group comprises of User1, User2 and User3. This feature prohibits the User1 to select User1 (self) as approver.
Database Schema DN Tables
The following new DN tables are added for Service Management in SummitAI Service Management Database Schema Definition Guide.
- DN table are now developed to capture the checklist parameters such as Checklist Name, Status, Updated By – This can be used to build Reports that would help provide visibility on how the checklists are updated by Analysts for Incident Management module. (IM_RPT_DN_Change_Checklist_History)
- DN table are now developed to capture the checklist parameters such as Checklist Name, Status, Updated By – This can be used to build Reports that would help provide visibility on how the checklists are updated by Analysts for Service Request module. (SR_RPT_DN_Change_Checklist_History)
- DN table are now developed to capture the checklist parameters such as Checklist Name, Status, Updated By – This can be used to build Reports that would help provide visibility on how the checklists are updated by Analysts for Change Management module. (CM_RPT_DN_Change_Checklist_History)
- DN table are now developed to capture the catalogs parameters such as Catalog Response SLA, Catalog ID, Catalog Response Business Days – This can be used to build Reports that would help provide visibility on how the Service Catalogs are updated by Analysts. It holds all the detail about the Service Catalogs. (SR_RPT_DN_ServiceCatalog_Master)
Asset Management
Add Software screen is improvised to facilitate simplified configuration of the Software Inventory and License Management Modules.
Asset return process is enriched to enables best-in-class asset tracking mechanism.
New provision to an Administrator for the custom Sub Status configuration of Fixed and Non-fixed assets.
IT Operations Management
Service Dashboard
- Service Dashboard helps the Analyst or Admin to monitor all the details about the available services. This dashboard provides complete information about the service and its components.
Support for API related to monitoring Meraki devices
- A new feature is added to monitor Meraki devices in the Discovery using API as a Monitoring Protocol. This enables the Admin to monitor the Meraki devices in the Discovery.
New Features
Platform
Feature Name | Feature Description | Feature Benefit |
License Expiry Notification Target Persona: Admin | The License Expiry Notification feature helps to configure the license expiry notification and send notifications to desired set of configured users. Using this functionality, an admin can set the expiry reminder to alert the user(s) about the license expiry. The UI using the ‘Set License Expiry Reminder’, instead of the Web.config file. For more information, see License Expiry Notification. |
|
Offboarding User Policy List Target Persona: Analyst | The Offboarding User Policy List feature enables in addressing the pending and progressive dependent items associated with the offboarding analyst. A new tracking incident is created, and e-mail notification is triggered to respective stakeholders about the dependents of offboarding user accounts. For more information, see Offboarding User Policy. This feature enables to:
A new Offboarded User link is implemented to view the list of dependent records associated with offboarding user account specific to the selected Domain, Tenant, and Workgroup. Note: The records are accessible, if the logged in user has analyst privileges and associated with the respective workgroup. Else, the records appear greyed out. |
|
API Configuration Target Persona: Administrator | To discover multiple type of devices, SummitAI now offers API based discovery. Based on the API configuration, the Servers, Networks, Links, Printers, and Laptop devices in the organization can be identified or define to establish connection with the configured APIs. It identifies or supports all the devices wherever an APIs is required. Using API configuration, you can:
For more information, see API Configuration. |
|
Service Management
Feature Name | Feature Description | Feature Benefits |
|---|---|---|
Incident Closing Mode at Business Rule Designer level Target Persona: Admin | On a Business Rule page (Admin > Basic > Infrastructure > Business Rule > UPDATE FIELDS), a new drop-down box Incident Closing Mode is introduced with two new options Auto and Manual. On a Business Rule page, a new text box Auto Closing days is introduced. This text box is enabled if Incident Closing mode is selected as Auto. It will also have the drop-down with the following Business Days and Calendar Days options. For more information, refer to Business Rule Designer. At Tenant configuration level for Incident module, a new drop down is introduced along with text box for Auto Closing Days. This drop-down will have the Business Days and Calendar Days options. Note:
For more information, refer to Configuring Incident Management Module. Note: Incident Closing Mode configuration done at Business Rule Designer will override the incident closure configuration done at Tenant, Category and Workgroup level. For more information, refer to Configuring Category, Configuring Workgroups. |
|
Configuring a Schedule in Business Rule Designer Target Persona: Admin | A new check box Schedule is added for Trigger Type on the BUSINESS RULE page. New filter Trigger Type is added under FILTERS with the following options:
Schedule Info icon is introduced which will be displayed along with Business Rule ID in SHOW LIST under ACTIONS. For more information, refer to Business Rule Designer. |
|
Bar Caller from the Approver List Target Persona: Admin | A new check box Bar Caller from Approver List is added on the TENANT page (Admin > Basic > Infrastructure > Tenant), under the For Approver section for Service Request. For more information, refer to Configuring SR Management. If Enable Approver Selection under CONFIGURE USER GROUP is disabled then in case of multiple approvers, this feature will remove the caller from the approver list after submission. If the caller is the only approver, then system displays a validation message and blocks the SR submission. If Enable Approver Selection under CONFIGURE USER GROUP is enabled then in case of multiple approvers, if user selects only caller as an approver, system displays a validation message and blocks the SR submission. If user selects multiple approvers including a caller, this feature will remove caller from the approver list once the SR gets submitted. If the caller is the only approver then system displays a validation message and blocks the SR submission. |
|
Auto Close Change Request Target Persona: Admin | On the TENANT page (Admin > Basic > Infrastructure > Tenant), a new sub-section CHANGE REQUEST CLOSURE is added under DETAILS section for Change Management module with the following new configurations:
For more information about how to configure CHANGE REQUEST CLOSURE for the automatically or manually, refer Configuring Change Management Module. |
|
Manage CR Approval, Update, and Task Notifications in Change Management | Administrator can manage the CR Approval, CR Update, and Task notifications triggering to the workgroup members while creating the workflow by selecting the following fields. On the PROPERTIES pop-up (Approval), the following fields are added newly.
On the PROPERTIES pop-up (Task), the following field is added newly.
For configuration, see Configuring CR Approval Workflow. | Better control over the notifications – Make sure the right notifications are sent to the right stakeholders at the right time. |
Creating, Viewing and Updating a Work Order for a PR Target Persona: Admin | You can configure the Operation Level Specifications (OLS) for Problem Management also under the DEADLINE tab on NEW OPERATIONAL LEVEL SPECIFICATIONS like Incident Management and Service Requests. For more information, refer to Operation Level Agreement (OLA). Analyst can create, view and update the Work Orders. For more information, refer to Creating Work Orders, Viewing and Updating Work Orders. |
|
Problem Record (PR) approval via e-mail Target Persona: Analyst | For every Problem Record (PR), the Approver can quickly do one click approval from email. Configuration An Analyst needs to select Enable PR Approval by E-mail check box under the APPROVE tab on the CONFIGURE PARSING CONDITIONS section on the NOTIFICATION PARSER page. *APPROVAL_TABLE* and *APPROVERACTIONS* are added in the template Authorization, RCA Approval and RCA review template to display the PR details in the PR approval e-mail notification. For more information, refer to Approving Problem Record via E-mail. |
|
Knowledge Articles Recommendation in New Call Record for User Page | The Analyst can use the Knowledge Records (KRs) to provide solutions to the End Users and avoid logging new Incidents, Service Requests, or Enquiries. For more information, see Creating Call Records. A list of Knowledge Records relevant to the entered subject will display in the Recommended Solution(s) Found pop-up, as you start typing in the Subject field on the NEW CALL RECORD FOR USER page (Call > User > Manage Calls > New Call Record for User), Various sections of the KNOWLEDGE RECORD DETAILS page:
If a knowledge article is a Public Article, the above fields will not be displayed. For more information about the public article, see Creating Call Records. |
|
Closure Code for Call Management | A new field Closure Code is introduced on the NEW CALL RECORD FOR USER page (Call > User > Manage Calls > New Call Record for User). Also, while closing an Enquiry call record or creating/submitting an Incident or Service Request call record, the analyst needs to select a Closure Code. Closure Code for Enquiry Call record Earlier, the Solution and Private log fields were displayed when an Analyst changed the Information or Enquiry call record status as Closed. When the Analyst selects the Information or Enquiry call record status as Closed, the following fields are displayed.
Closure Code for Incident/ Service Request Call Record While submitting an Incident or Service Request call record, the analyst needs to select a Closure Code. The selected Closure Code will be tagged to the call record only if the call record is successfully converted to an Incident or Service Request. Enable Closure Code Menu How to enable closure code sub menu, see Configuring Closure Codes. Using this menu, the admin can configure Closure Codes based on the organizational needs. The Closure Codes defined by you are available to the Analysts while closing enquiry call records or while creating/submitting an Incidents or Service Requests call record. For more information about how to configure closure codes, see Configuring Closure Codes. |
|
Use Problem Management Custom Attributes in the PM Work Orders | Earlier, using the Form Builder, the Administrators can configure the custom attributes for the Problem Management module and can make specific custom attributes mandatory based on the problem record status. Now, the Administrators can enable/extend or disable the custom attributes configured for the Problem Management module to work orders created from a problem record. Under the PROPERTIES section, a new check box, Extend to Work Order is added for all the controls. Drag and drop control and select the Extend to Work Order check box to view the custom attribute in the work order created from a problem record. For more information, refer to Configuring Custom Fields for Customers. Note: If custom attributes are configured in a parent-child relationship, and only for child custom attribute Extend to Work Order check box is selected. In this case, the child custom attribute will not be displayed in the work order. If you want to use custom attributes configured in the parent-child relationship, select Extend to Work Order check box for both parent and child custom attributes. |
|
Asset Management
Feature Name | Feature Description | Feature Benefits |
Custom Sub Status configuration of Non-fixed assets Target Persona: Asset Manager (Admin) | This feature is available under: Asset > Configuration > Status Configuration With this feature, Asset Manager can now configure sub statuses for Non-fixed assets too. Earlier, Sub status configuration was possible only for Fixed assets. The feature is configured in a parent-child relationship model where each Status is a parent node and corresponding Sub statuses are its child nodes. Accordingly, various pages are improvised to accommodate Status and Sub Status of Non-fixed assets. To view the page changes, Click here. | AM module is now capable of capturing Status and Sub status of both Fixed and Non-fixed assets and configure them. For more information, see Status Configuration that explains the Status and Sub status configuration of Fixed and Non-fixed assets. Once the Status and Sub status of the assets are configured and then later captured, it helps an Analyst to accurately track the statuses and sub statuses of Fixed and Non-fixed assets in a detailed level at any point in time. |
Standardized Asset Return Movement Process Target Persona: End user, Analyst, Administrator | To ease the experiences of user and IT store manager, the Movement configuration screen is now optimized. Also, the following consoles are introduced into the Web application newly:
| A standardized process is established to monitor the entry and exit of assets seamlessly. For more information, Click here. |
Optimized software inventory Target Persona: Analyst | New tabs such as General, Licensing Mapping, Contract Mapping, Baseline Profile mapping, Users, and Devices are appended under the Details section of the ADD SOFTWARE page. | This enhancement helps the Analyst to perform all the action that are pertaining to software management at a single flow with minimal click. For more information, see Adding Software. |
IT Operations Management
| Feature Name | Feature Description | Feature Benefits |
|---|---|---|
Introduction of new Service Based monitoring Dashboard to view the details of all the components (such as servers, network devices, and links) categorized under each service. Target Persona: Analyst/Admin | A new page named Service Dashboard is added under Operations > Views. Service Dashboard helps the Analyst or Admin to monitor all the details about the available services. This dashboard provides complete information about the service and its components. This new feature is available under: Operations > User > Views > Service Dashboard For more information, see Service Dashboard. Note: Create a new service at CMDB > User > Services > Add New. | Service Dashboard helps the Analyst or Admin to analyse and understand the following:
On the Service Dashboard page, Analyst or Admin can view the following information about the services:
When you click on a particular service, you can view the following information about the service and its components:
|
Support for API related to monitoring Meraki devices. Target Persona: Admin | A new feature is added to monitor Meraki devices in the Discovery using API as a Monitoring Protocol. When adding or editing a device in the Network Topology, a new option named API is added to the dropdown list of Monitoring Protocol field along with SNMP.
Operations > Users > Networks > View > Create View/Edit View For more information, see Application Dashboard > Meraki UI. | This enables the Admin to monitor the Meraki devices in the Discovery. The Admin can perform the following activities:
|
Service Management
| Improvement Name | Improvement Description | Improvement Benefits |
|---|---|---|
Caller Mapping – Mail Parser | A new list option Caller is added to the Fields on New Incident page drop-down box on the NOTIFICATION PARSER page in section CONFIGURE PARSING CONDITIONS (CREATE > FIELD MAPPING). For more information, please refer to Configuring Notification Parser. | Admin can configure the caller and can enable the mapping of one of the e-mail fields to a caller attribute. |
Addition of four new keywords for Change Management module | The end user will receive the e-mail notifications about Analyst logs, Change Manager Log, Configuration Team Log and Change Advisory Board Member log configured under Logs tab on Change Record ID details page. To achieve this functionality, the following four new Keywords are added related to Change Management module.
On the NOTIFICATION TEMPLATE page (Admin > Advanced > Notifications > Notification Template > Select a Tenant > Select the Change Management module> Select a Template Name > Click the Keywords hyperlink), you can view the list of all the Keywords. For more information about Notification Templates, see Configuring Notification Template. | Inclusion of Analyst Logs in the mail provides a one stop view for the technician to view all the information in one place, thereby reducing the number of clicks and time required to traverse back & forth between mail and application and keeps stake holders informed about the latest update/logs. |
Modify – Mandatory PIR Configuration for Change Record and Mandatory PIR Configuration for Task | A hyperlink is provided for Change Type and a new icon is added to achieve this functionality under the tab MANDATORY PIR CONFIGURATION FOR Change Record and Mandatory PIR CONFIGURATION FOR TASK. For more information, refer to Configuring Change Management Module. |
|
Standard attributes/keywords in Custom Notification Target Persona: Admin | A list of standard keywords is available to be used in the subject and body of the custom notification templates (Notifications as part of Workflow). To achieve this functionality two new buttons, Keywords and Show HTML, are added in the properties of Custom notifications. (Admin > Notifications > Notification Template > ACTIONS > Add New). For more information, refer to Configuring Notification Templates. |
|
| Enhancements for Extend SR Feature | Keywords Related to Extend SR Feature Two new Keywords related to extend SR feature, *Extended SR* and *Original SR*, are added. The Administrator can include these keywords in any of the required notification templates. If included, it will capture the original and extended SR ID as shown below. On the NOTIFICATION TEMPLATE page (Admin > Advanced > Notifications > Notification Template > Select the required Tenant > Select the Module as Service Request > Select a Template Name > Click the Keywords hyperlink), you can view the list of all the Keywords. For more information about Notification Templates, see Configuring Notification Template.
On the Service Request List page, a new configure column, Extended SR is added. Also, the Extended SR is added as filter. User will be able to view the original SR ID in the extended SR. User will be able to view extended SR and original SR under the RELATIONSHIP tab. For more information, see Viewing My Service Requests List. |
|
| Enhancing APPROVAL STATUS table for Level Number and Approval Level | User will be able to see the following level of approvals:
Navigate to Admin > Advanced > Notifications > Notification Template to view the Approval Mail templates. APPROVAL STATUS table will provide detailed information of levels. Level Number and Approval Level will be displayed in two separate columns on APPROVAL STATUS table. | User will be able to see all level of approvals to bring more transparency to the user to get to know which levels are already approved and which are pending. |
Platform
| Improvement Name | Improvement Description | Improvement Benefits |
|---|---|---|
Enhancement in ADVANCE BI DASHBOARD CONFIGURATION page. | In the ADD TAB section (grid) of ADVANCE BI DASHBOARD CONFIGURATION page (Admin > Basic > Infrastructure > Advance BI Dashboard Configuration List, click ADD NEW button), the order of the fields is re-arranged in following manner.
| Provision for better visibility of the details. |
Mobile Application
| Improvement Name | Improvement Description | Improvement Benefits |
|---|---|---|
Service Validity | Service validity functionality is introduced in the Mobile Application to provide a seamless and consistent user experience between the Web App and Mobile App. The Service Validity is introduced under the SR DETAILS tab of the following pages:
For more information, see Mobile App Enhancement. | Admin can configure the Service Validity in the SR DETAILS tab to set the validity of provisional entities. It could be extended based on the requirement. |
Auto Populate check box Target Persona: Admin | A new Auto Populate check box is available on the PROPERTIES panel for the following controls for Service Catalog Management Custom Attributes on the FORM BUILDER page.
The newly added Custom Attributes are displayed on the Service Catalog and Service Request pages (requesting Service from the Service Catalog). | It auto-populates the User details for the selected Custom Fields. |
Service Request Extend Validity Target Persona: Admin | Using this functionality the validity of the services can be extended. By default, the validity of newly created Service Request is auto extended from the Validity expiry date of the parent SR. It is also extended based on default duration configured in the web application. | It enables admin to extend the validity based on the requirement. |
Asset Management
| Improvement Name | Improvement Description | Improvement Benefits |
|---|---|---|
Improvised Software Details page
Target Persona: Analyst |
For more information, see Viewing Software Details. | Analyst can view the number of inactive software of all stores on a single screen. It avoids navigating to detail page of each software and thus saves the time of the Analyst. Analyst can view the complete software details irrespective of the store by clicking the hyperlink of required status. Using this option, the Analysts can export the software details to a Microsoft Excel Sheet. Additionally, in the Microsoft Excel Sheet, the Analyst can view the complete description and information of Software without being trimmed. |
Deallocation option in Software Inventory. Target Persona: Analyst/Admin | A new action Deallocate is made available in the Action panel of Software inventory. For more information, see Deallocating software license. | It is now possible for an Analyst/Admin to deallocate software licenses directly from the Software Inventory. |
Provision to display all additional IP address details associated with the device in the Remote session and in the Hardware Discovery tab of Asset Details pop-up page. Target Persona: Analyst | Additional IP addresses that are mapped to a device are displayed in the following screens by clicking on the
Additional IP address details are also made available in the Agent Online Status Report. Click on the hyperlink under IP Address column to view the other IP Address details that are mapped to the selected device. | This feature will enable analysts to view the IP addresses associated with an Asset. Using this information analyst can choose right IP address for Remote Desktop Connection. |
Inclusion of Store keyword in the mail alerts with respect to the store threshold values set for a specific store. Target Persona: Administrator | Notification mail templates are improvised to include the Store keyword (*STORE*) in the subject and mail body sections of the mails configured for both Fixed and non-fixed assets (Consumable, Accessories, and software). The respective mail alerts are sent to the configured recipients updating them about the breach of maximum or minimum thresholds for a specific category of assets . The e-mails can also be configured to log service requests automatically to ensure procurement process is initiated. On the NOTIFICATION TEMPLATE page (Admin > Advanced > Notifications > Notification Template > Select a Tenant > Select the Asset Management module> Select the template Asset Threshold notification for Category > check the Subject field), you can view the newly added *STORE* Keyword. Refer the Screenshot. | With this new improvement, the Store name is included in the subject and mail body of the alert notifications. Thus it is easy for the recipients to know about the breaching store threshold values of asset categories with respect to a specific store. For more information See, Configuring Notification Template and Store Threshold. |
IT Operations Management
| Improvement Name | Improvement Description | Improvement Benefits |
|---|---|---|
Inclusion of two new columns 'Circuit ID' and 'Incident Count' in Uptime Report. Target Persona: Analyst/Admin | Two new columns Circuit ID and Incident Count are added to the Uptime Report of Network Devices and Network Links. Circuit ID is specific to a network device or network link. Incident Count depicts the number of incidents raised on behalf of the corresponding network device or link. The count is displayed as a drilldown on the report. Clicking the drilldown gives the uptime details of the corresponding network device or link. Reports > ITOM > Reports drop-down > Uptime Report For more details, see Uptime Report. | With the inclusion of Circuit ID in the report, Analyst or Admin can identify the network component correctly. Incident Count notifies Admin or Analyst regarding the highly malfunctioning components briefly. The Uptime Details pop-up gives a complete picture regarding the uptime and downtime behavior of the selected network device or network link. |
Introduction of new columns 'Down Since’, ‘Down time duration’, ‘Up Since’ in ITOM Dashboard Status Details page. Target Persona: Analyst/Admin | New columns ‘Down Since’, ‘Down time duration’, and ‘Up Since’ are added in the ITOM Dashboard Status Details page of down and Up network entities. Down Since value displays the exact time at which the corresponding entity got down or stopped functioning. Down time duration value shows the total down time duration of the corresponding entity from the moment it stopped functioning. Whereas Up Since value gives the time moment from which a network component has been working without down time. Dashboard > IT Operations Dashboard The Status details page also has a selection option with which Admin can view only down time details, only Up time details, or both down and up time details of network entities. This enhancement is available based on configuration settings in the Tenant Configuration page. Admin > Basic > Infrastructure > Tenant > Select the Tenant > Click Configure Details in the right Action panel. | With this enhancement, user would get a comprehensive report regarding the downtime status details of network entities such as Network Device, Network Link, Servers, Printers and Proxy Servers. This feature is implemented in a very user-friendly way such as, by selecting the appropriate option on the Status Details page, user would get uptime details, downtime details or both status details of the components present in the network. |
Addition of new columns ‘Incident ID’, ‘Resolution Code’ and ‘Status’ in the Details popup page of network components. Target Persona: Analyst/Admin | Three new columns such as ‘Incident ID’, ‘Resolution Code’ and ‘Status’ are added in the table which displays top five down time details of network entities such as Servers, Network devices, Network Links and Interfaces. Incident ID has a hyper link to view full details of the corresponding incident. It shows in a popup. Resolution Code value is displayed in the table once an incident is resolved whereas Status gives the current status of the corresponding incident, for example, ‘Closed’, ‘Pending’, ‘In-Progress’, etc. Operations > Users > Views > Network Device View / Server View For more details, see Viewing Server Details. | This enables the user to have a detailed view of incidents raised with respect to the top five downtime occurrences of network components such as Servers, Network devices, Network Links, and Interfaces, if any. The inclusion of incident details helps an Admin to analyze the top five downtime occurrences more accurately and also empowers him to measure the business impact of these down timings. |
Limitation
All old configuration of the Auto Problem Record creation will be deleted when you upgrade from pre-Denali SP1 to Denali SP1 or a later release. Hence, the Administrator needs to do configurations based on CONDITION and TARGET fields again.
For more information, see Configuring Auto Create Problem Records.
Performance Improvements
- Service Catalog details page access is faster.
- Admin module DN job performance is improved.