Idea Details

Correct the destination of the approval request according to the guide

Last activity 18 hours ago
北澤 寿浩's profile image
By: 北澤 寿浩
06-05-2023 08:00

Regarding the operation when "Any approver" is selected in Interact > Create form > Default approval type, the guide says "anyone who is a member of the role will be able to approve any

But actually, approval requests are sent not only to the approvers within the role set on the form, but to all users who have been granted approver privileges. When I asked for the support desk about this point, it was the answer that it is the current specification.

However, when operating Interact in a large-scale organization, even if there is a case where approval is requested to the superior of one's own group, there is no case where an approval request is sent to all approval authority holders within the organization regardless of the group. Therefore, we are unable to use the approval function in actual operation.

Please consider changing the specifications that Approval requests can be sent to any approver within a specific group, such as sending to approvers within the role specified in "Interact role" or allowing the selection of a role to which approval is sent separately from "Interact role" 


Interactフォームの基本設定 > 「デフォルト承認タイプ」で「任意の承認者」を選択した場合、ガイド上は「役割(role)のメンバーであれば~承認できます」と記載があります。



「Interact role」で指定した役割内の承認者に送信する仕様とするか、「Interact role」とは別に承認を送る「役割(role)」を選択できる仕様とするなど、特定のグループ内の任意の承認者に承認依頼が送信されるよう、仕様の変更を検討お願いします。

Ideas Portal

• Like this idea? Tap the up arrow!  Ideas with over 15 votes will be discussed with our product teams in our idea review meeting.
• Discussion is healthy! If you have a question or comment, don’t be afraid to jump in and start a discussion in the comments section below.
• Collaboration is the key to making magic happen!
This idea is new to the community and hasn’t been reviewed yet. While in the New stage, it is particularly important to vote and comment to further the discussion around this idea.
This idea already exists! A change to the Duplicate status will include a comment linking to the existing idea, so all voting and feedback can be collected in one place.
Need More Info
We’ve reviewed this idea, and determined we need a bit more info before deciding on how to move forward. An update to the Need More Info status will be accompanied by a comment explaining which additional details are needed. Ideas are still open for voting and comments while in the Need More Info stage.
We have all the info we need and are planning to review the idea for implementation feasibility and value added to the product. Ideas with this status are still open to community voting and discussion.
Under Consideration
We have all the info we need and are currently considering the feasibility of implementing this idea. Ideas in the Under Consideration status are still open to community voting and discussion.
Not Planned
We’ve reviewed this idea, and determined that it’s not feasible to implement right now. Ideas in the Not Planned status are no longer open for voting.
We’ve reviewed this idea and have determined that it will be delivered in the near future. Ideas in the Planned status are not attached to a binding timeline, but there is a concrete plan to implement this idea.
We’ve reviewed this idea and confirmed that this is planned for delivery in the next 6 months.
Congrats! Your idea has been accepted by the team and is now delivered! Give yourself a pat on the back – you contributed to the improvement of one of Blue Prism’s products or services!