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.
35 results found
-
Avatar API Driven Capability
Avatar —
Customer would love to have the API Driven Capability to Upload to the user’s Avatar, and might require additional API parameters like “center point” to ensure a portrait is centered.
Customer stores Avatar/Portraits of their people in centralized personnel databases, which is the key store for that data. Their users engage with it there for uniformity. Also API Driven would allow them to build Avatar Processes into their Native Mobile Apps that also impact their Box Experience in a positive manner.
They already have several workflows that output Avatar to outside systems upon change internally.
7 votesThe Upload Avatar API was released earlier this year. Please find more details on developer website at https://developer.box.com/changelog/#2022-05-18-new-endpoints-for-user-avatar
-
Update the .NET SDK to support .NET Core 3.1
The current .NET Core NuGet package is set to support .NET Standard 1.4, but this means that support for old libraries is required. For example, the SDK throws exceptions when getting an admin client due to incompatibilities with System.IdentityModel.JwtToken >= 5.4. These sort of problems are going to continue to happen as the framework progresses.
2 votesStarting from .NET SDK version 4.0.0., .NET supports Standard 2.0.
We dropped support for .NET version <2.0, so the issues mentioned in this request should not be valid any more. Please reply to this message or submit an issue in Github repository if you still face any difficulties.
-
Provide overwrite switch in CLI to account for existing folder in download location
Currently BOX CLI download doesn't have overwrite action. If a folder already exists in the location where the new folder is being downloaded, the CLI errors out.
There should be a over-write switch to the box CLI folder download. It should be something like:
box folders:download Folder_ID --destination=<location> --over-write=Yes
8 votesWe have added functionality to overwrite folders in Box CLI v3.13
-
Allow Metadata search for files uploaded via Box API
Documents in BOX are not searchable based on Metadata when uploaded using BOX API
Document uploaded into BOX via EPHESOFT using BOX API and 3 metadata elements are attached to the document. We can see the document in the BOX and the metadata elements are present in the Custom Metadata section in the BOX.
2 votesThere are two ways to find files in Box based on the metadata. The existing Search API provides a metadata filtering option and also indexes metadata content. The Metadata Query API provides SQL-like syntax for finding files based on specific metadata condtions. See https://developer.box.com/guides/metadata/queries/create/ and https://developer.box.com/guides/search/full-text-search/
If there are unmet needs please add a comment!
-
error in documentation
On the Authenticate with JWT (SDK) page the Node code snippet creates a const "configJSON," but then when the page references it later, it calls it "appConfig" in another code snippet instead. It references the enterpriseId in the configJSON variable but calls it appConfig.enterpriseId out of nowhere instead. The code breaks like this. Please fix for the sake of people trying to use these code snippets.
1 voteThis has been addressed in the latest version of the docs, available at https://developer.box.com/guides/authentication/jwt/with-sdk/
-
Stop interception of browser search shortcut in developer docs
The box developer docs hijack CMD+F and that's exactly not what I expect it to do
CMD+F is a shortcut for most (all?) browsers to bring up a native Find dialog, but your reference docs hijack it in favor of some type of auto-complete search on the page which is actually never what I want, or expect to happen.
1 vote -
Qs re: API and "is_external_collab_restricted" parameter
I believe that the API allows for updating the "isexternalcollab_restricted" parameter. However, the API documentation and example does not illustrate this. Would you kindly update the documentation on this?
If I'm wrong and adjusting this paramter via the API actually isn't possible, would it be possible to request this be available?
1 voteThis capability is available via API and our documentation now reflects that.See https://developer.box.com/reference/put-users-id/
-
15 votes
In the Developer Console, under App configuration, it is possible to set multiple redirect URI for OAuth application.
See screenshot attached for details
-
Display service account login in JWT app configuration console.
Request:
It would be really helpful if the service account login were displayed on the JWT app configuration page. This would make it easy to identify the login without having to run a separate script and would lower the barrier to entry for developing unprivileged BOX JWT apps.Background:
We are making heavy use of service accounts to promote development server/automation-friendly Box apps. Our development model, outlined here (https://github.com/box-community/sample-jwt-app-primer) involves inviting low-privilege service accounts to collaborate on folders. This enables programatic access to Box files on a selective basis.A major pain point is identifying the login associated…
22 votesWe launched a feature that will show the email address of the system generated Service Account for JWT, Client Credentials Grant, and App Token apps. Find this information in the General Settings tab of your app after it has been authorized. For more check out or product update here: https://support.box.com/hc/en-us/articles/1500003965281.
-
Add Python code example
On page https://developer.box.com/docs/work-with-users
It would be super-helpful to have a Python example for Generate a User Access Token.
I've had a tough time finding the right Python call to use for App Users for getting an access token.1 voteThere is now an example of how to get an access token for an app user with the Box Python SDK available at: https://developer.box.com/guides/authentication/jwt/user-access-tokens/
-
Clarify Python example
On page https://developer.box.com/docs/work-with-users
Creating a new App User, Python.
Should specify login=None for clarity in create_user() call. Also addSpecify login=None to indicate you are creating an App User.
1 voteView the updated developer documentation at https://developer.box.com/guides/users/create-app-user/
-
API currently doesn't expose email addresses of non-Box uploaders who upload via email
Specifically in the context of uploading via email.
API currently does show emails of uploaders that are Box users, whether in enterprise or not. It does not show emails of uploaders that are not Box users (name shows as "Unknown User".
Webapp shows names for Box users, email addresses for non-Box users. It seems odd that the webapp would expose the email address but the API doesn't.
1 voteA field called ‘uploader_display_name’ is now available on the file object via API and documented at https://developer.box.com/reference/resources/file/. This field should contain the email address of users that upload via email or the new file-request capability. Read more about the latter at https://support.box.com/hc/en-us/articles/360045304813-Using-File-Request-to-get-Content-from-Anyone
-
File ID for older file version
To enable the ability to preview older file versions without promoting them to current.
0 votesYou can now preview previous versions of files in the Box web application. See https://support.box.com/hc/en-us/articles/360043697054-Accessing-Version-History
-
3 votes
This feature is in limited GA – please contact your Box representative if you would like to use it.
-
0 votes
We have added the ability to get and set Terms of Service for users through the Box API. Please see our developer documentation for more detail: https://developer.box.com/reference#terms-of-service-object
-
Add all webhooks v2 event triggers to the Java SDK
It's currently unclear whether all event triggers listed in developer docs are supported, as the Java SDK does not specifically list them: https://github.com/box/box-java-sdk/blob/master/src/main/java/com/box/sdk/BoxWebHook.java#L584
0 votesThis has been addressed in https://github.com/box/box-java-sdk/pull/497
-
Add As-User support to the Java SDK
A GitHub issue exists for this but no updates have been added since the issue was created in 2015: https://github.com/box/box-java-sdk/issues/76
0 votesSupported now!
-
More efficient way to get metadata on files in search
Search by metadata returns a list of files. That list isn't much use without knowing the metadata it matched. To use Box's metadata for anything past the initial search query that's related to display, each individual search result must be queried for its metadata.
4 votesWe are now in the process of rolling out the new Metadata Query capability to all Box enterprises and expect to be complete by the end of June 2020.
Please refer to https://developer.box.com/guides/metadata/queries/
and
https://developer.box.com/reference/post-metadata-queries-execute-read/ -
1 vote
-
Add "FOLDER.TRASHED" event trigger to Webhooks v2
The existing event trigger "FOLDER.DELETED" only triggers a notification when a folder is permanently removed (deleted from Trash). Currently, there is no option to receive a webhook notification if a folder is sent to the trash. "FOLDER.MOVE" does not capture this action either.
0 votes
- Don't see your idea?