Build better products with our product team.
hey all, was looking through my HTTP actions that i’ve created in the Agent Studio console today trying to find one i created and kept missing it and thought, it would be nice to organize or group these by connector.for example if i have 4 actions that are using my MS Graph connector, and 6 that are using a ServiceNow connector, it would be cool to either filter the list of all HTTP actions for only the actions that match that defined connector OR even develop a view that just separates the actions visually and groups them together by sibling connector.i have a naming scheme for my actions that i follow and it is nice that the most recently edited/used action shows at the top most of the time, but this i think would possibly be a little bit of a cleaner way to look through my ever growing list of HTTP actions.cheers!
Search for Box files in Enterprise Search
Search for Shared Drive and My Drive content in Enterprise Search
Enables users to search for millions of documents from Confluence Cloud in Enterprise Search
Next-gen connector for MS Graph API to search Sharepoint Online and OneDrive
Next-gen connector for Sharepoint Online for Enterprise Search
Would be helpful to have an SDA on/off toggle on each plugin as we’ve noticed that it calls on some plugins that we don’t want it to run on.
It would be very helpful if we could initiate a user sync. If I am making a change to how users are mapped (adding in a new app, adjusting attributes, adding in new custom attributes, making changes due to changes in the applications), I have to wait 4 hours just to see if the change I made was successful. If there was an error, now I have to wait 8+ hours. In general this just impacts development time, but it has impacted production when applications change their attributes which has caused users to lose access until it synced correctly.
At our company we do not ingest every single wiki article for various reasons - nor is every content type ingested from our intranet. I perform manual download of knowledge ingested and xlookups against an igloo report i get weekly to see if all the ingested wiki articles i expect to be ingested in Moveworks is. I would love if we had a data api to access the ingested, indexed knowledge so i can automate compares and reduce the manual labor to do checks on what was ingested by Moveworks and how long ago , etc. Would love a similiar capability for user ingestion. A data api so i can see what users are enabled and not to compare against on new hire and TLX rosters.
Currently, developers don’t have access to which interaction surface a request came from when Moveworks executes an action and sends the payload to the API. It would be great if we could customize the payload of an action to be able to send to the API where the interaction came from, example: ‘zoom’, ‘slack’, ‘movewebchat’, etc. Our use case is that we want to synchronize sending images across all interaction surfaces for a particular agent so if we had access to interaction surface, we could tell if it came to zoom send to the image to the user’s Moveworks chat in zoom, if it came from slack send the image to the user’s Moveworks chat in slack, etc.
Some users are not aware that they have multiple approvals pending. If the button could have in parentheses the number of approvals a user has left, we hope it will help reduce the number of missed approvals.
We sometimes run campaigns where we encourage users to complete a specific task (like download an app, change an account setting, etc.) There’s a reasonable expectation that some number of them are going to need assistance or run into issues. However, the messages for campaigns don’t include the feedback buttons, most importantly the Get Help link. Hoping they’ll realize they can conversationally request to file a ticket isn’t a good solution since users have a wide range of technical literacy.At the very least, I’d like to see these small buttons included on these messages. Even better would be additional options for button configuration in the campaign to include a Get Help button in line with the others. This could also be expanded to include other ingested forms as well.
Hi Team,The result of query ‘List all my reportees’, should exclude people with start date/hire date (from workday) is in future. Please refer to conversation from service ticket: Case 00040244 ThanksShaila
We have an onboarding series that is working great for introducing new employees to the bot. We’d love to be able to send messages based on days of the week instead of days since they were hired - like, always send messages on the first Monday after they start, etc.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK