Customer Fixed Issues and Known Issues Tahoe SP4 HF11
| 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 << Tahoe SP1 << Tahoe SP3 HF01 << Tahoe SP3 HF01 (v1) << Tahoe SP3 HF02<< Tahoe SP3 HF03 << Tahoe SP4 << Tahoe SP4 HF01 << Tahoe SP4 HF02 << Tahoe SP4 HF03 << Tahoe SP4 HF04 << Tahoe SP4 HF05 << Tahoe SP4 HF06 << Tahoe SP4 HF07 << Tahoe SP4 HF08 << Tahoe SP4 HF09 << Tahoe SP4 HF10
On this page:
Customer Fixed Issues | Known Issues
Hotfix Merges
Following are the merged releases in Tahoe SP4 HF11:
Customer Fixed Issues
This section provides details about the fixed customer issues in following modules.
Service Management
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
130442 | The Planned Start Time filter values were not working as expected as it was not properly identifying and including all CR records. | Steps:
| Planned Start Time filter values is working as expected. |
Agentless Discovery
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
122857 | Template Filter logic for with or without (DOT) for SNMP was not working appropriately. For example, for devices discovered with 1.3.6.1.4.1.9.1.1208 and .1.3.6.1.4.1.9.1.1208(preceding with DOT), those discovered with preceding DOT were not retrieving the Serial No and Model information.
| Steps:
| Template Filter logic for Agentless Discovery job works appropriately after the resolution. |
122857 | While configuring the Discovery templates, the parsing condition was not able to fetch the value and trim it to have the required information retrieved. | Steps:
Note: Parser logic will not be applicable if two IDs are given for a field/parameter. Dash logic [-] is for stack switch and will not also allow parser logic to be applicable. | The parsing condition can fetch and trim the value to retrieve the required information after the resolution. |
122857 | In the Discovery Template, when a device was being mapped, the following issue occurred:
| Prerequisite: Configure API configuration. Steps:
| The templates can be mapped without any issue. Notes
|
Known Issues
This section describes the known issues detected by the Summit Dev and QA team in this release.
Issue ID | Issue Description | Scenario | Workaround <if applicable> |
---|---|---|---|
127807 | Using Report Builder only a few reports like Asset Management, CMDB, or Service Catalog reports can be generated. When a Tenant is mapped for example to Knowledge or Call management then the Report Type drop down is displayed as NO DATA. |
| NA |
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ