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
-
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 -
Box Sign action in Relay
I would like to have a Box Sign action relay.
I expect use cases like once it is approved internally, we move to submit Sign request via Box Sign23 votes -
Be able to specify a document or a shared link in “Send Notification” outcome
It would be convenient if the “Send Notification” outcome had an option to specify a document or a shared link in the notification body.
Right now it is only possible to input plain text.
23 votes -
Have Docusign integrated with Relay
Use Relay+Docusign to manage contract approval process
23 votes -
Ability to include the name of the triggered file in the subject line when sending Relay notifications
We would like to be able to include the name of the triggered file in the subject line when sending Relay notifications.
We want to be able to easily check which file the notification is for when the user who received the notification receives the notification email.
When a user receives a notification email, I want to be able to easily check which file it is for.
(In Japanese)
通知の相手に割り当てられたユーザーへの通知の際にファイル名を含めた通知を行いたい。
通知を受け取ったユーザーが通知メールを受け取っても、どのファイルに対する通知なのかを
簡単に確認できるようにしたい。22 votesWe are conducting user feedback sessions to gather more information
-
Relay：Users who have already been invited in a group will not be invited with "Invite assignees as Viewers/Editors"
[Background]
A new feature has been added to Relay called "Invite assignees as Virwers/Editors".
"Invite assignees as Virwers/Editors" are sent to users who have already been invited in the group.
This is confusing because additional invitations are carried out to users who have already been invited.
Furthermore, operationally, this requires the collaboration to be removed from the relevant file each time.
*As a company rule, we are not allowed to collaborate with individuals individually, except in groups to which they have been previously invited by Admin.[Request]
Users who have already been invited to a group should not be invited.…
22 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.
20 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の構成で登録できるようにしてほしい。19 votes -
Relay: Involve external Users to a manual workflow as "not-owner" of the folder/file
Hi,
i discribe a situation:
The Admin is the owner of all folders/files, directors has co-owner-rights and all employees are editors. It is similarly discribed in "Folder Structure Best Practices" under "Business Unit Drive"
Now we invite some external users... not only the owner can invite them.
Then we create some relays for specific folder, especially some manual ones, assign a task and set the Assignee to "Specify at startup"...not only the owner can do this.
Last but not least we start the manual workflow and choose as Assignee an external user... but wait...ONLY the owner of the folder (1…19 votes -
API for "CRUD" for Box Relay and Box Relay Lite
We have created over a hundred of Relay workflows and have currently faced a difficulty in adjusting all rules when our orgnization is changed. We would like to have a set of APIs for Relay for creation, reference, update and delete operations (so called CRUD).
Also we would like to have an way to update folder ID(s) on existing workflows. It would help so much especially when annual org change happens.
19 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!
18 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.
18 votes -
Allow service accounts to initiate Relay workflows via the Box API
Allow service accounts to own and initiate Relay workflows via requests to the Box API
17 votes -
Ability to comment on Box Relay approval tasks
Currently, there is no function to enter comments when executing approval tasks using Box Relay.
We are currently using email and the Mention function, but this is inconvenient, so we would like to have the ability to enter comments at the time of approval or rejection.
Having a comment when approving or rejecting a task will help us communicate with users, so we would appreciate it if you could add this as a feature.
現在Box Relayを利用した承認タスク実施時に、コメントを記載する機能がありません。
メールやメンション機能を現在は利用しておりますが、不便なため、承認時または却下時にコメントを入力する機能が欲しいです。
承認時や却下時にコメントがあることで、ユーザーへの意思疎通ができますので、機能として追加をいただけますと幸いです。17 votes -
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.
16 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 -
Box Relay Trigger "Update File"
Currently there is no "file update" in the Box Relay trigger.
If you upload a file with the same name in Box, it will be saved as a new version of the existing file instead of a new upload.
There is currently no trigger to trigger in such a case, so it would be nice to have a "update file" trigger.現在BoxRelayのトリガーには、「ファイルの更新」がありません。
Boxにて同じ名前のファイルをアップロードすると、新規アップロードではなく既存のファイルの新しいバージョンとして保存されます。
そのような場合に発動するトリガーが現在ないので、「ファイルの更新」トリガーがあれば嬉しいです。13 votes -
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.
13 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.
- Don't see your idea?