Settings and activity
17 results found
-
16 votes
-
26 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
An error occurred while saving the comment -
2 votes
-
7 votes
We are happy to inform you that development work has begun on your requested feature. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.
-
2 votes
-
13 votes
-
4 votes
-
5 votes
-
7 votes
We are happy to inform you that development work has begun on your requested feature. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.
-
9 votes
The feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.
-
2 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
9 votes
James Good
supported this idea
·
-
24 votes
The feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.
James Good
supported this idea
·
An error occurred while saving the comment
James Good
commented
Requesting an expansion of the Flow Server messaging functionality to support targeted communication beyond global message sends to Portal. While acknowledging the utility of global targeting, there's a strong need for more precise messaging options such as targeting specific Flow user IDs, user roles, and user workflows. This enhancement would significantly empower communication in multi-user setups, providing greater flexibility and efficiency in message delivery within the Flow environment.
-
9 votes
James Good
supported this idea
·
-
2 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
52 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
James Good
supported this idea
·
-
5 votes
James Good
supported this idea
·
Currently, end users can be grouped, but all users with access to a Page can see all Applications on that Page, including Applications they may never use.
In Classic, workflows could be added to multiple menus, and menu visibility could be controlled for different users or roles. This allowed the same workflow to be available in multiple places while controlling which users actually saw it.
We would like similar functionality for Applications, allowing visibility to be controlled by user group or role at the individual Application level. This would allow Pages to contain Applications for multiple user groups while ensuring each end user only sees the Applications relevant to them, rather than requiring separate Pages or Packages to manage visibility.