Build better products with our product team.
We will improve search ranking to prioritize certain sources depending on the query type. For example, HR queries may surface Workday sources first, and project-status related queries may surface Jira/Confluence first. This changes helps to improve answer quality by bringing relevant sources upfront and reduce noise from less relevant systems. This update will be for US, CA and EU regions. We will follow up with the remaining regions as a separate roadmap item.
It would be great to have a native connector for Azure DevOps Wiki.A lot of engineering teams use Azure DevOps Wiki to maintain runbooks, onboarding docs, architecture documentation, and other internal knowledge. Having a native connector would make it much easier to surface this content without building custom integrations.Some useful capabilities could include:Automatic sync of wiki pages and updates Support for both Project Wikis and Code Wikis Links back to the original Azure DevOps Wiki pagesThis would make it much easier for teams to find technical documentation and keep their knowledge accessible in one place.
Invoice templates streamline billing, reduce errors, save time, and enhance professionalism for your business.Invoicing is an essential part of every business, but it often goes unnoticed. Fortunately, a wide variety of free invoice templates are available online, making it easier for businesses from all industries to streamline their billing process. Tap the link, to get startedhttps://www.invoicetemple.com#free invoice templates #invoice templates for your business #invoice #pdf invoice template
When handling higher-priority tasks, the session times out and all progress is lost.We would like the ability to save configuration progress temporarily, or for users to manage their own session timeout duration.
Recently ServiceNow Studio has integrated dragging tabs within its studio interface. I”m looking to do the same on Agent Studio when doing development on conversational process, compound action. And I need to preview both tabs simultaneously.
It would be great if the helptext in feedback sharing area could be made customizable. We want to inform our end-users that feedback submitted through it is not anonymous as per surveying best practice. Currently, we don’t have a way to do it.
Idea: Develop an automated testing framework for chatbots that periodically and automatically runs test cases to verify access, functionality, and performance. These tests should be executed by both admin and user roles and triggered following any Moveworks updates or changes.Key Features:Periodic and Automated Testing: Schedule tests to run at regular intervals and automatically after updates. Role-Based Execution: Ensure tests cover both admin and user roles to validate different access levels and functionalities. Comprehensive Coverage: Include tests for access, functionality, and performance to ensure all aspects of the platform are verified. Alert System: Implement an alert mechanism to notify the team immediately if any test case fails, ensuring quick response to potential issues. Custom Flow Validation: Ensure that all custom flows are tested to confirm they are not impacted by code changes.Benefits:Increased Confidence: Provide peace of mind that the platform is functioning correctly after updates. Early Issue Detection: Quickly identify and address issues before they impact users. Efficiency: Automate repetitive testing tasks, freeing up resources for other critical activities.Similar to Automated Test Framework - Now Platform - ServiceNow
I’ve tried the Agent Architect but didn’t have much luck with getting a good answer. My question related to what reasoning level and model I should use to process my payload to avoid deadline errors and it recommended GPT4o which had a harder time processing the information I was sending.On the prompt optimizer I was thinking of something similar to OpenAI’s prompt optimizer but trained for compatibility with your Agent Studio environment and documentation for System Prompts. It would also be useful to have a way to benchmark a prompt to quickly see the output without having to re-trigger another webhook payload. e.g. An option to replay a recent Webhook payload from recent logs.
Please enhance the Unily connector so that content marked as Hidden in Unily is not ingested or used by Moveworks, even if it is published.Current BehaviorContent with isHidden: true is still ingested because the connector filters on isPublished and isTrashed, but does not currently account for the Hidden flag.Why This MattersWe use the Hidden status in Unily to:Temporarily disable content Prepare content for future release Quickly turn features/widgets on or offIngesting Hidden content causes unintended exposure of content that is intentionally suppressed.Expected BehaviorContent marked as Hidden in Unily should be excluded from Moveworks ingestion and usage.
We’ve found that the bot returns all content from published Unily pages. This includes widgets that are hidden to those viewing the page, but available to those editing.Here are two examples of when this can be problematic:When a team is preparing sensitive content for an upcoming announcement, this should only be visible to page editors. Because of this issue, draft information is available to anyone with access to the bot, which is a compliance risk When a team hides a widget from display because it contains outdated information, this still serves in the bot which is problematic and reduces confidence in answers the bot givesWe’ve been informed that Unily has two APIs:The Content API which returns all content on a page (even content that is unpublished) The Search API which only returns published contentOur understanding is that Moveworks uses the Content API. Please could you fix this issue and ensure that only published Unily content is visible in the bot?
Right now there is a bad user experience when installing plugins from the marketplace. When we install plugins that have actions/components that were already built from other templates it says to rename them because they need unique names. When we rename the component in the template it shows as if it’s accepted and allows to install the plugin but then it fails with the same error. The only workaround I found so far is to rename the component already installed, delete and reinstall the template. This is not a great experience because I then have to go back to the first plugin installed and update the components and delete the duplicate(renamed) one. It would be great if there was an option to note that it’s installed already so it doesn’t install it or some other version of that to avoid this.This recently happened with the Outlook Plugins I was installing and some of them have many pieces.
We'll add a new UI language setting that controls the UI (navigation, controls, labels) independent of what language a user types, across Assistant (Web & EmployeeWorks) and Search. Citations will show in the original content language, with an option to translate to the query language.
Updating Basic tier to GPT 5.2. Read more about the model upgrade program here.
Brief Me can now see the pictures, not just read the words. The architecture diagram, the revenue chart, the table someone screenshotted — all searchable now, right alongside the text. Works across PDFs, Word, and PowerPoint.
When installing a new version of the same plugin, either from the marketplace or from a lower production environment, you can now selectively keep previously imported components – reducing duplication & simplifying updates.
Implement a feature that allows customization of the default response displayed when a sensitive question is detected. The current message—"I am sorry that I can't help you."—may not be sufficiently informative or helpful for users dealing with serious inquiries or issues.We recommend enabling the ability to replace this default message with a more meaningful, context-appropriate custom response that can better guide or support users.
Provide a configurable option in Knowledge Studio to exclude specific ServiceNow assignment groups from ticket ingestion and analysis used for knowledge recommendations.Certain assignment groups are managed by third-party vendors who maintain their own external knowledge bases. Ticket activity from these groups should not be treated as internal knowledge gaps.Knowledge Studio currently includes all ticket data, resulting in non-actionable and irrelevant recommendations from vendor-managed queues.Recommended solution: Enable assignment group–level filtering (denylist) to exclude selected groups from:Ticket ingestion Knowledge gap analysis Recommendation generation
As of now, multipart/form-data is not supported in http actions in agent studio. Therefore most of my requests have to be made using the application/x-www-form-urlencoded content type. This results in numerous encoding issues as Moveworks is not natively handling encoding like postman does. Can we get datamapper to support multipart/form-data alongside application/json?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.