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.
68 results found
-
Support deleting the current version
Currently there is no way to delete the current version or head of the version history. The only way to achieve the same effect is to promote a previous version and delete what was once the current version.
3 votes -
Enable API apps for select users
Right now, we can disable published APIs for all users, or enable them - we'd like the ability to restrictively enable.
3 votesWe currently do not plan to selectively enable or disable access to the Box API for specific users within an enterprise.
-
Allow external conversion engines for proprietary formats
We receive various proprietary formats that can only be converted by the original manufacturers. We want the platform to configure external conversion providers which would then be able to convert the formats to neutral Box formats such as PDF or MP4. This will create new integration opportunities for providers such as Autodesk, Adobe, CCTV providers.
3 votes -
Expose the functionality for auto-deleting folders and files on a specific date via the API.
Currently, the web app has a file/folder setting in which a folder or file can be deleted on a specific date. We don't expose this service via the API.
We work with documents in packages (folders) and so when the documents expire and are deleted, we would also like the containing folder to be deleted as well. All of these packages are customer applications and so if not cleaned up then they will accumulate over time.
Right now, retention deals with files only, leaving behind the folders. The auto-delete on the folder is perfect for this purpose except that it…
3 votes -
Provide read-only scope for user information
I'd like to provide our central identity management team a way to tell whether or not a given Box user has a > 0 byte usage before they delete the user's account (for example, as someone leaves our organization). I'd like to give them read-only API access to https://api.box.com/2.0/users, without giving them any additional access. Support tells me that this isn't currently possible. It'd be nice if it was--this could be useful for a number of other uses, too, such as reporting.
2 votesThanks for the suggestion! Providing a read-only scope for Users via API is not currently on the roadmap, but we’ll update this request if that changes.
-
Support for Collections in Content Explorer & Content Picker
Some of our use cases revolve around searching for specific metadata field or date range.
If UI Elements were able to be initialized with a collection, this would allow us to pass in a specific collection of files and display them easily even though those files may live in disparate folders.
2 votes -
Surface either EID or user_type when requesting collaboration object
Currently, requesting a collaborationobject does not surface either EID or usertype. (as seen in https://developer.box.com/v2.0/reference#get-collabs)
2 votesThis request is not currently on our roadmap but we’ll update this request if that changes. In the mean time, you can use a subsequent request to get the user information and specify the enterprise in the `fields` query string parameter.
-
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 -
1 vote
At this point we have no plans to create powershell specific SDK. However, the Box Command Line utility can be called from within powershell which may be of help. https://developer.box.com/guides/tooling/sdks/cli/
Furthermore there is some good (if a bit dated) information on how to use the Windows SDK from within Powershell here: https://community.box.com/t5/Platform-and-Development-Forum/Automating-box-processes-using-powershell-and-the-box-windows/m-p/50342
-
Provide a Go / Golang SDK for Box
Add Golang SDK
1 voteAt this point we have no plans to add SDK support for Go/Golang
-
Add length of field to API documentation
It would be nice to explicitly mention the length of some of the fields. In our enterprise account all the users had 10-digit UIDs, so I thought that was the standard length, but we had some users with preexisting lite accounts rolled in and a few of them had 8-digit or 9-digit UIDs. I see now that the example UID provided had 9 digits, so my bad there, but I initially just looked at the 'id' attribute under 'user object' to try and find the length and it would be nice I think to have something like 'id / string…
1 voteThanks for the suggestion. We generally don’t provide lengths for fields unless there is a concious decision to define a specific length or range as a contract. Given that the type of field for user id is a string, the fact that user id values ranged from 8-10 digits is an implementation detail, not a guarantee.
-
Improve CORS whitelist wildcard support
I would love to be able to use wildcards in CORS with a little more specificity. In particular, for review apps on Heroku, you will have a url that is auto-generated for each pull request, so something like http://my-app-dev-pr-523.herokuapp.com. I would like to be able to add http://my-app-dev-pr*.herokuapp.com to the CORS list but it currently flags that is an improper URL so I have to do the much more broad (less secure) http://*.herokuapp.com
1 voteThis is not currently planned
-
Rollback option when db crash
After creating folder or uploading files into box there will be chance of occuring backend database crash or lose connection between datasource . In this case we should roll back our transaction(like revert folder creation or file upload).
1 voteMany actions in both are idemptotent and can be safely retried. For those which are not, it is the responsibility of a client to implement transaction guarantees if required. There are common patterns for this such as the two-phase commit and SAGA pattern. If there is more information for a specific capability that is required to faciliate these, please add that to the comments.
-
Create Persistent Access Tokens
We want to embed a folder into our sales portal. We want our users/partners to be able to search within the folder.
We don't want to manage a separate code repo just for generating a downscoped token. Would be great if Box could support downscoped permanent tokens to cover these use cases.
We cannot search with in a folder with an embed widget.
1 vote -
Make the digest header in the Commit Upload endpoint optional
Currently, Commit Upload endpoint requires passing a Digest header for the sha1 of the entire file.
Given that the integrity of each file part is already verified, consider making the Digest header in the Commit Upload endpoint optional
1 vote -
Allow Recents to be filtered via API
Currently Recents is implemented globally across all Box content the user has access to. Ideally, Recents could be filtered to some ancestor folder IDs (like Search is) to show Recent items only within a particular folder.
The use case is a custom application which is integrated with a company's primary Box instance. A custom app wanting to leverage the Recents feature does not have a way to get Recent items relevant to just the application content.
1 vote -
1 vote
This is not planned.
We don’t see enough customer demand for this yet, and supporting every additional content type takes a significant amount of engineering time and effort.
-
Adapt Annotations to achieve Accessibility guidelines
Box View does not conformance with W3C Web Content Accessibility Guidelines, version 2.0 (WCAG 2.0) at conformance levels A and AA - specifically, annotations can only be viewed around mouseover. This is a blocker for us as we work with public universities who have to meet those guidelines.
1 voteThank you for the feedback. It’s on our backlog and we’ll do our best to get to it as soon as we can.
-
Support image tags in Metadata preview.
Currently images from external sites are not supported.
1 vote -
Thumbnails should be able to be requested in a batch.
You should be able to download all thumbnails for the items within a folder.
1 voteGreat suggestion – we don’t have any plans to do this anytime soon, however.
- Don't see your idea?