Feature Request here, or elsewhere?

  • 18 November 2020
  • 6 replies
  • 74 views

Userlevel 2

Here are some feature ideas; if i need to post elsewhere or contact our rep, please let me know.

 

On Network Plan 360, being able to set individual heights for access points.

Although if I'm being honest, the individual height part should have been an initial option, and not a feature request.  You may have adjoining rooms, with an AP on the ceiling, and in the other room, it wall mounted and so each ones height would be different.  A global set height isnt helpful when looking at a heat map.

On Network Plan 360, being able to state whether the access point is mounted horizontally or vertically.   We know the RF signal is very different from it being vertical or horizontal:  https://www1.aerohive.com/what-is-the-range-of-wi-fi/ the link may only show horizontally mounted though, but you get the idea.

 

Thanks,

J.

 


6 replies

Userlevel 6
Badge

Hello,

the official and most sustainable way to create a Feature Request is through your sales team (ideally with a business case). The System Engineers will support you in this process. Through them you can also check the progress.

 

In the GTAC user guide you will find the relevant information (https://cloud.kapostcontent.net/pub/c78c8044-2183-4acd-94f3-45e3be2166f4/gtac-user-guide.pdf?kui=jGDahrG0vCQxu0jPkSMG1Q).

 

There is also the possibility to request new features via a GTAC case. But there is no possibility to prioritise and track them.

 

Userlevel 2

Thank you for your quick reply, but……

 

……..“With a business case” This is not about the business need for the feature request, this is about the product, and the flexibility of the product, to deliver accurate and dependable data.  If an AP is mounted one way, the signal will be different than if it was mounted another way, which will affect any data within the insights portion of the interface. The same thing would be true of differing heights between AP’s in different rooms (of the same building). I do not see why a business has to justify its case for a feature request.  I would expect the people behind the product would want it to be the best it could be. 

 

I apologize if I am coming across as a bit “snarky”, its just I am surprised a business has to make a case for this type of feature.  Again, I would have thought this would be an obvious feature that should have been available at the very start of this product; after all we are talking about the way an AP is mounted, and if you have multiple AP’s in different offices that are mounted at different heights.

 

Ill pass along my feature requests to our System Engineer.

 

Thank you,

J.

Userlevel 6
Badge

Hello,

I understand you perfectly. Basically I also feel like you.

 

However, with limited resources you have to consider what to do first and what to do afterwards or not at all.


In a business this means that a decisive factor is the money you can earn more with a feature. I don't like that, but that's the way the world ticks.

Userlevel 2

So very true, sad but true.

Userlevel 2

I’d love to see a system put in place where feature requests are able to be voted on. I’ve seen a lot of tech companies operate this way, and not only does it allow the best ideas to rise to the top, I also believe it promotes creativity and thinking outside the box by getting to see lots of suggestions, and think about which ones would really improve the product.

 

Userlevel 5

I agree John, that is something I’d like to see as well. Without giving too much away, we are working on some new features and opportunities for/within the community, and feature requests and the ability to vote on them are definitely on that list. 

Reply