Refer to the listed KB article for details.

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. Open any Zurich instance.
2. Upload the sys_properties file for glide.ui.escape_text.
3. Run a /cache.do.
4. Load any relevant record, such as 'Incident'.

Expected behavior: The record should load normally with the glide.ui.escape_text sys_property activated.

Actual behavior: A blank screen with a basic message at the top will call out the ampersand issue.

1. Navigate to an instance.
2. Open Service Operations Workspace.
3. Open any incident record with a large amount of activity stream entries (~2000 entries).
4. Open the browser's dev tools window.
5. Select the 'Performance' tab.
6. Select the Record and reload button.

Expected behavior: The page load time shouldn't be affected by CitationHighlightBehavior.js and require less time.

Actual behavior: The page takes about 6 seconds or more to fully load, and the 'Performance' tab displays that it is due to CitationHighlightBehavior.js.

1. Log in as an agent.
2. Mark the agent as online.
3. Log in as non-admin requestor.
4. Navigate to /aix/employee/chat.
5. Enter Live agent.

   Notice that no agent connection is established with the message 'Live agent engaged. Connecting you to a live agent now. Please hold while I transfer you to a human support representative' on the client side.

6. Select Support.

Expected behavior: The live agent is connected and the work item is displayed in the Agent workspace.

Actual behavior: No agent is available, even when the agent is available in the workspace.

1. Have Dynamic Translation set up on Agent Chat.
2. Start a conversation with language 'fq'.

Expected behavior: On the agent side, observe a message 'Message will be automatically translated from Canadian French'.

Actual behavior: The language isn't displayed at all, or in some cases, the region code isn't correctly handled.

1. Install glide.awa and nowassist-ai-agents plugins on a Zurich or Australia instance.
2. Enable 'Include AI Agents' for a assignment rule which has both AI agent and manual agents.
3. Start a incident.

Observe that incident is not assigned to an AI agent as preference even though it is available.

Scenario 1:

1. Log in to an instance.
2. Navigate to /now/risk/compliance/record/sn_grc_reg_change_regulatory_feed.
3. Open a record.
4. Navigate to AskNowAssist > Get action plan.
5. Select Yes after the action plan is displayed.

Notice that number of regulatory tasks in the related list doesn't change, tasks are not being created.

Scenario 2:

1. Create a skill tool that outputs a JSON object.
2. Create a script tool that takes the skill output JSON as input.
3. Return that input as is for displaying in VA.

Expected behavior: The JSON object returned by the skill tool should display in VA.

Actual behavior: The JSON object will be wrapped/contained in a format like this: { response: { model_output: 'actual JSON object' }}

1. Navigate to Search preview.
2. Select a profile.
3. Perform a search.
4. Record the pre-processing time for search.
5. Navigate to that profile.
6. Remove all the Genius Result (GR) configurations.
7. Re-run the search in the 'Search' preview.
8. Observe the pre-processing time.

Expected behavior: The pre-processing time with GR as opposed to without GR isn't different since the filter generated from the first request is being used.

Actual behavior: The pre-processing time is more than double with GR.

1. Open a base instance.
2. Create a non-stardard role containing an uppercase letter and space, such as 'CSC - Knowledge'.
3. Create a KB.
4. Fill the Role field with 'CSC - Knowledge'.
5. Perform a search as a non-admin user targeting that KB.

Expected behavior: The KB is returned.

Actual behavior: The KB is not returned.

1. In ais_datasource, set 'force_late_binding' for KB to true.
2. Make sure KB plugins are installed to get child tables.
3. Run search using a profile that has KB as the search source.

Observe that the log contains entries like '[ais] AclFilterGenerator: Exception during converting ACL for table kb_template_faq, use late-binding'. When the user sets force_late_binding to true, the KB and its child table ACLs should not be translated to filters.

Try to enable hybrid search on global search.

Observe that enablement is blocked.

1. Implement AISDynamicFilter pre-processing.
2. Make an AI Search call by setting filters and passing additional context.

Observe that an additional call is happening per search source. For the second call, the additionalContext value is null even though the additionalContext is passed as parameter to AI Search API call. If filters aren't applied, then the additional call doesn't happen. It happens when filters are applied and additionalContext is null when it should not be.

1. Using v4 ingestion API, import the user principals payload.
2. Import user mapping.

   Notice the first one honors groups and user insert.

3. Update the payload to include another group.
4. Send POST.

   Observe that a group or user will be missing from the update.

5. Delete the user mapping, user script above with single group and user mapping =.
6. Send POST.

Observe that the first insert is not honored unless more than one group is present.

Call the Suggestions GQL API with additionalContext parameter containing DynamicFilter information.

Observe that the VA Skills that should be filtered by DynamicFilters are not being properly filtered, and the additionalContext is lost in the call chain and never reaches the AI Search service where DynamicFilters are applied.

Call the Suggestions GQL API with a term that will return search-based suggestions.

Expected behavior: The payload has the source label field for user-friendly labels based on what is configured for the corresponding source's 'Source Facet Bucket' label on the Search Application.

Actual behavior: There is no label based on the Source Facet Bucket.

1. Open a base instance with AI Search.
2. Navigate to /sp?id=search and search for something that will return results (for example, email, device).
3. Set your window size to 1280x1024.
4. Zoom in to 200% and 400%.

Expected behavior: Content is not cut off at 200% and 400% zoom

Actual behavior: Content is cut off at 200% and 400% zoom

Refer to the listed KB article for details.

Refer to the listed KB article for details.

1. Navigate to EAW > Business portfolio.
2. Create a sub-capability for some parent capability.
3. Add a few sub-capabilities (with names like Test 1, Test 2, Test 3, etc.).

   Notice that the capability is added to the bottom.

4. Select Update Hierarchies.
5. Refresh the page.

   Notice that the order of capabilities changed randomly.

6. Delete the current sub-capabilities.
7. Complete steps 2-5 again (add capabilities with the same names and order again).

Notice that the order changes again and doesn't follow any logic.

1. Impersonate Abel Tuter.
2. Navigate to sn_hr_core_case_workforce_admin.do?sys_id=.
3. Select the Manage attachment icon.
4. Add an attachment.

Observe the two RCAs generated Source as 'UI Page: attachment' and 'Script Include: AttachmentSensitive'.

1. Run an ATF test with a modified client script and UI action.
2. Immediately after the test ends, select Calculate code coverage on the test result page.

Observe that sometimes the frontend aggregation data is not accurate, as all the code coverage from the frontend hasn't been fully processed and persisted.

Refer to the listed KB article for details.

1. License NAFC for an Australia instance.
2. Attempt to install.

Observe that it can't be installed because the BA app is not included as part of distribution.

1. Provision an Australia instance.
2. Navigate to Application Manager.
3. Select the Sync Now button.
4. Search Now Assist For Creator.
5. Select Install.

Notice that the install is successful, but the Install button is still active because BA trial version fails due to the missing hosted plugin com.glide.app_build_agent_core.global.

1. Impersonate a user who has access to the HR Portal.
2. Navigate to the HR Portal.
3. Initiate a Virtual Agent Chat.
4. Enter the prompt: 'Show me my open HR cases'.

Expected behavior: Information about the user's open HR Cases is displayed.

Actual behavior: The user receives the error 'An unexpected error occurred. Please try again.'

1. Open an HR case.
2. Upload an attachment.

   Observe that attachment summarization is working fine.

3. Select Transfer case from the side menu.

   Observe that modal opens.

4. Choose any transfer type (for example, 'transfer to a new case number') and any New HR service (for example, Dental Benefits Inquiry).
5. Select Ok.

   Observe that this HR case transfers to a new HR case, and all the attachments are also copied to new HR case.

6. Select Summarize on the new HR case.

   Observe that attachment summarization is not available even though HR case has attachments.

Expected behavior: Attachment summarization works on the new HR case with attachments after using Transfer case.

Actual behavior: Attachment summarization doesn't work after using Transfer case on the on new HR case with attachments.

1. Provision an instance with the Knowledge Recommendation plugin and Article Optimization plugins installed.
2. From the Knowledge Management properties, turn on the ece.
3. Create an article from the related list of any HR case.

There's an RCA from KC to HR core.

1. Navigate to All > Change > Create new.
2. Select More actions.

   Observe that Create new template is enabled.

3. Select any model.

Observe that Create new template is disabled.Create new template should be enabled only if a model is selected, and the model should be passed to the change model page for creation.

Navigate to All > Change > Create new.

Observe that the background of the create page is colored in Polaris and Coral themes.

1. Run dynamic IRE so that the cache gets initialized.
2. Evict some of dynamic IRE's keys from the cache manually.
3. Try and retrieve the evicted member from cache.

Observe that dynamic IRE runs as though that element was never configured and does not exist.

1. Create a new glide record on sys_archive table using a glide script.
2. Navigate to /sys_archive_list.do?sysparm_query=tableSTARTSWITHtask.
3. Find the archive rule with the name 'Created from glide script'.
4. Open the rule.

Observe that the condition builder conditions aren't rendered. When other fields in the form are updated (Description, Name, etc.), the condition is erased from the record.

1. Install sn_cg and sn_cp.
2. Create a Content Request and CRI.
3. Add any content and schedule the content request item.
4. Add Abel Tutor as approvers to the CRI using 'Manage approvers'.
5. Move the CRI status to 'In Review'.
6. Impersonate the user 'Abel Tutor'.
7. Navigate to hrm_todos_page.
8. Find the CRI and reject it.

Expected behavior: The approver can approve or reject the CRI successfully.

Actual behavior: There is a console error on the page, and the CRI is not getting rejected and remains in a 'Requested' state.

1. Ensure that the Content Publishing package is installed.
2. Navigate to the sn_cd_content_portal list view.
3. Open any existing content type: URL - record.
4. Change the Title value.
5. Navigate to Context Menu > Insert and Stay.

Expected behavior: The changes should be captured and established in the new record.

Actual behavior: It does not. Previous values are retained.

1. Navigate to Knowledge Graph Tag to create a new record.
2. Add relevant Content Publishing tables.
3. Provide a description for KG Tag.
4. Save.
5. Navigate to Conversational Interfaces > Assistants.
6. Select Manage Assistants > Now Assist in Virtual Agent > Information sources > Knowledge Graph.
7. Set 'Natural Language Query' with Enterprise Graph.
8. Under Tags, add the created tag from step 3.
9. Save.
10. Create some sample news articles / company events.
11. Navigate to /esc to ask NAVA simple queries on news, such as 'Show me a news article' or 'Show me a company event.'

Observe that any RCA's necessary are provided/approved, and NAVA returns a response.

1. Navigate to Content Publishing > Create New > Notification > Email.
2. Fill out the required details.
3. Add some rich text to the body.
4. Save and create a schedule content to send the email.
5. Check that the email was logged in the event queue with a valid parm2 value of the email body.
6. Navigate to System Log > Emailto find the record in the email logs once it's processed.

Expected behavior: The subject is filled out as the email content title, along with a valid non-empty body

Actual behavior: The subject is empty and email body has 'undefined' value in the HTML.

1. Set up an instance for archive table migration.
2. Start the migration.

Expected behavior: Only archive tables which meet a TBD threshold should be migrated. There should be a scheduled job to look for tables which were previously skipped, but can now be migrated.

Actual behavior: All archive tables are migrated immediately.

Refer to the listed KB article for details.

With JSON or GraphMetadataBuilder, create an edge with type 'Depends On:Used By'.

Observe the error that says only alphanumeric and underscore characters are supported.

1. Create a data fabric table with no primary key.
2. Try to create a knowledge graph with that data fabric table.

Expected behavior: An error message says that WDF tables with no primary key aren't allowed on the graph.

Actual behavior: The error message says 'Error: Table named u_df_wdf_without_pk is not allowed in graph schema.' The user may not know that WDF with primary key is a qualification to be considered in KG.

1. Add the encoded query string 'priority=3^state' to the incident node.
2. Execute the query from GraphQueryBuilder.

Observe the cytosm exception.

1. Create a graph without specifying migratedToTable flag and custom node type (for example, User).
2. Specify migratedToTable flag.
3. Call get() method.

Expected behavior: The node_type should be the table name (for example, sys_user) and the custom node type (for example, user) should be given as a synonym.

Actual behavior: Cached JSON is returned with node_type. The custom node type is given.

Run any of the following queries:

• Select top 10 log(cost) from cmdb where cost != 0;
• Select top 10 log10(cost) from cmdb where cost !=0;
• Select top 10 mod(priority,2) from incident;
• Select top 10 repeat(first_name,2), first_name from sys_user;
• Select top 10 replace(first_name,''a'',''ba''), first_name from sys_user;
• Select top 10 right(first_name,2), first_name from sys_user;
• Select top 10 second(sys_created_on), sys_created_on from incident;

Execute the script.

Notice that a NullPointerException error is thrown.

Scenario 1:

1. Log in to the instance.
2. Configure the Now Document component.
3. Navigate to Service Operations Workspace (SOW).
4. Open any existing incident.
5. Create a document.
6. Select secondary actions, such as Edit Metadata.

Expected behavior: Sharing permissions are enabled for newly created documents for Upgrade customers in the DMS component.

Actual behavior: Sharing permissions are not enabled for newly created documents for Upgrade customers in the DMS component.

Scenario 2:

1. Log in to the instance.
2. Configure the Now Document component.
3. Navigate to SOW.
4. Open any existing incident.
5. Create a document through the Document component.
6. Select secondary actions, such as Track Versions.
7. Upload any attachment to create a version.

Expected behavior: Version attachment size appears in the component.

Actual behavior: Version attachment size is not appearing.

1. Disable tiered caching.
2. Call new sn_db.GraphMetadata(''graphName'').get().

Expected behavior: The tiered cache with GraphCacheableJSONString isn't used.

Actual behavior: The GraphCacheableJSONString wrapper is used even though the value is in a regular cache.

1. Create a view with an explicit set of fields from a table.
2. Run extractTable.

Observe the value for one of the fields that wasn't included in the view.

Migrate an instance to RaptorDB.

Expected behavior: The max length of the archive table dictionary length entry is mismatched with the actual SQL length.

Actual behavior: The max length of the archive table dictionary length entry matches the actual SQL length.

1. Create a FAILOVER request.
2. Attempt to slowdown the new PRI promotion by 60 seconds.

Notice that glide side considers this as operation timed-out, and does not compute any new topology or detects the next failover.

1. Create a sys_meta_graph record with two nodes added.
2. Create an edge between these two nodes.
3. Try to select the two nodes as source and target node.

Observe that the nodes can't be selected from the UI or directly imported from the attachment.

1. Provision an anowassist instance with GenAI set up and platform 10.0.3 version and KG 6.0.6 installed.
2. Perform any transaction that invokes KG.

Observe the prompt and token count.

Attempt to query an SN table with Trino.

Expected behavior: By default, the user should have access if they have read access to the table.

Actual behavior: The user must have specific data_fabric access granted to that table to run the query.

1. Create a DB view between task_sla and incident, and DB view table records with prefix with mixed case (for example, the prefix 'inC' for incident).
2. Have the where clause as 'task_sla.task = inC.sys_id'.

Notice that the execution errors out.

1. Navigate to the Data Product module.
2. Create or open an existing data product.
3. Attempt to edit the data product.

Observe that the asset IRI is not being captured/stored, and that the edit operation cannot proceed or fails due to the missing asset IRI.

1. Install the com.snc.pa.mlb and com.snc.pa.premium plugins.
2. Navigate to Data snapshots.
3. Create a new DS source with Data frequency as 'All Activity'.
4. Add a fact table.
5. Add supported fields in the fields section, such as assigned_to.
6. Navigate to pa_cdc_breakdown_hierarchy.
7. Add Manager Hierarchy as a record.
8. Ensure the scheduled jobs have run and scores are collected in pa_cdc_fact table and pa_cdc_sysuser table for the breakdown hierarchy.
9. Navigate to Automated Indicators - Data Snapshots.
10. Create a new DS indicator by selecting the source created in step 2.
11. Choose the standard calendar and daily frequency.
12. Choose the 'Aggregate' as 'Count'.
13. Save and submit the form.
14. Navigate to Dashboards.
15. Add any new visualization with the source created above with DB view as facts table.
16. Add a filter on the dashboard with the breakdown hierarchy.

    Observe the scores.

17. Later remove the applied breakdown hierarchy.

Expected behavior: When all the filters are removed, the hierarchy ID is removed, but on the UI side the hierarchy toggle should toggle off.

Actual behavior: When all the filters are removed, the hierarchy ID is removed, but on the UI side the hierarchy toggle is not toggling off.

1. Create an automated indicator with some combination of fields, like Choice, Boolean and Reference fields.
2. Run the data collection jobs to enable data for the created indicator (if not available already).
3. Create a heatmap visualization and pivot table.
4. Add them to created indicator.
5. In 'group by', select any Reference fields (for example, Assigned_to).
6. Add a filter to the groupby column configured in step 5.
7. Select a reference record for which the score is available from the filter.

   Observe the scores for that record on both visualizations.

8. Remove the previously selected record.
9. Add a record which doesn't have any scores.

Expected behavior: It should show 'No data available' since the multivis API returns no scores.

Actual behavior: The pivot table shows an empty matrix and the heatmap shows previously cached data.

1. Provision an instance with com.snc.pa.mlb and com.snc.pa.premium installed.
2. Navigate to data snapshots formula indicator.
3. Create an indicator with any formula.

Observe that a TableDescriptor exception is thrown in the sys log table.

1. Enable DSBs.
2. Do not restart the node controller.
3. Create a sandbox.
4. Run the script in the controller node.
5. Check sys_dsb_message.

Notice no message was created because the listener didn't run.

1. Create a sandbox.
2. Switch to a sandbox_user account.

Observe that the sandboxes list is empty, but allocated sandboxes shows '1'.

Use the query: SELECT number, priority FROM incident WHERE priority NOT BETWEEN 2 AND 4 ORDER BY priority, number.

Expected behavior: It returns incidents where priority is outside the range 2-4, such as 'priority = 1' or 'priority >= 5'.

Actual behavior: Returns incidents where priority is inside the range 2-4 because the 'NOT' is dropped and the condition becomes priority 'BETWEEN 2 AND 4'.

Use the query: SELECT CASE priority WHEN 1 THEN 'Critical' WHEN 2 THEN 'High' WHEN 3 THEN 'Medium' ELSE 'Low' END AS priority_label, number FROM incident ORDER BY 1, 2.

Expected behavior: It returns each incident's number with a human-readable priority label derived from the simple 'CASE' expression.

Actual behavior: The execution fails with the exception, 'Switch statements in case expressions are not supported.'

Refer to the listed KB article for details.

Refer to the listed KB article for details.

1. Initiate the Discovery process.
2. Trigger the translation log functionality during Discovery.

Observe that an exception is thrown, and the Discovery process does not complete due to the exception.

Refer to the listed KB article for details.

1. Log in as an admin user.
2. Type sys_properties.list.
3. Search for the property glide_encryption.set_value_support_cle.disabled.

Expected behavior: The admin user cannot set the property to 'true'.

Actual behavior: The admin user can set the property to 'true'.

1. Install NAVA.
2. Create new connector for AWS.
3. Don't index anything.
4. Run the script.

Notice the error in background scripts.

1. Navigate to any instance.
2. Log in as an admin.
3. Open any system properties UI page.
4. Attempt to toggle any checkbox.

Expected behavior: Users should be able to turn on or off checkboxes on properties pages to modify system configurations.

Actual behavior: Checkboxes on UI properties pages are non-functional and can't be toggled.

Scenario 1:

Attempt to query large datasets using ODBC.

Scenario 2:

To reproduce using only SOAP, increase the max limit and query 30k+ records in a single request.

1. Navigate to Service Operations Workspace.
2. Select Create Interaction.
3. Fill in the required fields.
4. Save the Interaction.

Notice that an error banner is displayed stating insufficient access for query_range operation on sys_user.email.

1. Log in as user with the connection_admin role.
2. Navigate to WDF connect Hub from navigator.
3. Select New > System.

Expected behavior: The user should be able to create new a system.

Actual behavior: The user is unable to create a new system.

1. Navigate to Service Portal Workspace > EAP.
2. Select any team backlog.
3. Select Personalize columns in the header.
4. Select any columns and apply it.

Notice the new columns are not added to the backlog presentational list, and when selecting Backlog personalize panel, notice there is no illustration is present.

1. Provision an instance with multiple Clotho servers.
2. Run the Test Connection utility from the Metricbase Configuration page.
3. Change one of the fields in any one Clotho configuration to an invalid value. For example, provide an invalid username or give an invalid port number for the URL.
4. Note down the original value.
5. Run the Test Connection utility again.

   Notice that it returns true, when it should fail since one of the endpoints is invalid.

6. Change all configurations to an invalid one.

   Notice the Test Connection test now fails as expected.

7. Restore all endpoints to their correct values.
8. Run Test Connection again.

Notice that it passes now.

1. Create a Boolean Data Type metric.
2. Run the script in scripts background.

Expected behavior: Valid query result.

Actual behavior: An error occurs, 'Script execution error: Script Identifier: null.null.script, Error Description: com.snc.clotho.ClothoException: com.glide.db.glideSQLException: Element doesn't exist. Table: mb_dex_installed_app_metrics col: false.'

1. Log in to the agent app.
2. Download an offline cache.
3. Go offline.
4. Create a Work order task > Incidental.
5. Open the incidental.
6. Add activity stream attachments.
7. Sync.
8. Go online.
9. Go back offline.
10. Load the Work order task > > Incidentallist again.

    Observe the error 'Could not find application content in offline data'.

Expected behavior: The incidental list loads offline and displays the created incidental with activity stream entries.

Actual behavior: The offline-online-offline incidental list doesn't load after syncing records that were created offline.

Create a record with an attachment on a table configured in glide.platform_mm_service.supported_tables.

Observe the results in the sys_mm_result table , and the error message in the 'Error message' column.

Refer to the listed KB article for details.

1. Open an instance.
2. Navigate to any summarizable incident record.
3. In the Now Assist sidebar, start a new chat.
4. Enter, 'Summarize this incident.'

Expected behavior: It is in a well-formatted summary.

Actual behavior: The bulleted item text appears on separate line from bullets.

1. Open an instance.
2. Open Now Assist Admin > Finance & Supply Chain > Sourcing & procurement operations.

   Notice that the sentiment analysis skill is hidden here.

3. Open background scripts.
4. Run the code to execute the sentiment analysis skill.

Notice that the record sentiment analysis invoked.

1. Open a list of ACL roles.
2. Apply the filters 'Application is OCS'and 'ACL.application is global'.

Expected behavior: No records appear.

Actual behavior: 8 records appear.

1. Navigate to the background scripts execution page.
2. Run a script to create a formula indicator using the automated indicator.
3. Check whether a formula indicator is created.

Expected behavior: The user can create the formula indicator without any errors when valid data is passed.

Actual behavior: The error 'Cannot invoke 'java.util.Map.containsKey(Object)' because 'nameToSysIdMap' is null' is returned.

Refer to the listed KB article for details.

1. Open Platform Analytics Workspace.
2. Open library.
3. Select Indicators.
4. Select an indicator.

Observe that the indicator opens in a new page. The kp-details page doesn't have an icon next to the title that navigates back to the library page.

Run GetMobileVisualizationIT#verifyAsNoRoleUser.

Expected behavior: The API returns properly formatted JSON with error code.

Actual behavior: The API returns an invalid format.

1. Set the system property com.glide.par.unified_analytics.enabled to false.
2. Navigate to the CoreUI dashboard overview page: $pa_dashboards_overview.do.

The following info banner is displayed: 'If you can't find the dashboard you're looking for, try the Platform Analytics library. Visit Platform Analytics experience.'

1. Create CoreUI dashboard (pa_dashboards).
2. Add Dynamic content block to it.
3. Set 'com.glide.par.coreui_single_migration.enabled' system property to 'false.'

Expected behavior: The info message should be hidden

Actual behavior: The info message is shown.

1. Set 'com.glide.par.unified_analytics.enabled' to 'false'.
2. Navigate to Migration Center.
3. Perform bulk migration.
4. Activate all content.
5. Check the unified property.

Expected behavior: Unified property is set to 'true'.

Actual behavior: Unified property remains false.

1. Create a core UI dashboard.
2. Add a static content block.
3. Add some contents within them, such as an embedded URL.
4. Select the Migrate to Next Experience button to migrate the dashboard to Next experience.

Notice that in the migrated Next Experience dashboard, the rich text has HTML tags in them.

1. Create a Playbook with launch properties.
2. Activate it.
3. View it in the playbook workspace demo.
4. Return to the playbook.
5. Modify the launch properties, such as title description.
6. Reactivate it.
7. Return to the workspace.
8. Refresh it.

Notice the record generator/launcher UI step carries stale/outdated information.

1. Navigate to a playbook with a custom layout type.
2. Once the record generator is loaded, trigger the record by selecting Continue.

Expected behavior: The playbook loads properly.

Actual behavior: The page shows 'There is no playbooks available' briefly.

1. Install the Process Automation Experience Demo plugin with demo data.
2. Navigate to /sys_playbook_experience_record_generator_list.do.

Expected behavior: In the list and on the record, all the records that have 'Show Create Record Form' as 'true' if a form view is selected.

Actual behavior: All the records in 'Show Create Record Form' are false in the list.

1. Open a Zurich base instance.
2. Configure a record generator for any form, such as incident.
3. Add a field decorator for a field on that form by navigating to All > Field decorator.
   1. Set the table to 'Incident'.
   2. Set the type to 'Client script'.
   3. Have the script console.log something.
   4. Enable this for all configurable workspaces.
4. Navigate to a workspace.
5. Create a new record to see the record generator.
6. Select the Field decorator within the form of the record generator.

Expected behavior: There is only one log.

Actual behavior: In the console, it is logged twice.

1. Navigate to Configurable Workspace > Lists > AGR Connections > All.
2. Create a record with subcategory 'WebEDI'.
3. Proceed with Playbook.
4. When asked for 'Fast Follower', select True.
5. Proceed with Playbook until 'Packaging Data Exchange' (lane 7) is reached.
6. Perform the complete Playbook restart.
7. Proceed with Playbook to 'Validate Connection Type' (activity 1.4) activity.
8. Change the subcategory to 'ClassicEDI'.
9. When asked for Fast Follower, select False and proceed.
10. Proceed with Playbook until 'Testing' (lane 9) is reached.
11. Perform the complete Playbook restart again.
12. Proceed with Playbook to 'Validate Connection Type' activity.
13. Change the subcategory to 'WebEDI'.13. When asked for Fast Follower, select False and proceed.

    Observe that the 'Fast follower' phase is initiated even if the fast follower is not marked, which isn't correct. Also, observe that even if the subcategory is 'WebEDI' now, the phases / activities for 'ClassicEDI' are still initiated, which isn't correct.

Expected behavior: If fast follower is set to true, then WebEDI and ClassicEDI don't appear on the playbook. If fast follower is set to false, then WebEDI or ClassicEDI appear on the playbook.

Actual behavior: If fast follower is set to true, WebEDI and ClassicEDI appear on the playbook. If fast follower is set to false, then fast follower, WebEDI, and ClassicEDI appear on the playbook.

Create a new playbook.

Notice that 'Is On-Demand Playbook' is present on the 'Create new playbook' page.

1. Create a finding definition.
2. Create an OR condition.
3. Give step criteria (not cross-step criteria) to one or more of the OR conditions.
4. Mine the finding.

Expected behavior: It matches the correct number of records which qualify for the step criteria.

Actual behavior: It matches more records than expected and doesn't honor the step criteria.

Navigate to Process Mining > sn_icu > sn_gaf NAFC.

Notice that a true-up install is blocked due to a missing sn_gaf dependency.

Update the instance.

Notice that the inbound status of the RPS connection moves to an error state with following error, 'The current operation ended in state: ERROR. Detail: Error: Cannot find function map in object .,Detail: Cannot find function map in object. Adding 'ih_sync_inbound_queue_record' in attachments.'

1. Create time limited role window for 'admin' role for future start and end time, assign it to abel.tuter.
2. Log in as abel.tuter.

Even though all future time limited roles are not needed now, it will load in heap memory as a result of below PR.

1. Ensure there are multiple requests raised in SP.
2. Launch a base instance.
3. Navigate to Request on the header menu and activate it.

   Notice that multiple records will be displayed.

4. Choose any request.
5. Open the Request summary.
6. Navigate to Search catalog.

   Notice that menu items are displayed.

7. Run 'Evinced Flow Analyzer' and AXE devtool.

   Observe the issue.

Expected behavior: The ARIA attribute is not allowed as seen in 'aria-selected='false'' and an element's role supports its ARIA attributes.

Actual behavior: Elements only use supported ARIA attributes, as seen in the element location: sn-search-combobox,sn-search-combobox-desktop,.-search-popover__item--is-active.

1. Open a Zurich instance with multiple nodes.
2. Upgrade the instance from Zurich to Australia RP2.
3. Run a quick Discovery or discover a few IPs.

Notice that the Shazzam probe creation or Shazzam sensors processing has an error. The Shazzam probe isn't created with a name (likely skipping some business rules), and Shazzam sensor processing doesn't create the further probes in the chain. This results in discovery not running effectively.

1. Configure dcg-cc to store a password2-type field in the connection.extended attributes for a collection.
2. Deploy the app to glide.
3. Open wdf-meta/metadata-collector.
4. Configure a collector.
5. Select Run.
6. Set a breakpoint in the KOS SPI class 'AbstractKosCollectorProvide'.

   Notice that an encrypted string for the password, encrypted with a glide-specific key, which the collector doesn't have access to.

7. Configure dcg-cc to store an AWS access and secret key in the aws_credentials table.
8. Open wdf-meta/metadata-collector.
9. Configure a collector that requires AWS credentials.
10. Select Run.
11. Set a breakpoint in the KOS SPI class 'AbstractKosCollectorProvider'.

Notice that the AWS secret key is missing, and that it isn't on the list of the six Password fields that work.

1. Create a PPN and two software models with details matching that PPN's DMAP.
2. Import an entitlement with that PPN.

   Observe that an entitlement import error is generated with the reason 'Multiple software models found for the Publisher Part number. Please choose a software model.'

Expected behavior: There is handling for this situation, either preventing duplicate software models from being created, picking one of the duplicates during import or after selecting the Import button, or allowing users to select a software model without needing to clear the PPN field.

Actual behavior: Selecting Import just reloads the page without automatically selecting a software model, and a software model can't be selected from the field without clearing PPN.

1. Create a table with a very long table name, such as u_very_long_table_name_abcdefghijklmnopqrstuvwxyz.
2. Send a rest request to Trino Connector API /api/now/integration/trino/query/sql?sql_type=physical&connector_type=loopback with body containing the following: SQL query: SELECT * FROM .

Expected behavior: The query returns a response with no records since the table doesn't contain any data.

Actual behavior: The SqlParser throws an exception, 'Invalid table name.'

Install the 'ETL Consumer Kafka' plugin.

Observe that 'Managed Hermes' is installed.

1. Make a daisy chain of discovery schedules to trigger one after another.
2. Set 'Even if canceled' to 'true'.
3. Run discovery and cancel it.

Notice that even though the next discovery should be triggered, it does not always happen.

1. Create a file type data source with the retrieval method SCP.
2. Make a connection where the protocol version is longer than the default 512 characters.

Notice that it takes the default protocol version size because there are no parameters being set to alter the default configuration of the SSHEngine/SSHConfig from the glideSSHSessionPool.

Open a syslog_transaction record in form view.

Observe that the http_response_code field may be editable.

1. Open any incident record in the instance.
2. Navigate to System Diagnostics > Session Debug > Enable All.

Observe the error in the localhost log, users notice the warning called many times: 'DBMacro WARNING *** WARNING *** Macro missing: sn_wwna_nacm_component'.

In on-load client script, add the line: 'g_form.addModerateMessage('moderate msg')'.

Expected behavior: A purple color should be displayed for alerts.

Actual behavior: It displays an AI color.

Refer to the listed KB article for details.

1. Install the GenAI Q4 feature or upgrade an existing instance.
2. Ensure the plugin com.glide.ai_record_activity is installed.

Observe the system logs or error output about an error getting a record for sys_ai_record_activity: java.lang.NullPointerException.

1. Install NVDA screen reader.
2. Open an instance.
3. Wait for the timeout pop-up 'Extend Your Session' to appear (timeout is update 'glide.ui.session_timeout' in system property).

Observe that the screen reader doesn't announce the status message 'Extend Your Session'.

1. Navigate to a configurable workspace, such as Service Operations Workspace.
2. Open at least two records.
3. In the top level navigation tabs, hover over a deselected record tab.
4. Note that a popover appears with a short summary of key fields for the record, such as Short description, Priority, and State (varies by table).
5. Attempt to navigate record tabs with the screen reader enabled.

Expected behavior: When a tab for a record has focus, the preview popover also appears and remains visible. Screen reader users should hear the details in the preview popover announced.

Actual behavior: When the user navigates through the tabs, screen reader users report confusion because a record number isn't enough detail for many to remember which tab is which, and they aren't aware they are missing the preview popover details.

1. Navigate to Now Assist panel.
2. Run alert analysis.

Notice that the response contains HTML tags.

1. Ensure Citation can be selected in the Synthesized Results.
2. Update the output type.
3. Track the previous clicks in sys_cy_analytics.
4. Write back the 'state' of the citation clicked/auto-started to the 'Output' type column for completed asset tracking.
5. Ensure citation/asset selection in Virtual Agent writes the correct deflection type, such as Catalog ≠Synthesized.
6. Update the deflection log to filter out small talk to avoid unnecessary records.

Observe that for agentic execution, the ending state is written back to the deflection log.

1. Attempt to have a regular NLU conversation.
2. Ensure it goes through a search flow.

Expected behavior: Flow goes through and the user receives results.

Actual behavior: Flow errors out and goes to the fallback topic. When checking the syslog, the error log 'Error parsing additional context: JSONObject['conversation'] not found' is seen.

1. Change the language to any language, such as French.
2. Navigate to /esc.
3. Trigger the 'Hello' message.

Notice the untranslated string.

1. Setup NAVA Enhanced chat without full page search on Service portal (SP).
2. Use a search term on SP which provides a skill execution option, such as 'notification'.
3. Select the Skill execution option from the Genius results.

Notice the greeting.

1. Set up NAVA with Enhanced Chat.
2. Start a conversation in VA.
3. Check the virtual_agent flag on an interaction.

Invoke the startVoiceInteraction voice API to create an interaction.

Expected behavior: The API creates a new interaction every time it is invoked.

Actual behavior: The API reuses the interaction if it's active.

1. Select NAP.
2. Select Chat history.

Notice that all the closed chats have the same name.

1. Ensure 'sn_nowassist_va.synthesized_response.shorten_response.disabled' is set to 'true' so that the Show More button is hidden for the synthesized response.
2. Ensure streaming is on.

Expected behavior: On setting the property to 'true', Show More is hidden even while streaming.

Actual behavior: When a long response shows up for the synthesized response, Show More is still shown during streaming and gets hidden after streaming is done.

1. Change the user language to anything other than English.
2. In NLU mode, end the conversation.

Expected behavior: The closing conversation message is translated to the user language.

Actual behavior: The 'hi' contextual action isn't translated to the user language.

1. Start a topic execution, such as 'Order stationary' (which has a couple of questions to ask to the user).
2. When the tool execution starts and the first question is asked to the user, give the reply, 'Exit immediately.'

Notice that the conversation gets stuck, and no incoming payload is sent to AO.

1. Choose an agent, such as 'Order fruit flavored chocolate.
2. Enter an utterance, such as 'order'.

Notice that the execution is stuck and the input returns empty, leading the execution to be stuck.

1. Open the Menu items from the branding.
2. Add a long link.

Notice that the width of the window increases beyond the chat window, and the label is shown in plaint text and the link shows.

1. Create a Zurich instance.
2. Set up NAVA.
3. Set up DTAC.
4. Start a conversation between a requester and agent.
5. Make sure the requester is in a non-English language and the agent is in English.

Observe that dynamic translation for messages doesn't work when the agent sends messages to the requester. It throws NPE.

1. Provision an instance with the latest Google Chat plugin (3.0.0) installed.
2. Navigate to CI Admin Settings page for Channels and select Google Chat > Integrate with Now Virtual Agent.

Notice that Admin is redirected to an error page.

1. Enable localization.
2. Start a conversation in NAVA using a non-English language

Expected behavior: Agent is executed successfully.

Actual behavior: Agent fails to execute because the agent name lookup in AIA always uses the English (untranslated) name for comparison, causing a mismatch when a translated name is returned by the Unified Planner.

1. Log in to a Washington DC instance.
2. Navigate to sys_property - com.glide.cs.general.multi_file_size_exceed_msg.
3. Modify the value.
4. Clear the cache.
5. Create a virtual agent topic within designer.
6. Add a 'File Picker' component.
7. Test it by adding a file that's more than 10MB.

Observe that the following message is displayed, even if the value within com.glide.cs.general.multi_file_size_exceed_msg is modified: 'Looks like that file was too big to upload. 10 MB is the max.'

1. Start a new chat.
2. Give some input.
3. Start another chat before the response comes in.
4. Give a new input in the new chat.

Notice the response from the previous chat sometimes show up in the new chat, and when refreshing the page, it's all in the same conversation, and the new input entered is merged in the previous conversation.

1. Log in with admin access.
2. Navigate to sp_config page.
3. Select Designer.
4. Add a page.
5. Add a container.
6. Add the Portal Banner Carousel widget.

   Verify only one widget was added on the Service Portal designer based on the page carousel.

7. Verify the widget works when opened in the new page.
8. Add another widget (simple list widget) to see if it's properly added.
9. Add the following variables in Coral theme:
   • now-dropdown-list--background-color-focus
   • now-assist-selfservice_FAB_icon
   • now-dropdown-list--background-color.

Notice that they are displayed on the Network tab when the page loads.

1. Create a topic in the designer with a text node with an response message containing a ` (backtick) character.
2. Test the topic.

   Notice the response shows unintended HTML.

Expected behavior: Parsing is broken and links are highlighted.

Actual behavior: The HTML output is broken.

1. Log in to an instance.
2. Open NAP.
3. Enter, 'What is spam' followed by 'Thank you.'

Expected behavior: The 'Thank you' text disappears after the message is sent.

Actual behavior: The 'Thank you' text says in the chat even after sending and receiving response. It is also observed that other prompts like 'What is spam' appear in the chat until a response gets generated.

Refer to the listed KB article for details.

1. Open a Service Operations Workspace (SOW) incident record.
2. Launch contextual NAP by setting switchContextConversation on AIEX launcher.
3. Pick a non-active conversation under the 'Incident' tab in the NAP conversation picker.

   Notice that 'Start a new chat' shows at bottom.

4. Select a conversation.

Notice that the conversation opened doesn't get mapped to a record.

1. Impersonate a user who doesn't have the Walk-Up manager role.
2. Navigate to the Walk-up portal to check in.

Notice that the image will not appear on the page.

1. Log in to ServiceNow.
2. Hit Word doc APIs with the wrong URL.

Observe that the fallback doesn't happen in a 404 case.

1. Make changes to the content control fields with 'Track Changes' on.

   Observe that the selected paragraph should not have any styling.

2. Attempt to replace the value.

Notice that it will throw an error.

1. Create a glide table with >30 characters.
2. Create a WDF table with a column that references a column in the glide table.
3. Open the WDF table and include the reference column in the list view.

An error displays on the page.