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.
341 results found
-
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 -
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…
3 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…13 votesThanks for your feedback. We’re exploring introducing new cascading triggers or system-wide workflows which would address this issue.
-
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.
-
Copy files to Relevant Folders based on Tags or Automation Rules
We would like to setup Automation rules for folders that would COPY and not MOVE new files to designated folders.
To take the idea even further, if the COPY could be triggered by a TAG assignment, it would be even better, because some of the files in the affected folder should not be copied, while other should.
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).
5 votes -
Create a new workflow, after the folder creation.
We want to create a new workflow, after the folder creation.
We are planning to have two types of flows, "Project folder creation flow" & "Approval flow(under the newly created folder)".
The "Project folder creation" is fine, but for "Approval flow" we need to create it each time after new project folder has created.
So it would be great if we can create the "Approval flow" after the project folder has created.Project folder creation
Trigger: Folder creation
Outcome: Copy the prepared folders underneath the folder which triggered the relay.
the prepared folders include "Review" and "Approved" folders.Approval flow…
5 votes -
Workflow is giving away private data- this should be fixed
When viewing my workflow folder, I see a name of the last person that edited some workflow + an indication of the number of workflow items in general
1 vote -
Automated Set of Subfolders
I'd like the same set of subfolders to be created automatically for every matter (parent folder) I create, so i don't have to constantly re-create the subfolders.
1 vote -
Use a relay to output reports periodically.
Use a relay to output reports periodically.
6 votes -
name folder based on data created
When a new folder is created through Relay, have various options to name the file beyond a default name field, such as data created as an insert field variable.
3 votesWe are conducting user feedback sessions to gather more information
-
The ability to put comment with mentions in a file as an outcome
As a user, I would like to add comment with multiple @mentions as Relay outcome
2 votes -
Selecting approvers and move destination folders of outcomes dynamically
I got a request from my business partners that it might be very nice for them to be able to select approvers and move destination folders of each outcome dynamically.
They feel inconvenience to create Relay flows as the sames number of external collaboration folders of every company.1 vote -
Box Relay variable support
Could we have a variable for approvers Instead of harcoding them to a relay?
For example, if a document contained a metadata field for approver and it was populated with a user, could we use that metadata as a variable for the approval step of the relay workflow?
61 votesThis is still on the roadmap.
-
Users don't get email notifications for assigned tasks unless they're in the folder
Users don't get email notifications for tasks in Relay unless they're collaborators in that folder. It doesn't always make sense for the users to be collaborators and this can add clicks to the Relay experience. Because of this, users that rely on Box Drive don't get notified that tasks have been assigned to them unless they log into the web app to check.
Can users get email notifications when they've been assigned a task in a workflow regardless of whether they're collaborators in the folder?
3 votes -
automatic periodically delete
Current feature only delete on specific date/time. please add regular/recurring delete/trash feature. e.g: every 1 week delete certain folder. Every 1 month delete specific folder. Thanks.
2 votes -
Ability to trigger multiple workflows
“Lets put it like this, if you have the functionality to split workflows based on different files in 1 folder, people here would want to switch from Sharepoint to Box ?. It is currently the key reason to stay with Sharepoint as far as I’m made aware of.”
Basically, the customer wants to be able to trigger multiple workflows within one folder, but only on some files for each workflow. Currently they could achieve this through metadata, but this would not be contained to the folder.
2 votes -
It will be great if we can connect folder action between multiple flows.
When you have in the first flow a folder action (copy, move or create), you won't be able to reference the folder in a seconf flow if you want to take action if the task that has been rejected.
I have created a couple of Relay Flow (Contract Management and HR Onboarding) during the flow I create folder to collect more information from either a vendor a new onboard person, but when the flow get rejected and could not create a rejection flow (Second flow) because could not take action on a folder.
This could be important when we will…
2 votes -
Need ability to migrate workflows between Box instances
For M&A use cases, it's my understanding that Relay workflows cannot be migrated once Box instances are merged - it'd be nice to have this built into the product so that companies that are constantly acquiring other companies (on Box) don't have to worry about losing access to business critical workflows.
1 vote -
2 votes
- Don't see your idea?