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.
427 results found
-
Assign Relay task to person who completed previous task.
If you create a task and assign it to multiple users, say Tom, Bill and Susan where only 1 person needs to complete it, I want to be able to automatically assign the subsequent task to the person that completed the preceding task. For example, if Susan is the person that completes task 1, I would want the subsequent task to be assigned to Susan only, eliminating Bill and Tom from the process.
2 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 -
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.
29 votes -
Add enabling & changing Shared Link as an outcome for files/folders
For example, we have a situation where shared link is turned on the ahead of x days.
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 -
Box Relay Lite email notification
The current behavior of "Box Relay Lite" is that workflow creator gets the approval notification.
The The expectations from us is that a notification email of the approval result will be sent to the approval requester who uploaded the file to the specified folder.
7 votes -
Add Folder Event Workflow Relay Feature
Add Folder Event Workflow Relay feature. The current feature only supports File Event instead of Folder Event.
2 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 -
Allow folders to be uploaded with File Request
File Request is a helpful feature, but often isn't useful as most external parties want to share folders (including sub folders) of documents with us. Can a feature be added to allow folders to be shared as part of File Request - perhaps renamed to Folder/File Request?
39 votesAt this point, there is no short to medium-term plan to extend File Request to accept folder uploads. Please continue to upvote/add feedback so we are able to revisit the prioritization at a later time. Thanks!
-
Support multi-file for rejected task trigger in Relay
Suppose you like to assign an approval task to a person with multiple files and when the task is rejected, you like to move the package of those “rejected” files to a different folder("Rejected folder) instead of having them sat in the triggered folder.
For a single file, you can create the following workflow containing 2 flows and it works perfect as expected, however it doesn't work for multi-files...
Flow 1: Trigger Manual start-> Outcome: Assign task -> When rejected, the flow is end
Flow 2: Trigger Task -> Outcome: when the task is rejected, move the file to “Rejected…43 votesWe are conducting user feedback sessions to gather more information
-
Remember the folder location for your flow on folder picker component
Once you built your workflow, sometimes you want to doublecheck folder location for your flow.
When folder structure is deep, the path is not visible on your flow, so you click the folder picker but it will navigate you to a root folder instead of the folder you selected.
It will be helpful if it has an option to go to the selected folder location for the flow rather than root folder.1 vote -
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 -
Create a Box group/alias or ability to select a different name to replace the workflow owner’s name.
I’ve created several Relay workflows across the business and the issue I found is that people are reaching out to me because my name is tied to a task that is assigned to them. Often times, I do not have any context to the workflow so it results in me having to reach out to the person who started/uploaded the document. We want to avoid approvers having to reach out to the workflow owner vs. the actual owner of the program. This process would not be sustainable if it were rolled out to a larger company.
Currently Example: Hayley creates…
116 votes -
Enhance page view for Relays in new UI
When accessing Relay in the new UI, not all Relay workflows incrementally load nor are there pages to navigate through to view all workflows. I would like the ability to see all relays on one or multiple pages without using text filters.
1 vote -
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 -
When copying a folder with File Requests configured within it, add an option to have the File Request configurations copied as well.
We have a need to setup folders with File Request features for our customers. When we do this manually, it takes a lot of time to set everything up as we need it. We'd like to be able to copy a folder (along with its subfolders) and its File Request setup. This would make any existing setup, like a template, which we can simply copy and rename in preparation for another customer.
Currently, we can only copy the folders with or without contents. But either action does not copy the File Request configurations in the source folder.
Thanks for your…
1 vote -
Allowing further personal branding in the "File Request" link.
Currently only able to edit title and add a description but would be link to put company logo within link.
6 votes -
Automatic email response for file request submitter
Would like a feature whereby the person submitting files using Box File Request receives an automatic confirmation email with a customizable message. For example, after the submitter uploads files using the File Request web widget, that person gets a email to the effect of, "Thank you for contacting us. A team member will review your submittal and follow up within 24 hours." The person would be required to provide an email address but not required to have a Box account. Many of our external customers send us application materials using File Request, and then they contact us separately wanting to…
45 votes -
Improve Relay error messaging for missing info
If there is info missing, the relay workflow can still be saved. Instead of wiping out all that you've drafted, it goes into an inactive state so you don’t lose your work when you close the window.
Even better would be if the error tells you WHERE you are missing info. Instead of the vague, “please fill out all required fields before saving" messaging
1 vote -
Ability to run relay workflows as a group
Relay workflows and approval tasks are started and sent as the user that created the relay. Ideally you want to get the box approval task that is sent to the users to approve to look like it is coming from the team that is requesting the approval.
Example: Invoice approval
When an invoice approval relay starts, pick dept. from metadata and start an approval process to the appropriate user as defined in the workflow. The user gets an email that says 'boxadmin' (in out case the user that created the relay) has sent you an approval task.It would be…
5 votes
- Don't see your idea?