Yokohama Patch 2
The Yokohama Patch 2 release contains important problem fixes.
- Yokohama Patch 2 was released on April 4, 2025.
-
- Build date: 04-02-2025_0516
- Build tag: glide-yokohama-12-18-2024__patch2-03-20-2025
For more information about the release cycle, see the ServiceNow Release Cycle.
For a downloadable, sortable version of the fixed problems in this release, click here.
Overview
Yokohama Patch 2 includes 159 problem fixes in various categories. The chart below shows the top 10 problem categories included in this patch.
Changes in Yokohama Patch 2
- Question font sizeEnter the desired font size for the questions in the guided decision tree. Example: 14
- Hide completed guidanceHides the guidance recommended for a case resolution.In other words, the completed guidance in the View my response section of a Decision Tree is not displayed for the agent.Note:This field is visible only when the Guided Decision Experience plugin is installed. You may need to configure the form to add this field.
- Question font sizeThe font size of the questions in the guided decision tree. It reflects in the workspace and service portal.
The font size defined in the parent decision tree is inherited by the child decision tree even though the Question font size for the child decision tree has its own Question font size defined.
You may need to configure the form to add this field. - Select Hide completed guidance to hide the guidance recommended for a case resolution.
- Exploring Instance Data Replication
- You can only create one scheduled replication set in IDR, with only one outbound entry in that set.
- Set up scheduled replication
- You can only create one scheduled replication set, with only one outbound entry in that set.
Notable fixes
The following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
|
User Criteria for Service Catalog PRB1819841 |
Semaphore exhaustion is caused by the getAllUserCriteria function getting called in widgets | When a public page is accessed by a guest user or web crawler, this prompts a call to the getAllUserCriteria API, which causes semaphore exhaustion. | |
|
Playbooks (Family Channel) PRB1839341 |
Update Set with Playbook change failed to install | The invalid preview error, 'Could not find a record in sys_pd_snapshot for column snapshot referenced in this update' occurs when moving changes to related to Playbook via update set from one instance to another. |
Refer to the listed KB article for details. |
|
Flow Engine PRB1825217 |
When applying inline scripting to pass the value in an input of a dynamic template, it's not working, and the field appears empty | When users create a new action from scratch with one input of a dynamic template and apply inline scripting to pass the value to this input in the flow, it doesn't work. |
Refer to the listed KB article for details. |
|
Database Persistence - Data Management PRB1859358 |
The orphan cleaner does not check both the primary and archive tables to determine if a record is an orphan | Orphan cleaner is enabled by setting property 'glide.db.orphan_cleaner.peripheral_tables' to clean records from the peripheral tables sys_attachment, sys_attachment_doc, and sys_audit, sys_journal_field. It only checks if a record exists based on the document ID reference's tablename. When the document ID reference's tablename is not updated after archiving records during archive reparenting, the orphan cleaner deletes non-orphan records. |
Refer to the listed KB article for details. |
|
Standard Change Catalog PRB1856886 |
Value is not populated from the template if a new text area field is added when creating or modifying a standard change proposal |
The template_value field contains 'STARTSWITH' instead of the '=' operator, which doesn't allow the field to be populated with the value when the template is applied to the change request record. |
Refer to the listed KB article for details. |
All other fixes
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
|
Activity Stream PRB1858896 |
Posts generated by Agentic AI or Now Assist should be posted as an 'AI' user vs ServiceNow | This is a product update. | |
|
Advanced Work Assignment PRB1857820 |
Agent Outside Workspaces that use OpenFrame soft phone are set to an 'Offline' presence state within a minute after the agent moves to an available state | If an agent isn't also on a workspace, the presence reverts to 'Offline' within about a minute. Since the agent is using OpenFrame to manage capacity, it shouldn't automatically revert to 'Offline'. The issue occurs after an Xanadu upgrade. | |
|
Advanced Work Assignment PRB1858547 |
Flow Designer interactive mode should be base instance for phone, video, chat, and messaging service channel types |
Expected behavior: The 'new' and other external event subflows that are executed should indicate that they were run in interactive mode. Actual behavior: The subflows are executed using the standard FDIH jobs, not in interactive mode. |
|
|
AI Search PRB1849325 |
thumbnailHeader in the mini Genius Result Card is not translated | This problem occurs in both global and portal search. |
Notice that the thumbnailHeader in the mini Genius Result cards are not tagged with the translation prefix except for 'Catalog'. |
|
AI Search PRB1850218 |
ais_child_table cache is not flushed when glide.ais.disable_kbb property is changed | KBBs (knowledge blocks) should not be indexed as separate document. Instead, they are indexed with the KB document as embedded documents. When only KBB is enabled, the KBB table is removed from the tables. |
Observe that the KBB is indexed as separate documents. |
|
AI Search PRB1851725 |
Typo Handling blocked terms state doesn't change from New to Published when publishing a search profile | Blocked terms are published, and the UI did not change the state from New to Published. |
Observe that the new term still has a New state, the blocked term is actually published, but the UI did not change the state. |
|
AI Search PRB1857237 |
Images aren't returned for Now Assist actions on Service Portal |
Expected behavior: Images should be returned for the Now Assist actions Genius Results. Actual behavior: Notice that the images aren't coming back for Genius Results. |
|
|
AI Search PRB1861957 |
Duplicate migration requests for a model upgradation is allowed for same target version of a model upgrade request | ||
|
AI Search PRB1863971 |
RAGRertirval API throws an error if the searchSource given request is not present | When the user submits a RAGRetrieval API request with a search source that is not part of the search profile or is not an indexed source, RAGRetrievalAPI fails with no search results. | |
|
Application Install Engine PRB1836818 |
A parent application installs successfully despite missing dependencies | A parent application (for example, Generative AI Controller 9.0.1-Snapshot) is installed successfully even though its dependencies (for example, Microsoft Azure AI Speech Spoke) were not installed during the process |
Observe that the parent application still installs, creating a record in the sys_store_app table, but dependencies remain missing. |
|
Appointment Booking PRB1853892 |
When the daily capacity is reached, the appointment booking modal shows a slot for that day, but throws an error upon booking | Even though the capacity definition is set, appointment slots still appear even if the day if fully booked. When a user attempts to book an appointment on a fully booked day, the error 'ErrorAppointment window is no longer available. Please select another appointment' occurs. |
Expected behavior: Since the capacity is already booked for that particular day, slots should not appear. Actual behavior: Slots are visible for that day and upon booking, and the page throws as error 'ErrorAppointment window is no longer available. Please select another appointment'. |
|
Appointment Booking PRB1860174 |
The appointment calendar does not work in Request a replacement catalog | Select appointment is displayed as blank. | |
|
Appointment Booking PRB1860844 |
In Portal, when unified UI and week view is enabled, if a holiday falls in the next week, that holiday isn't considered | When Consider holidays in leadtime is checked in at the service configuration level, the holidays aren't honored properly to recalculate the leadtime. Users are still seeing the slots in the next week. |
|
|
Cache PRB1860082 |
CacheMetricsManager causes a performance bottleneck at high workloads | Enhance the performance of the Cache Metrics API to accommodate a high volume of concurrent requests. | |
|
Calendar Component PRB1837613 |
A robot calendar isn't working on Y trueup instances | On nightly builds, the robot calendar isn't loading and timezones aren't associating with the calendar. |
Expected behavior: The calendar should be loaded to show the schedules of robots. Actual behavior: The calendar doesn't load. |
|
Capacity and Reservations Management PRB1847774 |
There's a performance issue in the capacity console | For Group by demand channel, all territory data is fetched for the expanded demand channel. When adding a customization function for a summary, the event alt text should be labeled but it'd coming as a field name. | |
|
Cloud Provisioning and Governance PRB1852065 |
Stack state is changed toTerminated when deployment fails, and no task is created | The stack status is changed to Terminated instead of Resolving Error. |
Observe that if deployment fails, stack status is changes to Terminated instead of a Resolving ErrorPFA. |
|
CMDB CI Class Manager PRB1845236 |
Update CMDB table descriptions based on current documentation | The CMDB table descriptions are not updated based on current documentation. |
Notice that the descriptions are not updated based on the current CMDB table description documentation on the ServiceNow Documentation site. |
|
Code Signing PRB1857413 |
Signatures created by Signing jobs have the update_name field empty |
Run the Signing job to generate a signature for records. Expected behavior: Generated signatures should populate the update_name field. Actual behavior: The update_name field is empty for a generated signature. This prevents records from Git check-in and the 'Publish to App' repo. |
|
|
Code Signing PRB1857416 |
Signatures created by signing jobs have an empty update_name field | The record field update_name is empty for generated signatures to prevent records from being checked in to git and to be published to the App repo. Generated signatures should populate the 'update_name' field. |
Run a signing job to generate a signature for the record field update_name. |
|
Customer Service Management PRB1855041 |
Unable to create an email draft in an application scope | The sys_email_draft table has table-level access limitation. Only Can Read is allowed in the application scope. |
Observe the email response tool 'Draft Email' returns an error message 'Email draft is failed created'. |
|
Database Persistence - Data Access PRB1857656 |
A Glide function with a substring function may return a 'negative substring length not allowed' error if the arguments are negative | A Glide function with a substring function may return a 'General Data Exception detected by database (ERROR: negative substring length not allowed)' error if the arguments are negative. |
Refer to the listed KB article for details. |
|
Database Persistence - Data Management PRB1844907 |
Orphan Archive Related Records (sys_archive_related) with empty Archive_Map values are not ignored by the archive job | When instance has orphaned archive related records, the archive job does try to find orphan related records, and archives them as a part of the archive run being processed by the archive job. Archive related records should not be created without an archive_map defined, and every archive related record should be linked to an archive rule. |
Expected behavior: The archive job should ignore invalid archive related records, and only linked archive related rules should be picked up and processed. Actual behavior: The archive job is finding and processing orphaned archive related records for all the archive rules the job runs. |
|
Database Persistence - Data Management PRB1850816 |
z_tmp tables should not be eligible for compaction | Compaction is running on z_tmp tables when they should not be. |
Generate a z_tmp table that is eligible for compaction. |
|
Database Persistence - Data Management PRB1854621 |
Archive reparenting issue occurs when sys_attachment is configured as a related record for an archive rule | The table name 'incident' remains instead of being renamed to 'incident_task' after running the archive rule. |
Notice that the table name is still 'incident' instead of 'incident_task'. |
|
Database Persistence - Data Management PRB1855929 |
Investigating sys_attachment records that are not reparented correctly in Vancouver | Reparenting issue for records in sys_attachment in the gateway DB. | |
|
Database Persistence - Data Management PRB1859358 |
The orphan cleaner does not check both the primary and archive tables to determine if a record is an orphan | Orphan cleaner is enabled by setting property 'glide.db.orphan_cleaner.peripheral_tables' to clean records from the peripheral tables sys_attachment, sys_attachment_doc, and sys_audit, sys_journal_field. It only checks if a record exists based on the document ID reference's tablename. When the document ID reference's tablename is not updated after archiving records during archive reparenting, the orphan cleaner deletes non-orphan records. |
Refer to the listed KB article for details. |
|
Data Privacy (Classic) PRB1840597 |
Admins are unable to see the rollback record fields | After installing the data privacy application, security ACLs were installed for the sys_rollback_context table. The user is unable to see anything in the table even though they have admin access. | |
|
Data Privacy (Classic) PRB1850400 |
End user cannot use Privacy APIs to redact sensitive data during chat session | An error in the logs occurs and the message is unable to send, when chat messages should say, 'Message not send as it contains sensitive data'. | |
|
Discovery PRB1860779 |
True-up licensing app | This problem is for true-up licensing. | |
|
Document Intelligence Unified Backend PRB1855732 |
DocIntel is not working properly after being trained | ||
|
Dynamic Translation for Virtual Agent PRB1853153 |
Virtual Agent responses are in English when Dynamic Translations are on | This impacts Brazilian Portuguese, French, German, Italian, Japanese, and Spanish. |
Expected behavior: All chatbot responses, including those for Serial ID item inputs and other user-provided answers, should be entirely in Japanese. Actual behavior: The chatbot responds in English for every input provided by the user, including Serial ID item inputs and any other follow-up responses in the process. |
|
Dynamic Translation PRB1847469 |
A Spanish user runs skills and gets a response in English |
Expected behavior: The user gets the entire response in Spanish. Actual behavior: The user gets a response in English and Spanish. |
|
|
Dynamic Translation PRB1859540 |
Missing functionality for inbound text from Virtual Agent (VA) to bypass DT for an LLM conversation |
Expected behavior: VA shouldn't DT the user utterance before sending to LLM. Actual behavior: VA DTs the user text to English and sends to the LLM, which responds in English. This isn't expected since the user language is different than English. |
|
|
Employee Center Pro PRB1814341 |
The 'Give Feedback' text in Experience Feedback Drawer widget is upside down for the Chinese/Japanese/Korean languages | All the vertical languages are considered and are read from top to bottom. |
Expected behavior: The 'Give feedback' text displays vertically. Actual behavior: The 'Give feedback' text displays upside down. |
|
Event Management PRB1829897 |
Description field of the Event Rule transform tab execute JavaScript code | In cases when the Event has spacial characters, using the marker for those inputs won't work and the regular expression has to be written manually. | |
|
Event Management PRB1852761 |
NullPointerException (NPE) in Impact Calculation after topology change | NPE occurs after performing a topology change in Event Management. |
Observe the following NPE, 'Exception at executeImpactCalculation. Msg: Cannot invoke 'java.lang.Integer.toString()' because 'this.fContributedSeverity' is nulllastImpactCalcDate: nullImpactSyncHandler'. |
|
External Triggers PRB1848664 |
Change the spoke sys_id to the spoke ID in the definition for external triggers telemetry | ||
|
Flow Engine PRB1825217 |
When applying inline scripting to pass the value in an input of a dynamic template, it's not working, and the field appears empty | When users create a new action from scratch with one input of a dynamic template and apply inline scripting to pass the value to this input in the flow, it doesn't work. |
Refer to the listed KB article for details. |
|
Flow Engine PRB1828174 |
Do-In-Parellel branch remains on a 'Waiting' state after MID action | Flow should go to a 'Complete' state after it returns from MID, but it remains in a 'Waiting' state with only one of the parallel branches having been executed. |
Refer to the listed KB article for details. |
|
Flow Engine PRB1865703 |
Support retries for interactive, non-quick flows | This is a product update. | |
|
GRC Platform Plugins PRB1843595 |
The Details field is missing in Attestation Designer after Xanadu upgrade | TheDetails field is missing in the attestation designer after the upgrade to Xanadu from Washington. |
Observe that the Details field is present. |
|
GRC Platform Plugins PRB1854275 |
Risk Assessment Designer doesn't launch or open a saved assessment | The session hangs and causes the browser to time out when using Risk Assessment Designer. |
Notice that it hangs and eventually times out the session. |
|
Health Log Analytics (Family) PRB1846612 |
MID server stops when it fails to format a log message | ||
|
Hermes (Family) PRB1836241 |
Topic sync deactivates topics when the topic is deleted | The topic sync job deactivates a topic when it is known and not in one cluster. |
Notice that the sys_kafka_topic record has 'active' = false. |
|
Hermes (Family) PRB1849037 |
Backport revert of glide.graphql.gliderecord.maxResults.limit | The property ensures the GraphQL engine is not overconsuming resources for GlideRecord_Query requests. | |
|
Hermes (Family) PRB1856357 |
syncTopics sets service incorrectly on non-managed clusters | Topic sync job will attempt to get topic metadata on some clusters and will run into an error. |
Run topic sync job using any non-default cluster. Notice the error, 'Note that the topics will eventually be synced through updateKnownTopicsAndNotify()'. |
|
Hermes (Family) PRB1857188 |
When DISH sends back an empty response for a Hermes Service (e.g, MIF-Hermes) the preexisting hermes_cluster_config records are not cleared | Instances connected that have called the Hermes callback listener and set up the hermes_cluster_config table cannot be removed by returning an empty response to those instances from MIMIR. | |
|
HR Service Delivery PRB1819942 |
HTML tags are seen in the Description(description) field of an HR case | ||
|
Inbound Email Actions PRB1841147 |
Sensitive data redaction problem | This issue impacts inbound email actions even if 'stop processing' is enabled. | |
|
Instance Data Replication (IDR) PRB1829495 |
High turn around time to send scheduled seeding through metadata topic | After schedule seeding data has been processed, the system should not send data to the consumer and block the metadata topic. |
Expected behavior: Once data is processed, the turnaround time should be quick. Actual behavior: The turnaround time is long. |
|
Instance Data Replication (IDR) PRB1829496 |
Retry shows duplicate run log records | When Retry is initiated, the DCT result and run log should not have duplicates. | |
|
Instance Data Replication (IDR) PRB1858358 |
Excessive KMF traffic on some instances | This is a product update. | |
|
Instance Data Replication (IDR) PRB1863650 |
There is a limit to sets and entries | One replication set with one outbound entry can be scheduled for Yokohama. Scheduled seeding should work for five replication sets each with a single outbound entry. | |
|
Integration Hub PRB1839006 |
OpenAPI Step with MID is failing | When following the OpenAPI Step document to create an action to make an API to an OpenAPI Step, a Guice configuration error occurs. |
Refer to the listed KB article for details. |
|
Integration Hub PRB1865702 |
Support Retry policy when using Async HTTP | This is a product update. | |
|
Issue Auto Resolution for Virtual Agent PRB1862157 |
IAR Simulation does not use the correct API | Custom intents are returned when the regular IAR flow is executed. Custom intents are not returned when simulation is used, because the API takes in a list of objects instead of a single object. The simulation feature is using the single prediction instead of the bulk one, so the custom IAR's are not being returned. | |
|
Key Management Framework (KMF) PRB1839570 |
Upgrading to Xanadu causes module keys that are wrapped with a deactivated IKEK to be rekeyed with the active IKEK and then deactivated | This is an issue in KMF that causes module keys that are wrapped with a deactivated IKEK to be rekeyed with the active IKEK and then deactivated. The user is using a specific filter to find the correct module key to use for CLE, based on the sys_id. However, because that key was deactivated, CLE failed. | |
|
Knowledge Article Templates PRB1852356 |
Articles in the 'Published' state are not changed state to 'Pending retirement' when retired | Knowledge Base (KB) articles that have the retire policy set to 'Knowledge - Approval Retire' cannot be changed to the state 'Pending review'. This problem is found in Yokohama. |
Notice that the workflow state has not been updated yet. |
|
Knowledge Management PRB1827639 |
Selecting a knowledge base from 'Explore our Knowledge Bases' in a portal redirects to the wrong URL | A strange URL with incorrect seach results is returned when selecting a knowledge base from /esc?id=kb_home with AI Search enabled on the application 'Knowledge Management - Service Portal' version 1.0.0. | |
|
Knowledge Management PRB1849608 |
Knowledge Management (KM) notifications are unable to be triggered | Email notifications aren't triggered for Knowledge Articles because some KM artifact records in the Knowledge Advance plugin are overridden by the Activity Subscription plugin. This occurs in Xanadu and Yokohama. |
Notice that the notification is not getting triggered for 'KM Subscription: Article published'. |
|
List Administration PRB1866920 |
Support export to Google sheets functionality in UI16 | This is a product enhancement. | |
|
List Controller PRB1826487 |
Record watcher stops working if more than 1000 records exist in the query | Records don't appear on the list if there are more than 1000 records. |
Expected behavior: When a new record is created, it should appear on the list. Actual behavior: The new record doesn't appear because the list contains more than 1000 records. |
|
MID Server PRB1840424 |
MID Server ECCSender thread gives an 'Invalid byte 2 of 4-byte UTF-8 sequence' error, blocking sending of valid ecc_queue inputs to an instance | This is most likely to be seen in LDAP user imports, or Import Set JDBC Data Sources, where large data is involved. Large data is likely to include extended unicode characters such as emojis. For LDAP probes, emojis have been seen in OU/CN group names and user details data. For REST integrations synching incidents, emojis have been seen in comments of cases. They could potentially appear anywhere, for any feature's probe result data. |
Refer to the listed KB article for details. |
|
MID Server PRB1840424 |
MID Server ECCSender thread gives an 'Invalid byte 2 of 4-byte UTF-8 sequence' error, blocking sending of valid ecc_queue inputs to an instance | This is most likely to be seen in LDAP user imports, or Import Set JDBC Data Sources, where large data is involved. Large data is likely to include extended unicode characters such as emojis. For LDAP probes, emojis have been seen in OU/CN group names and user details data. For REST integrations synching incidents, emojis have been seen in comments of cases. They could potentially appear anywhere, for any feature's probe result data. |
Refer to the listed KB article for details. |
|
Mobile Platform PRB1845305 |
Issues with Edit event on Field Service Management mobile | The schedule event can't get a record from context. | |
|
Now Assist Panel PRB1852531 |
The latency feedback messages are cut at the bottom | The problem likely stems from a height issue for the container. |
Expected behavior: The message text is displayed whole in the container. Actual behavior: The bottom part of the messages are cut. |
|
Now Code Editor PRB1813293 |
Editor Keyboard Shortcuts in i18n | Shortcuts are different across different editors. |
Observe that some are not the recommended in an A-Z alphabetical order based on i18n best practices. |
|
Performance Analytics PRB1835575 |
NAM tables access changes | ||
|
Performance Analytics PRB1850078 |
References to deleted tables should be removed | Ensure that all references to deleted tables are removed from the codebase, including fix scripts, ACLs, and any other related configurations. | |
|
Performance Analytics PRB1862995 |
Increase the Raptor Pro limit to 30M from the current 10M on source tables |
Instead of an 'unsupported' message, the user should be able to activate it for up to 30M records. |
|
|
Playbooks (Family Channel) PRB1839341 |
Update Set with Playbook change failed to install | The invalid preview error, 'Could not find a record in sys_pd_snapshot for column snapshot referenced in this update' occurs when moving changes to related to Playbook via update set from one instance to another. |
Refer to the listed KB article for details. |
|
Playbooks (Family Channel) PRB1847073 |
Questionnaire data definition and flow data variable (questions) are missing after duplicating a playbook |
Expected behavior: The questionnaire is duplicated. Actual behavior: The questionnaire isn't duplicated. |
|
|
Playbooks (Family Channel) PRB1857887 |
sys_flow_data_definition is missing sys_update_name in sys_update_xml payload | This PR makes sys_flow_data_definition use FlowDesignerSuppress which blanket returns 'true' for suppressNameAndUpdateName. |
Expected behavior: The payload has non-empty sys_update_name and sys_name and sys_package. Actual behavior: The payload has empty sys_update_name and sys_name and sys_package. |
|
Playbooks (Family Channel) PRB1861572 |
Exporting a playbook between instances results in missing activities, though stages appear | When editing a Playbook (sys_pd_process_definition) on Yokohama, and then exporting update sets or using source control to move the playbook to another instance, the playbook will be missing its activities. Observe that the sys_update_xml itself for the sys_pd_process_definition is missing proper sys_pd_activity elements, resulting in incorrect playbooks when moving them between instances. | |
|
Playbooks (Family Channel) PRB1861824 |
Localized UI messages are not generated on Playbook activation | No translation UI Messages are generated. |
Expected behavior: Translation records (UI Messages) for Playbook label, Stage label and each Activity Label, Activity Description. Actual behavior: No translation UI Messages are generated. |
|
Process Mining PRB1852247 |
Work Notes results shows HTML code in cluster concepts | Work notes are collected from sys_journal_field table which stores results with HTML tags. |
Notice that HTML tags are present in cluster concepts. |
|
Process Mining PRB1860897 |
Allow sample mining on an evaluation project from workbench | Sample mining an evaluation project works from a KPI but not from the workbench. |
Notice that the user receives mining exception. |
|
Process Mining Workspace PRB1832584 |
The 'Top 3 KPIs by # records & opportunities' widget always displays one record even though there are many |
|
|
|
Process Mining Workspace PRB1834072 |
OR conditions don't work in transitions | An error occurrs: 'Exception encountered processing path: /GlidePromin_Query/scheduleModel - Relation between advanced transitions cannot be empty or NONE'. | |
|
Process Mining Workspace PRB1834143 |
Projects have duplicate child tables shown as use cases | This is found with both process configuration and templates. |
Observe that all tables are doubled. |
|
Process Mining Workspace PRB1834213 |
On an archived data table on the 'Scope your analysis' page, activities are grouped by default |
Observe that the fields are grouped automatically. If users add the same field from the platform, they aren't grouped automatically. |
|
|
Process Mining Workspace PRB1834656 |
Freemium RCA and clustering is not being disabled on Summary & Insights with more than 100 records | In some scenarios, an error message occurs, and RCA and clustering are disabled. |
Scenario 1:
Notice the error message, 'RCA, Clustering are disabled for the try-out project version' with the option being disabled. Scenario 2:
|
|
Process Mining Workspace PRB1835539 |
Only users with elevated privileges users can see the Copy as process configuration button in the header in the Process Configuration template |
Observe that process configuration does not exist, and the Process Configuration button in the header is missing. |
|
|
Process Mining Workspace PRB1835680 |
Transition condition on project setup doesn't allow for the process start or end | Attempting to add a transition condition allow for the process start or end. |
|
|
Process Mining Workspace PRB1838225 |
Limit control flow fields to one for Process Configuration Guided Setup | Control fields should be limited to one, but multiple fields can be added. |
Expected behavior:The user can add only one and remove the option to group control flow. Actual behavior: Up to three fields can be added. |
|
Process Mining Workspace PRB1839094 |
Full mining is enabled for a freemium project on the 'Project list' page | No users should be able to edit the evaluation project. No users should be able to delete the evaluation project(s). Users with a Process Mining role (analyst, power or admin) role can copy any project, including an evaluation project(s). The copied project is handled as a regular project and follows regular license check validation. No users should be able to do a full mine on evaluation project(s). The option shouldn't be available on UI16 and project card list | |
|
Process Mining Workspace PRB1842762 |
The Go to process details button is not working in Guided Process Configuration | When the user doesn't complete the Process Prospectives section, they are prompted with the message, 'No recommendations available' when creating a process configuration for a project or entity such as 'incident' after selecting 'Get recommendations'. |
Scenario 1:
Expected behavior: The message, 'No recommendations available' should be displayed. Actual behavior: The message, 'All recommended definitions are already included in the library' is displayed when there are actually no findings added. Scenario 2:
Expected behavior: The message, 'No recommendations available' should be displayed. Actual behavior: The message, 'All recommended fields are already in use in other activity definitions' is displayed. |
|
Process Mining Workspace PRB1848238 |
Transitions freeze when max constrains are set to 0 | The max duration in the constraints set is automatically handled as 0 when not filled in. This results in 0 matched records. Second, the UI freezes when the transition as 0 records, making it impossible to set a max duration field manually. This can also happen when a filter set has a transition with an activity from a previous version, which isn't present in the current version. |
Expected behavior: When the max duration is left empty, the max duration should be set to infinite (so all records longer than the min duration should match). Also, the user should be able to use the transition UI to add/remove fields and constraints. Actual behavior: When applying the transition, zero records match despite some matches. The max duration fields are set to 0 rather than kept empty. Also, when zero records match the condition, the user isn't able to change anything in the transition. |
|
Process Mining Workspace PRB1850566 |
Histograms show odd percentages in the pop-up values |
Observe the percentages in the modal for the values. |
|
|
Process Mining Workspace PRB1857498 |
The Full mining and Deletion option is enabled for evaluation projects on the project list page | Users should not be able to edit the evaluation project except those with a role with elevated privileges. The Edit option in the project card list is still be visible, but users cannot save or add any new configuration in the guided setup for the evaluation project. Users with a Process Mining role (analyst, power or admin) can copy any project, including evaluation projects. However, users without a Process Mining role can sample mine evaluation projects such as KPI Details, Project card list, Guided setup when they shouldn't be able to do a full mine on evaluation projects. |
Expected behavior: The message should be 'Full: 'Generating full model'', 'Sample 'Generating sample model'', or 'Evaluation project(s): 'Generating sample model''. Actual behavior: The mine project (Sample) option shows it is doing a full model when actually a sample model is taking place. |
|
Project Management PRB1864892 |
The Time Constraint field dictionary default value does not work in Project Workspace while creating the Project Task | The default value for the Time Constraint field is set to 'ASAP' irrespective of Default value. |
Observe that the default value for the Time Constraint field is set to 'ASAP' irrespective of Default value. |
|
RPA Hub PRB1848733 |
pickWorkItem component is throwing error when reducing the number of robots running automation in the robot pool | The pickWorkItem component throws the error, 'the object parameter passed does not contain any sys_id attribute'. |
Refer to the listed KB article for details. |
|
RPA Hub PRB1849100 |
Ignore RPA license property default value should be 'True' | The property sn_rpa_fdn.ignore_license_verification should be 'true'. |
Expected behavior: Default value of the property should be 'True'. Actual behavior: Default value of the property should be 'False'. |
|
Security Data Filters PRB1854682 |
Dot walks are not working as expected in Business Rules, ACLs, and UI actions in both condition builder and scripts | ||
|
Seismic Framework PRB1859951 |
ClientInteraction aggregate transactions creates a performance bottleneck | Setting glide.client_metrics. aggregation.enabled=true on a fully loaded system will cause performance to decrease significantly. | |
|
Server-side scripts PRB1836577 |
Hoisting is broken within try blocks in global | Global throws a ReferenceError on referring to _sortGyoBango. This was observed in Xanadu. | |
|
Server-side scripts PRB1847921 |
Fetch is not properly detecting the scope | The user receives an error about a whitelist, but it will say module.parent rather than the current scope name. | |
|
Service Mapping PRB1816925 |
Service Mapping (SM) Discovery state always remains 'Active' if entry points are not reachable | When SM scheduler is run, the Discovery status for SM Discovery and end point status is created. The host is not in CMDB, so the end point status runs 'Host detection'. Host detection creates a new prob with agent_correlator with horizontal Discovery. When host detection is finished, it updates the end point and the state becomes 'Complete'. However, SM Discovery doesn't update, so the business rule was not triggered to set the Discovery status to 'Completed'. |
Notice that the discovery state will always remain 'Active'. |
|
Service Mapping PRB1851972 |
Updating the same last_mark in blob table during recomputation | During recomputation, the blob tables (svc_model_obj_relation for example) are updated with today's date in the last_mark field. The code is using 'date time' instead of the date to update the field. |
Observe the same record updating with the same date. |
|
Service Portal PRB1855070 |
Post-Upgrade to Yokohama EA, an error is caused by the business rule 'Create SP Communication ChannelList' | An error found in the logs after upgrading to Yokohama EA 'Recursive business rule call for 'Create SP Communication ChannelList' on sp_portal'. A number of simple transaction results in this error. | |
|
Software Asset Management PRB1854090 |
Cross product downgrade rights should exclude inactive downgrade relationships | There's no behavior change for the users on recon. This is intended to exclude inactive products in the backend. |
Although the reconciliation result is as expected, it was found that inactive cross products downgrade rights been processed during recon logs, which is incorrect. |
|
Standard Change Catalog PRB1856886 |
Value is not populated from the template if a new text area field is added when creating or modifying a standard change proposal | The template_value field contains 'STARTSWITH' instead of the '=' operator, which doesn't allow the field to be populated with the value when the template is applied to the change request record. |
Refer to the listed KB article for details. |
|
Stream Connect Core PRB1859532 |
Producer Retry job fails to run | ||
|
Survey Management PRB1842390 |
The HR case number is not displayed completely on the survey card on the My surveys page | The HR case number is not displayed completely on the survey card rendered using the 'My surveys' widget on My surveys page. |
Refer to the listed KB article for details. |
|
Survey Management PRB1855459 |
Additional service and service endpoint needed for clotho as part of Digital End-User Experience (DEX) |
Navigate to sys_service and sys_service_endpoint table. Notice the records for this service. |
|
|
Territory Planning PRB1848653 |
Problems on Capacity Console | ||
|
User Criteria for Service Catalog PRB1819841 |
Semaphore exhaustion is caused by the getAllUserCriteria function getting called in widgets | When a public page is accessed by a guest user or web crawler, this prompts a call to the getAllUserCriteria API, which causes semaphore exhaustion. | |
|
UX Framework PRB1833790 |
There's a 'Max Tab Reached' message on Workspace | The user has Next Experience off and has a link in the menu to open the workspace. This issue happens only when a user opens a workspace from the link directly. |
Expected behavior: Opening more than 10 tabs should work. Actual behavior: Opening more than 10 tabs isn't working in workspace after an Xanadu upgrade. Users get the message 'Max Tab Reached: You have reached max number of tabs you can have open at one time. Close tabs in order to open more.' |
|
Virtual Agent Designer Legacy PRB1817185 |
In an LLM-enabled user input, the enforced user prompt isn't translated |
Expected behavior: There should be a prefix 'MSG: May I know your name?'. Actual behavior: There's no prefix 'MSG' for the customer name prompt. |
|
|
Virtual Agent PRB1849287 |
Topic reduction causes some unexpected errors when selecting an action |
Check the topic execution from the skill picker, by clicking from a synthesized response, and on auto launch. |
|
|
Virtual Agent PRB1851004 |
Skill discovery and execution fails with the proxy sys_prop enabled in Yokohama | Discovery and execution fails when the sysprop com.glide.cs.one_extend. auto_proxy_enabled = false. This is enabled by default. |
Observe that discovery fails with a sorry message. |
|
Virtual Agent PRB1852222 |
'Time Out Abandoned Virtual Agent (VA) Conversations' is not respecting the timeout configured for NAP in sys_cs_channel | VA conversations are not closed out according to the timeout configured for NAP. |
Expected behavior: Conversation should be closed after four hours. Actual behavior: Conversation is closed after two hours. |
|
Virtual Agent PRB1855393 |
User KnowledgeGraph data should be applied for search | ||
|
Virtual Agent PRB1857219 |
Skill discovery fails on xselfservice upgraded instance | This is a product update. | |
|
Virtual Agent PRB1857900 |
A deflection log table doesn't set a 'no response' state when AI Search returns 'no answer found' |
Notice that the State field isn't set to 'no response'. |
|
|
Virtual Agent PRB1858954 |
Follow-up after a navigation skill isn't working |
Observe that a processing message keeps loading and no response is displayed. |
|
|
Virtual Agent PRB1859339 |
An attachment icon isn't aligning with the rest of the other icons in the chat box |
Expected behavior: All the icons in the chat box should align. Actual behavior: The attachment icon is slightly above the other icons and doesn't align with the rest. |
|
|
Virtual Agent PRB1866633 |
In APAC data center instances, AI agents are not working even after accepting the Global Routing Consent information message | Global routing is not working even after consenting on the info message for data center instances in the Asia-Pacific region. |
Expected behavior: The AI Orchestrator should be invoked. Actual behavior: Even after accepting the consent, AI agents are not functioning, and the error message occurs: 'Sorry, there was a problem on my side trying to complete this request. Try asking again later'. |
|
Virtual Agent PRB1866635 |
Trail Assists are incorrectly loaded for 6 or more tools triggered from Now Assist Panel (NAP) with skill Discovery | This problem doesn't occur with playground and NAP triggers. |
Expected behavior: Trail Assists should be 50. Actual behavior: Trail Assists are loaded as 25. |
|
Virtual Agent Web Client PRB1861185 |
An animated icon isn't visible in NAVA when enabled |
Expected behavior: An animated icon is visible next to the loading messages. Actual behavior: No icon loads next to loading messages. |
|
|
Workspace App Shells PRB1838088 |
A breadcrumb isn't updating when updating the corresponding record page data | This issue is specific to the master version of Glide. |
Expected behavior: The breadcrumb should reflect the new name. Actual behavior: The breadcrumb isn't updated. |
|
Workspace App Shells PRB1839369 |
SCREEN_STATUS_CHANGED isn't working for a breadcrumb app shell | The functionality for the SCREEN_STATUS_CHANGED event to close a page in breadcrumb app shell workspace is broken. |
Fixes included
Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.