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.
15 results found
-
External Notification Support
Allow for notifications to be sent to external (non-box users) partners, vendors, submitters, etc as part of an automate workflow.
Box Forms and File Request allow for seamless ingestion of content and metadata but does not allow for an easy way to update those submitters after their document has been ingested. Many times there is a formal internal review process where a submitter would want to receive an email notification as the document or application moves through the review process inside of Box.
Example use cases: notifying an external submitter that their submission has been rejected after an internal approval…
17 votes -
Task Feature in Box Automate
In the current Box Automate, the Task outcome fails when the folder or enterprise setting is "Only folder owners and co-owners can send collaborator invites", which we understand is officially stated on the Box Support page.
However, many companies in Japan use this configuration, making the Task feature in Box Automate practically unavailable.Our understanding was that Box had initially stated the existing Box Relay features would remain available after the upgrade to Box Automate. If that is not the case, this may impact customers’ existing business operations, which we consider to be a concern.
We would like to request…
14 votes -
We want to apply classification labels using Automate without granting Editors permission to change labels
In Relay, we had a workflow where users would manually trigger a workflow, assign an approval task, and upon approval, automatically change or assign a classification label. This was done to assign a label indicating that the content is ready for public release, enabling external sharing.
However, this cannot be achieved with Automate workflows. Upon checking the specifications, we found that unless the Admin Console allows Editors to modify classification labels, Automate workflows cannot assign labels. In our organization, we have only permitted Co-owners and Owners to change labels. If we allow Editors to change labels, general employees would be…
6 votes -
Reference loop variables in a conditional branch within the loop in Box Automate workflow
In a Box Automate workflow, when looping through files, we need to be able to run conditional checks on values/properties of the file within that loop.
Potential use case: a user may want the workflow to ignore certain file types, or to only run Box AI Agent operations on certain files.
Currently, many variables can be referenced within the "conditional split" element within a "loop" element, but not the loop variables themselves.
5 votes -
ability to select a source folder and have the outcome automatically include all subfolders
In Box Automate, I created a custom extract agent and selected a source folder. However, after reviewing the run history, I noticed that only the files in the top-level source folder are processed, while files in subfolders are ignored. I would like the ability to select a source folder and have the agent automatically include all subfolders within it or give you the option to include them.
We currently have a couple scenarios where we would like to run extraction on existing files and folders in a parent folder retroactively, not just new uploads.
Thank you, and please let me…
3 votes -
Allow api.box.com in Box Connectors for HTTPS Request steps in Automate workflows
Please allow the HTTPS Request step in Box Automate to make requests to the Box API (api.box.com).
There are many things not currently supported natively by Box Automate steps which could be solved if the HTTPS Request step/outcome were allowed to consume the Box API.
For example:
- generate Box access tokens
- get file EXIF data from Box representations API
- lock files
- create shared links
- get number of files in a folder
- get file path
- create shared link passwords
- applying metadata cascade policies
- metadata extraction on a group of files (rather than…2 votes -
Loop through folders in a folder, and other lists of IDs/strings in a Box Automate workflow
hi team. any thoughts on when we'll be able to loop through folders?
(the ability to loop over files in a folder is good, and would be even better if we could have that within a loop that loops over folders)
some use cases:
customers wanting to process files (i.e. move, rename, MDE) in folder trees, involving multiple levels of folders in the tree, and some but not all folders should be included excluded
customers wanting to bulk process folders - e.g. loop through folders in folders in folders, and then move/delete empty folders
loop through folders and validate certain…
2 votes -
"File that triggered the flow" variable is unavailable in Box Automate.
In Box Automate, when implementing a process triggered by a file request and selecting "Move" as the "File Action," the "File that Triggered the Flow" variable is unavailable as the file to be moved.
This variable is available in Box Relay and can be used for purposes such as distributing the triggered file to a specified folder.
Without this variable, Box Automate is clearly inferior to Box Relay.
We hope that the "File that Triggered the Flow" variable will be made available soon.
2 votes -
Increase the Maximum Number of Actions per Box Automate Workflow
{English}
We would like to request an increase in the maximum number of actions that can be executed within a single Box Automate workflow.Currently, the limit is 200 actions per workflow execution. However, based on real customer business requirements, some workflows are reaching this limit and cannot be fully implemented within the current constraints.
Increasing the limit to approximately 2,000 actions would address these use cases and enable customers to automate larger-scale business processes without requiring complex workarounds or workflow redesign.
This request was submitted based on customer feedback.
====
{Japanese}
Box Automateワークフローで一度に実行できるアクション数の上限拡張を希望します。現在、1回のワークフロー実行で利用できるアクション数は200に制限されています。しかし、実際の顧客業務要件を考慮すると、この上限に達してしまい、実現できないフローが存在します。
上限を2,000アクション程度まで拡張いただけると、このようなユースケースに対応でき、大規模な業務プロセスをワークアラウンドや複雑なフロー分割なしで実装できるようになります。
本要望は顧客からのフィードバックに基づくものです。
1 vote -
File Outcome Actions for Form Uploaded Files
Include the ability to take file actions on files uploaded from a Box Form like you can in Relay. We have several Forms and Relays that not only take text/date/dropdown input but also have file upload fields and were hoping to move them to Automate so that we could take advantage of the additional features, but are unable to since there is no option to use an Outcome to take action upon the uploaded files.
1 vote -
Regarding how to handle abnormal termination in BoxRelay
I would like to be able to forcibly terminate "in progress" tasks that have been interrupted due to an error in BoxRelay.
1 vote -
Signer Verification in Box Automate
Request to have a configurable option in an automate workflow to require a pre-defined signer verification method when sending a signature request from automate. Ex: Form is submitted, document is generated, document is sent for signature and user is required to sign with CAC/PIV card, use 2FA, etc.
1 vote -
About Automate's sharing settings
If sharing for "Automate" is disabled in the admin console, please deactivate the "Sharing" setting.
1 vote -
I’d like the workflow error messages to include specific details about what the problem is.
Now that BoxAutomate has been released, I’m really excited about all the new possibilities it will unlock inside Box.
However, with the current specifications, when an error occurs in a workflow, a message is displayed, but it doesn’t tell us what exactly went wrong.
With things the way they are, it’s impossible for us to fix the workflow on our own. It’s like being told, “Something’s broken… somewhere… good luck!”
To enable users to fix errors by themselves, we’d like the error messages to clearly specify the detailed points where the problem occursワークフローでエラーが発生した場合、メッセージが表示されるが、具体的にどこが問題なのかが分からないです。
これではワークフローを自分たちで修正することもできません。
ユーザーが自分でエラーを直せるように、エラーメッセージには詳細なポイントを明記してほしいと考えています。1 vote -
Allow for Duplication of Automate Workflows and Creation of Automate Templates
Currently, Relay has the ability to duplicate workflows, but Automate does not. We can also create templates for Relay workflows, but not for Automate. Automate should have the same capabilities.
1 vote
- Don't see your idea?