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.
425 results found
-
Change File Request to accept emails that begin with a number
File request currently flags an email that begins with a number as an invalid email and won't let the user continue with that email. Please update to accept emails that begin with a number.
1 vote -
Entering multiple accounts should auto-populate under in Assignee(s) field.
For the Relay window, users should enter emails one at a time so that the assignee options populate. For collaboration window, if entering all emails at once works, pasted accounts will be auto-populated. So it should also work in the Relay window.
5 votes -
When are you going to bring back file aliases? Bookmarks are not the same and don't cut it.
We need to be able to create symlink/aliases for files in multiple locations so that we aren't forced to upload a file multiple times, in several folders.
We use Box to allow our clients to download files, and we sort those in a way that makes sense for them. We also use Box to upload all of our files in a way that makes sense for our employees to find assets. Without symlinks/aliases this is tedious to do and ridiculous to manage.
3 votes -
Copy file in workflow should create a new version if file already exists
I am creating Quality Management workflows. At the end of the workflow the released document is copied to a new area, that is shared with the consumers of the QM-documentation.
Works fine the first time we run the workflows. If we update the document and run the workflow again, the target file is not versioned: we get a new file with the same name and a timestamp added to it.
I appreciate this behaviour in some situations and understand why you have chosen this solution. However we would like to have the option in the workflow to "version the file,…
7 votes -
Time based relay tasks
Support time based triggers in Relay. For example, 180 days after an item has been uploaded to a folder either delete the file or move it to another location.
13 votes -
Ability to utilize file request as an outcome within Relay
Having the ability to upload a file or utilize file request as a step within Relay. Currently you can only kick off a workflow with either action. There are several document review use cases where a task is completed such as a lease review and a new task is assigned to a different user to upload the lease renewal document to be reviewed prior to being sent out to the client.
1 vote -
1 vote
-
1 vote
-
1 vote
-
Workflow should be able to utilize metadata field to send notifications.
we have buyers as part of the metadata. Workflow should have a notification as an outcome and retrieve email or user info from metadata to send notifications for folder events.
We also have due date and status on the metadata, workflow should be able to check the date, status and sending overdue messages to the buyers.
4 votes -
Relay Approval for a new folder
Currently, there is an option to get approval when a new file is uploaded, looking to get approval when a new folder is created or uploaded.
Thank s
1 vote -
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
6 votes -
Ability to communicate with non-folder collaborators on Box Relay / File request links
We are using box Relay and the File Request link as a document review intake, and our main goal is to get away from sending files and questions back and forth via emails. Currently, when someone drops a file to the link, in order for us to communicate with the requestor via the request (using the comments section) the names only populate (using @) when they are added to the folder as collaborators. Can box make it that we can add a communication feature to anyone with the link? or at least, to whoever dropped the file on the link?
1 vote -
Additional Relay Approval options beyond Go to Outcome 1 and End the flow
When using an approval task and sending a notification you are given two options, End the flow and Go to outcome 1. I'd like to be able to advise it to go to Outcome 2 or Outcome 3 of the workflow so things are more flexible in more complex workflows.
1 vote -
Add more detailed information to Relay workflow tracking
When viewing the tracking for an individual document progressing through a workflow, the task completion status is not granular enough to tell if any or no assignees have completed a task. For example: if there were four people required to approve a step, and three had approved, but the last person hadn't, this level of detail is only visible from the activity pane on the document, not from the tracking in Relay.
12 votes -
Allow the Admin to Set File Request requirements and default settings
Allow admins to require all File Requests globally to have certain fields (like email address or a pre-populated description Box with a legal disclaimer) or settings
17 votes -
File Request Timestamp
File request duplicate timestamps:
When we upload files with same file name via the file request link, time stamp will be automatically added to end of the file name in UTC+0000.
We would like a way to select the timezone used to add the timestamp (maybe the timezone abbreviation can be specified at the end of the file name timestamp for when other collaborators view it)
13 votes -
Specify how date is displayed within the dynamic naming feature in Relay
For non US customers... Specify how date is displayed within the dynamic naming feature in Relay. For example, 02/24/2021 vs 24/02/2021
2 votes -
Make the message area editable on relay manual workflows
In manual workflows, it should be possible for the workflow starter to customize the message field.
5 votes -
Relay Workflow period Allocations based on work days rather than natural days (i.e Exclude Weekends)
When assigning a task in relay you can assign the period in days associated to the task. at This point in time this does not allow the option to assign such days to working days but only natural days. Therefore if and when a weekend occurs during the timeline of the workflow action weekend days (non-working days absorbs the task timeline. the request is that there must be an option to assign a task only for working days (excluding weekends)
25 votes
- Don't see your idea?