Content Server Perspective Manager -- Bug in Shortcut Group Widget

Steven_Knoll · 2021-09-27T20:49:26+00:00

There was an error rendering this rich post.

Hi Everyone,

In CS 20.4, 21.1, 21.2, & 21.3 on Windows Server -- several of our customers are facing the same bug that OpenText support is unable to reproduce. Can you please check your environment and let me know if you face the same issue with "Volume Fallback" rendering as a text field when it's supposed to be a drop-down? This can be reproduced in all supported browsers (i.e. Chrome, Firefox, Edge) under Standard Widgets: Shortcut Group.

The admin help describes Volume Fallback should be a drop-down selection, not a text field.

Access this page in your environment here: ?func=perspectives.perspectivemgr

ISSUE in Shortcut Group:

NO issue in Single Shortcut:

Thanks,

Steven

Find more posts tagged with

Comments

Nizar Ghazal

Hi Steven,

Taking a look at the current main build:

The textfield in the Shortcut Group is what will appear when you're using legacy ActiveView Perspectives.

The drop-down is what will appear in the Shortcut Group when you're using the new Perspective node type ( Created in 20.2 ).

In your development/test environment, you can easily toggle between the two with:

UPDATE KIni SET IniValue = 'false' WHERE IniKeyword = 'UseNewPerspectiveNodes'

To go to AV Perspectives.

UPDATE KIni SET IniValue = 'true' WHERE IniKeyword = 'UseNewPerspectiveNodes'

To go to the new Perspective type.

Bounce services (because this is registered on startup), and notice that if you go to ?func=perspectives.perspectivemgr, any Perspective created will have a different icon depending on if it's an AV or a Perspective. Also, you may see this Shortcut Group has a different fallback field. :-)

Additionally, you can append &debug=true to it, so you're served the unminified js, if you're having a look.

Just having a quick look to see why the Shortcut Group is doing this, though. Each one of these widgets has each of its fields/attributes and descriptions (ie: tooltips) determined by the widget manifest in their particular csui bundle.

On a side-note, to perform the proper migration FROM AV TO Perspectives, you'll go to ActiveView Administration -> Convert ActiveView Perspectives

Hopefully, run it all successfully, etc. Then Convert ActiveView Perspectives will disappear from the admin index, and you're on the new node type, now. No going back.

Toggling KIni is for the developer types.

Thanks,

Nizar

Nizar Ghazal

So, I think it's a bug. Have converted it and told Support my decision.

I read through the support request that support logged for you, and I think it's abundantly clear that we need some sort of icon to indicate what type of Perspective Manager you're on. They weren't able to repro because they were using a new vanilla CS system, which is definitely not going to initialize with ActiveView Perspectives. :-)

I logged LLWR-15821 for the icon.

Nizar Ghazal

I should also add as a final caveat: we've released a few Perspective Manager hotfixes before, if any of your environments don't align to what I see in the main build, it might be because of that.

Take a look to see if any of your patches say "LLWR" and have anything to do with Perspectives. The JS that runs the AV Perspective Manager is distinct from the new Perspective Manager.

Off the top of my head, the only other thing that affects the type of Perspectives being used is if you used Transport Warehouse for system setup.

If you try to transport old AV Perspectives in, with new Perspectives in the system, it'll tell you off with a warning.

If the system is completely fresh with no configuration, if I recall correctly, it toggles to the transported node type.

Steven_Knoll

@Nizar_Ghazal thanks so much for your response and the message funneled downhill to our ticket. Setting the value to TRUE resolved our issue and I agree with the idea to leverage an icon indicator. Thanks for logging LLWR-15821. Nice work!!

Steven_Knoll

Thanks, OpenText

https://knowledge.opentext.com/knowledge/llisapi.dll/kcs/kbarticle/view/KB19015821