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.
340 results found
-
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 votesWe are conducting user feedback sessions to gather more information
-
Ability to create dynamic forms
For example: A Word document to convert into a dynamic form with pre populated field.
108 votes -
Error notification about Relay Workflow
Currently there is no way to know whether the relay workflow has failed or not.
So when there is an error in a workflow, I would like to have admins and or the workflow owners to receive a notification to inform about the error.81 votesHello all,
Thanks for requesting this feature. The product team reviewed this request and added to our backlog for consideration. We look to revisit this next year and once we start working on this, we will update the status.
Thanks,
Nirmal
-
Relay lite: allow admin to change the workflow owner
Box Relay creates a workflow (Folder creates a task that requests invoice processing and is used to manage outstanding tasks) that enables clerical employees to process invoices more efficiently. However, when the employee is transferred, the workflow that has been created is not transferred to the next person in charge. If a useful workflow can be managed as a company, not as an individual (Change the workflow owner for contact changes), it will be very useful for business efficiency.
69 votesEnterprise, Enterprise +, and grandfathered Relay full users are now able to transfer workflows
-
"File Request Link" report similar to the "Shared Link" report
Would like Org level report on what folders have "File Request Links" very similar to the "Shared Link" report. We need to report on what folders are shared publicly.
69 votesWe are creating a file request dashboard for Admins to manage their enterprise’s FR links.
-
Tasks in relay are owned by Relay owner rather than workflow initiator
Currently tasks have owner and assignee. The owner is always relay owner, who gets notifications when there are any changes to the task which may not be ideal.
Allow for an option to have the task owner be the workflow initiator instead.
66 votesHello all,
Thanks for requesting this feature. The product team reviewed this request and added to our backlog for consideration. We look to revisit this next year and once we start working on this, we will update the status.
Thanks,
Nirmal
-
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.
-
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.50 votesWe’re evaluating this as a feature now.
-
Transfer Workflow Ownership (not sending it as a template but as a workflow)
Recently the workflow ownership transfer has been released.
https://support.box.com/hc/en-us/articles/4402945686291-Transferring-Your-Workflow-to-Another-UserHowever, this is to make the template of the workflow that is needed to be transferred.
There is a need to transfer the actual workflow for below reasons:
- the new owner needs to check the past workflow activity but with the template it is not possible
- since it is a template, the new owner still needs to make the workflow
Thank you for your consideration.
40 votesWe definitely want to address this use case (new owner sees past workflow activity) but do not have plans to address it in the near term. We will update when we have a firmer idea of when this can be tackled.
-
Support multi-file for rejected task trigger in Relay
Suppose you like to assign an approval task to a person with multiple files and when the task is rejected, you like to move the package of those “rejected” files to a different folder("Rejected folder) instead of having them sat in the triggered folder.
For a single file, you can create the following workflow containing 2 flows and it works perfect as expected, however it doesn't work for multi-files...
Flow 1: Trigger Manual start-> Outcome: Assign task -> When rejected, the flow is end
Flow 2: Trigger Task -> Outcome: when the task is rejected, move the file to “Rejected…39 votesWe are conducting user feedback sessions to gather more information
-
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.
35 votes -
Allow folders to be uploaded with File Request
File Request is a helpful feature, but often isn't useful as most external parties want to share folders (including sub folders) of documents with us. Can a feature be added to allow folders to be shared as part of File Request - perhaps renamed to Folder/File Request?
33 votesAt this point, there is no short to medium-term plan to extend File Request to accept folder uploads. Please continue to upvote/add feedback so we are able to revisit the prioritization at a later time. Thanks!
-
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
32 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 -
Allow groups to be added as collaborators in Relay “Add Collaborator” outcome
Would be great to be able to add a group of collaborators “Add Collaborator” outcome. Right now only single users are accepted as input.
31 votesWe are conducting user feedback sessions to gather more information
-
Make Workflows Shareable Among Users (Box Relay and Box Relay Lite)
In Box Relay, we can check the progress of workflows in the [Tracking] function.
Currently, only the owner of the workflow, and Admins who are granted to access to workflows can see this [Tracking].However, the progress of workflows within the enterprise should be visible to other users as well.
(e.g. Users who have tasks assigned in the workflow, or Co-Owners of the folder where the workflow is triggered.)It would be useful if the owners could share their workflows to other users.
31 votes -
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 -
Relay：Enable/disable the "Invite assignees as Viewers/Editors" option
A new feature has been added to Relay called "Invite assignees as Virwers/Editors".
Perhaps, it is possible that, due to a mistake, users who should not be collaborating are automatically collaborated with.
However, in the current specification, the checkbox for this feature cannot be changed from enabled.We would like the checkbox to be able to be unchecked optionally.
誤操作により、本来権限を付与されるべきではないユーザーがコラボレートされてしまう可能性があるため、
チェックボックスのチェックを任意で外せるようにしてほしい。26 votesWe are conducting user feedback sessions to gather more information
-
Add "Updated/Changed" File Event as a Trigger
Add "Updated/Changed" File Event as a Trigger.
Triggering a Relay on a specific file when it has been updated directly or updated with an upload, maintaining file history.
The current workaround is to create a "New upload" Trigger, then the file needs to be Deleted and create/uploaded from new, thus requiring 2 steps and losing file history.
25 votesWe are conducting user feedback sessions to gather more information
-
File request - Block upload of domains not on enterprise allowlisted domains
For File Request where Enterprise requires user to login prior to submission, would like an additional security check for Enterprises that only allow for external collaboration from allowed domains as listed in the Enterprise console. If the domain is on the list then allow for file request upload, if domain is not on the allowlisted domains, block upload.
25 votes
- Don't see your idea?