Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
-
Error notification about Relay Workflow
Currently there is no way to know whether the relay workflow has failed or not.
So when there is an error in a workflow, I would like to have admins and or the workflow owners to receive a notification to inform about the error.47 votes -
Box search function will not search pdf documents I have personally OCR'd using Adobe.
Box search function will not search pdf documents I have personally OCR'd using Adobe. Please advise.
44 votes -
Enhance Metadata Search for Text field for Japanese language ("contains" instead of "exact match")
Currently, texts in Metadata can only be searched by exact match especially for Japanese characters. We would like to see an improvement to make it "contains" search as it is available in the standard search.
40 votes -
Allow for multiple primary admins
There are several functions within the Admin Console that are only accessible to the primary admin. Setting up SSO for example requires the primary admin, and co-admins are unable to integrate with SSO. In many environments there will not be a single administrator with privileged access across multiple systems, which means the primary admin role will need to be assigned and re-assigned multiple times to perform necessary tasks.
To promote a secure environment where tasks may need to be performed by multiple administrators, I would request either 1) admin console allow for multiple users in the primary admin role, or…
17 votes -
Improve the use of Variable Strings in the JAVA SDK
For customers who are leveraging an API gateway using Java SDK version 3.2.1 some URL prefix text strings are not dynamically adjusted.
For example, when customers are downloading the file representation in it tries to call directly the box API URL like the following URL:
https://api.box.com/2.0/internal_files/123/versions/345/representations/
Some customers may be leveraging a customer specific gateway, so they need to be able to dynamically change the URL where https://api.box.com/ is replaced with the gateway prefix like all the other calls:
{{CUSTOMERGATEWAY}} /internalfiles/123/versions/345/representations/jpgthumb32x32
There are a number of places where the prefix was not dynamic.
1 vote -
Tasks in relay are owned by Relay owner rather than workflow initiator
Currently tasks have owner and assignee. The owner is always relay owner, who gets notifications when there are any changes to the task which may not be ideal.
Allow for an option to have the task owner be the workflow initiator instead.
27 votes -
Support Drag & Drop from Box Web App to Outlook
Please enable the ability to drag and drop files FROM Box Web App TO Outlook email client (including the option to insert them as links OR to add them as normal attachments). Currently there is no native Drag and Drop functionality available between the Box Web App and Outlook. Therefore, the process to add file attachments/links to emails via the Web App or Outlook Plug-In is actually currently LESS efficient with BOX than without it. Since BOX Drive is not available for virtual clients (such as Terminal Server or Citrix), their only option is to use the Web App or…
21 votes -
Office Online Only Setting
A setting that folder owners could implement that makes it so the document can only be opened/edited with Office Online.
25 votes -
Allow users to see who the file owner is
If a user does not have access to a file, Box politely reports: "This shared file or folder link has been removed or is unavailable to you." That's fair! How does one know whom to contact regarding access? Would it be feasible and acceptable to let us know who the owner is? A link to "E-mail Owner" or "Request Access?"
15 votes -
shared link password
Currently there is an opportunity for Shared Links with a password to be brute force broken, as there are not any controls in place to disable after unsuccessful attempts. Two options to handle this are:
- Implement the configuration in the Shared Link Password protection option to set the number of unsuccessful attempts
- Implement an audit event that documents an unsuccessful Shared Link Password attempt, so that a custom implementation can monitor the unsuccessful attempts, and react accordingly.15 votes
- Don't see your idea?