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.
418 results found
-
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 -
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 -
Ability to delete, transfer, and hide workflows created in Relay for accounts that have been deleted due to retirement, etc.
Ability to delete, transfer, and hide workflows created in Relay for accounts that have been deleted due to retirement, etc.
Currently, workflows created with a deleted account cannot be deleted or transferred, and the display remains, so in some cases, it may get in the way. I will.
16 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: Invite external user at Manual Workflow start
We have a manual start workflow where we want to collaborate a volunteer to a template folder where they need to fill out some forms and upload back to a Box folder. Relay does not seem to let the workflow starter enter the collaborator's email UNLESS they already exist as an external user.
14 votes -
Copy file from relay should version the target, not create a new file
We have a release workflow, where documents are being copied to a shared environment after they have been approved. This works well for the first version of the document.
However, if we change the document and send it through the approval process again, Box creates a new document at the target area. Box does NOT create a new version of the existing document.
Since this process is really key to creating "Quality Managed" documentation, Box relay should offer to version an existing document. Defaulting to creating a new document, makes Box unusable for these kind of approvals.
14 votes -
Ability to start Box Relay workflow by selecting folder.
Currently, users are not able to start workflow by selecting folder. Customer store contract, project schedule worksheet, and project documents within a folder and like to move the folder to another folder.
14 votes -
Create Folder From Relay Folder Navigation View
In order to create a Relay Workflow the folder structure has to already be in place. This is not always the case. It would be helpful to be able to create a folder from the Relay Folder Navigation view.
For example: if I am creating a File Request flow, I navigate to Relay, start a new workflow, select my File Request trigger, and I want my first outcome to move the file to a folder.
If that folder hasn't been created I need to cancel or navigate away from Relay back to my All Files, create the folder, go back…
13 votes -
Have and or logic to drive an outcome in Relay based on metadata values
Having the ability to say if a metadata value = abc then create a folder with a standard naming convention derived from a metadata template, if not do not create a folder.
13 votes -
Create automated Relay against multiple folders
Many times, there is a single automated workflow, e.g. from a file action or folder event, that actually applies across different folders in the structure.
Today, we can only select one folder for the workflow and therefore have to duplicate the workflow multiple times if we want it to work in different places. Then, if the workflows needs updating, then it has to be done in multiple places, which isn't the best place use of time.
It would be great if, in the workflow builder, if you can select more than folder for where the workflow should listen for the…
13 votes -
"apply workflow to all subfolders" should be an option for every trigger
When using the "manual start" trigger of a workflow you can check a box that will apply the workflow to all subfolders. This would be useful for all triggers.
Currently I need to create 10+ duplicate work flows that are exactly the same, but applied to separate folders.
I am unable to use the "manual start" trigger because the workflow is most efficiently start by an external collaborator - and Box does not enable external collaborators to start manual workflows13 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 -
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 -
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.
-
Expand Capabilities for Adding External Collaborators to Relay Tasks/Notifications
Currently, a user can only add an external collaborator to a Relay Task/Notification if the following are true -
- The user owns the content
- The user has added the external collaborator to content
- The user has to have less than 5,000 external collaborators on items they own
Many customers have a closed folder structure, where one admin user owns all content, so this admin user would be the only one who can create the workflow with external collaborators added to tasks/notifications. For large organizations especially, this is difficult to administer and maintain, so ideally even users who do not own…
12 votes -
Relay admin should allow editing of relay flows
Users are confused when going into relay on the Admin dashboard vs. relay on the main toolbar in the user experience. Users should be able to edit relay flows when in the admin dashboard, or there should be clearer messages to users why they can't edit a relay flow in the admin. It leads users to create new workflows because they don't know where to edit the files.
12 votes -
Add option to cancel workflow
Currently there is only delete option to stop the workflow.
Workflows are stalled or stacked as in progress sometimes. We want to assign similar task manually or re-assign the same task to complete the workflow in time.
But it will cause duplicated tasks assigned unexpectedly or file operation (move or copy etc.) is executed twice. This is very confusing.
So we want to cancel the existing workflow before manual workaround.12 votes -
Add “Do something after a certain period of time” option in outcome
Accessing to some of our manual documents is strictly managed and we would like to delete these documents which are not effective anymore after a certain period of time (e.g. 1 day, 1 week, custom lengths etc.). If Relay is capable of this, we can streamline other systems that are currently implemented.
12 votes -
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 -
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)
12 votes
- Don't see your idea?