Vancouver Patch 1

Access Control List (ACL) Rules

PRB1683744

1. Log in to an instance.
2. Navigate to REST API Explorer.
3. Select the following options:
   • Namespace: now
   • API Name: Table API
   • API Version: latest
4. Select Create a record (POST).
5. Set the table name to sys_ux_lib_component_attr.
6. Enter a JSON record within 'Requested body'.
7. Send.

An 'Error 500' is displayed.

Activity Stream

PRB1669510

1. Navigate to sys_properties_list.do.
2. In the name header of the list, search for 'glide.activity.compose. always_show_compose_email'.

Expected behavior: The system property should not exist and shouldn’t return results.

Actual behavior: The system property appears in the results list.

Agent Chat

PRB1675123

AI Search Glide

PRB1653832

AI Search

PRB1625004

AI Search

PRB1673750

AI Search

PRB1676568

KB1442411

Refer to the listed KB article for details.

AI Search

PRB1683982

AI Search

PRB1685095

1. Define user.active dot-walk field mapping on kb_author.active.
2. Add a new user.

Expected behavior: No 'Update by queries' calls should be executed for the kb_knowledg indexed source on AI Search.

Actual behavior: 'Update by queries' call gets executed for the kb_knowledg indexed source on AI Search.

AI Search

PRB1688073

AI Search

PRB1690229

Analytics Hub

PRB1666661

KB1336388

Refer to the listed KB article for details.

Application Navigator

PRB1683254

1. Log in to an instance.
2. Pin a menu.
3. Log out.
4. Clear the browser cache local storage.
5. Log back in.

Expected behavior: The header label should display the correct text.

Actual behavior: While the page loads, the pinned menu header label might display as 'Undefined'.

Appsee - Platform Infrastructure

PRB1675325

1. Create a user with the analytics_admin role.
2. Log in to an instance as the user created in step 1.
3. Navigate to the 'Detection Policy Providers' page.

Expected behavior: Detection Policy Providers Page displays.

Actual behavior: An error message displays.

Appsee - Platform Infrastructure

PRB1687197

Attachments to Records

PRB1687437

Authentication

PRB1679962

1. Ensure that com.sn_customerservice is installed.
2. Create a provider account and a customer account on a provider instance.
3. Create a consumer contact with the sn_sb_pro.consumer and snc_external roles.
4. Register the new consumer.
5. Log in as the new consumer in the provider.
6. On the consumer side, connect to the provider.

The consumer should be able to onboard, but the consumer is encountering an issue.

Benchmarks

PRB1679098

Cache

PRB1683372

KB1506244

Refer to the listed KB article for details.

Cloud Provisioning and Governance

PRB1682568

1. Log in to an instance.
2. Open the Cloud Admin portal.
3. Under the 'Manage' section, select Alert Configurations.
4. Select a new record to see the red and blue banners.

Code Signing

PRB1666367

1. Log in to a trusted sub-prod instance.
2. Create an update set and make it current.
3. Create a script include record.
4. Close the update set and ensure that the update set captured the new script include.
5. Run a 'Sign Update Set' job to create signatures for the script include in the update set.
6. Export the update set and ensure that the signature record is captured in the update set.
7. Import the update set into an instance that is the 'production' (code signing enabled).
8. Attempt to verify the signature record via background scripts.

COE Legacy Family Component

PRB1682470

Field Encryption

PRB1687427

Condition Builder

PRB1679541

1. Log in to a Utah instance.
2. Navigate to sc_cat_item.
3. Build a filter condition where Catalog 'contains' Service Catalog.

   Note that the 'contains' and 'doesn’t contain' operands are available on this glide_list field.

4. Navigate to sc_req_item.
5. Build the following filter condition: Variables Request Developer Project Equipment = 'What software do you require?'
6. Expand the operands available for the variable.
7. Notice users don't see any of the 'contains' options.

Expected behavior: List Collector variables should be inline with other glide_list fields when it comes to searching via Condition Builder.

Actual behavior: List Collector variables can no longer be searched for a contained value. The same operands on other glide_list fields should be available for List Collector variables.

Configuration Management Database (CMDB)

PRB1682098

KB1444123

Refer to the listed KB article for details.

Configuration Management Database (CMDB)

PRB1688715

Scenario 1:

1. Call the create or update template API from a data broker (in the CMDB Workspace scope).
2. Observe that the template isn’t created/updated.

Scenario 2:

1. Call the get template API from background scripts in the sn_cmdb_ws scope.
2. Observe that the user can’t get the template.

Core Platform

PRB1688749

1. Navigate to the system properties list.
2. Set the application scope as Deployment Pipeline (scope: 'sn_deploy_pipeline').
3. Create a system property and add a suffix.

The property name is automatically populated with a 'sn_deploy_pipeline.u_' prefix.

Currency Administration

PRB1675528

1. On the 'Problem' table, create a field Test FX Currency of the 'Fx Currency' type.
2. Navigate to the incident form 'Configuration slushbucket'.
3. For the default view, add a Problemreference field.
4. Test FX Currency.
5. Navigate to an open incident in UI16.
6. Set the problem reference to a 'Problem' with a value set for 'Test FX Currency'.

Expected behavior: The referenced FX Currency field displays the value from the reference problem.

Actual behavior: The FX Currency field is empty and a console log is thrown, 'Syntax error, unrecognized expression: option[value=$1,000]'.

Customer Self-service and Omnichannel Engagement

PRB1686180

KB1445219

Refer to the listed KB article for details.

Database Persistence - Data Access

PRB1682827

Database Persistence - Data Scale

PRB1679628

1. Provision an HA enabled instance.
2. Provision an additional node on the near-side.
3. Assign node_type='Maintenance.Primary'.

The max value for the Glide pool displays 32. If the sys_node_type record that defines 'Maintenance.Primary' is missing, the node doesn't start up.

Database Persistence - Data Scale

PRB1684437

Database Persistence

PRB1636262

1. Create a test table or two.
2. Move them to a gateway, or use one of the default critical tables: sys_attachment or sys_audit.
3. Add the table to the list of critical tables with the property name 'glide.db.gateway _checker.critical_tables'.
4. Bring down the gateway database or make it otherwise inaccessible by Glide.
5. Restart Glide.

   It should keep trying to check if the critical tables are accessible.

6. Make the gateway database available to Glide.

The startup sequence should resume.

Database Persistence

PRB1681458

Data Privacy (Classic)

PRB1672454

1. Schedule a job with cmdb$par1 as a target table.
2. Add a couple of other tables.
3. Start the job.

Expected behavior: No error is shown.

Actual behavior: An error is shown, 'Error creating job handler for type null: [Unknown dictionary table:cmdb$par1, column:null]'.

Discovery

PRB1676183

Document Intelligence Unified Backend

PRB1689429

1. Create an instance with APO 2.0 and DI 3.0 and make sure that there’s a task that has been left in the work in progress state.
2. Upgrade DI 3.0 to 3.1.
3. Verify that the WIP task has the same field level-confidence level after upgrading.
4. Upgrade APO 2.0 to 3.0.
5. Complete the fields in the task and mark it as done.
6. Verify that the staging table has maintained the submitted values.

Expected behavior: The staging table maintains the submitted values.

Actual Result: The staging table doesn't maintain the submitted values.

Document Management Services

PRB1671560

Document Viewer

PRB1683746

KB1518992

Refer to the listed KB article for details.

Dynamic Translation

PRB1659930

1. Install the Dynamic Translation plugin.
2. Create two fields.
3. In field 1, type a string and in field 2, type HTML.
4. Enable the Dynamic Translation for both fields.
5. Enter additional text into the fields and save the record.
6. Confirm that Dynamic Translation is working as expected.
7. Set both of these fields to read-only from the dictionary.
8. Reload the form.
9. Click the Dynamic Translation button.

Expected behavior: HTML field should be translated.

Actual behavior: Only the field with the string can be translated.

Employee Experience Framework

PRB1690601

Event Management

PRB1680120

1. Navigate to SOW.
2. Click the 'Service Dashboard' icon on the left.
3. Click any service.
4. Click the prompted Service map button to launch the service map.
5. Click the Gear button in the upper right.

   Nothing happens.

6. Click any other service.
7. Click the prompted Service map button to launch the service map.

   Users now see the 'Display' settings, but can't change them.

8. Try to close the 'Display' settings.
9. Try to close the service maps.

Users can only do this by refreshing the page.

Field Service Scheduling

PRB1685671

Flow Designer

PRB1674573

Flow Designer

PRB1683738

KB1449357

Refer to the listed KB article for details.

GraphQL API

PRB1689955

KB1504069

Refer to the listed KB article for details.

Hermes (Family)

PRB1671367

1. Access a the Kafka broker with a delay, due to a heavy load.
2. Run the 'Diagnostics' page.

Expected behavior: The sending and receiving messages assessment and test should be independent of list topics, and succeed/fail individually.

Actual behavior: The receive part of the 'Send test message' test times out with a log error indicating: 'KafkaTimeout on listTopics'.

HR Service Delivery

PRB1680871

KB1437725

Refer to the listed KB article for details.

Inbound Email

PRB1691195

1. Open an existing email with a few non-ASCII values.
2. Ensure that there's no 'In-Reply To' header.
3. Reply.

The inbound email is classified as 'New' instead of 'Reply.

Instance Data Replication (IDR)

PRB1663086

1. Set a random glide.idr.bootstrap_server value in the sys_properties table.
2. Attempt to create a 'Hermes Producer & Consumer' replication set.

Expected behavior: The user should be able to successfully create a 'Hermes Producer & Consumer Replication' set. The property should be ignored in a Hermes-only environment.

Actual behavior: The user isn't able to send the 'Consumer Replication' set REST request to the producer.

Instance Data Replication (IDR)

PRB1686080

1. Have two instances in GCC with Hermes active and IDR installed.
2. Create a producer replication set.
3. Create a consumer replication set.
4. In the consumer set, request approval for 'Replication'.

Expected behavior: A REST message provides a producer ID and auto-fills in the consumer replication set.

Actual behavior: An error (ArrayIndexOutOfBoundsException) displays: 'Too much data for block: maximum 214 bytes) occurs in Producer instance that blocks REST response from reaching Consumer instance'.

Integration Hub

PRB1682478

1. Disable a job.
2. Insert a row with one attachment.
3. Delete the attachment and save the record.
4. Add a new row with an attachment.
5. Update the same record and add another attachment.
6. Save the record.
7. Run the job.

Expected behavior: Both rows get processed in the same job run.

Actual behavior: After the first change is processed, the job exits. Upon running the job again, the change is processed.

Integration Hub

PRB1689368

1. Open Flow Designer.
2. Click Create New.
3. Click Spoke.
4. Put any name in name field.Notice that 'x_snc' in the scope field.
5. Click Submit.

An error is thrown.

Integration Hub Stream Connect

PRB1687737

1. On a San Diego or Tokyo instance, create Kafka message flows.
2. Ensure that the flows are published and active.
3. Upgrade the instance to Utah (or later).
4. Ensure that the upgrade to Utah isn't executed as a user with elevated privileges.

This error doesn’t manifest in the same way when the upgrade is run as a user with elevated privileges.

Issue Auto Resolution for Virtual Agent

PRB1665233

1. Install the app-iar-hr plugin.
2. Activate sn_hr_core_case IAR configuration by going to 'sys_cs_auto_ resolution_configuration.LIST'.
3. Activate the VA response channel in the same configuration's notification preferences.
4. Create any general inquiry HR case through portal/email.
5. Open the VA notification for the case.
6. Select 'No, wait for human' in the notification.

A comment was added stating 'Auto-Resolution topic (topic name) started' before the comment 'The user declined the notification', even if the topic isn't started by the user. This is observed in all cases no matter the type of the recommendations (AI Search results/VA topic).

Key Management Framework (KMF)

PRB1668571

Key Management Framework (KMF)

PRB1679671

Language and Translations

PRB1649790

1. Log in to an instance running Tokyo Patch 6.
2. Install the French Canadian language plugin.
3. Navigate to the planned_task.LIST.
4. Add the the Planned Duration column to list layout.
5. Double-click the Planned Duration cell in any row.
6. Type '1' to indicate 1 second of time.
7. Click Save.
8. Switch the instance to the French Canadian language.
9. Open the edited planned_task record.
10. Notice that the Planned Duration says "'1 Deuxième'.

Expected behavior: It says '1 Seconde.'

Actual behavior: It says '1 Deuxième.'

Language and Translations

PRB1681379

Language and Translations

PRB1687119

Language and Translations

PRB1693668

List Administration

PRB1685869

1. Log in to a Vancouver instance.
2. Impersonate or log in as an (IT Infrastructure Library) ITIL user.
3. Access any workspace, such as CSM or SOW.
4. Navigate between different lists.

Expected behavior: The URL should include ListIDs pertaining to each list type.

Actual behavior: The URL doesn't have ListIDs when impersonating.

Machine Learning APIs

PRB1653604

1. Open an instance with the "Service Operations Workspace" scoped app installed.
2. Connect to the instance.
3. Navigate to SOW.
4. From the incident list, open an incident record.

Expected behavior: The incident record loads with recommendations for similar incidents/KBs.

Actual behavior: The recommendations window displays the message "Error Loading recommendations. Please contact your IT Administrator".

MID Server

PRB1674231

Mobile Experience for Field Service Management

PRB1688314

1. On any Utah instance, enable Field Service Management demo data and the Field Service Mobile plugin.
2. Log in to the mobile app as an agent.
3. Navigate to 'My Schedule'.
4. From the top action, select Create Event.
5. Enter the event details.
6. Select 'Repeats Daily', 'Repeat Every 1', and 'Repeat until x Days'.
7. Click Submit.
8. Verify that the event appears in the calendar for the selected date.
9. Click Edit event.
10. Verify that the 'Repeat Until' date is changed to X-1 (one day less than the actual selected date).

Expected behavior: The 'Repeat Until' date should indicate the correct date.

Actual behavior: The event appears until the date selected.

Now Experience UI Builder

PRB1687012

1. Open UI Builder to create an experience.
2. Create a new page and variant.
3. In the content tree, hover over the (Modals and popovers).

Expected behavior: No button appears next to modals and popovers.

Actual behavior: There’s a (+) Add New button next to Modals and popovers.

Now Experience UI Builder

PRB1687155

1. Log in to the instance as an admin user.
2. Navigate to the UI Builder and open the Omni app.

The fields in the UI Builder aren’t editable and you can’t add components.

Now Experience UI Builder

PRB1687430

1. Navigate to UI Builder > Playbook Experience Builder.
2. Under Custom Layouts, select any layout.
3. In the bottom-left corner, click Data Click on Playbook Custom Layout.

Expected behavior: An output displays beside the controller tab.

Actual behavior: No output displays.

Now Experience UI Builder

PRB1688907

1. Open any page.
2. Click Add Component.
3. Search for any 'Eg Alert' component.

'Alert' isn't in the displayed message.

Now Experience UI Builder

PRB1689820

1. Create a page using any 2.0 template (such as related records).
2. Click Update layout.

   The upgrade process should show a 'finished upgrade' modal and a banner should appear over the top of the stage.

3. Dismiss the modal.

Users should see visible changes in the content tree where slots are transformed into containers. The structure should remain the same.

Now Experience UI Builder

PRB1692763

1. Open UI Builder.
2. Open any experience with an extensions point on a page.
3. Open any variant with extensions point.

An internal server error is thrown.

Now User Experience

PRB1683668

1. Set up Amazon Voice with a call transfer.

   After receiving the call, a new interaction is opened for the first agent in Agent Workspace.

2. Transfer the call to another agent.

Expected behavior: When the second agent receives the call, the agent should see the interaction pop-up in Agent Workspace.

Actual behavior: There’s a new tab labeled 'Not found' in Agent Workspace and the interaction is opened on the platform. Or if the 'Not Found' tab in the Agent Workspace is selected, this also transfers the platform's interaction page.

On-Call Scheduling

PRB1689939

1. The user preference 'Load related list in classic form' should be set to 'After the form loads'.
2. Create/edit 'On-Call Schedule'.
3. Select any group.
4. Navigate to 'Escalation Setup'.
5. Navigate to 'Override Escalation'.
6. Try to add an escalation step.

The fields load briefly but disappear after that.

Performance Analytics

PRB1658715

KB1507189

Refer to the listed KB article for details.

Performance Analytics

PRB1689920

1. Navigate to All > Analytics > Library > Filters.
2. Select Filters library.
3. Click New.
4. Specify any filter type (for example, Multiple select).

Expected behavior: User can specify the data source and target in the Data section.

Actual behavior: The 'Data' section is empty.

Platform Runtime

PRB1541236

KB1124245

Refer to the listed KB article for details.

Predictive Intelligence

PRB1579574

Process Mining

PRB1681123

1. Create a project.
2. Add a table configuration and mark any of the activity definitions added as Activity of Interest (AOI).
3. Mine the project.

Mining fails with the error 'The extraction wasn't successful. Try a different configuration, or contact your admin.' Mining for the same project completes successfully if the AOI field is removed.

Process Mining

PRB1683761

KB1437700

Refer to the listed KB article for details.

Record Watcher

PRB1681619

1. Navigate to an expensive record watcher dot-walk query.
2. Make repeated changes on an indirectly associated table to cause repeated evaluation of the slow query.
3. Find the slow query in sys_rw_indirect_query.list.
4. Use the 'active' check box to turn it off.
5. Make more changes, like in step 2.

Expected behavior: After turning off the query, there's no more logs.

Actual behavior: A large number of info-level logs from the log responder.

Reporting

PRB1672596

1. Add Generic Collection Framework (GCF) collectors, and record events for the new reporting API.
2. Add two events to collect usage details and run time.

Expected behavior: Telemetry details are added to track usage in the new Reporting API.

Actual behavior: No telemetry details are added to track usage in the new Reporting API.

Schedules

PRB1679730

Service Catalog Builder

PRB1686034

Service Mapping

PRB1691565

1. Navigate to the service dashboard.
2. Select a service.
3. Wait for the preview pop-up to appear.
4. Click the Service map button.
5. Wait for the map to load.
6. In the top-right, click Advanced Map.

Expected behavior: The metric tab shouldn't be there (resulting in node code/network requests from the client to the server).

Actual behavior: In the advanced map, there's a metric tab.

Service Reliability Management (Family release)

PRB1686861

Service Reliability Management (Family release)

PRB1687786

Session Management

PRB1683885

1. Enable active session timeout.
2. Log in as abel.tuter, wait 20 seconds, and refresh the browser.
3. When you see the dialog that session has expired, refresh the page.

Notice that you will still be logged in with a new session ID assigned.

Software Action Team (SWAT)

PRB1684958

Source-to-Pay Operations (Glide)

PRB1692263

System Export Sets

PRB1685206

KB1449172

Refer to the listed KB article for details.

Table Cleaner

PRB1678154

KB1441282

Refer to the listed KB article for details.

Table Cleaner

PRB1687480

1. Create a table with the 'iterative delete' attribute and a business rule that takes some time to execute.
2. Create enough records for the deletion to go long.
3. Create a table cleaner.
4. Execute the table cleaner.

Table Cleaner

PRB1688904

UI Builder (Store)

PRB1683774

1. Navigate to Service Operations Workspace 'Change Overview' page.
2. Select one of the containers within the views repeater (for example, 'Summary').

The properties don’t show for that component.

UI Form Administration

PRB1677178

1. Log in as an ITIL user.
2. Navigate to any existing incident details and remove a mandatory attribute, such as the 'Short Description' or ;Caller Go', on the 'Overview' tab.
3. Save the form.

   No user notification/error message displays to the user.

4. Navigate to the 'Details' tab and notice that there’s an error notification displayed inside the 'Details' tab.

Expected behavior: The user notification for the Error/Info displays on the top of the SOW incident form.

Actual behavior: The error/info is displayed inside the 'Details' tab.

UI Form Administration

PRB1678904

UI Form Administration

PRB1681716

1. Set up a local test harness that is passing an empty object as the prop for userSession.
2. Notice that the form section is using the empty object rather than finding the window object.

Expected behavior: On an empty object for userSession, the component should grab the window object.

Actual behavior: On an empty object for userSession, the component tries to use the empty object.

Upgrade Center

PRB1685471

1. Customize a record, 'ABC'.
2. Perform an upgrade with an upgrade plan that doesn't contain the ABC file.

The upgrade engine would revert the ABC record to the base version.

UX Framework

PRB1675051

KB1444833

Refer to the listed KB article for details.

UX Framework

PRB1683588

UX Framework

PRB1686081

Virtual Agent Bot Interconnect

PRB1679731

1. Install Bot interconnect (v1.0.1) on a Utah instance.
2. Set the property sn_appclient.app.install.offline to false.
3. Upgrade the instance to Vancouver.

Expected behavior: Bot interconnect should be upgraded automatically to v1.0.2.

Actual behavior: Bot interconnect store app is still using v1.0.1.

Virtual Agent

PRB1683331

1. Ensure that the Advanced Work Assignment (AWA) plugin is installed - com.glide.interaction.awa.
2. Open three browsers: Browser A (Control - Normal), Browser B (Incognito), and Browser C (Normal of a different type, such as Firefox).
3. In all browsers, log in to an instance.
4. In Browser A, impersonate user: Beth Anglin (Agent).
5. In Browser B, impersonate user: Abel Tuter (Customer - Chat Initiator).
6. In Browser C, impersonate user: System Administrator (Manager/Leader/Supervisor).
7. In Browser B, navigate to Service Portal > Chat Window > Live Agent.
8. In Browser A and Browser B, answer the chat with the agent and write back and forth.
9. In Browser C, view the live chat from the manager's perspective in Workspace's 'Interaction' list.

   The latest interaction record isn't closed.

Expected behavior: The system should display the user's avatar per message.

Actual behavior: Notice that the avatar doesn't display correctly when chatting between the agent and the customer.

Visual Task Boards

PRB1646449

1. Create a free form board.
2. Add a private task.
3. Click the number of the PVTSK to open a form that has a context menu.
4. Change the view of the PVTSK (it doesn't matter what view).
5. A window is opened for PVTSK.

If users attempt to update the record, they receive the following error: 'Dialog Closing. Click outside the dialog frame to dismiss'.