Australia Patch 3

1. Navigate to any record in any table.
2. Right-click the header or select the hamburger menu.
3. Select Analyze Access.

Expected behavior: The page redirects to Access Analyzer to analyze that record.

Actual behavior: 'The page you are looking for cannot be found'. It navigates using the previous URL.

1. Navigate to any instance on track/anowassist.
2. Open Service Operations Workspace.
3. Open a record with 200+ activity stream entries.
4. Scroll to a recent AI-generated response containing citation references.
5. Select Show sources.

The cited source (comment/email) should be an older entry — at least 3+ pages above the current viewport.

1. Select the citation link with work notes/comments.

1. Navigate to any relevant workspace.
2. Open any incident record.
3. Turn on the 'Rich text editor' in activity stream's Compose.
4. Add a work note or comment to the activity stream with some of the text set to bold.
5. Select the Copy to clipboard button on the new journal entry.

Expected behavior: When rich text is copied, a notification should display saying 'Copied to clipboard'. When pasted into a plain text editor, there shouldn't be [code] tags around the text.

Actual behavior: When rich text is copied, a notification doesn't display, and when pasted into a plain text editor, there shouldn't be [code] tags around the text.

1. Open the Service Operations Workspace list URL.
2. Navigate to an incident list.
3. Open any incident.
4. Select the + menu.
5. Select Create Interaction.
6. Edit the new interaction record fields.
7. Navigate to an incident record.
8. Open any reference field in a sub tab.
9. Close the incident record.

See that the focus shifts to an interaction record and the edited field values are lost.

1. Enable the conversation history by navigating to Conversational Interface > Agent chat settings.
2. Set the value for 'Number of conversations to display'.
3. Hop to an instance where Advanced Work Assignment (AWA) is configured in two browsers.
4. Log in as Abel Tuter.
5. Set the date/time preference to 'DD-MM-YYYY HH:MM:SS'.
6. Initiate a chat from the portal.
7. Connect to a live agent.
8. Log in as an agent.
9. Accept the chat.
10. Close the conversation.
11. Initiate a new chat.
12. Connect to a live agent.
13. Accept the chat as an agent.

Observe that the previous chat conversation is visible in the Active Chat window.

Expected behavior: The date/time format should display as 'DD-MM-YYYY HH:MM:SS' at the top of the Active Chat window.

Actual behavior: The date/time format is displayed as 'MMM DD, YYYY HH:MM AM' in the Active Chat window.

1. Navigate to Agile Development > Epics (or open an Epic from a board/backlog).
2. Open any active Epic record.
3. Select the Status field.

Expected behavior: 'No status' is available as a selectable option to represent epics with no status assigned, enabling accurate status transition tracking for usage analytics.

Observed: 'No status' isn't available as an option in the Status field list. Available options are limited to green, yellow, and red.

1. Navigate to Now Assist Skill Kit > Evaluation Results Dashboard.
2. Start an AutoEval run for:
3. Agent: Enterprise Architecture Explorer – Query Agent
4. Dataset containing multiple evaluation questions
5. Allow the run to process.

Observe that the evaluation stalls on certain questions, AutoEval keeps retrying internally, and the run never completes.

1. Trigger notifications to any non-admin user.
2. Log in.
3. Navigate to a portal.
4. Open a notification tray.
5. Select Mark all as read.

Notice that it's not marking as read in the background.

In an instance with KG, navigate to 'Make a kgnlq query'.

Observe one_api_service_ plan_feature invocation. It doesn't match the design with respect to the Caller field.

1. Provision an instance with the com.snc.itsm _pa.demo plugin installed to have more test data.
2. Open the list with records of the problem table (problem.LIST).
3. Filter records by Assigned to = Abel Tuter and State = Assess so that two records appear.
4. Remove one of the records.
5. Move the other record to the Fix in Progress state by selecting the Fix button.
6. Navigate to All > Library > Data visualizations.
7. Select New.
8. Select Visualization type: Pivot table.
9. Specify the following data sources:
10. Incident table with the conditions Assigned to = Abel Tuter and State in (New, On Hold, Resolved).
11. Problem table with the conditions Assigned to = Abel Tuter and State in (New, Fix in Progress, Assess).
12. Specify group by's:
13. Columns: Assign to; Show all; Individual metric.
14. Rows: State.
15. Set 'Show row total' and 'Show column total' to false.
16. Check the chart.

Observe that the chart renders and shows expected data.

1. Open the list with records of the problem table (problem.LIST).
2. Filter records by Assigned to = Abel Tuter and State = Fix in Progress so that one record appears.
3. Open that record.
4. Change the status to Re-Analyze.
5. Refresh the chart.

Expected behavior: The chart is rendered and shows the expected data with zeros.

Actual behavior: The chart shows 'No data available', despite data being available.

1. Open UI Builder.
2. Create a page.
3. Add a data visualization component.
4. Use the type, 'Line'
5. Check the Define Data Manually toggle under 'Under data sources'.
6. Copy and paste the 'defect response.txt' in the 'Data' section.

Notice that the chart is rendered, though no information from March is present.

1. Edit the 'Data' section.
2. Update the 'end' information in appliedFilters, from ''end':'2026-02-28' to ''end':'2026-03-31'.

Notice that data for March is now visible.

1. Navigate to Platform Analytics > Library > Dashboards.
2. Create a dashboard.
3. Add a Geomap widget based on the [sys_user] table with the following configuration:
4. Metric: Count
5. Group by: 'Location'
6. Save the dashboard.
7. Exit 'Edit' mode.

Observe that the created Geomap widget doesn't render all the data points and shows an error: 'Some of the data you selected cannot be visualized on the map due to latitude/longitude mapping errors'.

1. Navigate to Boxplot.
2. Select Export.
3. Pick JPEG as the file type.
4. Download the JPEG file.

Observe that a blank page is displayed. The same issue occurs with an embedded PNG and with PowerPoint files in a dashboard.

1. Create any visualization with some data.
2. Schedule that visualization and while scheduling, turn on 'omit' if no records toggle.
3. Select the export type of other > ppt > embed png.
4. Save the scheduled export.
5. Select Send Now.
6. Navigate to email logs to find the email record of the scheduled export.
7. Open that email record.
8. Select the 'Email attachment' tab at the bottom.

Expected behavior: The exported visualization should be attached there.

Actual behavior: Nothing is attached.

1. In Yokohama, create a list-simple visualization.
2. Change the Hide total number of records toggle in the configuration.
3. Save the visualization.
4. Upgrade the instance.
5. Open the same visualization.

Observe that it doesn't migrate to the new list visualization and have the corresponding property set for showing count.

1. Navigate to Software Asset Workspace.
2. Open the 'Software Asset Overview' page.
3. In the 'Activity Center' section, select the Asset Request link.

Observe the navigation to the target page.

1. Verify whether the expected navigation filter is applied.

Expected Result: The relevant filter is automatically applied after navigation.

Actual Result: On navigation, the filter isn't applied.

1. Navigate to an Australia instance.
2. Create a test to open SOW Workspace > Incident Form > UI action visibility > Save.
3. Run the test.

Observe the test takes up to 40 seconds to complete successfully. Sometimes intent timeout errors are seen.

1. Open a Zurich instance.
2. Ensure that the instance is set to the English language.
3. Open a change record.
4. Select the Check Conflicts button in the 'Conflicts' tab.

Notice that the progress bar title displays as 'conflict_detection' and the value is shown rather than the label, 'The conflict check is complete'. The label is translated in Finnish even though the user's instance language is set to English.

1. Open an instance.
2. Navigate to 'Update Set: Test Code Signing Updates'.
3. Validate that the signature is created for the Data source field.
4. Select Scan Signature.

Observe that the signature state for the Data source field still reflects as false.

1. All > Knowledge Graph Designer.
2. Select the Open global graph button.
3. Select Start with user table > Any node.

Note that the prefix is missing for some of the columns.

1. Expend any node on canvas.

Note that the prefix is missing for expended nodes.

1. Open the contribution graph.

Note that the prefix is missing for all the nodes, columns, and relations.

1. Offload a bunch of records to tier2 (using the 'Offload' job).
2. For a couple of records, remove the value from the sys_s3_bucket field.
3. For another couple records, find its sys_archvie_log record and delete it.
4. Turn on the tier2 bulk restore.

Scenario 1:

1. Navigate to the query builder.
2. Open the configuration item query block.
3. Select Filter.
4. Run the builder with multiple OR conditions on the location filter.

Observe that no results are returned.

1. Remove all the OR conditions for location (or use one location filter).
2. Run it.

Observe that once a second condition is added, the query builder fails.

Scenario 2:

1. Navigate to the CMDB Query Builder.
2. Add a server node to the canvas.
3. Apply filters to the node with the following conditions:
4. Location contains 'bock'
5. Location contains 'via'
6. Run the query.

Observe that no results are returned.

1. Remove one of the conditions (e.g., 'Location Contains 'via'').
2. Rerun the query.

Observe that results are now returned.

1. On a base instance, create a flow that is scheduled to run every minute.
2. Navigate to Flow Designer > Operations > Flow > Today's execution.

Observe that the flow is running successfully.

1. Create a sandbox.
2. In the sandbox, navigate to Flow Designer > Operations > Flow > Today's execution.

Observe that the flow is running successfully.

1. In the sandbox, update the flow.
2. Select Activate.
3. Navigate to the base instance.

Observe that, under 'Today's execution', the flow starts erroring out with 'Compiled flow not found for snapshotId'.

1. Open the main instance.
2. Navigate to All > Flow Designer.
3. Create a flow.
4. Schedule that flow to run at a certain interval, for example, 'Repeat every minute'.
5. Activate the flow
6. Navigate to All > Flow Designer > Operations > Flows > Today's executions.

Notice that the flow is running every minute.

1. Create a sandbox instance.
2. Navigate to All > Flow Designer.

Notice that the flow exists.

1. Navigate to All > Flow Designer > Operations > Flows > Today's executions.

Notice that the flow is not running.

1. If no record exists, create a record for a sys_email_template for sn_customerservicecase.
2. Navigate to CSM/FSM Configurable Workspace.
3. Select the 'Lists' icon on the left navigation pane.
4. Navigate to Cases > All.
5. Open case CS0001001.
6. Stay on the 'Comments' tab in the right-side pane.
7. From the right navigation, select Email Templates.
8. Apply any template.
9. Do this repeatedly until an error displays.

1. Update the 'glide.email_ client.configurable _send_enabled' value to 'sn_customerservice_case'.
2. Make sure configuration is done.
3. Log in as a user with elevated privileges.
4. Navigate to CSM workspace.
5. Open a case record.
6. Ensure activity stream isn't present.
7. Select Compose Email to open a modeless dialog.
8. Add [private] in the Subject field.
9. Add 'unknown user' in the To field.
10. Select the Send button.

Expected behavior: The pop-up is displayed based on the configuration.

Actual behavior: The pop-up isn't displayed when the user selects the Send button.

1. Log in to a Zurich instance with HAM 12.1.2 installed.
2. Navigate to Hardware Asset Workspace > Inventory.
3. Select the View button on the Stockrooms missing distribution channel.

See that no records are visible.

1. Open the Compliance workspace.
2. Navigate to List modules > All Policies.
3. Create any policy record with all the required fields completed.
4. Switch to the 'Policy text' tab.
5. Select Import word document.
6. Import the word document.
7. Select Request review.
8. Select Request approval.
9. Switch to the 'Approvals' tab.
10. Approve the record.
11. Switch back to the 'Details' tab.

Notice that there is a KB article generated in the Published policy field.

Notice that the formatting in the KB article 'Details' tab and the 'View article' view are different.

1. Navigate to an instance.
2. Navigate to the User Experience Analytics dashboard.
3. Select Employee Center in the menu.
4. Navigate to Data Foundation > Events section.
5. Open the 'View Knowledge Article' event.
6. Under 'Event properties', navigate to the 'Article Title' and 'Article SysID' widgets.
7. Observe the '...' empty value on the report chart.
8. Export the data to Excel.

Observe the exported report contains an empty field under the first column labeled 'Event property values'.

1. Turn on redirection properties for KC: sn_km_center. glide.knowman. redirect.enable.
2. Navigate to 'Knowledge Blocks' in Navigator in UI16.
3. Select Create.

Expected behavior: Knowledge blocks should honor KC redirection properties.

Actual behavior: Creating or editing a from UI16 doesn't redirect to KC.

1. Open an incident record.
2. Enter the following strings in the Description field:
3. 改行1
4. 改行1
5. 改行1
6. 改行1
7. 改行1
8. 改行1
9. Create a dashboard.
10. Add a list data visualization based on the incident table.
11. Show the description column on the data visualization.

Observe that the data visualization doesn't add new lines (multi-lines).

1. Open any default list in the workspace.
2. Select the browser address bar (don't modify the URL).
3. Press Enter to reload/refresh the page.

Observe that once the page reloads, it automatically navigates to My Lists > Opened by link.

Expected Behavior: Refreshing a default list via the browser address bar doesn't create a list artifact.

Actual Behavior: A new temporary copy of the default list is automatically created. The list appears in My Lists > Opened by link, even though the user never requested a copy. The list is not shared with anyone by default.

1. Verify that sn-list-selector has been updated to Version 26.0.0.
2. Create a list visualization against the incident table.
3. Select Edit.
4. In the configuration panel in the 'Columns and rows' section, next to 'Columns', select Add.
5. Scroll to 'Questions' and expand it.
6. Scroll on the list of variables and look for 'Legal Section'.

Observe that it can't be found. Users would like to be able to choose presentational variables as well, even if they don't contain any values.

1. Navigate to the table schema for the 'Incident' table.
2. Create a custom field named 'Test column' with the field type set to 'Workflow'.
3. Configure 2-3 choice options for the newly created custom field.
4. Select 2-3 incident records and set values for the Test column field using any of the available options.
5. Open UI Builder.
6. Create an experience and page by using the 'List Page' template.
7. Once the page is created, navigate to it on the instance.
8. From the sidebar navigation, navigate to Incidents > All.
9. Select the Personalize fields button on the list page.
10. Add the Test column custom field to the visible columns.

Observe that the workflow stages for the custom workflow type field appear empty.

1. Open any incident record that has a value set for this field (can be opened in classic view as well). If the field is not visible, add it to the 'Form' view.
2. Observe that the field displays 'Pending - has not started'. Note that even when the field value is changed via background script, it continues to display 'Pending - has not started'.

Expected behavior: The display value should be as per available choices.

Actual behavior: It displays 'Pending - has not started' even after changing value. 'Pending - has not started' is not even available as a choice option for a field.

1. Open Virtual Agent.
2. Perform a search that returns at least one Now Assist Genius Result (GR).
3. Select the Thumbs up icon or the Thumbs down icon on the GR.
4. Run the background job to process queued signals.
5. Open the sys_generative_ai_log table.
6. Inspect the Feedback field for the transactions relevant to the Genius Result the user provided feedback on.

Expected behavior: There should be a value such as 'Rejected' for negative feedback or 'Accepted' for positive feedback.

Actual behavior: The feedback is not logged.

1. Use the latest version of NAVA.
2. Enable a mic from NAVA assistant designer.
3. Change the experience to Enhanced Chat.

Expected behavior: The Send button appears in the input bar.

Actual behavior: On-Glide mic seen in input bar.

1. Open any CoreUI dashboard.
2. Open the dashboard selector.
3. Select All Dashboards.

Expected behavior: The dashboard selector avoids excessive ACL checks and runs one check per dashboard.

Actual behavior: It triggers permission evaluation for every dashboard the user has access to, including an ACL check per dashboard and multiple field‑level ACL checks.

1. Turn off the NLQ Prediction server from sys_properties by deleting the URL value 'glide.prediction _service.url'.
2. Navigate to Query Builder.
3. Create an NLQ query, which adds nodes to the canvas.

Notice that this results in the 'Oops...' error.

1. Navigate to CMDB Workspace.
2. Create an NLQ query, which should open a new tab.

Notice that this results in the 'Oops...' error, and the UI is incorrect.

1. Create an indicator (an indicator source isn't necessary).
2. Enable Render continuous lines under the 'Other' tab.
3. Open the scoresheet to edit the scores of the above indicator:
   1. Feb 28th: 200
   2. Jan 31st: 100
4. Create a single score visualization using this indicator.
5. Enable change and change percentage.

Notice that the change and change percentage aren't displayed.

1. Disable the system property 'com.glide.par .unified_analytics. enabled'.
2. Create a single score PA widget on the above indicator, with Visualization: Latest Score.
3. Leave all other fields as the default value.
4. Add the above widget to a Core UI dashboard.

Notice that the widget displays the change (100) and change percentage (100%).

1. Open a base instance.
2. Navigate to All > Platform Analytics > Library > Dashboards.
3. Open any dashboard.
4. Select the arrow to view the 'Recent Dashboards' list.

If this is the first login of the day, observe that the list contains dashboards that may not have been previously accessed.

1. Switch between several dashboards.

Observe that the 'Recent Dashboards' list updates to reflect the dashboards opened during the session.

1. Log out of the instance.
2. Log back in using a new browser tab.

Observe that the 'Recent Dashboards' list resets and displays a different, seemingly random list of dashboards instead of the ones previously accessed.

1. Provision an instance with the 'Customer Service' plugin installed.
2. Navigate to All > Recommended Actions > Contexts.
3. Open any existing context.
4. Under the 'Rules' related list, create a rule with the Name and Condition fields filled out.
5. Under the 'Recommended actions' related list, select New with the action type as 'Playbook'.
6. Set action as any playbook with inputs and save the record.

Expected behavior: The playbook inputs dotwalker should have content inside, and it's the case table meta fields.

Actual behavior: The dotwalker opens to have empty content.

1. Mine a MDM project on incident and Task_SLA.
2. Open Analyst Workbench.
3. Select any intermodal arc.
4. Once it's completed, select View result.
5. Select Show records.

Expected behavior: The user should be shown the incidents belonging to the cluster.

Actual behavior: Observe that the user is redirected to the 'Task SLA' list page with a 'No records to display' message.

1. Initiate 'Intent and activity analysis' on any node.
2. Apply breakdowns that should have a WIP node.
3. Select the WIP node.
4. Observe the results already generated on WIP node and select View.

Expected behavior: The 'View results' card shouldn't be displayed on a breakdown applied model. It's a new task altogether.

Actual behavior: It triggers and 'Intent and activity analysis' and generates the duplicate results.

Open Execution Dashboard > Data Quality tab in Strategic Planning workspace.

Observe a report_view ACL error for the 'No Planned Cost' and 'No Planned benefit' widgets.

1. Open a project in the Project Workspace (PW).
2. Navigate to the Status Report tab.
3. Create a status report.
4. Navigate to the Details tab.
5. Locate the Status field.
6. Ensure the Status field is different from the Overall Health field in the status report. If both values are the same, manually update the Status field on the project.
7. Open the 'Status Report' tab from the left panel.
8. Navigate back to the Details tab.

Notice that the Status field is automatically reverted to match the Overall Health value from the status report.

1. Navigate to Project Management > Projects > All Projects.
2. Open any active project.
3. Select the Status field.

See that a 'No status' option should be available.

1. Create a sys_record_hierarchy.
2. Immediately delete the associated rh.hierarchy.create event that's generated in sysevent.

Observe that the sys_record_hierarchy is in a PENDING_CREATE state with no event to progress it to the next step.

1. Visit the sys_record_hierarchy record.

Notice that there is no 'Reconcile Hierarchy' link under 'Related Links'.

1. Copy the sysId of the sys_record_hierarchy record.
2. Navigate to Scripts - background.
3. Execute SNC.RecordHierarchy API.get(). reconcilePaths(sysId).

Observe that nothing happens. No event is posted to resume creation of the hierarchy.

1. Open the project workspace.
2. Navigate to the project.
3. Create an unassigned assignment from the bottom grid.
4. Check any resource.

Notice its availability.

1. Update the assignment dates.
2. Check the resource availability again.

Observe that it's still the same, even though the availability should be updated as soon as the dates are updated.

1. Create any field on the resource assignment table which is dependent on any other Reference field.

Observe that the dependent config isn't supported in bottom grid choices. It should be supported.

1. Log in to an instance.
2. Navigate to the Service Catalog.
3. Open a catalog item.
4. On the catalog item form, ensure that the Requested For field is empty.
5. Select the Also Request For (multi-user) icon or selector and select a user (e.g., User A).
6. After selecting the user in Also Request For, attempt to select the same user in the Requested For field.
7. Fill in all mandatory fields.
8. Submit the request.
9. Open the associated REQ record and review the generated RITMs.

Actual behavior: Duplicate RITMs are created for the same user.

Expected behavior: The system should prevent selecting the same user in both fields.

1. Navigate to the 'Change Models' module.
2. Open the 'Normal' change model.
3. Set the assignment group to 'Application Development' in the Record preset field.
4. Save.
5. Navigate to the 'Change Request' form in Core UI.
6. Switch to the 'SOW-Overview-Change' form view.
7. Right-click the form header.
8. Configure > Form Layout.
9. Modify the 'Summary' form section.
10. Add Assignment group and Assigned to fields.
11. Save.
12. Navigate to Service Operations Workspace > Changes list > New > Normal card > Continue.
13. On the 'Change' form, the Application Development is pre-populated. Search the Assigned to field for a list of available users.

Expected behavior: See only users in the 'Application Development' group.

Actual behavior: More users are shown that aren't in the 'Application Development' group.

1. Provision an instance with the Change Risk Assessment v2 plugin installed.
2. Navigate to a change request (normal or emergency) in SOW.
3. Select the 'Risk assessment' related link.
4. Complete the assessment.
5. Submit from the 'Overview' page.
6. After it reloads, on the right-hand side (record information), there should be card titled 'Risk'.
7. Select the 3 dots to open a contextual menu.
8. Select Assess risk.

This should open a modal with the assessment and its answers to allow changes, but nothing happens. Also, there's a JS error in the browser's console.

1. Open or create a change request in SOW.
2. Verify that the Assignment Group field is updated.
3. In the 'Overview' tab, update a field in the 'Scope and Impact' section and move the control outside the field.

See that the 'Overview' section begins to refresh, which shouldn't occur. This same issue arises when updating fields in other sections.

1. Log in to Software Asset Management workspace.
2. Select the Licensing Operations module on the left pane.
3. Under the standard list, select Software contracts in 'Contracts'.
4. Select a contract.

Note that the 'Assets Covered' tab isn't converted to German.

1. Create a table.
2. Add a translated_text column.
3. Add Function field on that column.
4. Navigate to v_plugin.LIST.
5. Activate the plugin 'com.snc.i18n.swedish'.
6. Insert records (New Name=Alice and New Name=Bob).
7. Submit.
8. Add the Swedish translations (Älice_sv for Alice and Bob_sv for Bob).
9. Submit.
10. Switch the session to Swedish.
11. Open u_repro_translated_function.LIST.
12. Personalize the columns to show 'Name' and 'Name Function'.
13. Select the Name Function header to sort by ascending.

Expected behavior: The 'Name Function' column shows Älice_sv and Bob_sv (or the English fallback).

Actual behavior: The 'Name Function' column is blank for both rows.

1. Open any record from incident.list.
2. Select View - Service Operations Workspace.
3. Create a field type 'price'.
4. Give it any name and any value.
5. Save the record.
6. Open sys_user table for the name 'Beth Anglin' who has 'ITIL' role.
7. Add a County Code field with the value set to 'system(US)'.
8. Impersonate the user Beth Anglin.
9. Open Service Operations Workspace.
10. Select into the Price field under the 'Details' tab.
11. Without changing anything, select out of the field.

Notice that the value doesn't change.

1. End the impersonation.
2. Update the County Code field to 'Germany' or any other country for the user Beth Anglin.
3. Impersonate the user Beth Anglin again.
4. Open Service Operations Workspace.
5. Select into the Price field under the 'Details' tab.
6. Without changing anything, select out of the field again.

Observe that the value changes.

1. Open a Safari browser.
2. Log in to a Xanadu instance.
3. Open the CSM workspace.
4. Open any non-closed incident.
5. Navigate to the Activity Stream.
6. Navigate to the Compose section.
7. Under 'Subject, select the 3 dots (...) if formatting options are not available.
8. Select the Link button.
9. In the URL field, enter 'servicenow.com'.
10. Select the Save button.

Observe the message, 'The URL you entered seems to be an external link. Do you want to add the required http:// prefix'. The message is confined to the 'Compose' section, and not overlaying the entire page.

1. Provision an instance with Gen AI installed.
2. Open any existing record page (for example, an incident in Ui16).

Observe the AI Agent modified field API response.

1. Inspect the JSON response body.

Expected behavior: The boolean field is named 'isAiCreated'.

Actual behavior: The boolean field is named 'aiCreated'.

1. Log in to a Zurich instance.
2. Open any workspace, such as Service Operations Workspace or HR workspace.
3. Open any record.
4. Navigate to the Compose email section.
5. Enter the email addresses.
6. Select any email address.
7. Perform Copy (ctrl+c) or Cut (ctrl+x) on the email address.
8. Paste it in the 'To' or 'cc' or 'bcc' section.
9. Notice that the email address is not copied.

Expected behavior: The user is able to copy and paste.

Actual behavior: The user is not able to copy and paste.

1. Open a SOW record with Task Intelligence field level recommendations.

Notice that the form level banner appears with deep links to fields that have recommendations.

1. Cancel the alert.
2. Load the form.

Observe that the alert appears again.

1. Open a Safari browser.
2. Navigate to All > Virtual Agent > Designer.

Observe the following error: 'Safari and older versions of Internet Explorer are unsupported browsers, please switch to a different or newer browser.'

1. Log in as a contact/contact as a consumer.
2. Navigate to the CSM Portal.
3. Open Virtual Agent chat.
4. Select the Live Agent Support topic.
5. Close the conversation.
6. Select Live Agent Support topic again in the new conversation.
7. As an admin, open Interaction list(interaction_list).

The 'Assigned to = Virtual Agent' has the first interaction has Account and Contact fields filled, but the next interaction records are missing the Account and Contact fields.

1. Impersonate an external user.
2. Navigate to the ESC portal.
3. Open the Virtual Agent chat history.
4. Select the Bin icon to delete a closed chat.

Notice that the error message appears: 'Failed to delete conversation. Please try again'.

1. On a multi-domain instance, navigate to Now Assist VA admin UI > Chat Experience > Premium Messages tab.
2. Configure a static greeting message.
3. Save.
4. Refresh the page.
5. Navigate back to the chat.

Observe that the custom greeting message isn't populated even though the message was saved earlier.

Perform a cache fetch call for the cache key 'get_user\|table:{table}\|field:{field}\|value:{value}' for any user of the identity type 'ai_agent'.

See that it doesn't return the User field value.

1. Enable Now Assist in Virtual Agent.
2. Configure the agent chat configuration for the /esc portal.
3. Turn off all the other agent chat configurations, only keeping one active.
4. Navigate to /esc.
5. Select the Virtual Agent icon.

Expected behavior: It triggers the live agent support topic.

Actual behavior: It triggers the greetings topic. However, if you end the conversation and create a conversation, it goes straight to the live agent.

1. Navigate to the esc portal.
2. Select the Now Assist chat icon.
3. Type the utterance: 'Adobe access'.
4. Wait for the response to be streamed.
5. Select the Stop button immediately after the response is streamed.

Observe that there's an error.

1. Navigate to Dynamic Window.
2. Create a conversation.
3. Start a conversation.
4. Search for 'iPhone'.
5. Select See more of iPhone.
6. Navigate through the conversation without starting a catalog request.
7. End the iPhone search conversation with 'nothing else'.

1. Log in to an instance with dispatcher0400.
2. Select the Dispatcher workspace button.
3. Select a task from the left side pane.
4. Select the Sort by distance button.