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 a case record in CSM workspace.
2. Apply a template that adds a comment.
3. Clear the comment from the Activity Stream composer and click outside the text area.

   Observe that the form field, 'Additional Comments', and the Activity Stream comments sections are synced.

4. Apply a different template with comments.
5. Repeat step 3.

Expected behavior: 'Additional Comments' and the Activity Stream comments sections are synced.

Actual behavior: The Activity Stream comments section is cleared, but the form field keeps the old value.

1. Have a service channel / queue set up with default maximum agent capacity = 1, and an assignment rule with 'Enable auto-assign work items' checked.
2. Have an 'after' BR on the awa_work_item table that triggers every time the state changes to accepted.

   The BR invokes the sn_awa.Agent CapacityManager .requestWorkload Recalculation() scriptable method, passing the service channel sysID and assigned_to value as arguments.

3. Have a 'before' BR on the document table that triggers every time the assigned_to field changes from empty.

   Notice that this BR adds a delay of ten seconds and simulates the timing delays caused by BRs on the document table of the instance.

4. With an Agent set as 'Away', queue up multiple work items.
5. Set the agent to 'Available'.

Observe that up to three work items are assigned, exceeding the max capacity of the agent which was set to 1.

Prerequisites:

Provision an instance with Workforce Optimization for CSM Configurable Workspace installed (with Demo data).

1. Log in as a user with elevated privileges and navigate to Workforce Optimization for Customer Service > Scheduling > Event Configuration.
2. Open a meeting record and navigate to Evaluate access for an inclusion related list and open the 'Meeting - WFO Agent' record.
3. Enable 'Create', 'Update', and 'Delete' permissions and save the record.
4. Impersonate any Agent.
5. Navigate to CSM/FSM Configurable Workspace > Calendar.
6. From the New button, select Meeting and submit a meeting request.

Expected behavior: The app allows the Agent to create a meeting.

Actual behavior: The app throws 'Failed to create schedule p'.

1. Provision an instance with Now Assist for CSM Nov release (3.0.1) and all dependent plugins installed.
2. Navigate to /csm page
3. Impersonate an Agent and make them available to accept the chat.
4. Initiate a chat from contact.
5. Accept as an Agent from Workspace.

Observe that the summary card on the chat panel has missing iicon.

1. Make sure 'Show Tab Count' is enabled on any Search Application.
2. Set the 'glide.search.logger.enabled' property to true.
3. Perform a search on Portal with a linked Search Application.

Observe that the logs show a query time breakdown.

1. Provision any base instance.
2. Navigate to the portal where AI Search is enabled.
3. In the search bar, type 'General request'.
4. Search for a catalog item using a keyword, then delete or make that catalog item inactive.
5. Search the catalog with same keyword.

Expected behavior: After the catalog item is made inactive or deleted, it shouldn't show in the search results.

Actual behavior: After the catalog item is made inactive or deleted, it still shows in the search results.

Start from a base instance.

First Case:

1. Open Service Portal Default Search Profile.
2. Create and link a new Search Source.
3. Set Indexed Source to the Catalog Item Table.
4. Set Conditions to 'Catalogs contains Technical Catalog'.
5. Search *** in /sp.

Observe that the All tab contains a different number than the 'X results returned for ***'.

Second Case:

1. Create a new KB with knowledge base = Knowledge.
2. Create a new Search Source for Service Portal Default Search Application with filter = 'knowledge_base=knowledge'.
3. Search in sp.

   Observe that the All Tab shows 'Knowledge Base shows IT and Knowledge'.

4. Click Knowledge.

Observe that the document appears, but the All facet tabs show 0.

1. Enable AI search.
2. Upgrade to Track / AI search.

Notice that global search is missing from the list.

1. Create a user with the pa_admin role Navigate to Performance Analytics > Analytics Hub.
2. Open any indicator (for example, the number of open incidents).
3. Open the comment side panel.
4. Create a new comment and click Submit.

Expected behavior: The comment is added into the Analytics hub indicator.

Actual behavior: There is an 'Action not authorized' error.

1. Install SPW.
2. Upgrade the instance to Washington DC.

Notice that the rank config table does not reparent to the application file.

1. Navigate to Service Operation Workspace.
2. Open an incident record.
3. Open the Details tab.
4. Click the magnifying glass for Service reference input.

Observe the following issues when running a query: The default conditions are appended to the query, the Sort By conditions do not persist, and the Name column is sorted in Ascending order.

Refer to the listed KB article for details.

1. Create a new action layout and associate with a table (for example, sn_customerservice_case).
2. Leave Action Config ID blank.
3. Save the layout.
4. Create a new record page in CSM/FSM Configurable Workspaces in UIB (use the standard record page template).
5. Update the table to match the table specified in Step 1 (for example, sn_customerservice_case).
6. In the form controller, update the Action Layout to the layout created in Steps 1-3.
7. Save the page.
8. Open the URL path to check out the page at runtime.

Expected behavior: The page should use the action layout specified in the controller.

Actual behavior: The page is still referencing the CSM 'Case Actions' layout, not the layout the user created and specified.

1. On a Washington DC instance, create a global action by setting 'Enable for all Configurable Experiences' to True.
2. Navigate to any configurable workspace (such as SOW or CSM) and verify that the action shows up on any record (for example, Incident record).
3. Create a new action layout for any table (such as Incident).
4. Navigate to the same record on Step 2.

Expected behavior: Only one global action should show up on the record page.

Actual behavior: A duplicate global action shows up on the record page.

1. Navigate to an instance off track/webux.
2. Create a new UI Action.
3. Navigate to SOW and open any incident record.

Expected behavior: There should be a console warning that says to use the action _name if the Submitted action is changed to the action name (test_name) no error will show.

Actual behavior: Observe an error when the action is clicked. Also, the submit function does not complete, and the form does not save.

1. Configure a IAM Profile based MID server.
2. Navigate to the discovery home page.
3. Add an AWS Master account / Member account.
4. Provide the access role and accessor account.
5. Check the credentials-less discovery box and select the IAM role configured MID server.

Expected behavior: Test account validation should pass.

Actual behavior: Test account validation is failing.

1. Provision an instance with the Discovery Admin Workspace app installed.
2. Execute one of the instance scan suites (Discovery or MID) parts of the tuning advisor.
3. Navigate to the tuning page as Discovery Admin.

Observe most of the data is not visible to the discovery admin. However, as an admin, the data is rendered properly.

1. Configure IBM Netcool connector (or OMi connector etc) which doesn't have isDebug defined in the script used in Connector Definition.

   It fails with error 'isDebug is not defined'.

   If the user clicks Test Connector, it shows, 'Undefined'.

2. Check the XML of the connector instance.

   Notice that the running field shows 'True'.

3. Set the running field to 'False' from background script, which will trigger another ecc_queue.

In the Agent log, notice that the ECC job fails with error: 'isDebug is not defined'.

1. Log in as admin or impersonate as admin.
2. Navigate to flow designer and open a flow that is read-only.
3. Click Deactivate.

Expected behavior: The user is able to deactivate the flow successful.

Actual behavior: A 500 error occurs.

Refer to the listed KB article for details.

Refer to the listed KB article for details.

1. Open a case in Workspace.
2. Make sure glide.ui.form .breakpoints.enable is enabled.
3. Adjust the split pane just around the point where it changes.

Notice that the case details form gets stuck.

1. Provision an instance with sn_hr_agent_ws 3.0.1-rc.2 installed.
2. Create a user and add the case_writer and kb_writer role to users.
3. Open HR Agent Workspace.
4. Click Lists > Knowledge > All articles.
5. Click New.

Notice that only the Article body field is displayed in the new knowledge form.

Refer to the listed KB article for details.

1. Create a JDBC data source for Azure DataBricks DB.
2. Define the connection URL with a username and password.
3. Test a load of 20 records.

Observe an error.

1. Install the Microsoft Dynamics 365 Finance and Operations Spoke.
2. Navigate to the connection aliases and open the 'MicrosoftD365FinAndOps' alias.
3. Be in the Global scope or any scope other than the 'Microsoft Dynamics 365 Finance and Operations Spoke' scope.
4. Click the Create Connection & Credential related link.
5. Fill in the details as prompted in the authentication template.
6. Click Create and Get OAuth Token.

Expected behavior: The OAuth Token retrieval should be successful.

Actual behavior: The OAuth Token retrieval fails. Upon opening the OAuth Application Registry, the Tenant ID in Auth URL, Token URL, Refresh URL, Revoke Token URL and Environment URL in Scopes are not replaced with the user-provided information.

1. Activate IPKI on the instance.
2. Deactivate the IPKI key pair.
3. Repeat Step 1, which will generate a new key pair and IPKI Issuing Certificate

Observe a 'Corrupted instance certificate signing key' error on the instance.

1. Navigate to incident List.
2. Add group by on Assignment Group.

   Observe a total count of 23 assignment groups. Observe the total group count in pagination and number of pages.

3. Navigate to any workspace.
4. Load the same incident list.
5. Add group by on Assignment group.

   Observe a total count of 21 groups with two pages where first page shows 20 groups.

6. Navigate to second page.

Observe the remaining three records, but the total group count shown in the pagination is still 21. There is a difference noticed in the group count between UI16 list and Workspace List when group by is applied. The main issue occurs when the groups are 21 including the 'empty' group, but the pagination does not show the second page, since those groups are counted as 20.

1. On latest instance install pattern plugin with version 1.3.0
2. Configure a IAM instance profile based mid server
3. Navigate to Discovery > Home page and perform a test account.

   Test account should be successful.

4. Navigate to plugins page and upgrade the pattern plugin to 1.8.0
5. Perform the test account again.

Observe that the test account fails with the error, 'Required credential or accessor account and access role name for validating service account.'

1. Click Preferences > Notification > System Notification > New Window > Under System Notification > Any notification > Schedule.
2. Click Advanced Filter and add the condition.
3. Save the record.
4. Reload the page and navigate to the notification.

Expected behavior: Filter information should be visible.

Actual behavior: The use observes a 400 error.

1. Set disableMaxHeight and autoResize to true.
2. Set glide.activity. compose.textarea .autoresize_line_limit (for plain text editor) or glide.activity .compose.html .autoresize_line_limit (for HTML editor) to a large value like 100.
3. Press Enter in the until the text area goes off the bottom of the page.

Notice that when the user is off the page and types, focus is shifted and goes to the top of the compose.

Prerequisite:

Navigate to Preferences and disable 'Put Line Breaks in lists'.

1. Create a highlight for the case list on the Short Description (for example, yellow when the state is New).
2. Open the case lists and set the filter state to 'New'.
3. Hover over the highlighted Short Description.

Notice that two tooltips appear.

1. Install the Japanese language plugin.
2. Open Record Produce: Create Incident (any catalog item should be able to reproduce the issue).
3. Add a new variable with Date/Time type.
4. Open Now Mobile.
5. Log in with Japanese language mode.
6. At the home tag, navigate to a quick link and choose 'Request IT assistance'.
7. Click the calendar icon from the variable in Step 3.

Expected behavior: The calendar should be in Japanese.

Actual behavior: The calendar is in English.

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. Create a Project and add a rate modal.
2. Navigate to Project workspace.
3. Create a task and add a Resource assignment
4. Move task dates.
5. Click the Resource sync dates icon.

Notice that the 'Function instance is not allowed in scope global' error on UI.

Refer to the listed KB article for details.

1. Open any large table's dictionary entry.
2. Click Delete all records.

   Notice that the delete activity is logged in a rollback context.

When the 'Clean Expired Rollback Contexts' job starts to clean this rollback context (possibly after seven days), the issue occurs. The DELETE query can run for a few hours.

1. Enable the Order Guide sequencing plugin.
2. Generate Sequencing for 'New hire' and configure the lanes in the PAD process.
3. Clear the cache by running /cache.do.
4. Search 'New hire' from the Service Catalog module.
5. Order the new hire.
6. Check RITM stages.

Expected behavior: Only stages configured in first lane in the PAD process should be started.

Actual behavior: All stages start immediately.

1. Create a catalog item with following specifications
   1. Variable1 (type: container start, order: 100)
   2. Variable2 (type: checkbox, name: checkbox1, order: 200)
   3. Variable3 (type: checkbox, name: checkbox2, order: 300)
   4. Variable4 (type: container split, order: 400)
   5. Variable5(type: checkbox, name: checkbox3, order: 200)
   6. Variable6 (type: checkbox, name: checkbox4, order: 300)
   7. Variable7: container end
2. Write a catalog UI policy to mark the container start as mandatory.
3. Try the item in catalog conversational request and observe the result.

Expected behavior: As the container is mandatory, the two checkbox containers should also become mandatory. There shouldn't be any option to skip the c1, c2 or c3, c4.

Actual behavior: Mandatory conditions are honored but the skip option is still shown for the c1, c2 and c3, c4 checkbox containers, which is misleading.

1. Configure the SLA Timer component on any UIB / Workspace page.
2. Set the Task sys_id and Configuration sys_id properties of the SLA Timer.
3. Open the page on runtime.

Notice that the SLA Timer doesn't show anything and disappears if there is no matching task_sla found based on the configuration.

1. Create a boolean property 'glide.appsee.consent .allow_impersonated' with value 'True'.
2. Impersonate a user.
3. Open a Service portal page.

Expected behavior: Heartbeats should have start appearing.

Actual behavior: No Heartbeats are visible.

1. Log in to the Latest Vancouver version.
2. Create a custom script include or open any existing script include.
3. Set breakpoints in server side script include.
4. Open Script Debugger.
5. Call the script include from 'Scripts - Background'.

The script runner stops on the first breakpoint, but is not able to step through the code.

1. Invoke the OutputCardDao.getCardGlideRecord() and OutputCardDao.getMessageGlideRecord() methods.
2. Inspect the break point on the CacheManager.get(cacheName, sysId);.

Notice that the cache entry is a glideRecord object.

Refer to the listed KB article for details.

1. Make sure an affected table has enough records to trigger an online alter (5k +)
2. Enable instant alter.
3. Perform an alter operation on an affected table (for example, add a new column).

   Observe that the alter is online and not instant.

4. Alter the table again.

Observe that the second alter is instant.

1. Open any configurable workspace (for example - CSM configurable workspace).
2. Open a case record.
3. Try to attach a file.
4. Rename the attachment name on the pop-up (type quickly).

Expected behavior: Words are typed as expected.

Actual behavior: The cursor jumps to the end of the text.

Install a plugin com.glide.dev-studio.

Expected behavior: Before the fix is Global, notice the log message, 'PluginUpdateManager: Evaluating claims for plugin com.glide.dev-studio since it is global scope'.

Actual behavior: After the fix is Studio, notice the log message, 'Evaluating claims for scoped app com.glide.dev-studio'.

1. Enable Now Assist VA for Teams.
2. Create a Dynamic choice LLM topic.
3. In Now Assist VA Teams mode, start a conversation.
4. Run the Dynamic choice control topic.

Expected behavior: The topic runs and results are returned.

Actual behavior: The topic doesn't return any results and gets stuck.

1. Navigate to VA. Enter 'Apple Standard Laptop'.
2. Choose 'Get started'.

Notice that all options (Lost or Stolen, Replacing an existing laptop, Additional Laptop, My Laptop is Broken) are shown. Some of them should be hidden based on the user profile.