Network Atlas Update?

stuartd Great info here - appreciate you sharing these details. 

1) Right angle and curved connections: Agree with your statement here. It is not as easy of a task as one might think but we will do our best to get that incorporated for a future release. 

2) Simple Migration Utility: We will certainly look into this. I think it should be very feasible to create Orion Map Projects with the name of the old Atlas Map with all the entities pre-populated. Perhaps we can take that further, we will have to see.  

3) Improved Group Details behavior and pages or a mechanism to incorporate custom map widget: This is well understood also, thanks for added detail. 

4) Maps and Permissions: With your current setup, I do not foresee any issues but be sure to test and share what updates you would like to see.  

Thank you jblankjblank some comprehensive answers there - let me address the key ones, but yes, I think we are going to need to deploy a test bed to see what's what with this version.

1. I don't have any specifics I can think of, but you mentioned one that is good to have, curved and angled lines. Is it absolutely necessary? Possibly not, but a good number of our maps would start to become unwieldy / unusable with just straight lines.

2. That 'tool' sounds like an excellent option and would be most welcome here.

3. For my role, at present, I am mostly concerned with maps but I do get involved with other aspects such as group pages, nodes, etc. So yes, not having group or node deatils the same across all would be a welcome option. As an example, I'd like to deploy a Top 10 per parent group (for parent group read client) so we can see the top 10 for that sub-section only. Our current Top 10 gets dominated by shared kit which most of the time is working well within capabilities but shows as a Top 10 just because.

4. Specifically we would need to control who can or cannot edit maps.We'd want all to be able to see and utilise any map created. Currently in 2019.4 the majority of users cannot edit pages, add / delete widgets, etc and neither can they access Atlas (plus the link to d/l it is removed).

stuartd 

The only way for you to know is to honestly test it out. There are certainly features that may not make it in the newer version. Unfortunately that is just the case sometimes. I think we have also made some significant improvements in many areas that Atlas was never going to have the chance to do. 

Questions:

1. Does it now replicate all that Atlas could do? JB - Truthfully this is a bit of a broad question. Orion Maps does a number of things that Atlas could never hope to do, or make it easier to do than Atlas could.  I will say one of the things I really want to be able to do is provide users with the ability to manipulate connections to right angle or curved lines and that has not yet been implemented as of this release. Beyond that, you will need to share what is an absolute must have that you cannot accomplish in Orion Maps.  
2. Is there anyway to take what's in an Atlas map and 'migrate' it? Sadly I'm goign to guess no there isn't.  JB - Your guess is correct. It would take years to likely get close to what you are hoping would happen from migrating an Atlas map to an Orion Map. Likely it still wouldn't fit the bill.  However it may be relatively simple to provide a quick tool that creates an Orion Map with the specific entities in it. Would that be enough? You would have all your maps and all the nodes/ connections, which would leave you with adjusting the aesthetics of the map. Interested in your feedback.
3. Of prime importance is the issue with assigning specific maps to specific groups now solved? i.e the map is not assigned globally. JB - this is a well understood issue, but is this really limited to maps? I would assume that a welcome change would be that Group Details pages are not stuck being the same view across all groups so that users could add any widget to a group and not have it propagate to others automatically. Is this the case, or it just a map? Would this apply to node details as well?  
4. Will Orion maps editing be controllable on the permissiosn front? JB - there will not be granular permissions for every control. In essence, anyone has the ability to create their own maps. These are there maps, and can be shared via the Share button, or by placing the map in a widget on a public view. Administrators have the ability to see all maps by all users. What are you specifically needing?  

jblankjblank 

@pseudocyber @JaroslawLadyga @stuartd Please take a look at the latest Orion Maps release - An Orion Map to Success!

So I took a look, and yes, it looks very nice. Buuuuuuut, I'm also a little concerned about the deprecation note on 2020.2 RC page without knowing that Orion Maps will now do all we need. Essentially, it has to be able to replace Atlas and it would be really nice if it could migrate maps across from Atlas - having just spent some weeks (literally) building 1000's of maps, I'm not looking forward to havign to update / recreate them all.

So, questions that arise for me are:

1. Does it now replicate all that Atlas could do?
2. Is there anyway to take what's in an Atlas map and 'migrate' it? Sadly I'm goign to guess no there isn't.
3. Of prime importance is the issue with assigning specific maps to specific groups now solved? i.e the map is not assigned globally.
4. Will Orion maps editing be controllable on the permissiosn front?

pseudocyber JaroslawLadyga stuartd 

Please take a look at the latest Orion Maps release - An Orion Map to Success! 

li-migration 

Are you truly working on upgrading / fixing Network Atlas or are you just going full tilt into 'Orion Maps' beta, which, for us, and as I've described on the page is far, far, far from ready to be used.

For those of you interested in new Mapping capabilities, I would encourage you to try the new Orion Maps Beta available through the NPM, NTA, and SAM Beta Forums.

Still actual request for defaults (my request from 2012):

1. default font and font size
2. default line style, thickness and color
3. default Graphic Image - not only led; as well default image for a specific machine type
4. default for child status - switch off or on
5. default background for labels

I Linux version would be useful!

This is something we are working on.  There is a similar thread here: