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.
25 results found
-
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…
20 votes -
Enable processing in folders with editor permissions in Box Automate
Currently, due to Box restrictions, if the option “Limit sending invitations to collaborators to folder owners and co-owners only” is enabled for a folder specified in an Automate flow, and the flow owner specifies a folder to which they have been invited as an editor, errors will occur for “task assignments, file operations, and folder operations,” causing the process to fail.
Many companies allow co-owners and higher-level users to be invited, but if that were the case, it would significantly reduce usability under the current system. Therefore, I would like the workflow to function properly even when folders with editor…
16 votes -
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 -
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 -
Enable Metadata Cascading when using the Add Metadata outcome
Description
Allow users to enable metadata cascading when applying the Add Metadata outcome to a folder. This should be a user-selectable option in the workflow builder (for example, a simple "Enable metadata cascading" checkbox for this outcome).
Business Value
Many document-centric processes follow the same pattern:
- A user submits a request through a form.
- A workflow automatically creates a dedicated folder for that request.
- Documents related to the request are uploaded into that folder over time by multiple users.
While workflows can already create the folder and assign metadata to it, there is currently no way to enable metadata cascading…
5 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 -
"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.
4 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…
4 votes -
Request to Make Service Accounts Created During Box Automate Use Easier to Identify
When a workflow is created and saved in Box Automate, a service account is created (e.g., InternalPlatformUser1234567ABCDEFGHIJ@boxdevedition.com).
However, at present, it is difficult to determine whether this account was created as part of using Box Automate, making it hard to distinguish it from a suspicious user that may have been created maliciously.
Therefore, we would like the service account (e.g., InternalPlatformUser1234567ABCDEFGHIJ@boxdevedition.com) to be made more easily identifiable as an account created for the use of Box Automate.
For example, after a workflow is created in Box Automate, we would like a pop-up to be…2 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 -
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.
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 -
Automate Outcome Based on Metadata Field Change
We would like an Automate outcome based on a change to a metadata field that was assigned in a previous outcome. An example would be in an HR recruiting workflow when the Role Stage metadata field changes to BC Complete a Send Notification outcome fires notifying applicable teams, HR, IT, Manager, etc. to begin preparations for the new employee.
As it stands now, the only way we've found to do this is by assigning a task to the recruiter.
The issue is that there are always multiple positions being worked at any given time and some positions take weeks or…1 vote -
Enable Metadata Cascading and Autofill on Folders
It would be very helpful to have the ability to enable cascading and autofill on folders when a metadata template is added as an outcome. In our case, we create new folders for each new position requested and being able to automate the process of applying a metadata template to files added to the folder and then have the metadata populated would be save a lot of time and effort for our HR team.
1 vote -
Box Doc Gen Outcome Doesn't Keep Values
Using the Doc Gen outcome in Automate, we've found that when a change is made to a Doc Gen template, an update to the workflow outcome is required. This is expected behavior. However, performing that update causes all previously assigned field values to be cleared, requiring the user to manually reassign each one — even when the template change had no effect on any variable or field mapping.
We have several Doc Gen templates with more than 50 fields, and a few exceeding 70. Reassigning all values each time a minor change is made is not practical at scale. Until…1 vote -
workflow notification send to groups
Be able to send automation workflow notifications to groups instead of individual email addresses
1 vote -
Automate - Variables not accessible outside of loops
Extracted variables can only be referenced inside the loop they were created in, forcing extraction and application steps to run per-file inside the loop. For batch uploads (e.g. 60 images) this extends run time to 15-20 minutes and consumes excess AI units.
1 vote -
Automate - Send e-signature requests to non-managed users
Signature steps in Automate can only send to managed users. External signers are not supported even though Relay supports this, blocking external signing workflows end to end.
1 vote -
Workflow Management Report
The new Automate features are much more powerful than the previous Relay, and I’m excited to start using them going forward. After enabling Automate, I expect many users will create workflows, so the number of workflows in a tenant will increase significantly.
Currently, I can visually check the workflows created in a tenant from the admin console, but as the number of workflows grows, it becomes difficult to review them all and properly manage them.
It would be very helpful to have a way to export or list all workflows that exist in a tenant.
Example fields:
Workflow name
Creator…1 vote -
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
- Don't see your idea?