Australia Patch 1

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.

1. 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.

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. 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.

1. Select Update Hierarchies.
2. Refresh the page.

Notice that the order of capabilities changed randomly.

1. Delete the current sub-capabilities.
2. 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.

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. Open an HR case.
2. Upload an attachment.

Observe that attachment summarization is working fine.

1. Select Transfer case from the side menu.

Observe that modal opens.

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

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

1. 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. Navigate to All > Change > Create new.
2. Select More actions.

Observe that Create new template is enabled.

1. 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. 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.

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. 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.

1. 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.

1. Remove the previously selected record.
2. 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. 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. 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.

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

Notice that the sentiment analysis skill is hidden here.

1. Open background scripts.
2. Run the code to execute the sentiment analysis skill.

Notice that the record sentiment analysis invoked.

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.

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. 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.

Navigate to Process Mining > sn_icu > sn_gaf NAFC.

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

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.

1. Choose any request.
2. Open the Request summary.
3. Navigate to Search catalog.

Notice that menu items are displayed.

1. 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. 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.

1. Configure dcg-cc to store an AWS access and secret key in the aws_credentials table.
2. Open wdf-meta/metadata-collector.
3. Configure a collector that requires AWS credentials.
4. Select Run.
5. 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.

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'.

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. 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. 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. 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. 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. 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. 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.

1. Verify the widget works when opened in the new page.
2. Add another widget (simple list widget) to see if it's properly added.
3. Add the following variables in Coral theme:
4. now-dropdown-list--background-color-focus
5. now-assist-selfservice_FAB_icon
6. now-dropdown-list--background-color.

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

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.