Versions Compared

Old Version 8

changes.mady.by.user Allena Kendrick (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Allena Kendrick (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties


Target release

New York - Patch 4


Platform OwnerDeanna Burns (Unlicensed)
Document statusWork In Progress
SN Discovery SMEAllena Kendrick (Unlicensed)
Business AnalystVandana Bansal
CMDB ManagerChristopher Abbott (Unlicensed)
SN CMDB LeadVimalpriya Kothandapani (Unlicensed)
PMDavid Swanson (Unlicensed)
Service ManagementChristina Lago (Unlicensed)


...

The following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.


Filter by

Discovery
Clear filters
ProblemShort descriptionDescriptionSteps to reproduce

Discovery

PRB1343838

This PRB fix addresses a New York Patch 3 issue where Cloud Discovery would fail when the Discovery plugin is not activated

Discovery

PRB1364492

After clicking 'Discover now' on any discovery schedule, the page keeps loading and the discovery does not start
  1. Navigate to Service Account and create a service account.
  2. Click Discover Datacenters.
  3. Click Create discover schedule.
  4. Follow the steps to create the discovery schedule.
  5. Click Finish.
  6. Navigate to the discovery_schedule page.
  7. Navigate to the schedule you just created.
  8. Click Discover now.

Notice that the discovery does not start and the pop-up window keeps loading. In the console, the following error appears: 'Script: DiscoveryAjax not found in scope: global, and HTTP Processor class not found: com.glide. processors.xmlhttp.DiscoveryAjax: no thrown error'.

Note: Only Cloud Management Core and Cloud Management are activated here.

Discovery

PRB1365469

KB0780957

Errors occur for Horizontal DiscoveryResult Handler.update DeviceHistory() when the CI does not have the name and the ip_address populated

Refer to the listed KB article for details.

Discovery

PRB1366194

Patterns SSH sudo command using CyberArk with no credential ID failsFor the SSH credential saved on CyberArk, if users do not use the credential ID for the credential defined on the instance, when using patterns:
  • Any non-sudo command step works fine. It falls back to the target IP address and the result is returned.
  • Any sudo command step fails.

Discovery

PRB1367623

KB0782858

The Windows OS - Desktops pattern sensor fails with the error 'Cannot deserialize object'

Refer to the listed KB article for details.


Import / ExportList v2EmailTransaction and Session ManagementService CatalogInstance Automation
Clear filters
Problem FixedShort descriptionDescriptionSteps to reproduce
























Service Catalog

PRB1325867

KB0728538

Unable to update catalog tasks if the 'Email' or 'URL' type variables are present in the variable editor

Refer to the listed Known Error KB article for details.

Email

PRB1329356

KB0744354

SLAs are not attached automatically when an email comes in and a ticket is createdThe task_sla is not attached when a task is created from an inbound action even though the start condition matched the SLA definition. It only gets attached when an update is made on the task.

Refer to the listed Known Error KB article for details.

Service Catalog

PRB1321520

KB0723666

Variable with a tree picker attribute doesn't show any results if a reference qualifier is appliedNo values are displayed for a Reference catalog variable when the variable has 'tree_picker=true' attribute.
  1. Create a reference type catalog variable.
    1. Choose the reference as 'Category [sc_category]'.
    2. Reference Qualifier: Simple
    3. Reference Qualifier Condition: 'Active' 'is' 'True'.
  2. Set the variable attribute 'tree_picker=true'.
  3. Submit the variable.
  4. Click Try It for the catalog item.
  5. Click the magnifying icon for the variable.

The pop-up does not show any results.

Email

PRB1327655

KB0746840

Quick messages do not render accurately in the email client templateQuick messages do not render accurately in the email client template. The <div> tags are inserted around the new line characters.
  1. Create a table in a quick message that has two rows and one column.
  2. In the first row, type Thank you for replying to this email. in one line and We will get back to you soon enough. in another line.
  3. In the second row, type Regards, in one line followed by the name of the agent in another line.
  4. Open an existing case record or create a case.
  5. Click the Email button in the upper right tab of the case form.
  6. Select the quick message you just created.

Notice that the rendering is incorrect as the <div> tags are incorrectly added in the email.


...