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.
15 results found
-
Box Sign action in Relay
I would like to have a Box Sign action relay.
I expect use cases like once it is approved internally, we move to submit Sign request via Box Sign30 votes -
Approval Task With Box Relay Enhancements
When allocating approval tasks in Box Relay, users are able to uncheck the "Invite the person in charge as a viewer" function.
In addition, if "Invite users as viewers" is enabled, and the members in charge have been granted permission as members of a group, which prevent them from being invited to the file as viewers.52 votesWe’re evaluating this as a feature now.
-
File request - Allow only Manage Users from an EID to upload via File Request
In file request, have the ability to state that only a managed user in the EID or an external user that has been invited to the folder can upload, no one else. By doing this, it prevents a file request link from being randomly guessed or found on the internet AND prevents a random user from uploading bad or malware/virus infected content. The current state of requiring the user to login is too generic and doesn't meet the requirement of keeping the file request locked down. Using the collaboration role for upload is not what is needed. The File Request…
30 votes -
Make Workflows Shareable Among Users (Box Relay and Box Relay Lite)
In Box Relay, we can check the progress of workflows in the [Tracking] function.
Currently, only the owner of the workflow, and Admins who are granted to access to workflows can see this [Tracking].However, the progress of workflows within the enterprise should be visible to other users as well.
(e.g. Users who have tasks assigned in the workflow, or Co-Owners of the folder where the workflow is triggered.)It would be useful if the owners could share their workflows to other users.
38 votes -
Conditional fields on File Request form
It'd be great to be able to have conditional fields in the File Request form so that certain fields are only exposed depending on the answer in the field(s) above.
9 votes -
box relay shared link
Using Box Relay, create the following new outcome: Based on a metadata value when stored on on a file or folder, create and share a web link to the email address(es) in the metadata value, with specified collaboration.
21 votes -
cascading auto-start workflows
cascading auto-start workflows. We have a specific use case defined that would greatly benefit from this capability - shield classification being applied automatically alerts the uploader of the file that the content needs to be moved. This would be a big win for USAA
5 votes -
File request: add the ability to pre-populate fields
It would be great if there would be a way to pre-populate the fields of a file request with "known-information" if available.
This would allow us to reuse a single file request in a portal, but set the metadata on the uploaded documents, based on the current user's context. Content can then be routed in the Box system based on the metadata set.
4 votes -
Auto overwrite if the file is uploaded with the same name in the folder via File Request.
In the current spec, the file with the same name in the folder is uploaded via File Request, the file name is automatically changed to containing date and time.
I want the option to overwrite the file when it has the same name of existing files.7 votes -
Metadata triggers without folder specification
--I want Box Relay to be able to kick workstreams off in sub-folders that don't exist yet. We have a general "Accounts" folder, and I want my metadata tag triggers to affect sub folders in that parent folder. However, the metadata trigger requires me to specify which specific folder to trigger the Relay within. I suggest one of two things:
1. Remove the need for folder specification. If I have a metadata trigger, do I really need to specify the folder in which the content lives? Relay should scan for that metadata tag, wherever it occurs.
2. Allow for Relay…15 votesThanks for your feedback. We’re exploring introducing new cascading triggers or system-wide workflows which would address this issue.
-
Relay action: create Box note
From trigger, create a Box note from an existing template.
10 votes -
Ability to create dynamic forms
For example: A Word document to convert into a dynamic form with pre populated field.
118 votes -
Report / Customizable dashboard for a workflow
I would like to get an overall view of my workflow and which files are at which stages, including:
- How many files are in Step 1, Step 2, Step 3, etc.
- How many files have completed
- How many files were denied (or stopped in process)32 votes -
Shared Link Creation or Distribution as step
Adding the ability to generate and/or send a file to a party as a step within Relay.
1 vote -
1 vote
- Don't see your idea?