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.
417 results found
-
Approve each file separately for a manual start with multiple files
We want to approve each file separately for a manual start with multiple files.
For example, I get an application for three files and I want to turn back only one of them, but as it stands, I need to turn back all three. The applicant has to choose three files again and re-apply, which is very time-consuming.
2 votes -
Provide the ability to customize the message that is sent to workflow participants when starting a Relay workflow.
I have a review workflow that I want to use repeatedly. Each time I start the workflow I have specific instructions that I want the workflow participants to see. This is usually a complete timeline for the review cycle in which the current review might be the first or subsequent steps.
My workaround right now is to send a separate email to the workflow participants, but this means they get 2 emails about the same review.
1 vote -
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 -
1 vote
-
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 -
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 -
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 -
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
- Don't see your idea?