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
-
Box Automate: Support for “Form Metadata Template”
When a large number of metadata fields are captured via Forms, mapping each variable to metadata fields within the workflow becomes time-consuming and complex.
It would be highly beneficial to support applying metadata to files using a “Form Metadata Template,” similar to Relay, to simplify workflow creation.
formsで入力するメタデータフィールドが多い場合、ワークフロー内でフォームで取得した変数をメタデータフィールドにマッピングするのに手間がかかってしまいます。
Relayと同様に「Formメタデータテンプレート」を使ってファイルにメタデータを付ける操作もサポートしてほしい。3 votes -
workflow
Hi, I was wondering if we could revert the workflow for sharing folders with other users. There was a recent UI/UX update that changed my Box such that when I share a folder with someone, it doesn't auto-populate my cursor in the "Invite People" field, and after typing the name of the person I'd like to share it with, pressing enter or tab does not select the person. The old Box used to highlight the first person that matched what you typed. Once the person is added, I also have to click "Send" manually instead of being able to press…
1 vote -
Revert UX for creating folders
Hi, I was wondering if we could revert the workflow for creating folders. There was a recent UI/UX update last week that changed my Box such that when I create a folder, it doesn't auto-populate my cursor in the "Name" field, and after typing the name of the folder, pressing enter does not create the folder.
It was very smooth when I was able to click "new folder," immediately type the name of my folder, and then press enter to immediately create it. Now, I have to either click the "name" field directly or press tab before I'm able to…
1 vote -
Create a New Folder Bugs - cursor not in text box, no return to create
Sometime in the last month, there was a UI update with Box that changed how creating a New Folder functions. Now, when creating a new folder, the cursor does not start in the name box, so you have to manually click into the box to start typing. Secondly, you can no longer press enter/return to create the folder; you have to drag your cursor and click the "create" button. This combination has been a frustrating change for seemingly no reason. Renaming a folder still automatically lets you type in names and press return to create, so it's definitely an accidental…
1 vote -
Create folders in bulk by a specific destination folder using Relay at run time.
Hello,
As an example for you: our practice uses box.com for our architectural packages. Currently when we want to create a new project folder with specific names and sub folders we have to duplicate an existing set of folders and rename them all then move them to a new location.
It would be helpful if Box Relay could let users choose a destination folder in Box at run time as part of a “Project folder creation” workflow.
For example, during a form submission (or via a simple pop-up), the user could browse/select where the new project folder—and its standard subfolders—should…
1 vote -
Scheduled Metadata-Based Automation for Document Lifecycle Management
Today, Relay workflows are primarily event-driven and lack the ability to run on a recurring schedule to evaluate metadata conditions.
For knowledge management use cases, it would be highly valuable to support:
Dynamic metadata setting on approval
When a knowledge article is approved, automatically set a “Next Review Date” based on configurable offsets (e.g., +30, +60, +90 days)Scheduled Relay execution
Ability to run a workflow on a recurring basis (e.g., daily)
Evaluate metadata fields such as “Review Date” or “Expiration Date”Conditional actions based on date evaluation
If Review Date = Today, trigger actions such as:
Notify knowledge manager…1 vote -
Add collaborators as viewers/uploaders
I have created a workflow to apply to files that need signatures and approvals. If all I needed was approvals, automatically adding the assignees as viewers is fine. I need signatures as well so it would be nice to choose to add the assignees automatically as viewers/uploaders so they can also sign the document.
1 vote -
Allow Forms driven dynamic destination folder in Relay Folder Action
In Box Relay, the Folder Create outcome requires selecting a fixed destination folder. While Forms data can be used for folder naming, it cannot be used to dynamically set the parent folder (for example, from a submitted Folder ID field).
Allow Relay to set “Where should the folder be created?” using a variable/token from trigger data (e.g., Box Forms field), including support for folder ID and optionally folder path.
This limitation forces teams to build custom middleware/services just to translate form input into folder creation logic. Native support would remove extra engineering overhead and enable fully no-code workflows for common…
1 vote -
I want to reuse the content entered in File Request as a task message
We are running tasks in a Relay workflow, triggered by uploads via File Request.
In Box’s current specifications, the “file description” entered by users in the File Request form is saved in the file’s description field in its properties after upload.
However, when the Relay workflow starts, the message sent to the task assignee is the one configured in Relay. This message is recorded under the file’s “Activity,” but we also need to check the description field in the file properties, which means switching views and creates extra work.
If there were a feature that allowed us to set the…
3 votes -
Export Relay Workflows as a JSON file, and use JSON file for updating workflows
Some customers have a large number of Relay Workflows that can be cumbersome to edit or update if changes to internal processes are made that affect a large number of flows. Having the option to download the JSON and edit that file, then reupload the JSON can allow them an easier way to make changes to existing workflows with bulk edits.
2 votes -
from Box Folder (Filtered) View - Start Box Relay
Most of solutions would need filtered data for example, to track the status of any document or request, one would need Status field to track the progress and showing user a filtered view is necessary. From same view, if relay can be initiated would be highly appreciated.
1 vote -
Add New Trigger under Signing Events for "Reassign Request"
There are times when our users would like a recipient, who is not part of the signing chain, added as a CC if a document is reassigned to a different signer. It would be nice to have a new trigger option under Relay/Workflow /Signing Events for "Reassign Request" where, if a document is reassigned, we could add an Outcome that would Send a Notification to a particular acct.
1 vote -
Display of account name when approval task or Box Relay creator user is deleted
After an account is deleted, the user who created an approval task is displayed as "Previous Collaborator," making it impossible to verify the approval status at that time. Please change this so that the username from that time continues to be displayed even after the account is deleted.
＝＝＝
アカウント削除後に承認タスクを作成したユーザが「以前のコラボレータ」と表示されてしまい、当時の承認状況を確認できないため、アカウント削除後も当時のユーザ名が表示され続けるよう変更してください。5 votes -
Request to automate shared link generation upon file upload
A customer regularly uploads files into multiple folders (with different locations and hierarchy levels) and then has to generate a shared link for each file. Currently, they need to create each link manually, which is quite time-consuming.
It would be very helpful if features such as Relay could automate this process by automatically generating shared links for uploaded files and sending notifications with created links
1 vote -
Display by name, Alphabetical as a Default. Necessary for our business!
It is 100% Necessary for our file Storage and Sharing needs for files to show up alphabetically BY DEFAULT. We just transferred over from Dropbox, and this is really annoying and a waste of time to have to set viewing each time we log in, and when we share files to have to explain to customers how to set their display. Display by name alphabetical should not only be an option, but a Default. Please make this available immediately. Our business model and client sharing workflow success depends on this. Thank you for implementing right away
1 vote -
Share multiple files at once
Currently, you can only share one folder/file at a time. Not a smooth process.
1 vote -
Enable the selection of permissions when "Specify when started" is chosen in Relay task assignment
When creating a workflow that is started manually in Relay, if you select [Assign a Task] as the result and turn on [Specify when started], the default permission for inviting assignees is fixed to Viewer.
Changing the permission to invite the person in charge to an editor every time when starting manually is cumbersome, so I would like the option to select editors as the default when creating a Relay.-in Japanese-
手動で開始するワークフローをRelayで作成するとき、結果で[タスクの割り当て]を選択し[開始時に指定する]をオンにすると担当者を招待する権限のデフォルトがビューアーで固定されてしまいます。手動で開始するときに、都度担当者を招待する権限を編集者に変更するのは手間なので、Relayを作成するときに編集者をデフォルトとして選択できるようにしてほしい。1 vote -
create pdf in relay
I'd like to be able to generate a PDF of a file when approval is complete as the final workflow step, so the pdf version can be sent to the customer.
1 vote -
Prevent LFO from occurring due to Box Relay
When running folder actions (copy/move/delete) in Relay workflows, if the source or destination folder contains a large volume of content, that folder may become subject to LFO, causing files to be locked and preventing other users from accessing them.
Therefore, when a user attempts to configure a flow with a folder that could be subject to LFO, we want to prevent unexpected LFO by clearly indicating on the flow creation screen that the workflow cannot be created due to LFO—for example, by displaying an error message or making the folder unselectable.
〈Box RelayによるLFOの発生防止〉
Relayのワークフローでフォルダアクション（コピー／移動／削除）を実行する際、コピー元またはコピー先のフォルダに大量のコンテンツがあると、そのフォルダがLFOの対象となり、ファイルがロックされて他のユーザーがアクセスできなくなる場合があります。そのため、LFOの対象になり得るフォルダをフローに設定しようとした時点で、フロー作成画面でエラーメッセージを表示する、または該当フォルダを選択不可にするなどの対策により、「LFOの影響で当該ワークフローは作成できない」ことを明確にし、想定外のLFO発生を防ぎたいと考えています。
8 votes -
Visualizing Template Usage and Deletion within the Tenant
In Box Relay, users can publish the workflows they create as templates, allowing other users within the tenant to use them.
However, when we want to delete templates that haven’t been used within the organization for a long time, we have to ask the original creator to unpublish or delete them, which is cumbersome.
If unnecessary workflows remain, the interface becomes cluttered and administration becomes difficult.These issues can be resolved by surfacing templates that haven’t been used for an extended period within the tenant and allowing administrators to unpublish or delete them.
We request a feature in the Admin…4 votes
- Don't see your idea?