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.
432 results found
-
File Request Scripting
Customer would like to use File Request instead of FTP, however, there is no way to script a automatic process to upload via file request.
We have a vendor that needs to upload files to us. They have an automated/scripted process using FTP so wanted to know if there was a way to do the same via File Request, otherwise it would be a manual process.
1 vote -
Ability to start 'manual start' workflows at levels other than editor
It would be great for the workflow owner to be able to set a lower level of permission to be able to kick of certain manual start workflows. The use case is that a client has a bunch of reference documents that they don't want their general audience to be able to download or edit, but still want them to be able to request changes to be made as part of a formalised process. At present those people can still annotate and comment, but the team making the changes can't track what's being asked, and so have to manually keep…
1 vote -
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 -
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.
-
options dialog when moving and file already exists in destination
Currently, when a file is in the process of being moved from one folder to other and a file with the same name already exists in the destination folder, an error message is given and the operation is candelled.
Maybe an options dialog would be better, asking the user if they want to overwrite (add a new version of) the file, or rename either of the files within the dialog.1 vote -
Relay: Folder picker, select folder in search
When choosing a folder when building a relay, there is a search box at the top. Often you will know the name of the folder you want to select, however, from the search results you can't put the dot in the folder name.
Instead you have to search for the folder that contains the folder you want, then find the destination folder by scrolling down the list so that you can put a dot in the select box.The ask is to make searching and then selecting the folder one smooth operation
5 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 -
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 -
File Request Action in Box Relay
A file request action on Folder in Relay that could automate generation of the File Request link and email it to a specified email address. Supporting automation of uploads from individuals without Box accounts.
9 votesAn integration between File Request and Relay was delivered this year. At the moment this programmatic generation of a link can be achieved with an API. An outcome type in Relay to generate a FR link is not yet planned.
-
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 -
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 -
Enhance relay feature
Relay limitations:
Not being able to tie outcomes from one flow to other outcomes from other flows all within the same workflow. Dynamically having related outcomes is critical to Relay’s usefulness.
Cascading folder metadata not being brought over when copying a file.
Having a third option for approval tasks (approved with feedback/conditionally approved).
7 votes -
Request Link via API
Scenario for Request Link via API: 1) Ticketing system support case requires the openee to upload files to the ticket 2) Use app to collect case number, authenticate user, create folder with case number 3) Set File upload link "Title", "Add Instructions" and "require users to provide email" 4) Get file upload link from API for pasting into the support ticket
2 votes -
Ability for variable dates in metadata templates
When assigned a metadata template as a Relay outcome, customer would like to have the Date value be dynamic and reflect the date the template is assigned, vs the date the workflow was created. The idea is that each outcome would change the status field of the file, and they'd also like to capture the date the status was changed. Knowing the date the status changed would allow end users to search for content in a certain status, by date range.
This functionality currently does not exist without asking the end user to manually update the date. Use case for…3 votes -
Use a relay to output reports periodically.
Use a relay to output reports periodically.
7 votes -
After file request is complete, allow customization of who receives notification
Ability to notify specific email address (not user who upload file) after user uploaded file via File Request.
2 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 -
I like automation; I would like to be able to pull data from different Google Sheets that are all located in my Box.
In Google Drive, all the documents can be referenced to each other. For instance, I can pull data from one Google Sheet to another separate Google Sheet (using the IMPORTRANGE function). This function no longer works as it now says "spreadsheet cannot be found."
13 votes -
Auto Delegation of task
Allow user to set OOO (Out of office) and pick someone to auto delegate the task during his/her absence. This should delegate only tasks assigned directly to the user or if every member of a group is assigned a task. If the task is assigned to a group and marked as "Only 1 member from group to finish", then auto delegation should not happen.
17 votes -
Add the ability in Relay to move the parent folder in addition to moving the file the triggered the relay workflow
Currently, I'm able to use Metadata to trigger a relay on a specific file. When this happens, I'd like to have the ability to move the folder that the file is in, and not just the file. Currently, I'm only able to move the file and that doesn't work when we have multiple files that would need to be moved in the same folder. It's simpler to just move the folder that the file is in.
Example use case: When managing a hiring process, we receive a lot of resumes. In addition to the resumes we receive other documents like…
4 votes
- Don't see your idea?