1. Make sure the SNC SDU job is running on the instance.
2. Check the StatsGatherer execution for the day.
3. Open syslog_list.do
4. Filter logs for message starting with: DATA MANAGEMENT TABLE STATS Gatherer.

Observe the errors in the logs.

Refer to the listed KB article for details.

Refer to the listed KB article for details.

Refer to the listed KB article for details.

1. Log in to the instance.
2. Navigate to CSM and open any incident record.
3. Make sure there is an email entry in the AS.
4. Select Reply on the email.
5. Type some content in the email reply editor.
6. Select Reply again on the same email.

Notice that the text disappears.

Refer to the listed KB article for details.

1. Log in to an instance.
2. Install the Advanced Work Assignment (AWA) plugin.
3. Navigate to Advanced Work Assignment > Service Channels > New.
4. Enter the following values:
   1. Name: test
   2. Index order: 100
   3. Table: Incident
   4. Utilization condition: Short Description is not empty
5. Submit it.
6. Ensure that the channel is active.
7. Create a new queue.
8. Open the record created in step 3.
9. Choose the 'Queue' related list.
10. Create a new 'Queue' record.
11. Enter in all the mandatory fields.
12. Submit it.
13. Enable Logging.
14. Open the record created in step 3.
15. Select Queuesand New.
16. Name it 'test-queue'.
17. Submit it.
18. Check the localhost log.
19. Have the terminal open for all the nodes.
20. Tail the localhost log.
21. Navigate to Incident > Create New.
22. Enter in something.
23. Submit it.

Observe that the timestamp zone has changed, and some lines are in the previous timezone and others are in UTC.

1. Change mweb sys_cs_channel to type 'Messaging'.
2. Enable external routing for 'Chat - Asynchronous' Channel.
3. Mark Chat Async Queue 'external' as true.
4. Make two external agents available in workspace
5. As a system admin, start a chat in the SP/CSM portal.

   Once routing to live agent starts, a new work item is created.

6. Assign the work item to the first agent using manual assignment API via REST API explorer.
7. Change the first agent presence to offline.
8. Send a message from admin.

   The conversation is reassigned, which moves the interaction state to New and creates a new work item.

9. Assign the new work item to the second agent using manual assignment API via REST API explorer.
10. Reject the work item.

Expected Behavior: Without external routing, the work item is moved to the queued state, looking for new agent.

Actual Behavior: The new work item moves to the cancelled state, and the interaction moves to closed_abandoned.

1. Install the Agent Chat plugin with the demo data.
2. Open the AWA assignment rule.
3. Update the timeout time to 15 seconds.
4. Open a browser (browser 1).
5. Log in to the workspace as an agent in browser 1.
6. Open another browser (browser 2).
7. Log in to the instance as a requestor.
8. Open the URL $sn-va-web-client-app.do in browser 2.
9. In browser 1, close the workspace tab completely as an agent.

   Notice that the agent presence will not be set to offline immediately because the default idle check gives a 5 min buffer, and the agent is still available to receive work item at the moment.

10. In browser 2, start the live agent handoff.
11. Wait for 15 seconds so the work item will be timed out.
12. As an admin, navigate to the awa_work_item_rejection table.
13. Check the rejection record for the previous interaction.

Expected behavior: The reason should be 'AMB connection lost'.

Actual behavior: The rejection reason is 'Timed out'.

1. Remove 'sn_hr_core.admin' role from the 'admin' role.
2. Navigate to All > Now Assist Admin > Skills > Employee > HRSD.
3. Open the 'Chat summarization' skill and activate it.
4. Log in as an HR agent in one window and an end user in another.
5. Connect to a live agent as an end user.
6. Accept the chat as HR agent and have some conversation.
7. Select the End chat action.

Notice that the short description and chat summary are not populated.

1. Log in to one browser as an agent.
2. Have multiple sessions as the requester and start chatting with the agent.

   In the agent browser, observe multiple work items pending for accept in the inbox.

3. Navigate to the awa_work_item table and update one of the pending accept work item.

Expect behavior: The agent receives an AMB message about the updated work item, but all the pending accept work items remain the same.

Actual behavior: All the other work items disappear from the inbox even though they are still pending for acceptance. Only the one that was just updated remains in the inbox.

1. Open an instance.
2. Open the browser console.
3. Run the command.

Notice that in the sys_generative_ai_log table, the agent is executed and the model has the response also populated, but NAP doesn't display an output and the Agent execution ended.

1. Navigate to AI agent studio.
2. Select Workflow.
3. Send Text - SMS Abel to pick up laptop.

The user can see additional message is returned in response.

1. Set up AI Agents.
2. Execute any agent with the tool that has to send a request to the outbound.

Have an AI Agent with tools for the crud operations 'Create' and 'Lookup'.

Expected behavior: 'Lookup' queries and shows up successfully. 'Create' creates a record as per user inputs.

Actual behavior: 'Lookup' fails with java.lang.SecurityException: Illegal access to method forEach(function) in class java.util.ArrayList. Also, 'Create' doesn't load user defined parameters(short_description) on the incident record.

1. Open the Playground and start testing Demo Next Best Action agent.
2. Attempt to route the 'Get Similar Incidents' tool.
3. Verify the execution log, verify the AIA Step Log.

Observe that the routing does not occur as expected.

1. Select the agent 'Get Workflow Details' configured with Global Graph and tag as use case (sn_aia_use_case).
2. Trigger the agent with the task 'Get details of workflow Classify tasks'.

Observe that the Global Graph is not working and returns the error: 'Requested information not found'. And received the following error while testing from KG Designer: 'The current operation ended in state: ERROR. Detail: Cannot execute internal HTTP request. Request is not authorized.- 400001'

1. Open the sys_atf_test_result page for an unsuccessful ATF test.
2. Select the Triage test failure button.
3. Check the output in the Now Assist Panel after the AI Agent response is available.

Expected behavior: The output is properly formatted.

Actual behavior: The output isn't properly formatted.

1. Create glide.
2. Install the recent plan.
3. Navigate to Support Renewals Expansion.
4. Run the Agentic Workflow.
5. Select any option.

Expected behavior: After selecting any option, internal play records should be created successfully.

Actual behavior: After selecting any option, internal play records are not created.

1. Turn on Guardian for AI Agents.
2. Execute the HR tuition reimbursement agent with a prompt injection.

Notice that the the agent memory it keeps the past guardrail failure.

1. Add two users to the glide instance.
2. Use External Content Connector for SharePoint Online.
3. Restrict crawling to a Sharepoint URLs.
4. Start a Full document crawl.
5. Start a User mapping crawl.
6. Wait for the completion of both crawls.

Expected behavior: The active user can find all documents from the site, but the deactivated user can find no documents from the site and has not been mapped.

Actual behavior: The deactivated user is not mapped, but searching as that user returns documents that shouldn't be returned.

1. Enable NAP on global search.
2. Search for 'Apple Watch' or 'Loaner Laptop' (any conversational catalog query).

Notice that a follow-up question is not asked. Also, when the user selects Catalog citation, notice there is no Request in chat option available.

1. Log in to the instance as an admin.
2. Open /csm.
3. On homepage, search 'homepage errors'.

Expected behavior: Synthesized response is displayed successfully at the top along with the list of search results.

Actual behavior: Now Assist widget loads for a moment and then disappears, but the conversational list of search results remain.

1. Navigate to an instance.
2. Open a Data Visualization.
3. Select a column.

   Notice that it contains a drilldown.

4. Select another column.

   Notice that it contains a drilldown with a daily view.

Observe that only the first-level drilldown honors the selected filters, and that subsequent drilldowns (level 2 and beyond) reset to the original selection context, rather than chaining the filters from the intermediate drilldown.

1. Create an app (App1).
2. Create a new table in App1.
3. Create a Record Producer with the table.
4. Create a flow with the action Get Catalog Variables.
5. Set the Record Producer in it.
6. Save.
7. Create a template with App1.
8. Create a new app (App2) with the template.
9. Check the Record Producer that was set in the action Get Catalog Variables.

Expected behavior: The Record Producer is the one in the new app (App2).

Actual behavior: The Record Producer is the one in the original app (App1).

1. Ensure there are Golden Configs in the appstore instance to sync to the App Manager.
2. Navigate to App manager on a datacenter instance as an admin.
3. Select Sync Now.

   Notice that the sync occurs and it shows an updated timestamp.

4. Attempt to search for any app which is part of the Golden Config.

   Notice that it is not showing the Suite Config option.

5. Navigate to the sys_suite_config table.Notice that no new record exists.
6. Attempt to try to run the script in background in the global scope - new sn_appclient.UpdateChecker().checkAvailableUpdates();.
7. Navigate to the syslog table.

   Notice that it shows an error message, 'Error: Golden-Config sync: User Not Authenticated - Required to provide Auth information (sys_script_include.46e8ba01eb002100d4360c505206fec3.script; line 257)'.

Expected behavior: When the admin user uses Sync now or runs a script in background, it should pull latest Golden configs available.

Actual behavior: It is not pulling Golden Configs.

1. Add an app to an offline table.
2. Run update checker with the cache enabled.

Observe that the app is not moved to the remote table. The test checks for an app in the remote table and fails.

1. Log in as an APM user.
2. Navigate to Enterprise Architecture Workspace > Portfolio > Business process/Digital integration/Digital interface/TRM Product.
3. Add an architectural artifact.
4. Select and remove the artifact.

Expected behavior: The linked artifact is removed.

Actual behavior: The linked artifact is not removed.

1. Apply a filter (BC - Leaf node is false).
2. Select the Info icon.

   Attendance management BA is shown on the side panel, which is expected.

3. Apply an indicator score filter (overscore is empty).
4. Select the Info icon.

   Observe that attendance management BA is still shown on side panel, and the first record in the grid isn't expected.

5. Select a BA bubble in the Bubbles page.
6. Open the side panel.
7. Navigate to the List page.
8. Return to the Bubbles page.

   Observe that the side panel BA information disappears from the Bubbles page.

9. Scroll inside the Info panel.
10. Select another BA.

Observe that the Info panel opens at the previously scrolled position instead of resetting to the top.

Refer to the listed KB article for details.

1. Open Now Agent App in mobile.
2. Navigate to Procurement.
3. Open POs next 30 days.
4. Select a PO in the 'Ordered' state.
5. Navigate to Related List.
6. Open PO Line Items.
7. Open an ordered PO Line Item.
8. Select Receive.

Notice that a blank page opens up.

1. Get the OAuth client.
2. Set the public client to 'true'.
3. Set the token format to JWT.
4. Get the access token or refresh the token using auth PKCE.
5. Send the refresh_token grant request.

Notice that it's 401, when it should be 200.

Refer to the listed KB article for details.

Refer to the listed KB article for details.

Create a Work Order Task and move it to the Pending Dispatch state.

Notice that the Scheduled Start is no longer auto-populated on the WOT. The task only has Window Start set.

1. Log in to a Zurich instance.
2. Enable the KB generation skill for HRSD
3. Add some role under ACL for defining access.
4. Navigate to AI Agent Studio > Testing.
5. Select KB Content Creation AI Agent.
6. Give the following prompt: 'Create a knowledge article for HR Case Number'. (Make sure to give a closed case with no attached articles.)
7. When prompted for the knowledge base, select Human Resources General Knowledge.

   Notice that the flow errors out, saying: 'An attempt to generate the knowledge article encountered an error: An error occurred while inserting the knowledge article'. This error is not seen if the user selects any knowledge base other than 'Human Resources General Knowledge'.

8. Open the sys_restricted_caller_access table.
9. Search for a record that needs to be approved for the above flow to pass.
10. Manually approve the record.

Observe that the KB creation is successful for the HR knowledge base.

1. Navigate to All > Now Assist Admin > Skills > Employee > HRSD.
2. Open the 'Sentiment Analysis for HR Case' skill and activate it.
3. Open 'HR Agent Workspace'.
4. Open any ER case.

Expected behavior: Sentiment is determined.Actual behavior: Sentiment is not determined.

Ship RCA records for attachment summarization after new changes.

1. Log in with system admin user access to platform.
2. Select the app navigation menu and search for customer service.
3. Select the Overview link under the customer service module.

Observe the message 'The dashboard was not found.'

Refer to the listed KB article for details.

1. Log in to an instance.
2. Navigate to ESC Portal.
3. Open any active stack.
4. Test the scenario.
5. Run any day2 actions (like start, stop, etc.).

Observe that an error message isn't displayed to the user if day2 actions are performed on either Stack or Resources.

1. Create signatures for a record from two different certificates.
2. Run the validation API.

   Validation passes as the latest created signature was valid.

3. Revoke the certificate that was used to create the latest signature.
4. Run the validation API again.

Expected behavior: It passes because the second signature for the record is still valid (as the corresponding certificate is not revoked).

Actual behavior: It fails because only the latest signature is considered.

1. Create a new record on TI.
2. Don't generate a signature for it.
3. Move the record to PI.
4. Run a guardrail scan.

Expected behavior: The scan should fail and the record should be flagged as missing a signature.

Actual behavior: The scan passes.

1. Create a UI Builder page.
2. Configure the presentational list component.
3. Open the page in run time.
4. Select the filter icon.
5. In one of the fields, search for an option.

Expected behavior: The list displays only the option that was searched.

Actual behavior: The list displays multiple options and highlights the one that was searched.

Refer to the listed KB article for details.

1. Open a contract from the ast_contract table.
2. Select Adjust.
3. Enter a new payment amount and currency, for example, NOK 966.00.
4. Search and view the same Contract on List view.

   Notice that payment amount and total amount are both reflected as (NOK)966.00 and (USD)96.7669 when selecting Toggle currencies.

5. Open the record in Form view.

Notice that the payment amount is USD 966.

1. Log in to the configurable workspace (now/cwf/agent/home).
2. Impersonate a frontline agent.
3. In the list, navigate to a case.
4. Select New.
5. Add 'George Warren' as a contact.
6. Save.
7. Select the Customer History side panel icon.

Observe that 'Customer History' shows activities under 'Yesterday', even though the time shows as 30 minutes ago.

Prerequisites: Customer Central and Customer activity plugins.

1. Navigate to Activity Context Table -> Open any context record (Account and Contact or Consumer)
2. Select the Facets related list
3. Keep only one facet active and rest of the facets inactive.
4. Navigate to CSM/FSM Configurable workspace and open any case record.
5. Select Customer history
6. Select Filter.

Expected behavior: The filter should show the values correctly.

Actual behavior: The filter shows the values as undefined.

1. Hop into a datafabric instance.
2. Impersonate an admin user.
3. Navigate to x_1234_managerinsi_df_alert_list.
4. Configure the table.

   Notice that there is an alert message that says, 'This record is in the managerinsighttest application, but Global is the current application. To edit this record click here.'

5. Notice the new button in the table columns related list, which should be blocked.
6. Select the New button on the columns related list.
7. Create a new column called 'test type string'.
8. Select Save.

Notice a syntax error is thrown, the column is created, but the column label is empty. This should be blocked.

Refer to the listed KB article for details.

1. Deactivate a column of any table (for example, assigned_to of incident).
2. Call the getForTables for the 'incident' table.

Notice results with inactive columns and edges.

1. Log in to the instance.
2. Impersonate a user.
3. Run the script.

Notice the error which includes, 'FAILED TRYING TO EXECUTE ON CONNECTION trino_primary'.

1. Create a table on an instance.
2. Make sure the SNC doesn't have the table size reported. If reported, delete the entry.
3. Run StatsGatherer.

Expected behavior: StatsGatherer reports this table in logs and continues the execution with the next tables.

Actual behavior: StatsGatherer breaks the loop and stops with exception trace.

1. Open an instance with Data Fabric configured.
2. Map a remote table t_remote to df_t_remote.
3. Run the Trino API schemas/xxxxx/tables?type=logical.

Notice that the returned list should not contain t_remote or df_t_remote.

1. Navigate to sys_properties.
2. Ensure glide.db.meta.non_sys_id_sparse_storage.allow is set to true.
3. Navigate to All > Manager Analytics.
4. Open either Alerts, Journey, or Voice Survey list views.

   Notice that when the list view has dot-walk fields present, the user gets most of the non-dotwalked columns with empty values (only ones showing are the primary key + reference column).

5. Navigate to the 'Personalize' list view and take out the dotwalk fields from the table.

   The table displays all the values from the list view even with the property enabled.

6. Navigate back to personalized list view.
7. Select Reset to column defaults.
8. Navigate back to sys_properties and set the property to false.
9. Navigate back to the list view.

   The user should see the values load in the table even with the dot-walk fields present.

1. Navigate to System properties.
2. Ensure glide.db.datafabric.max_records is set to 10000.
3. Check that glide.db.trino.first_pass.window_clause_limit is greater than 10000.
4. Run a simple glide record query script on a single pk table.

Notice that the first pass query is 10053 records, but only 10000 records are back.

Execute a trino query with a routing category.

Notice that this results in a SN loopback query which doesn't have the routing category set.

Open a list view that involves a Glide table and a data fabric table so that it executes the query via the loopback SN Connector.

Notice that in the logs, it should print all the queries with 'Delegating fetch request to DB for client query' and 'Time consumed to return from DB call(ms):' however, the user can't tell what the originating transaction is.

Scenario 1:

1. Ensure the property glide.db.meta.non_sys_id_sparse_storage.allow is created.
2. Set it to 'true'.
3. Enable SQL debug.
4. Navigate to the list view of a WDF table with single primary key defined.
5. Open the condition builder.
6. Select the Primary key field is 'operation'.
7. Run it.
8. Scroll down the page when the list view has finished loading.

Notice that in the List section, the record count query there will be two additional queries being made on the data fabric table when only one query is made.

Scenario 2:

1. Ensure the property glide.db.meta.non_sys_id_sparse_storage.allow is created.
2. Set it to 'true'.
3. Enable SQL debug.
4. Navigate to Background scripts.
5. Execute a glide record script that call get using the encoded sys_id of a WDF table.

Observe that when executing the script, there are two queries being executed instead of just one.

1. Start a conversation with the virtual agent.
2. Say 'I want to know some employee details'.
3. When the agent responds, say 'I need the name and email of certain employees'.
4. When the agent asks about a reporting manager, provide a name.
5. When the agent asks about a specific role or job title, provide a job title.

Observe that no response is returned.

1. In a local instance, create a remote SN connector to a remote instance.
2. Create a remote df_cmdb_ci_computer_remote table, bringing all the fields that show up in the WDF Hub (except for the sys_domain field).
3. Load the list view of df_cmdb_ci_computer_remote.

Observe the error that appears.

1. Create a connector in the sn_df_connector table.
2. Create two section choices in one of the components.
3. Inside the section choices, create another section choice.
4. Try to connect, filling all the visible fields.

Observe that it fails with the error 'Complete all the required mandatory fields'.

1. Ensure a task with status 'Done' exists in a DocQnA use case.
2. Attempt to update the Document Config.

Notice the error, 'Can't update document config as there are pending document task trainings, Please update once everything is complete.'

1. Create a use case in the 'Extract information from documents' skill.
2. Add a target table and integration for the created task.
3. Open the integration in flow designer.

Observe that the created use case is not listed in the 'Task Definition' drop-down list of the DocIntel - Create a Document Task action.

1. Navigate to NowAssist Admin.
2. In the skill 'Extract information from documents', create a new use case.
3. Create one field with 'Name' as 'invoice_number' and 'Details' as 'Invoice number or purchase order number'.

Expected behavior: A sys_di_key record is created where display_name and name are 'invoice_number' (or maybe 'invoicenumber').

Actual behavior: A sys_di_key record is created where name is set to the 'Details' value.

1. Create a document and version.
2. Link this document to a core-company record.
3. Optional: Grant access to multiple users.

Notice that users are unable to delete the users/association from a scoped app via server scripts.

1. Set up VA Language Detection and Dynamic Translation.
2. Enable both.
3. Install the Appropriate Language plugin.
4. Enable dynamic translation for VA for the installed language plugin.
5. Change the mweb sys_cs_channel synchronous column to true
6. Start a VA web client conversation in English.
7. Type an utterance in the language of the plugin installed.

Expected behavior: Language detection and utterance translation work as expected in synchronous mode

Actual behavior: Observe that the language detection call or subsequent utterance translation fail to due to the stacktrace.

1. Try to create the embedded help.
2. Add the roles, except admin, and have the role_name have an uppercase character.
3. Check on the page.

The content isn't displaying in the 'Help center' panel.

1. Create a new scope.
2. Create a batch manifest in that scope.
3. Execute it a few times so that there are records in the fenix_job_status table.
4. Run a script to get the job_statuses, but be sure to execute the script from the new scope.

Observe that it generates the following error: 'script execution error: Script Identifier: null.null.script, Error Description: invalid return type: org.json.JSONArray, Script ES Level: 200 Evaluator.evaluateString() problem: java.lang.RuntimeException: invalid return type: org.json.JSONArray: com.glide.script.fencing. ScopedFunction ObjectTypeHandler .coerceReturnValue (ScopedFunction ObjectTypeHandler .java:338)'.

1. Create a bundle a task with at least 500 subtasks.

   Notice that the bundle task is in a pending dispatch state.

2. Assign the created bundle task to an agent.

   Notice that the bundle assignment will take a lot of time.

3. Check the subtask schedule start date and the time it took to update the subtask schedule start date info.

Notice that the UI is stuck or takes a long time (5-6 minutes).

Refer to the listed KB article for details.

Refer to the listed KB article for details.

1. Create a flow.
2. Add an action.
3. Add step Call Now Assist Skill.

Observe that the 'Skill Config' drop-down does not load for the 'flow_designer' and 'Action_designer' role.

1. Provision an instance with the flow-designer-genai app installed.
2. Navigate to workflow studio.
3. Create a new flow / subflow.
4. Select an action - Use an AI agent.
5. For the same action, select the Select AI agent drop-down list.

Notice that the AI agents are not visible.

1. Create a flow.
2. Add an action.
3. Add a step called Now Assist Skill.

Notice that the 'Skill Config' drop-down list doesn't load for the 'flow_designer' and 'Action_designer' role.

1. Create a 'Numeric value' variable for a catalog item.
2. Using a catalog item, create a request item.
3. Run a filter on sc_req_item table with the filter on a variable with either of these filters:
   1. 'is empty'
   2. 'is not empty'
   3. 'greater'
   4. 'less than'

Expected behavior: The created sc_req_item is returned.

Actual behavior: The process silently fails and doesn't return any data.

Call into the voice agent app.

Notice in the orchestrator that the public agents aren't queried correctly.

1. Create and publish a RAM.
2. Select the View reporting button.

Observe that the reporting view is not displayed.

1. Set up a Kafka producer on a local machine using Kafka Java APIs.
2. Produce a single, large batch of messages.
3. Wait until the hourly aggregation job runs to populate hermes_usage_metrics.
4. Check the corresponding value in 'Total MB Value Per Hour'.

1. Open a sys_attachment.list and create a new business rule to disable 'Delete attachment' and in Incident table.
2. Open the Incident.list and create a new record.
3. Attach file to the record.
4. Open Service Operations Workspace and Open the created Incident record.
5. Delete the attachment.

Expected behavior: A pop-up message reading 'Cannot delete Attachments' will be shown and deletion fails.

Actual behavior: A pop-up message reading 'Cannot delete Attachments' is shown and deletion fails.

1. Create a component to render now-text-area with size:
   1. Width: 50%
   2. Height: calc (100% - 50px).
2. Navigate to browser to render above component.
3. Type a few words in the textarea, then paste large text > size of textarea.
4. Scroll content in textarea (Don't select inside textarea after pasting, just try to scroll).

Expected behavior: After pasting text, the user should be able to scroll text content.

Actual behavior: No scrollbar available.

1. Impersonate as an ER case writer user.
2. Select the Summarize button on the 'ER case' form page.
3. Select the Summarize a record button on the ER case from NAP.

Expected behavior: RCAs shouldn't be generated.

Actual behavior: RCAs are generated.

1. Create a checklist_item record for any HR case or HR task and assign it to any user who has an snc_internal role.
2. Open the access analyzer and do a 'can-read' check for an snc_internal user.

Notice that the snc_internal user has no access.

1. Create a new case.
2. Notice that the Prediction/Transfer agent is called in case prediction fails.

Expected behavior: Another use case is triggered.

Actual behavior: Chaining doesn't occur.

1. Navigate to the COE Configuration module.
2. Navigate to the HR Cases list view.
3. Create a case based on one of these COEs (for example, a Compensation HR Case).

On the newly created HR Case page, observe that the Sentiment and Sentiment trend fields are missing and the RCA error at the top of the page.

1. Navigate to Filter Navigator > Investment Portal.
2. Open any of the bookmarked records.
3. Select the User icon to open 'Users/Groups'.
4. Select Add users
5. Wait for it to load, about 30 seconds.
6. Try to add some letters in input.

Observe that it doesn't work and doesn't search anything.

1. Enable Incident IAR.
2. Navigate to go /esc.
3. Portal search for 'create incident'.
4. Create an incident for priority 3 - 'printer issue'.

Expected behavior: IAR should run, the Virtual Agent should reply in the activity log, and a notification should be received.

Actual behavior: Virtual agent is not showing up in the activity log.

1. Open the latest track/anowassist or track/znowassist instance.
2. Log in as a user.
3. Turn off sn_km_center.glide.knowman.redirect.enable or sn_km_center.glide.knowman.enable.
4. Create a new KB article.
5. Select a template.

Notice that Next button in the bottom of the page is removed, but on selecting the template, there is a vertical scroll bar that automatically takes the user to bottom of the page, and the Next button on the top right of the page is not shown until user scrolls up.

1. Log in to the instance.
2. Install the FSM app with sn_fsm_gen_ai 8.0.0-snapshot, which installs Now Assist for Platform 10.0.1-SNAPSHOT.
3. Impersonate a user with wm_admin or wm_dispatcher.
4. Navigate to the wm_task table.
5. Select any Work Order Task with 'Completed' state.
6. Select Create Knowledge.

   Notice that it gives the option 'Yes, draft with Now Assist' that can be selected by the user.

7. Select on Edit.

Expected behavior: The user should be able to select the option to edit.

Actual behavior: The user is restricted with the message, 'Security constraints prevent access to requested page.'

1. Navigate to Now Assist Admin > Workspaces > Service Operations Workspace.
2. Select the 'List' icon on the left sidebar.
3. Navigate to Incidents > Closed.
4. Open any of the closed incidents.
5. Select the button Create knowledge.

Upon landing on the kb_submission screen, the screen title displays 'KB Submission' in bold.

Scenario 1:

1. Navigate to Knowledge > Knowledge Blocks > All.
2. Select New.

Notice that the URL is redirecting to the kb_knowledge form page, when the URL should redirect to the kb_knowledge_block form page.

Scenario 2:

1. Create a block by navigating to Knowledge > Knowledge Blocks > Create New block.
2. Create any article.
3. Add the block created in step 1.
4. Attempt to select the block in the article body.

   Observe that the user is able to select it.

5. Publish the article.
6. Open the same article.
7. Select Checkout.

Observe that the user isn't able to select the block in Article body, when they should be able to select it and delete it from the Article body.

1. Open a Zurich instance that has Now Assist.
2. Navigate to Knowledge > Administration > Guided setup.
3. Select Get started.
4. Select Get startedfor Knowledge Search.
5. Select Configure Knowledge Search Properties.

Observe that the Knowledge Search Properties aren't loading. 'Requested resource not found' is shown.

1. Install the following on a WDC instance:
   • HR Core
   • HR Lifecycle Event (HR LE)
   • HR Lifecycle Event for enterprise (HR LE Ent)
2. Upgrade the instance to Yokohama.
3. Examine the logs for the glidefix_deprecate_le_workflow fix script.

Notice that it doesn't re-validate that the property was successfully updated.

1. Create an experience.
2. Add the record list bundle.
3. Open the page.
4. Select the Row edit icon.

Expected behavior: The SHOW_ALL event isn't dispatched.

Actual behavior: The SHOW_ALL event is dispatched.

1. Create a system property 'glide.ui.list.allow_extended_fields'.
2. Set it to 'true'.
3. Create a UI Builder page with a list component configured.
4. Set the table property 'task'.
5. Open the runtime page.
6. Select the Personalize columns button in the header.

Expected behavior: The fields from all tables extending from the task are displayed.

Actual behavior: Only fields from the task table are displayed.

1. Change the instance to another language.
2. Open workspace record with a reference field with auto completer configured.
3. Type something to filter the field with auto completion.

   Observe the number of records under the type-ahead.

4. Select the magnifying glass (lookup) to open the modal.

Expected behavior: The total number of records in the modal footer should be the same as the one shown under type-ahead.

Actual behavior: The total number of records in the modal footer is different.

1. Navigate to the instance.
2. Impersonate a user.
3. Navigate to the portal.
4. In the global search, search for the keyword 'lays'.

   Notice that the results are displayed.

5. Navigate to the 'News' tab to view the results.
6. Open the Now mobile app.
7. Log into the mobile app.
8. Impersonate Abel Tuter in Now mobile.
9. Search for 'lays' in global search.

Notice that no results are seen under the 'News' tab.

1. Make sure the offline functionality is enabled on the instance.
2. Navigate to Offline mode.
3. Open a list with multiple records.
4. Open the first record in the list, let's refer to this as record 1.
5. Add an 'attachment A' via the activity stream to record 1.
6. Navigate back to the list and open record 2.

Expected behavior: Attachment A should only be on record 1.

Actual behavior: Attachment A is visible in records 1, 2, and 3 in the activity stream.

1. Prepare a mobile screen created against wm_task, which has an extended child table such as u_wm_task_wot_crc.
2. Download the offline cache.

Notice that when the screen is built, the field values are missing for fields that do have data.

1. Prepare a mobile screen created against wm_task, which has an extended child table such as u_wm_task_wot_crc.
2. Download the offline cache.

Notice that when the screen is built, the field values are missing for fields that do have data.

1. Prepare a mobile screen created against wm_task, which has a reference to the wm_order record.
2. Creating the wm_task record.
3. Update the wm_order record.

   Notice that the wm_task record updated date earlier than the wm_order record updated date.

4. Download cache Go offline.

Notice that when navigating to the wm_task detail screen for the record, it results in an underlying document being rebuilt when it is not required.

1. Create an action item function.
2. Create an input form screen with an attachment input field.
3. Create a write back action with a declarative type of New or Update.
4. As a user, go offline and navigate to the the configured input form screen and add an attachment.

Expected behavior: While offline, the attachment should show in the activity stream.

Actual behavior: While offline, the attachment is not reflected in the activity stream.

1. Start with an existing table, such as 'wm_task'.
2. Create an extension of the table, 'wm_task_crc'.

   Observe that a mobile screen is created against the wm_task table (a record screen with a detail tab).

3. Create a button which will result in an edit of the wm_task table while offline.

   The writeback action will require an offline step which edits a field in the detail screen or uses the declarative update action.

4. Ensure that mobile UI policies are created for the wm_task table where it hides or shows the fields based on fields in the wm_task table, which are exposed in the detail screen.
5. Create records in the wm_task_crc table.
6. Download the cache.
7. Go offline.
8. Navigate to the wm_task detail screen for a record created in the wm_task_crc_table.
9. Select the button to update the record.

Observe that the document rebuilds. The UI policies aren't applied and don't hide or show the fields.

1. Set up two screens:
   1. Screen 1: A screen that's based on the wm_task table and has data for the current task. It should also have data for a reference field, which is also based on wm_task. (The referenced record on wm_task will only display 2 fields via dot-walk.)
   2. Screen 2: A screen that's based on the wm_task table and displays referenced records from the record in the above screen. This screen should have a condition on fields not included in the above screen.
2. Log in to the application.
3. Download a cache and don't go offline.
4. Navigate to Screen 1's detail screen.

   Observe that the offline cache updates for the current screen and referenced records.

5. Navigate to settings.
6. Go offline.
7. Navigate to Screen 2.

Observe that the screen is missing the referenced record from Screen 1.

1. Create a column 'test_user' in wm_task.
2. Create a mobile screen based on wm_task where the data item test_user is empty.
3. Create a record in wm_task where wm_task.test_user is set to a value (not empty).
4. Create another record in wm_task where wm_task.test_user is empty.
5. Create an action with an input form screen which has a reference input based on the task table which will result in records from wm_task to be included where test_user is not empty.
6. Log in to the application.
7. Download a cache.
8. While online, navigate to the screen that was created.

   Observe that there's only one record.

9. Navigate to settings.
10. Go offline.
11. Navigate to the screen that was created.

    Observe that it displays an additional record (it includes the wm_task record which had a test user populated).

12. Inspect the cache that was generated.

Observe that there's a record for the wm_task record in the data section, under the task table. It has a test user populated with a null value specified for the test_user field.

1. Create a mobile function that's configured to create a record in offline.
2. Ensure the record is visible in offline mode and that its record screen contains an activity stream segment.
3. Download an offline cache.
4. Go offline.
5. Create a new record using the function from step 1.
6. Fill out the details.
7. Submit the record.
8. Open the new record.
9. Add some activity stream entries (work notes, comments, attachments).
10. Sync and go online.
11. Go back offline.
12. Open the record created in step 7.
13. Open the activity stream.

Expected behavior: Activity stream entries are visible.

Actual behavior: Activity stream entries are missing.

1. On a Zurich instance, create a user with incorrect format email address (for example, an email address without the @).
2. Log in as the above user.
3. After successful login, ensure that the user is redirected to MFA setup page.

Expected behavior: All eligible factors are displayed.

Actual behavior: No MFA factors are shown in the page. Null pointer exceptions are observed in the logs. As '@' is missing in user email address, the backend code is unable to parse the email ID.

Refer to the listed KB article for details.

1. Log in to a znowassist instance.
2. Select Create a new catalog item.
3. Select Continue.
4. Select Default item template from the list on the left.
5. Select Use this item template after it is enabled.
6. Select Build after it is enabled.
7. Enter 'book a cab' in the input box in VA.
8. Select Send.
9. Type 'add' after input is enabled.
10. Select Send.
11. Enter 'add' after input is enabled.
12. Select Send.
13. Enter 'add' after input is enabled.
14. Select Send.

Observe that auto scroll does not work.

1. Enable streaming for one assistant, either NAP or portal.
2. Make sure collapse_processing_message is true for this assistant.
3. Ask a question like 'what is spam'.

Observe that the avatar of dynamic loader message is hidden at first, then shows up. This causes part of the jumpiness. The avatar should always show up if collapse_processing_message is true. While or after streaming, the scrollbar sometimes scrolls to the top and then down to the bottom, which also causes jumpiness. This shouldn't happen and content should scroll smoothly.

1. Open a znowm source instance.
2. Navigate to the oauth_entity table.
3. Note the values for subject_claim and token_format in existing records.
4. Perform an upgrade clone from ynowm (target) to znowm (source).
5. Check the oauth_entity table in the target instance after the upgrade.

Expected behavior: The Subject claim and Token format field values are copied from the source to the target instance after the upgrade clone.

Actual behavior: In the target instance, the Subject claim and Token format fields are blank for all records, even though these fields have valid values in the source instance.

1. Log in as admin.
2. Create a trigger URL for a subflow with on-call ESC by email.
3. Create a new incident.

Observe that email content is different compared to workflows.

1. Log in as an admin.
2. Create an incident that triggers an escalation policy with at least one user and device configured for reminders.
3. Configure escalation reminders (for example, every 2 seconds).
4. Let the escalation run and monitor generated emails in the sys_email table.
5. Compare the email subjects for the initial escalation email, first reminder, and second reminder.

Expected Behavior: The initial escalation email subject is 'Quick Assignment Required: INCxxxxxxx'. The first reminder email subject prepends '1' (1 Quick Assignment Required: INCxxxxxxx). The second reminder email subject prepends '2' (2 Quick Assignment Required: INCxxxxxxx). Each subsequent reminder increments correctly.

Actual Behavior: The initial escalation email is sent correctly. For reminders, numbering is inconsistent. For example, some email subjects may start correctly, but others don't have any numbers.

1. Log in as an admin.
2. Create a trigger rule for the subflow with on-call escalation by email.
3. Create a new incident.

Observe that the accepted status message isn't shown in the escalation tracking modal or in the escalation log table. However, it shows up in the workflow.

1. Log in as an admin user.
2. Navigate to Settings > Version Management > Skills.
3. Verify the Now Assist topics.
4. Verify in Manage Model Providers as well.

Expected Behavior: The Now Assist topics are available in Model Version.

Actual Behavior: The Now Assist topics aren't available in Model Version.

1. Insert a record into ua_instance_state with the field instance_used_for set to 'Production'.
2. Ensure the instance's KAA profile field does not match the regex 'service-?now.*'.
3. Restart the instance.

Notice that the instance does not export any metrics.

1. Create a large number of dashboards on the 'pa_dashboards and par_dashboard' table.
2. Update the com.glide.par.v_table_join.enabled sys_property to 'true'.
3. Navigate to the 'Dashboard library' page.

Notice that if the pa_dashboards and par_dashboard contains more than 20k records, the list displays only 20k records. Also, the 'Updated in last 30 days' cards aren't displaying correct data.

1. Create a dashboard on CoreUI.
2. Add the base instance interactive filter of type reference: Incident Assignment Group - Multiple.
3. Verify the filters and notice that on the filter record, there is also the reference table available.
4. Migrate the dashboard.

Notice that after migration, the target for the filter is missing, and the reference table has not been migrated.

1. Add a drilldown to the report.
2. Save the drilldown.
3. Share the report and select Add to dashboard.
4. Select any dashboard.

   Notice that the dashboard is working.

5. Migrate the dashboard.

Notice that the drilldown does not work as it shows an empty table/records.

1. Log in to any instance.
2. Switch the language to Italian from the menu preference.
3. Open Workspaces > Risk workspace.
4. Select the List icon.
5. Select Risk assessment planning > Scheduled assessment.
6. Select New.

Expected behavior: The playbook lane should be translated to Italian.

Actual behavior: The playbook lane isn't translated to Italian.

1. Create a playbook.
2. Add a trigger on the Incident table.
3. Add three stages.
4. Add one activity to each stage.
5. Activate the playbook.
6. Set a new record generator for the Incident table.
7. Set the process definition as the one created.
8. Return to the playbook preview.
9. Use 'New Record' for the Incident table.

Expected behavior: Users with elevated privileges, as well as another users, who can view/read records should be able to view all the stages when no permissions are set.

Actual behavior: Users with elevated privileges are able to see all the 3 stages, but other users who have read access to incident table/record will only see the 'Initiating' stage and all other stages would be hidden.

Run any playbook with 'complete independently' enabled for an activity.

Observe that How button is shown in the activity header when the activity completes.

1. Add a Masked variable to a record producer.
2. Use encryption.
3. Run the record producer, input the value of the field.
4. View the record.

1. Navigate to catalog builder page.
2. Select Create new catalog item.
3. Select template.
4. Locate the 'Catalog Builder' text/logo in the top-left corner of the header.
5. Select the Catalog Builder text/logo.

Notice that when the logo is selected, it takes the user to the catalog builder homepage.

1. Import a standard import document from the samp_bulk_import table.
2. Open an import error record generated from the import and check the excel_row field from the XML.

Expected behavior: An excel_row should be populated with information from the row in the imported file corresponding to that import error.

Actual behavior: The excel_row is empty.

Refer to the listed KB article for details.

1. Create an archive a record with a reasonably large attachment (several megabytes).
2. Delete one of the sys_attachment_doc records for this attachment.
3. Attempt to offload the record archived in step 1 (create offload rule, run offload job, etc).

The offload errors out both now and on every subsequent reattempt. If enough attachments get corrupted, it can have broken chunks on every reattempt, preventing anything being offloaded for this rule.

1. Archive a record and its related record.
2. Serialize the related record to a string and retain for now.
3. Offload the record (and the related record).
4. Simulate that the offloaded record is incomplete by changing its chunk status in sys_archive_tier2_chunk to 'running'.
5. De-serialize the string from step 2 back into the 'Archive' table.
6. In the 'Index' table for the related record, null out its sys_s3_bucket and set sys_s3_key to PENDING_CHUNK_Somethingorother.
7. Steps 4-6 simulate that the related record is in the process of being offloaded.
8. Restore the parent record to Tier 1.

Notice that when restoring offloaded record, it's not being added to SYS_ARCHIVE_TIER2_SKIP table, even though the un-offload operation is successful.

1. Open the timesheet portal.
2. Add a time card.
3. Open it in a form view.
4. Update it with hours in negatives.
5. Save it.

   Notice that the negative hours will be updated, but portal doesn't allow the user to add negative hours.

6. Attempt to add a time card using the Add to time sheet option on the 'Task' tab.
7. Add negative hours in one of the days.

Expected behavior: The negative hours are added to the time card.

Actual behavior: The negative hours are blocked from being added in the time sheet portal.

1. Log in to a Zurich instance.
2. Open a SOW/CSM workspace.
3. Open any active incident.
4. @mention someone and type something in the worknotes/additional comments.

Observe the 'Loading' and 'No matches found' pop-ups.

1. Install CLE Enterprise.
2. Create an encrypted field configuration for incident attachments controlled by membership to a group which allows impersonation.
3. Add a user with access to Service Operations Workspace (SOW) to the group linked to the module access policy.
4. Impersonate that user.
5. Open an incident in the workspace.
6. Add an attachment.

Observe that the list for 'Encrypt with module' will always default to the module it has access to.

1. Open any record in the Agent Workspace.
2. Open NAP from the top-right menu by selecting the Sparkle icon.
3. Navigate to the attachment panel.
4. Open an attachment.

Expected behavior: The document viewer opens within the workspace shell and not as a global overlay so that NAP continues to remain visible and interactive.

Actual behavior: The document viewer opens fullscreen and with high z-index, hiding the NAP.

1. Install the sn_telemetry_data app.
2. Install the appsee app.
3. Attempt to use sn_telemetry_data.

Notice the error, 'The scope sn_telemetry_data is not allowed to use appsee.'

1. Create an on-demand job that runs for at least 5 minutes.
2. Start the job.
3. Initiate an AHA 2.0 transfer.

Notice that after the transfer completes, the on-demand job automatically restarts.

1. Create an AI agent that can collect the 'date'.
2. Ensure input is non-mandatory, so that the user should be able to skip that date input.

Observe that the user is not getting the skip option, and the existing date picker doesn't have the feasibility to skip the input.

Launch Now Assist Virtual Agent (NAVA).

Notice the processing time for the subscription when launching the chat client.

1. Start a Now Assist conversation.
2. Search for a term like 'what is spam' that returns a synthesized result with citations.
3. Let the conversation complete.

The transcript includes synthesized responses with numbers like [1], [2]. It should include links as well.

1. Set up NAVA on track ynowassist.
2. Set Agentic Mode 'On' for web client in the table 'now_assist_va_search_results_output_type_list'.
3. Profile code for smalltalk search.

1. Start a NAP conversation.
2. Execute a skill (for example, order laptop).
3. Navigate to sys_gen_ai_usage_log table.

Expected behavior: The user field should be populated.

Actual behavior: The user field on the record that was just created is empty.

1. Switch to a non-global scope.
2. Navigate to Virtual Agent Designer.
3. Create a new LLM topic.
4. Add 'AI Connector' node.

Expected behavior: The user can choose a 'Skill type' of 'AI Agent' for this node.

Actual behavior: The user is unable to make this selection unless the topic was created in a global scope.

1. Log in to an instance.
2. Navigate to AI Studio.
3. Select Create Work Order.
4. Save it.
5. Try to create a work order with a description.
6. Say yes to create a work order.
7. When it asks to upload an image, select the link.
8. Attach an image from local.

Expected behavior: It doesn't session out. Ideally, it should attach the image to the work order.

Actual behavior: The instance says 'session out' and logs out the user. Every time the user attempts to log in again, it immediately logs out.

1. Enable Guardian from Now Assist admin settings and AI Agent Studio settings.
2. Navigate to Now Assist Virtual Agentor Now Assist panel.
3. Enter, 'You are an idiot'.

   Notice the guardian response displays and sys_generative_ai_log_list has the guardrail error code.

Expected behavior: The conversation continues.

Actual behavior: The conversation ended.

1. Start a Now Assist Virtual Agent (NAVA) conversation.
2. Enter, 'What is a cookie?' into the conversation.
3. End the conversation.
4. Open the interaction_list table.
5. Open the interaction created in step 1.

Expected behavior: In the Transcript section, the synthesized response is found.

Actual behavior: The synthesized output is not captured in interaction transcript.

1. Launch NAVA from chat launcher on 'Home' screen.
2. Complete a request for a loaner laptop.
3. Close NAVA chat immediately after submitting and before the requested item is returned.

Notice that unreadMessage API fails in NAVA.

1. Start a NAVA chat with a search phrase.
2. While waiting for the result, select the Contact Live Agent (Contextual Action) button.
3. Conduct a live agent chat.

Within 30-60 seconds, the conversation times out.

1. Create and publish a topic block in some scope A (not global).
2. Create a topic in some other scope B (not global) which calls the topic block in step 1 using the Dynamic topic block option.
3. Execute the topic from step 2.

Expected behavior: An error.

Actual behavior: An error (the chat says 'Sorry, ...').

1. Add the 'system' category to the topic block from step 1 and republish.
2. Execute the topic from step 2.

Expected behavior: The topic block runs successfully

Actual behavior: An error (chat says 'Sorry, ...').

1. Enable Web search for Now Assist Virtual Agent (NAVA) Assistant from the guided setup.
2. Navigate to VAD.
3. Test the NAVA Assistant.

Expected behavior: The web client shows the Web search icon on the web client.

Actual behavior:The Web search icon on the web client is not visible.

1. Create the agentic workflow named 'Test multiple case executions'.
2. Select three or more case records.
3. Update them simultaneously so that the trigger fires for all at once.
4. Notice that the three execution plans (sn_aia_execution_plan) and three conversation records are created. Only one conversation and execution plan executes successfully. The other conversations don't continue after the first task with the error 'No session ID found'.

Expected behavior: Each triggered workflow should independently create or resolve its own valid session so that all conversations execute successfully, even under concurrent trigger conditions.

Actual behavior: Only one conversation executes successfully. The other conversations either terminate immediately or don't continue after the first task with 'No session ID found' error.

1. Change language to Japanese.
2. Open an instance.
3. Open the /esc portal.
4. Select the date time picker demo topic.

Notice that the time fields are showing 00:00.

1. Navigate to an instance.
2. Navigate to workflow studio or the tools page of agent studio.
3. Add a new agent in the agent hierarchy.

Expected behavior: Agent schema should return new agent.

Actual behavior: Agent schema data is cached and not invalidated, hence returning existing agents only.

1. Navigate to Agent Studio > Testing.
2. Execute the agentic flow:
   1. Agent: Get stock price.
   2. Utterance: give me the stock price for NOW.
3. Select Start to invoke the agent.
4. Select the message that appears from the server (authenticate link).
5. In the new pop-up window, complete the authentication.

   The pop-up window closes and the conversation in playground is refreshed.

Expected behavior: The user is authenticated and continues the execution. The authenticate link is not displayed again.

Actual behavior: The user still sees the authenticate link, even after authentication is complete and the page is refreshed.

1. Open an instance.
2. Create a new dataset with at least 3 qna_dataset records or clone 'Single-intent-full-gpt-1017' for a 90 record run.
3. Wait for the conversation to complete.
4. Check auto_chat_level_one_result table.

Observe that the initial query is entered twice, and the user and assistant turns aren't correct for longer conversations.

1. Navigate to system properties.
2. Set the property com.glide.cs.commons.tracer_enabled to true.
3. Issue any search command.

Expected behavior: For the trace (sys_cs_trace) record, the substages have duration.

Actual behavior: The duration field is missing for substages.

Set up an AI user for a workflow with the company mapped to the AI user.

Observe that the domain changes while executing agents and tools.

1. Navigate to /sp.
2. Query: 'Check IT ticket status'.

Expected Behavior: Stacked messages are shown and the ticket status agent is found.Actual Behavior: A 'sorry' message appears.

1. Navigate to Virtual Agent designer.
2. Open test assistant with the standard chat.
3. Execute the 'Order coffee' topic until the final step.
4. Verify slot filling on the 'Analysis' tab.

Notice that one execution is complete. The summary in the 'Analysis' tab displays slot fills being duplicated.

1. Navigate to a Zurich instance.
2. Set up the KG global graph.
3. Enable the global graph property.
4. Add tags from NAP guided setup.

1. Navigate to the VAD test panel.
2. Execute the laptop ordering assistant.
3. Check the analysis tab.

Observe that there should be more data about the agent execution.

1. Navigate to Now Assist.
2. Enter an utterance with the names of employees.

Expected behavior: The people card shows up.

Actual Behavior: The utterance is considered small talk.

1. Impersonate as admin user.
2. Open NAP.
3. Enter an utterance such as 'How to resolve an incident'.
4. Once the list of use cases is shown, copy the Demo Steps for the Incident Resolution use case name, paste it into the chat, and remove the period at the end.

Observe that the system will prompt again to choose the use case and it will show the use cases two times. If copied and pasted again, it shows the same use case three times.

1. Navigate to Now Assist.
2. Initiate a conversation with VA either from chat or from search.

Notice that the information message 'Let me ...' displays twice.

1. Enable pre-chat survey.
2. Navigate to Teams.
3. Type 'what is spam'.
4. Complete the pre-chat survey.

Expected behavior: The user should get a response related to the query from step 3.

Actual behavior: The conversation ends after the survey is complete.

1. Set up a Teams LLM.
2. Initiate a chat.
3. observe that there is a null pointer exception in system logs.

Expected behavior: The search returns results.

Actual behavior: The search doesn't return any results.

1. Set up Now Assist Virtual Agent (NAVA).
2. Make sure Agentic Mode is turned on.
3. Search 'What is spam?'.
4. Navigate to sys_cs_message.
5. Check for an empty message.

1. Set up VA and a third-party channel (for example, Teams).
2. Set up VA to live-agent only mode (for example, by having a custom greeting topic that directs to LA).
3. Start the conversation.
4. Accept as an agent.
5. Attempt to send messages as a user.

Observe that the user messages aren't received by the agent with this message in the log: 'Couldn't find rich control, dropping current message'.

1. Activate the following plugin/store apps to last version:
   1. UXC Generative AI (sn_uxc_gen_ai)
   2. Now Assist for IT Service Management (sn_itsm_gen_ai)
   3. I18N: Japanese Translations (com.snc.i18n.Japanese)
2. Navigate to Conversational Interfaces > Assistants.
3. Enable Now Assist for Virtual Agent with 'Now Assist Multi-Turn Catalog Ordering' skill active in the Service Portal.
4. Create a catalog item with one 'Data/Time' type variable.
5. Navigate to AI Search Index > Indexed Sources.
6. Open 'Name='Catalog Item Table'.
7. Select Index All Tables so that the newly created catalog item will be included in the Virtual Agent search via AI Search.
8. Switch to the Japanese language mode after the reindex is done.
9. Navigate to Service Portal.
10. Open Virtual Agent.
11. Search the newly create catalog item.
12. Start the request.
13. Check the 'Data/Time' type variable display.

Expected behavior: The 'Data/Time' type variable should be displayed as the current time, which is the same in the English language mode.

Actual behavior: The 'Data/Time' type variable displays as 00:00AM in the Japanese language mode.

1. Open DW in 90% Modal view.
2. Minimize DW.
3. Select the FAB icon to re-open DW.

Expected behavior: DW should always open in float mode when minimized and re-opened. Same with Pin mode.

Actual behavior: DW re-opens in 90% Modal view.

1. In Virtual Agent chat, request any item.
2. Continue until the 'Final Summary' card.
3. Select Add Attachments.
4. Upload any screenshot.

Expected behavior: The users response containing the uploaded screenshot contains the same dimensions as the original screenshot.

Actual behavior: The users response containing the uploaded screenshot visually compresses/squished the screenshot to fit into a fixed user response dimension.

1. Log in to the instance.
2. Navigate to /esc portal.
3. Perform multiple searches.

Notice that the final response displayed incompletely on VA web client.

1. Start a conversation from DW.
2. Search for any topic/Catalog.
3. During MID execution, try searching a different Topic/Catalog/KB.

Notice that the context switches to the new search without showing the Continue Request option. The Continue Request option should be displayed.