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.
14 results found
-
Relay Reports
Create a Report so I can export the task history of a Relay or selection of relays across a timeframe for all or selected users
35 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 -
The option to cascade Relay triggers to subfolders for all triggers
Box needs to add the cascade option to all Relay triggers to catch activity in underlying subfolders. The legacy automations feature that Box had did this by default. Now, the alternative is having to create several relay workflows that is too cumbersome to manage and doesn't scale.
55 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…
111 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 -
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 -
Admin Dashboard with visualizations of workflow stats
Looking for additional visual methods for a project manager or process owner to access open Relay workflows/action items
13 votesWe are exploring solutions for this request.
-
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.
2 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 -
1 vote
- Don't see your idea?