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.
424 results found
-
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を利用した承認タスク実施時に、コメントを記載する機能がありません。
メールやメンション機能を現在は利用しておりますが、不便なため、承認時または却下時にコメントを入力する機能が欲しいです。
承認時や却下時にコメントがあることで、ユーザーへの意思疎通ができますので、機能として追加をいただけますと幸いです。24 votes -
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.…
24 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 -
We want BoxRelay to work with the privileges of the user who actually started the workflow, not the user who created the workflow.
In the current specification, workflows in BoxRelay operate under the authority of the user who created the flow, not the user who executed the flow.
This causes confusion because there is a discrepancy with the actual operation performed. We would like to improve this so that Relay can correctly confirm who started the flow.【日本語】
BoxRelayについて、ワークフローを作成したユーザーではなく、実際にフローを開始したユーザーの権限で動作させたい現在の仕様では、BoxRelayのワークフローは、フローを実行したユーザー本人ではなく、フローを作成したユーザーの権限で動作するようになっています。
これでは実際に行われた操作と齟齬があり混乱を招くため、フローを開始した人が誰なのか、Relay側で正しく確認できるよう改善を希望します。20 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…20 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.
20 votes -
We want to make it easier to change the owner of a workflow in Box Relay.
In Japan, organizational changes and personnel transfers occur frequently, which necessitates changing the owner of workflows in Box Relay.
Currently, to change the owner, users have to transfer the workflow to another user and disable the original workflow.This process is not intuitive and is cumbersome for users. Additionally, there are too many steps involved. As a result, even though Relay is a good feature, it feels difficult to use and does not gain user adoption.
We would like to see improvements that allow for a one-click transfer of ownership.
For example, adding an option to change the owner in…19 votes -
Box Relay outcome to Apply Classification to a folder dynamically
It would be helpful if Box Relay would have the ability to apply a classification to the folder where the workflow was triggered on dynamically as an outcome, which would also classify all content within that folder structure as well. This would allow applying classifications to the folder that a new file event trigger happened in for example, which would then flow classifications to all content and sub-folders in that folder structure.
18 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.
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 -
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 -
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.
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…16 votesThanks for your feedback. We’re exploring introducing new cascading triggers or system-wide workflows which would address this issue.
-
"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 workflows15 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…
14 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.
14 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.
14 votes
- Don't see your idea?