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.
341 results found
-
Workflow max linking job folders to different jobs
Workflow max linking job folders to different jobs I have a screen shot evidently this can be done with suite files
2 votes -
don't show files till all the files are uploaded
I often send files to coworkers and I dislike that the file is downloadable to them before it's actually fully downloaded to box. This ends up creating a corrupt/ non-workable file for them. Also I think the files should not show up on their end before all the files are completely downloaded, in batch uploads because I will have coworkers then say only some of the files are downloaded and it looks like a mistake when it's just still uploading. Thanks!
2 votes -
File Request expiration
Due to security concerns, we have implemented an enterprise setting for shared link expiration. We would like to be able to do this with File Request links as well, but that is not a configuration option available. Would it be possible to add this functionality?
4 votes -
Allow enter date for tasks within a workflow
Today the initiator of the workflow can enter recipients for a task outcome, but cannot specify date. This is very limiting in case the tasks should be completed by a certain date that can only be known by the initiator.
I have a use case for a highly valuable workflow, but because of this missing capability it cannot be implemented.
I believe that adding this capability make a lot of sense and would make the use of tasks in workflows much more powerful.1 vote -
Allow enter date for tasks within a workflow
Today the initiator of the workflow can enter recipients for a task outcome, but cannot specify date. This is very limiting in case the tasks should be completed by a certain date that can only be known by the initiator.
I have a use case for a highly valuable workflow, but because of this missing capability it cannot be implemented.
I believe that adding this capability make a lot of sense and would make the use of tasks in workflows much more powerful.0 votes -
Relay outcome based on File Type
Use Relay to take actions on files based on file type - e.g. ability to create a workflow that if X file is uploaded to a folder and is a .JPG, the outcome would be to add Z metadata or copy the file to Y folder, etc.
1 vote -
Change a specification of the PST time given when conflicting item's name on Box Relay.
Currently, no matter what timezone users/enterprise set in its settings, the PST timestamp will be added to the item's name when conflicting name on Relay.
The specification will be changed to add the date and time depending on the user/enterprise settings.
10 votes -
Copy file in workflow should create a new version if file already exists
I am creating Quality Management workflows. At the end of the workflow the released document is copied to a new area, that is shared with the consumers of the QM-documentation.
Works fine the first time we run the workflows. If we update the document and run the workflow again, the target file is not versioned: we get a new file with the same name and a timestamp added to it.
I appreciate this behaviour in some situations and understand why you have chosen this solution. However we would like to have the option in the workflow to "version the file,…
7 votes -
Make Workflows Shareable Among Users (Box Relay and Box Relay Lite)
In Box Relay, we can check the progress of workflows in the [Tracking] function.
Currently, only the owner of the workflow, and Admins who are granted to access to workflows can see this [Tracking].However, the progress of workflows within the enterprise should be visible to other users as well.
(e.g. Users who have tasks assigned in the workflow, or Co-Owners of the folder where the workflow is triggered.)It would be useful if the owners could share their workflows to other users.
31 votes -
File Request User Configuration - error messaging
When configuring File Request for "enable for select users", users remain in the list even if they have been deleted from Box. If you try to add a new user to the list, you will receive an error message. The reason for the error is because a deleted user is still in the list, however the error is a standard message and does not explicitly say this. So customers do not know why they are getting an error. There should be clearer messaging in the error so customers know what they need to do.
1 vote -
1 vote
-
Relay Workflow to follow messages/ notifications to activities
It would be super helpful if you could use Box Relay to let a notification follow an activity. I know that you can generate tasks, but in that case I just want to let a certain group of users know that there is new content in a folder. A notification would be the best way to do this.
1 vote -
create folder while making workflow
Allow users when they are building a relay workflow to have the ability to search through a folder structure and create a new folder when they are building a new flow.
This would eliminate the issue of users having to have a predefined folder structure before making the workflow and make it significantly easier to use.
1 vote -
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.
19 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 -
Transfer the workflow ownership of the existing user
Currently we are not able to transfer the workflow ownership, while the user is active?(I know we can transfer when the admin delete the user)
When the user moved to the other department and we want to transfer the workflow to his/her teammates, before he/she leave the department.
2 votes -
Add more functionality to the 'submitter authentication' option for file requests.
＜Background＞
A new security option has been added to file requests.
This is a feature that forces the user to login to the Box when we upload from a file request.Link：https://support.box.com/hc/en-us/articles/360056763373
＜Request＞
Add a "Require Two-Factor Authentication" option to this feature.
We believe this is a necessary feature to make security more robust.■ファイルリクエストの「送信者の認証」オプションに機能の追加
＜背景＞
ファイルリクエストに新しいセキュリティオプションが追加されました。
これは、ファイルリクエストからアップロードする際に、ユーザーにBoxへのログインを強制する機能です。リンク：https://support.box.com/hc/ja/articles/360056763373
＜ご要望＞
この機能に「二要素認証を必要とする」オプションを追加してください。
これは、セキュリティをより強固なものにするために必要な機能だと考えています。4 votes -
File request: add the ability to pre-populate fields
It would be great if there would be a way to pre-populate the fields of a file request with "known-information" if available.
This would allow us to reuse a single file request in a portal, but set the metadata on the uploaded documents, based on the current user's context. Content can then be routed in the Box system based on the metadata set.
4 votes -
cascading auto-start workflows
cascading auto-start workflows. We have a specific use case defined that would greatly benefit from this capability - shield classification being applied automatically alerts the uploader of the file that the content needs to be moved. This would be a big win for USAA
5 votes -
Box Relay: Action to move file to a folder named after Metadata attribute value
Currently, you can have a trigger based on a Metadata condition. We would like to be able to have the outcome File Action to move the file to a folder that is named based on this Metadata value.
For example, if there is a Metadata template with an Attribute called "Organization" with a possible value of "HR", then you could have a workflow to trigger when the metadata template is applied and the workflow outcome would move the file to a folder titled "HR".
For another example, you could use a metadata template containing a date field and then move…
3 votes
- Don't see your idea?