*** title: Release Notes 2024 excerpt: '' deprecated: false hidden: false metadata: title: '' description: '' robots: index next: description: '' --------------- # December 2024 Product Release Notes ## New Releases ### **In-bot file attachment in Slack using Copilot** We’re happy to announce that Slack users can now add attachments to tickets in Slack itself! This is an optional configuration which applies to tickets filed via the Moveworks Copilot. ![](https://files.readme.io/f81adf0d780d1894903363cac67c722b900e8d983ea2aa5ddf32f49343cde5d4-image_31.png) **Relevant Configurations** This feature will require two configuration options: rich ticket filing with attachments enabled, and Slack file attachment enabled. **Prerequisite Slack permissions** Slack attachments require the file input block to be built on the Slack Modal, which requires a few permissions, notably `files:read` , which is used by the bot to construct the modal. `files:read` ONLY grants the Moveworks Bot the ability **to read file attachments that the user sends to the bot, in channels the bot is added to,** and the ability to construct a modal that has file input as a field. `files:read` Does **not** grant the Moveworks bot access to read file from your DM with others or any files that is shared in other channels channel. *These permissions can be enabled directly in the App Manifest page of the bot’s config.* ### **Log Viewer Role for Logs in MyMoveworks** In order to help you audit and limit access to the Moveworks Logs app, we added a new role to the Role & Permissions app in MyMoveworks. By default, users will NOT have this role enabled. **Who does this affect?** This only affects customers with access to Agentic Automation Engine. If you see a Plugins tab in your Creator Studio page then you have access to Agentic Automation Engine. ![](https://files.readme.io/7236d6dec5cef3be0bc23c1cf2b1cdd3a65d5f6c3d44ba40bbed4465b0ba757f-image_32.png) If you had Agentic Automation Engine enabled **before 12/13/2024**, then all of your developers that have access to Creator Studio **will have the role by default.** If you have Agentic Automation Engine enabled **after 12/13/2024**, than all of your developers that have access to Creator Studio **will NOT have the role by defau**lt. **What’s the Role?** The Role is called **Creator Studio Logs Viewer** ![](https://files.readme.io/06b0dd549e6977e9c184b9eb61b83e354c65102516a280228d399a54782ef247-image_33.png) **What does enabling this Role do?** If a user is granted the **Creator Studio Logs Viewer role**, they will be able to see and access the Logs app tile in the MyMoveworks menu. **What is the Logs app?** The Logs app lets you view all of the logs needed to debug Plugins, Compound Actions, and Actions created in the Plugins tab in Creator Studio. ![](https://files.readme.io/3e7179cdda27087acec0197fa103af913cfc8a8153de623052b34c90f1c37cba-image_34.png) **How do I set Roles & Permissions?** You can follow our [Roles & Permissions guide.](/service-management/administration/roles-permissions/overview) ### **Introducing User insights in copilot analytics** We are excited to launch the all-new User insights report. This is a new report launched for Copilot Analytics and provides insights on adoption and copilot usage. ![](https://files.readme.io/a304ef739efa5bbe63421be2d4abd5296b26c7a24a9d4cd338de47182366c50f-image_35.png) * You can now view adoption and engagement on the copilot by each department, and location and identify users who need more enablement on the copilot * By reviewing enabled surfaces, you can now identify surfaces where users are not interacting with the copilot, such as service portals. * By learning the user-preferred languages, you can now understand if new languages need to be enabled in Copilot to drive the adoption of users from a certain demographic Learn more about the report [here](/ai-assistant/ai-assistant/analytics-performance/ai-assistant-insights/user-insights). ### **2 new Quick Start Guides: Employee Communications & Knowledge Studio** We're thrilled to share the release of two new quick start guides designed to make onboarding and learning quick and easy. For each feature, all the steps should take about 2-4 hours in total and can be completed at your own pace. 👉 See the complete Employee Comms Quick Start Guide in Community [here](https://community.moveworks.com/employee-communications-75/employee-communications-quick-start-guide-your-complete-learning-path-1790). 👉 See the complete Knowledge Studio Quick Start Guide in Community [here](https://community.moveworks.com/knowledge-studio-81/knowledge-studio-quick-start-guide-your-complete-learning-path-1788). # November 2024 Product Release Notes ## New Releases ### **Easier access to handoff options in Copilot** This update is to enable users who are looking for handoff to a human to get to **file ticket** or **live agent** more easily, without going to Get Help (i.e. the reference popup). **Background: How handoff works in the Copilot** The Copilot offers a handoff option in chat based on two key factors: 1. Domain or category of the request. 2. The type of handoff (or “item”) that is being requested. For example: *“I need to file a ticket for my VPN issue”* 1. Domain: IT 2. Item: Ticket filing *“Can I talk to an agent? I have a 401k question”* 1. Domain: HR 2. Item: Live agent **Limitation of the current experience** In some cases, the user may ask a question for which the Copilot is unable to predict the domain from the list of domains configured: *“Create a ticket for an issue with the sidewalk outside the office”* * Here, it’s possible that the Copilot might not have a configured domain that can be predicted. *“Create a ticket for an issue”* * Here, the user has not provided any details about the issue, so a domain cannot be predicted. * In this case, the Copilot will prompt the user to offer more details to attempt to get information for the domain prediction, but the user may not offer the details. Similar, in some cases, the user may ask a question where they don’t explicitly mention the way in which they need help: *“I need assistance with an HR question”* * Here, the item is not predicted In both cases, since the Copilot was not able to predict both domain and item, it asked the user to click on Get Help to view more options and make their selection. **Upcoming improvements and user experience** With this update, the Copilot will offer easier access to handoff options even when either domain or item are not predicted. If the **domain is not predicted but the item is predicted with confidence**, the Copilot will provide a list of all available items across different domains: ![](https://files.readme.io/4fd28ace25db1082528253dd91327b16fcf045fbc1caf10bf96725a954400286-image.png) *Current experience* ![](https://files.readme.io/c54eeb0f51d54f49520ea8944b42882b4717742cea9a4ff09e9cb87fc2a82f6c-image.png) *New experience* If the item is not predicted but the domain is predicted, the Copilot will offer a list of the items configured for that domain: ![](https://files.readme.io/fba5cb359f8c32dafe6481134a13717cfa9fffc67dbb9a348057334850713d02-image.png) ![](https://files.readme.io/31a56acdec3ca9ecf8b2a9449e66ae3c768b3ebc554b6fed2b07aa1df592f39a-image.png) Note that if the user does not provide a description of the issue, the Copilot will still ask the user for more details before offering a handoff option: ![](https://files.readme.io/b6ffdd3b5f695defde148ea5b072fe4ef18261bb1350bdd7c5f4c431b9fa0fc4-image.png) In case neither domain nor item could be predicted, the Copilot will ask the user to click on “Get Help”: ![](https://files.readme.io/0b447856617f56d349e2bdbbcc0f3b326a21a9766209449e464f3b08113d1ce0-image.png) Also, note that all handoff options will continue to be available on the reference page, which the user can access via Get Help. ![](https://files.readme.io/b69d90c94f4b456cdb7b86eebd5eb43fc886911a8cd117a2e8b5379d29ce3c40-image.png) We expect that these updates will greatly reduce the effort from users in getting help and will get them to a solution to their issue faster! **Required handoff configuration update (for some customers)** * The required change below applies only to the customers who have multiple ticket filing or live agent options for different domains or categories. * If you do not have this type of configuration, no changes are required. As explained above, when the item is predicted but the domain is not, the Copilot will now present a list of all available types of that item. To enable users to select the most relevant type of file ticket or live agent handoff from the available domains, we will need to update the button labels for each of these from simply “File ticket” or “Live agent” to “File ticket - IT”, “File ticket - HR”, or “Live Agent - IT”, “Live Agent - Real Estate Services”. This will be a small change enables users to more easily identify and access the best handoff option and gives them the control to make the selection. You can use Moveworks Setup to make this change as shown in this example: ![](https://files.readme.io/dca87a7757d5113760f2c810a1ee7e25816a7a335ef98f26f09c191da1545232-image.png) which should be changed to the following with unique values: ![](https://files.readme.io/c00fe07220150fc335fae1809d3a6019a47124f0e78638842ff6aba619f92949-image.png)
### **Simplified support ticket filing for Copilot with conversation IDs** We are introducing an easier way for Moveworks admins and stakeholders to report issues. Previously, you had to rely on screenshots, user IDs and dates of the interaction to share a specific issue with Moveworks Support, which was both time consuming and error-prone. You can now get the conversation ID for any Copilot interaction, for any user - simply by clicking on the ℹ️ emoji in chat. This is a unique ID shared by a small number of interactions that are grouped as a conversation by the Copilot’s topic prediction model. Using the conversation ID makes it simpler to pinpoint specific interactions and share their IDs with Moveworks Support when filing tickets. It will also help reduce the time taken to provide help by eliminating the clarification process that adds multiple back-and-forts between you and the Support team. How to file a ticket with Support: 1. For specific chat interactions for which you have a question, you can now click on the ℹ️ emoji below the bot response to open up the reference page. 2. You will see the Conversation ID on the bottom right of the top section of this page, right above the Citations section, as shown below: ![](https://files.readme.io/a18226a28d423ef2a03822a7a395ef8c58c1ef6c7fc19837164f4f521f06778b-image.png) 3. Click on the conversation ID to select it, and provide it when you file a ticket.\ If you are reporting an issue on another user’s behalf, you may ask them for this conversation ID - this will be available to all users! 4. Proceed to filing your support request. See this [guide](/ai-assistant/getting-started/support/overview#how-to-report-issues) on how to report issues.\ We still want to get your feedback on what part of the experience was unexpected, and what your expected response should have been - so please feel free to add screenshots and comments in addition to the conversation ID. 5. Submit your support request!

### **Small UX change for accessing software within Copilot** We are making a slight experience change to the access software self-service messages. For context, there are 2 types of software access workflows. 1. The software is set up to be automatically provisioned by the bot 2. The software is not set up for auto provision, but the bot serves instructions for user to self-serve. This experience change only applies to the 2nd workflow type. **What is changing?** Before the change, the self-service message is sent to the user directly upon ask: ![](https://files.readme.io/4b8001eeeca78da2595b8c37a09274d7c7d6bb0b76e4568789585cfba481e504-image.png) After the change, a confirmation step is added before the self-service message is shown to the user: ![](https://files.readme.io/419867e54d545bbd4dffe5bcf6cbf95ccec5a12d25c7d93d2525cbe157a97785-image.png) **Why did we make this change?** 1. The biggest unlock is for Copilot analytics. Before, self-serve softwares do not get captured as a successful interaction, which resulted in confusion in our analytics dashboards. With this change, we are able to count self-serve software as a success and capture the impact of the plugin appropriately. 2. We are closely evaluating the impact and friction of this UX change and continue to improve the end user experience. ### **Introducing Permission Change Logs in Moveworks Setup** Permissions change audit logs allow Admins to get a real-time view of roles & permission changes done within their org's instance. With Permissions change audit logs, Admins can: 1. Investigate any unintended revocations of app access for any employee 2. Track and audit any RBAC changes done by specific App Admins or any Moveworks employee. ![](https://files.readme.io/de6a84d1ace1eb5966ccd3db9f58702319812c6e69707cc531adf5e3ab175e01-image.png) **How do I access Permissions Change Logs?** 1. Log in to Moveworks Setup 2. Navigate to Audit Logs in the left navigation menu 3. Select "Permissions Change Logs" from the sub-menu of Audit Logs Learn more about the feature [here](/service-management/moveworks-setup/audit-logs/permissions-change-logs).
### **Re-introducing User Profile View in ingested users within Moveworks Setup** User profile view provides a detailed view into ingested users and their corresponding attributes. The user profile view is an important screen within Moveworks Setup to conduct basic troubleshooting with regards to any bot access related issues for an employee. **How to access User Profile View?** 1. Log in to Moveworks Setup 2. Navigate to User Identity > Ingested User 3. In the "Find User" widget, search for any employee 4. Click on "View Profile" to navigate to the user profile view 5. User profile view can also be accessed by clicking on required user in the All Users table ![](https://files.readme.io/7f3a52c9304326104b0b8cb89d6e78c0678b755cd33260be501c6c008da987d4-0ef35b51-c312-4e8a-9567-6b7e98615ff8.png) **What has changed with the experience?** 1. **User Identity Attributes Table will now surface all Moveworks-standard attributes alongside the organization's custom attributes.** Earlier, only configured attributes of an org were shown in the table. For admins to infer which attribute is configured for their org, they can leverage % coverage column - which indicates the percentage of all users within the organisation for whom this attribute is populated. 0% or closer to 0% value suggests the attribute may not be configured for their organisation. 2. **Source of attributes is no longer available in the table due to engineering limitations.** To support Admins in attributing which attribute is coming from which source, we created this [troubleshooting guide](/service-management/core-platform/user-identity/user-profile-view).
### **Control Access to Publishing Employee Comms Campaigns** Users can now control the list of users who have the ability to publish campaigns within Employee Communications. To provide this access to specific users, simply enter their identifiers, in the Moveworks DSL rule format, within the "Access Control Publish Campaign Enabled" field under Additional Controls in the Notifications Module and save the configuration. ![](https://files.readme.io/920ffa6fb0ad847cb9848920e1bc9d67d2ec5043c35c6b0a1d2faff44863bea1-image.png) This feature ensures that not all users who have the ability to create a campaign can publish it, giving administrators the opportunity to review and make changes, if necessary.] ### **NEW course in Academy: EXI in Action - Use Cases and Workflows to Drive Impact** We're thrilled to share the release of a new EXI enablement course! 👉 [EXI in Action - Use Cases and Workflows to Drive Impact](https://academy.moveworks.com/catalog/courses/4138401). This new content builds on our foundational EXI certification and delves deeper into the practical application of EXI within essential business workflows. Additionally, it suggests focus areas and cadences for each workflow, as well as how to measure the impact of your efforts. # October 2024 Product Release Notes ## New Releases ### **Moveworks Copilot can now summarize multiple plugin responses** Moveworks Copilot can now call multiple plugins in parallel, review the responses from them, and combine their individual responses into a single, summarized response! This feature is called **multi-plugin response** and it enhances the user experience and utility from the Copilot by 1. Surfacing all the relevant plugins to the user for every request 2. Providing a concise and easy to scan response 3. Enabling the user to quickly understand what their options are and allow them to follow up on the one they want to pursue Here is an example of a multi-plugin response that combines information from Knowledge Search with Software Provisioning for Figma: ![](https://files.readme.io/c37884fb54a6253ccc248d274fd24476670c74cdb9f918534e0f3349a1a2a3dd-2d3e0c88-e703-44a9-86a8-c197c9a350be.png) You can see from the AI reasoning what plugins were accessed: ![](https://files.readme.io/6fd6ec16466b362be106decefb67aae88c646bc45ede00de2bec3c63a9a21798-copilot_multi_plugin_2.png) **What does a multi-plugin response look like?** Here are the key characteristics: 1. The top part of the response will be a summarized response that lists available options 2. If there are any buttons the user can click to execute the actions offered, they will be provided at the bottom of the response ![](https://files.readme.io/ed4a0611e1349bbb34f1589a9ce985cd5b9a29d6fd22e51e692af571828fe915-multi_response_2.png) 3. If there are multiple calls to action, you can see them at the bottom ![](https://files.readme.io/07737b90b9d8667b2abb25168ad71c0d1bf8c1278ea4c0344feab939473e6308-multi_responses_3.png) 4. When you take action, e.g. clicking on `Yes` for **Unlock Account**, it proceeds with the selected action ![](https://files.readme.io/a8f4c80dcd13f58aef3ff30a0ed965b1028f56adb6708cc5d3e7f9e9fa6b8426-multi_response_4.png) **How does this feature work?** Multi-plugin response comes with three key changes: 1. Tuning Copilot to call all relevant plugins simultaneously, 2. Executing plugins in parallel, and 3. Enhancing the response UX for calls to action (buttons). **(1) Simultaneous Plugin Calls** Before multi-plugin, Copilot almost always called one plugin to help with a request. The primary exception was multi-intent requests like “Do X AND help with Y,” which led to sequential plugin calls. Now, Copilot identifies and uses all helpful plugins. **(2) Parallel Execution** MultiPlugin executes plugins in parallel. For single intent requests, this ensures MultiPlugin latency is comparable to current performance; for multi-intent requests, this decreases latency as Copilot executes on all intents at the same time. **(3) Improved Buttons UX** With more plugins in use, calls to action have become more frequent. To improve this experience, we now include buttons for each separate call to action. Each group of buttons comes with a concise Copilot-generated description for button context. **What are some known issues and limitations?** These are some aspects of the first version of this experience that we are aware of, and will work on improving in future iterations: * While the Copilot will call multiple plugins as frequently as possible, sometimes the plugin you are looking for may not appear in the list of plugins * Duplicate call to action * In cases where multiple plugins require input from the user, like missing arguments or confirmation, we want copilot to emphasize the call to action. This makes it much easier for a user to identify action required to resolve their issue. We also leverage generative LLMs to generate headers for button groups, which are related directly to these calls to action. Sometimes this can lead to some redundancy in the response. * Occasional verbose updates and persistent calls to action * If the Copilot offers multiple options with follow-up actions, and the user selects one, it may sometimes continue to provide the option to select the other. * Free text inputs such as business justification are sometimes not recognized and the Moveworks Copilot may jump out to offer other plugins (sporadically occurred before the introduction of multi-plugin response also) * Any instructions added to customize Copilot’s input may need to be modified with multi-plugin response since the format of the response could be different. **How will this feature impact Copilot Insights?** The main impact will be an increase in plugin calls - both successful and unsuccessful. 1. In the interaction table, you will see more plugins in each interaction row. 2. In the list of plugins on your Copilot Insights home page, you will see an increase in the number of plugin calls, particularly for the most common plugins such as Knowledge Search. ### Add attachments to ticket comments in your Moveworks Copilot We’re happy to inform you that it is now possible to add file attachments to comments in tickets, when adding the comment to a ticket from the Copilot! This is in addition to being able to add an attachment while *filing* the ticket, which was already available. Moveworks offers the option to enable adding attachments through a configuration, and this was a feature available in Moveworks Classic. It is now available in Copilot as well. **How to use this feature** Simply add a comment to the ticket as you would and then click on edit request to reach the popup to edit your comment. The option to add attachments will be available as shown below: ![](https://files.readme.io/46c30301dc6d7c145f8f364e9e36d6f68598f710156960873491b079377f4b2b-attachment_1.png) ![](https://files.readme.io/86808c45db404529c4f622a652cc317695d19a22f8bf17625c6cce75412d96b5-attachment_2.png) **What do you need to do?** 1. If you already had this option configured, you do not need to take any action. Your users will now be able to add attachments 2. If you would like to enable this option, please reach out to your CS team **Upcoming enhancement** For Slack customers, we are working on a completely Slack-based experience to enable adding comments through a modal within Slack itself. Users will no longer be directed to a browser to accomplish this. This update is coming soon! ### Brief Me now supports PowerPoint files Brief Me within our Moveworks Copilot now supports **PDFs**, **Word docs**, and **Powerpoint files**! If you are already part of our limited preview program for Brief Me, your Copilot already has this update. Go to your Moveworks Copilot and start uploading any combination of these files — up to 5 files at a time, each file can be up to 25MB.