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.
422 results found
-
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.90 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?
82 votesThis is still on the roadmap.
-
"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.
81 votesWe are creating a file request dashboard for Admins to manage their enterprise’s FR links.
-
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.
70 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.
69 votes -
Notifications from Box Relay aren't very useful without linking back to the file or folder
Relay is a great tool - but the Notifications aren't very useful. There is no way to link to the actual file or folder that is involved, so the user gets a very nebulous notification that is basically meaningless. Instead of being helpful, it could actually cause confusion for the user, if there are multiple activities happening at the same time.
Please update this functionality! Thanks!
64 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.
-
Automatic email response for file request submitter
Would like a feature whereby the person submitting files using Box File Request receives an automatic confirmation email with a customizable message. For example, after the submitter uploads files using the File Request web widget, that person gets a email to the effect of, "Thank you for contacting us. A team member will review your submittal and follow up within 24 hours." The person would be required to provide an email address but not required to have a Box account. Many of our external customers send us application materials using File Request, and then they contact us separately wanting to…
48 votes -
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
42 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?
40 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!
-
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.
38 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)33 votes -
Generate Shared Links as a Relay Outcome
Would like the ability to automate generating shared links on files within Box Relay as an outcome. One use case for this would be to create a process for generating external shared links. Many security-conscience customers don't want everyone to have the ability to shared content externally without some sort of approval or oversight. If we added generating and sharing shared links as an outcome in Relay we could build approval flows that would allow users to get approval to share a file externally even if they don't have the access do so.
32 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.
誤操作により、本来権限を付与されるべきではないユーザーがコラボレートされてしまう可能性があるため、
チェックボックスのチェックを任意で外せるようにしてほしい。31 votesWe are conducting user feedback sessions to gather more information
-
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 -
We would like to be able to register a group in the Configure Relay even if the group's permission setting is not "Administrators only"
Currently, when we try to register a group in the Relay configuration, we can register the group if the group's permission setting is "Administrators only", but not if the group's permission setting is "Company" or "Group Members".
Registration location [Enterprise Settings > Content & Sharing > Configure Relay].
We are using "Company" and "Group Member" as the permission setting for groups to be able to respond to group invitations, etc. outside of the management console, so we would like these permission settings to be able to be registered in the Configure Relay.<グループの権限設定が「管理者のみ」以外の場合もBoxRelayの構成でグループを登録できるようにしてほしい>
現在Relayの構成でグループを登録しようとするとグループの権限設定が「管理者のみ」の場合は登録できるが、
「会社」や「グループメンバー」の場合は登録できない。【Enterprise設定＞コンテンツと共有＞Relayの構成】
グループの招待など管理コンソール以外でも対応できるようグループの権限設定を「会社」や「グループメンバー」として利用しているため、
これらの権限設定でもRelayの構成で登録できるようにしてほしい。29 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.
29 votes -
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.
27 votes -
When copying or moving a file via Relay, allow the file to overwrite an existing file of the same name as a version.
If we have a locked down area for SOP type files, as the SOP is updated and approved, a Relay workflow moves the file into the published location. If the published file is the same name as an existing file, we would like to have the new file come in as a version of the prior file, not be named with the date-time stamp on it.
25 votes -
Relay Workflow period Allocations based on work days rather than natural days (i.e Exclude Weekends)
When assigning a task in relay you can assign the period in days associated to the task. at This point in time this does not allow the option to assign such days to working days but only natural days. Therefore if and when a weekend occurs during the timeline of the workflow action weekend days (non-working days absorbs the task timeline. the request is that there must be an option to assign a task only for working days (excluding weekends)
25 votes
- Don't see your idea?