3 results found

1. Enhanced Concurrent Sessions in Portal Connect

   Portal 2 experiences performance issues when executing long-lasting queries across multiple tabs simultaneously, leading to excessive server load. Unlike Flow Client and Studio, which handle concurrent platform usage more effectively, Portal 2 struggles with this multi-tab functionality. This issue needs to be addressed in the upcoming Portal Connect to ensure smoother operations and better resource management.

   Proposed solution is to implement a more proactive approach to managing queries in Portal Connect. This should include mechanisms to optimize and balance server load when multiple queries are run in different tabs by the same user. Consider introducing features such as query prioritization, load balancing, and perhaps a more efficient handling of session data. These enhancements will aim to minimize server strain and improve overall responsiveness, ensuring that users can efficiently work across multiple tabs without degrading performance. This improvement is crucial for maintaining a robust and scalable system as user demands and concurrent operations increase.

   Portal 2 experiences performance issues when executing long-lasting queries across multiple tabs simultaneously, leading to excessive server load. Unlike Flow Client and Studio, which handle concurrent platform usage more effectively, Portal 2 struggles with this multi-tab functionality. This issue needs to be addressed in the upcoming Portal Connect to ensure smoother operations and better resource management.

   Proposed solution is to implement a more proactive approach to managing queries in Portal Connect. This should include mechanisms to optimize and balance server load when multiple queries are run in different tabs by the same user. Consider introducing features such as query prioritization,… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   declined  ·  AdminMalin Johansson (Admin, Novacura) responded

   The backend for Flow Connect is significantly different from Flow Classic, with performance being one of our main areas of improvement. We have introduced features like running the client in the browser and added caching layers. Further enhancements will be made in the future based on user requirements and feedback from Flow Connect users.

   We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

2. Toggles to Retain Table Row Selection and also Refresh Table in Portal 2

   When selecting a row or row(s) in a portlet table and then starting a workflow, the row selected is no longer showing as (gray) selected, making it hard to find what row was just worked with and pulled into the workflow. This may not always pertain to selected rows because some are actually deleted or removed from a portlet table.

   However, a good addition would be to allow for tables in Portal 2 to deselect/not deselect the row and to allow the table to automatically update/not update the table after completing or closing a workflow. These are possibly some things that can be toggled on/off in the table portlet settings titled "Retain Row Selection" and "Auto-Refresh Post Workflow".

   When "Retain Row Selection" is turned on it will not deselect rows in tables, and when turned off (default) it will deselect the rows. When "Auto-Refresh Post Workflow" is turned on (default), it will automatically update or refresh the table data after running a workflow, and when off it will keep the same data as before clicking a workflow button. This could even be added down to the workflow level settings themselves

   When selecting a row or row(s) in a portlet table and then starting a workflow, the row selected is no longer showing as (gray) selected, making it hard to find what row was just worked with and pulled into the workflow. This may not always pertain to selected rows because some are actually deleted or removed from a portlet table.

   However, a good addition would be to allow for tables in Portal 2 to deselect/not deselect the row and to allow the table to automatically update/not update the table after completing or closing a workflow. These are possibly some things… more

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Portal  ·  Delete…  ·  Admin →
   declined  ·  AdminMalin Johansson (Admin, Novacura) responded

   This functionality is already supported by the Table portlet. Configure the primary key setting to ensure the selected row remains selected after an action is performed.

3. Workflow Datasource Ordering in Portal

   When listing workflows for data source in e.g. a table Portlet, the ordering is appearing randomly. Ideally, a selected workflow should be on top and the remaining preferably ordered alphabetically by name given in Studio.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Portal  ·  Delete…  ·  Admin →
   declined  ·  AdminMalin Johansson (Admin, Novacura) responded

   We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

   This is done differently in Flow Connect; the data sources are sorted based on the application package.