2 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

   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. Make it possible to simulate an API when you want to limit access to the backend system for deveopers

   Pretty often you have either sensitive data in your backend system OR you only have access to a production API OR you have connectivity issues to the backend system.

   Furthermore, in Connect we have to develop apps in Dev for deployment to Test and Prod and thereby need to have connectors set up in all environments.

   To mitigate this situation and to make it possible having Developers developing app on systems like those above, an API simulator would be a nice solution.

   Suggestion to build support for API simulation like https://apisimulator.io.

   ALSO, this would be very useful for our internal use

   With the APi simulator we could create tests that can run without the need for a connection to a provider (IFS, M3 etc.) We could run these tests in the azure pipeline when releasing new versions, both service and built in. This would also be a very useful tool when investigating bugs, since we would be able to save server api calls from the api simulator in a yaml format, that we can then run in different versions of the connector in order to determine when and where the issues started.

   (Last part stolen from the Flow Classic team....)

   Pretty often you have either sensitive data in your backend system OR you only have access to a production API OR you have connectivity issues to the backend system.

   Furthermore, in Connect we have to develop apps in Dev for deployment to Test and Prod and thereby need to have connectors set up in all environments.

   To mitigate this situation and to make it possible having Developers developing app on systems like those above, an API simulator would be a nice solution.

   Suggestion to build support for API simulation like https://apisimulator.io.

   ALSO, this would be very useful for our… more

   1 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  ·  Connectors  ·  Delete…  ·  Admin →
   declined  ·  AdminPaul Phillips (VP Product Management, 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.