Business Automation Navigator: make the desktop default feature configurable in Platform and Content mode

Environment
CP4BA version: 24.0.1
Navigator: 3.1.0, build icn310.0802.4
Navigator mode: Platform and Content (navigatorMode 2)
Configuration database migrated from IBM Content Navigator on traditional WebSphere
Reference system: IBM Content Navigator 3.2.0 container without CP4BA, navigatorMode 0

Current behavior
In the desktop configuration, Layout tab, the field "Default feature" is not shown when the Navigator runs in Platform and Content mode. The row exists in the template ecm/widget/admin/templates/DesktopFeaturesPlatform.html, but it is hard coded with class dijitHidden.

When an administrator saves a desktop in this mode, the desktop type changes from "default" to "platformContent". From then on the getDesktop service returns the first entry of the displayed features as defaultFeature. The value stored in the configuration database is ignored.

In IBM Content Navigator without CP4BA (navigatorMode 0) the field is visible and mandatory, and the stored value is used.

Problem
Customers who move from IBM Content Navigator on traditional WebSphere to CP4BA expect their desktops to behave the same way. After the first save of a migrated desktop the start feature changes without any message. Users then land in a different feature after login.

The only way to control the start feature is to move it to the top of the feature list. That also changes the order of the icons in the navigation bar. Customers who want the start feature in a different position than first cannot configure that anymore.

Requested change
1. Show the field "Default feature" on the Layout tab in Platform and Content mode.
2. Use the stored default feature at runtime for desktops of type platformContent, the same way it works for desktops of type default.

If the current behavior is intended, please document it in the CP4BA documentation and in the migration guide for the Navigator configuration database.

Reference
The IBM technical document "IBM Content Navigator Configuration database migration" (support page node 7013537) tells customers to select the Navigator mode Platform and Content "to ensure the content capabilities from the traditional deployment are retained". In the step "Update desktop type for existing desktops" it tells them to change and save every existing desktop so that the desktop type changes from default to platformContent. The document does not mention that this step changes the start feature of the desktop.

Business impact
We operate more than 40 desktops for different business units. Several of them start with a feature that is not the first entry in the list. Every one of these desktops needs manual rework and user communication after the migration. The missing field also leads to support requests because administrators look for a setting they know from the traditional installation.

IBM IDEA 2

Title
Business Automation Navigator: keep ClassicNavigatorLayout selectable in Platform and Content mode, or warn before it is replaced

Product
IBM Cloud Pak for Business Automation, Business Automation Navigator (IBM Content Navigator)

Environment
Same as Idea 1

Current behavior
In Platform and Content mode the layout list on the Layout tab does not offer ecm.widget.layout.ClassicNavigatorLayout. The function _populateLayoutDropDown adds this layout only when the Navigator is not in a platform mode.

When an administrator opens a migrated desktop that uses ClassicNavigatorLayout, the admin client selects ecm.widget.layout.NavigatorMainLayout instead and marks the desktop as changed. If the administrator saves the desktop for any reason, the layout is replaced. There is no warning.

Problem
Migrated desktops lose their layout as a side effect of an unrelated change. Administrators do not notice it because the layout field already shows the new value when the desktop opens. On our development system 21 of 45 desktops use ClassicNavigatorLayout.

Requested change
1. Offer ClassicNavigatorLayout in the layout list in Platform and Content mode, at least for desktops that already use it.
2. If the layout is not supported in this mode, show a warning when such a desktop is opened and do not mark it as changed until the administrator confirms.
3. Document the restriction in the migration guide for the Navigator configuration database. The guide tells customers to save every migrated desktop once. It does not mention that this replaces ClassicNavigatorLayout. The sample desktops in the guide are even named ClassicDesktop.