2 results found

1. Better Agent Traffic Management

   As a customer, I would like to be able to push a certain amount of traffic to an agent within an agent group. As an example, I can have 2 agents in an agent group for prod. When updating Agent 1, before updating Agent 2, I would like to push 75% of the traffic to Agent 1. This would allow me to see that the Agent is working adequately before updating Agent 2.

   1 vote

   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.

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 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.