Is there a way to make the legacy custom property editor as the default one for everyone

Hi Everyone,

I recently updated to the latest orion platform, after ages with an older version that has always been impossible to update due to lack of maintenance windows for orion.

That said, I saw the new custom property editor and immediately switched back to the legacy one since we rely a lot on custom properties, and the new one is basically not usable for us.. my setting unfortunately applies only to me, all other users are finding the new one.

I noticed that my switch to legacy adds a row for my user in the database:

CPManagement_UseLegacyPage to true in the user settings

but the row is not even there for other users..so instead of injecting things manually..is there a way to make the legacy one as the default one for everyone?

Thanks.

Find more posts tagged with

custom property editor

legacy

2020.2.6

Accepted answers

All comments

tony.johnson

Thank you for the feedback, I'm sorry to hear the new CP editor does not meet your needs. Our intention was to have parity with the classic editor, can you elaborate on how you use the classic editor and how the workflow differs in the new editor? As you identified the setting is on a per-user basis, there is no global override.

LDave

Thanks for your answer... maybe a global "default" settings for everybody can be a nice addition.. then everyone can change his preference, but the initial situation should be decided/reset by the admin at a global level for me.

As for how the workflow differs:

Basically when we add one or more device that is the same type of already existing devices and/or shares the plant (and thus many properties) with devices already in the db, we use the custom property editor as an excel worksheet:

We can copy one full existing node row over another and then change the few properties that differ, or we can copy pieces of a row (i.e. 4/5 properties at a time) or we can copy one property and paste it, in a single step, over multiple devices and so on... all in a couple of clicks.

It was already a bit cumbersome since the keyboard arrows started to control the scroll instead of the cursor on the cells, but we were able to use it anyway.

The new one instead doesn't appear to even allow multiple property selection / copy and paste.. but also for a single property, the copy/paste is not immediate: with the selection of a property you access to the content, then you will have to select all the content, copy it, select the second device cell, eventually select everything in here too if you need to override the existing content, and then paste the value.. what was a single gesture before, it is now many, to be repeated as many times as the number of properties per node you need to copy and that is a deal breaker for us.

As a further feedback I also tried the new "manage entities" instead of manage nodes, and also that one, after a brief first look, seemed to lack something very basic, gaining a complex but powerful filtering ability:

On manage nodes I can search for a node or a set of nodes and then I can just see all the resources of the nodes right there in the results, by pressing the small arrows on the side of the nodes, and then I can manage those right away, i.e. I can delete multiple volumes from multiple nodes at the same time and with few clicks.

I can also change polling engine of multiple selected nodes, or place a maintenance on multple resource at the same time, being those nodes, volumes, interfaces or a mix of everything.

On the manage entities instead, I'm not able to do the same because:

- it doesn't list volumes amongst the related entities of a node.

- it does not have polling engine association.

- it does not have maintenance mode / rediscovery and so on for interfaces (nor volumes, since volumes are not there)

plus it is slower

I like the way you can filter on mutiple levels with ease even if it is slightly more slow as a process, though, before you could have filtering on any custom property added to the manage node table result, it was very nice for easy filtering, but didn't allow for "multiple levels / combination" of filtering, so that could be a nice addition.

Thank you.