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.
70 results found
-
We want to use "YYYY MM DD" format for Box Relay date variables
When entering dates as variables in Box Relay, it is inconvenient that the only formats available are "MM YYYY" or "MM DD YYYY".
We would like to be able to enter the date in the "YYYY MM DD" format.Box Relayの日付変数の形式に「YYYY MM DD」を使いたい
Box Relayで日付を変数で入力する際に、「MM YYYY」や「MM DD YYYY」のなどの形式しかないのは不便です。「YYYY MM DD」の形式でも入力できるようにしてほしい。
20 votes -
Worflow Starter should be the assigner of tasks instead of the creator/owner of Relay Workflow.
A relay workflow is created by one owner but used by several people. Since all the tasks are assigned by the workflow owner rather than the workflow starter, its confusing for assignees. E-mail and task notifications should show the workflow starter's name instead of the owner of workflow.
35 votesWe have delivered this functionality as part of Box Automate.
-
Name in the notification email of Box Relay should be the initiator of a workflow rather than workflow owner/creator.
Currently the name displyaed in the notification email of Box Relay is the name who owned/created the workflow.
It's idal to be displayed Name of initiator of a workflow in the notification email especially in caseunspecified majority of people might launch the workflow by manual.
Enabling the above feature makes it much easier to confirm user who start the flow.28 votesWe have delivered this functionality as part of Box Automate.
-
Box Sign action in Relay
I would like to have a Box Sign action relay.
I expect use cases like once it is approved internally, we move to submit Sign request via Box Sign41 votesWe have delivered this functionality as part of Box Automate.
-
Transfer Workflow Ownership (not sending it as a template but as a workflow)
Recently the workflow ownership transfer has been released.
https://support.box.com/hc/en-us/articles/4402945686291-Transferring-Your-Workflow-to-Another-UserHowever, this is to make the template of the workflow that is needed to be transferred.
There is a need to transfer the actual workflow for below reasons:
- the new owner needs to check the past workflow activity but with the template it is not possible
- since it is a template, the new owner still needs to make the workflow
Thank you for your consideration.
41 votesWe have delivered this functionality as part of Box Automate.
-
Ability to include the name of the triggered file in the subject line when sending Relay notifications
We would like to be able to include the name of the triggered file in the subject line when sending Relay notifications.
We want to be able to easily check which file the notification is for when the user who received the notification receives the notification email.
When a user receives a notification email, I want to be able to easily check which file it is for.
(In Japanese)
通知の相手に割り当てられたユーザーへの通知の際にファイル名を含めた通知を行いたい。
通知を受け取ったユーザーが通知メールを受け取っても、どのファイルに対する通知なのかを
簡単に確認できるようにしたい。25 votesWe have delivered this functionality as part of Box Automate.
-
Tasks in relay are owned by Relay owner rather than workflow initiator
Currently tasks have owner and assignee. The owner is always relay owner, who gets notifications when there are any changes to the task which may not be ideal.
Allow for an option to have the task owner be the workflow initiator instead.
91 votesWe have delivered this functionality as part of Box Automate.
-
File Request Branding EID wide.
Custom branding for file request feature. Ability to apply one custom branding template to the entire EID so that the branding is consistent across the entire enterprise.
25 votesIt is now possible to apply a logo and brand color to File Request webpages.
Please see the below link for more details -
https://support.box.com/hc/en-us/articles/1500002931362-Branding-Your-File-Request
-
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.
43 votesWe have delivered this functionality as part of Box Automate.
-
Create a Box group/alias or ability to select a different name to replace the workflow owner’s name.
I’ve created several Relay workflows across the business and the issue I found is that people are reaching out to me because my name is tied to a task that is assigned to them. Often times, I do not have any context to the workflow so it results in me having to reach out to the person who started/uploaded the document. We want to avoid approvers having to reach out to the workflow owner vs. the actual owner of the program. This process would not be sustainable if it were rolled out to a larger company.
Currently Example: Hayley creates…
117 votesWe have delivered this functionality as part of Box Automate.
-
Support multi-file for rejected task trigger in Relay
Suppose you like to assign an approval task to a person with multiple files and when the task is rejected, you like to move the package of those “rejected” files to a different folder("Rejected folder) instead of having them sat in the triggered folder.
For a single file, you can create the following workflow containing 2 flows and it works perfect as expected, however it doesn't work for multi-files...
Flow 1: Trigger Manual start-> Outcome: Assign task -> When rejected, the flow is end
Flow 2: Trigger Task -> Outcome: when the task is rejected, move the file to “Rejected…43 votesWe have delivered this functionality as part of Box Automate.
-
Conditional fields on File Request form
It'd be great to be able to have conditional fields in the File Request form so that certain fields are only exposed depending on the answer in the field(s) above.
9 votesConditional fields is now available in Box Forms (New). Please see the below link for more details. https://support.box.com/hc/en-us/articles/38272339986707-Introducing-Box-Forms
-
Relay lite: allow admin to change the workflow owner
Box Relay creates a workflow (Folder creates a task that requests invoice processing and is used to manage outstanding tasks) that enables clerical employees to process invoices more efficiently. However, when the employee is transferred, the workflow that has been created is not transferred to the next person in charge. If a useful workflow can be managed as a company, not as an individual (Change the workflow owner for contact changes), it will be very useful for business efficiency.
73 votesWe have delivered this functionality as part of Box Automate.
-
relay assign workflow
When a user leaves the company, the admin (or the user) should be able to assign his workflows to someone else. So far, the admin can only deactivate a workflow. We have cases where the relay workflow has 46 steps and if the owner leaves the company, the job is lost. It is a waste of time. As well, folder problems should be highlighted if the user is replaced, thus allowing either the assignment of permissions to the folder(s) or the ability to switch to new folder(s).
22 votesDelivered – Admins can now assign a new workflow owner when deprovisioning a user
-
3 votes
Users can change the classification via an outcome in the relay builder
-
Add "remove collaborator" option as option in a Relay workflow
In the same vein as being able to Add a collaborator as part of a Relay workflow, it would be nice to also Remove a collaborator as well. Customer would like to Add a collaborator as part of a workflow, have that collaborator do their part, then have them removed as they no longer need access to the content going forward.
19 votesThanks all for your patience on this feature.
We have not delivered this feature. Please refer this article for more details: https://support.box.com/hc/en-us/articles/360044628853
-
Allow users to share built workflows
Allow workflow builders to share their workflows with each other. Currently workflows need to be rebuilt by each user whereas it would save a lot of time to be able to share these workflows that have already been built.
37 votesWorkflow Ownership Transfer is currently live with our existing Relay full customers, Enterprise, and Enterprise Plus customers.
-
Notifications as a Relay workflow outcome
Add the ability to create a specific notification as an outcome/step in Relay.
I.E. "If step 2 of workflow is not complete after 5 days notify xyz person"
or
"once workflow is completed notify this group".
11 votes -
Relay workflow sharing across users
As far as I can tell, only the person who has created the Relay workflow has access to the workflow and I can't share the workflow I have already created with one of my colleagues. As a result, if he wants to start a new workflow using the same flow that I had built, he has to start over as I can't share mine with him. This is a really basic function you need to create ASAP if you want adoption with Relay.
20 votesWorkflow Ownership Transfer is currently live with our existing Relay full customers, Enterprise, and Enterprise Plus customers.
-
Transfering ownership of Relay workflow
If a workflow "owner" isn't functioning within the process where he is responsible for the flow anylonger (He is still within the organisation and so should not be decommissioned), Relay should allow transfer of that specific workflow to another member of the team rather can creating a new workflow.
1 voteThe ability to transfer your workflow to another user is now available. Please refer to this article for more details: https://support.box.com/hc/en-us/articles/4402945686291-Transferring-Your-Workflow-to-Another-User
- Don't see your idea?