Group Banner widget's navigation items are not affect by page header revert

Info:

- Verint version 11.1.8.16788

- Browser Chrome 93.0.4577.63

- OS Win 10

Issue:

Group  Banner widget's navigation items are not affect by page header revert

Steps to reproduce:

1. Create any new group

2. Open group banner for edit

3. Add any prefix to widget title (e.g. test)

4. Add any link to navigation items (e.g. test)

5. Publish changes

6. Check that changes to widget title and navigation items are applied

7. Revert current page header to factory default template and publish changes

Expected behavior

- Group banner options, widget title and navigation items, should be reset to factory default values

Actual behavior

- Only group banner widget title is being reset to original factory default value, but a "test" item in navigation items stay there and could not be reverted



Fixed mistake in description
[edited by: Eugene Shulga at 9:00 PM (GMT 0) on Tue, Sep 14 2021]
Parents
  • In the Revert dialog, before selecting a region to revert, try specifically selecting the Navigation Item customization from the list of customizations.

  • Hi Steven, 
    Thanks, your solution solved the described issue
    But now we encountered another issue

    We have a non-Social theme (site+group+blog) that we are distributing through /filestorage XML files, and it's loading into Verint server as factory default theme
    So when we want to change anything in a factory default page templates, we first do changes directly to page template on a Verint server and publish them as "custom" changes
    Then we export these templates as XML files, and put needed XML page template pieces into a /filestorage/factorydefaultpages on Verint server
    Then we goes to any group, opens factory default page editing and doing revert for all templates
    That usually works ok for us

    Now we noted, that it looks that when we do a Group banner navigation items changes, and trying to apply them with a procedure I described - it not being applied

    For me it looks like that Navigation items are not properly included into template, I don't sure

    e.g. here specific example, we were trying to remove a "Files" navigation item that were pointing to a Media Gallery, but we still see it even if we do factory default theme header revert with Navigation items option checked

    Here is a piece of resulting group template header

    <theme name="00ec0001bb9041c288cc63c14b3070ba">
      <defaultHeaders>
        <contentFragmentHeader layout="HeaderTopContent" themeType="c6108064-af65-11dd-b074-de1a56d89593" lastModified="2021-08-26 10:05:39Z">
          <regions>
            <region regionName="Header">
              <contentFragments />
            </region>
            <region regionName="Content">
              <contentFragments>
                <contentFragment type="Telligent.Evolution.ScriptedContentFragments.ScriptedContentFragment, Telligent.Evolution.Platform::ab92f9a89af24721bba1c464c1334be6" showHeader="False" cssClassAddition="no-wrapper responsive-1" isLocked="False" sourceConfiguredContentFragmentId="1533311608" configuration="fragmentHeader=%24%7Bresource%3AGroups_GroupBanner_Name%7D&navigation=%3Cnavigation%3E%0D%0A%20%20%3Clinks%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Controls.SingleGroupCustomNavigationPlugin%2C%20Telligent.Evolution.Platform%22%20id%3D%22ad164b2a370c415bbc34a89e1380c6a3%22%20configuration%3D%22group%3DGroup%253D0%26amp%3Blabel%3DHome%26amp%3BloadedFor%3D459%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Blogs.Plugins.CustomNavigation.GroupBlogsCustomNavigationPlugin%2C%20Telligent.Evolution.Blogs%22%20id%3D%22113e18ef8b6b41f4baf146ee9a38e829%22%20configuration%3D%22group%3DGroup%253D-1%26amp%3Blabel%3D%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Forums.Plugins.CustomNavigation.GroupForumsCustomNavigationPlugin%2C%20Telligent.Evolution.Forums%22%20id%3D%22bfc84935bef1446495b965b82930e643%22%20configuration%3D%22group%3DGroup%253D-1%26amp%3Blabel%3D%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Wikis.Plugins.CustomNavigation.GroupWikisCustomNavigationPlugin%2C%20Telligent.Evolution.Wikis%22%20id%3D%2213b28afcc6ee48eab4a25b8e96bfb3e6%22%20configuration%3D%22group%3DGroup%253D-1%26amp%3Blabel%3DDocuments%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Calendar.Internal.Controls.CustomNavigation.GroupCalendarsCustomNavigationPlugin%2C%20Telligent.Evolution.Calendar%22%20id%3D%2200afa562c81447d79c7973aca9a0fc09%22%20configuration%3D%22group%3DGroup%253D-1%26amp%3Blabel%3D%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Element14SE.DesignChallenge.Plugins.DesignChallengeApplicationType%2C%20Element14SE.DesignChallenge%22%20id%3D%22ab9c01b780454e19b456eb2b7be88971%22%20configuration%3D%22groupid%3D459%26amp%3Blabel%3DDesignChallenges%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Element14SE.RoadTests.Plugins.RoadTestItemApplicationType%2C%20Element14SE.RoadTests%22%20id%3D%221fb488199dfb449fb0a517fe53b90469%22%20configuration%3D%22groupid%3D459%26amp%3Blabel%3DRoadTests%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Element14SE.RoadTests.Plugins.RoadTestReviewApplicationType%2C%20Element14SE.RoadTests%22%20id%3D%2244e576382c204487bfa0834cd469a234%22%20configuration%3D%22groupid%3D459%26amp%3Blabel%3DReviews%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Ideation.Plugins.GroupIdeasCustomNavigationPlugin%2C%20Telligent.Evolution.Ideation%22%20id%3D%22c2bcd53b03ba4b2898a156d5f125bcee%22%20configuration%3D%22groupid%3D0%26amp%3Blabel%3D%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Controls.SingleGroupMembersCustomNavigationPlugin%2C%20Telligent.Evolution.Platform%22%20id%3D%2238d7c7a3003e45068ffb6babcd808246%22%20configuration%3D%22group%3DGroup%253D0%26amp%3Blabel%3D%2524%257Bresource%253ASingleGroupMembersCustomNavigation_DefaultLabel%257D%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Controls.SingleGroupMentionsCustomNavigationPlugin%2C%20Telligent.Evolution.Platform%22%20id%3D%22e8d35e3efcda4a1a81f626aa8d54c966%22%20configuration%3D%22group%3DGroup%253D-1%26amp%3Blabel%3D%2524%257Bresource%253ASingleGroupMentionsCustomNavigation_DefaultLabel%257D%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Controls.SingleGroupSubGroupsCustomNavigationPlugin%2C%20Telligent.Evolution.Platform%22%20id%3D%22f7f94714d50142e0aa4c6f8e2da4735e%22%20configuration%3D%22group%3DGroup%253D0%26amp%3Blabel%3D%2524%257Bresource%253ASingleGroupSubGroupsCustomNavigation_DefaultLabel%257D%22%20%2F%3E%0D%0A%20%20%20%20%3Clink%20type%3D%22Telligent.Evolution.Controls.SingleGroupTagsCustomNavigationPlugin%2C%20Telligent.Evolution.Platform%22%20id%3D%22e6f3ad0a2e0a4ff2b68589e1f470d2c3%22%20configuration%3D%22group%3DGroup%253D0%26amp%3Blabel%3D%2524%257Bresource%253ASingleGroupTagsCustomNavigation_DefaultLabel%257D%22%20%2F%3E%0D%0A%20%20%3C%2Flinks%3E%0D%0A%3C%2Fnavigation%3E&includeParent=True&includeAvatar=False&includeNewLogin=True&inheritNarrow=True&inheritNarrowAppTitle=True&designMode=color&paletteId=white-orange&coverPhotoUrl=&coverPhotoLayout=cover&coverPhotoFixedHeightHome=176&coverPhotoFixedHeightOther=88&coverPhotoLayoutDynamicHeightMode=defined&coverPhotoLayoutDynamicDefinedWidth=1500&coverPhotoLayoutDynamicDefinedHeight=375&coverPhotoAlignment=center%20center&coverPhotoBackgroundPaletteId=&blurCoverPhoto=False&shadowCoverPhoto=True" />
              </contentFragments>
            </region>
          </regions>
        </contentFragmentHeader>
      </defaultHeaders>
      <!-- other XML was not included -->
    </theme>

  • The process you describe will not work for scoped properties such as navigation items. Scoped properties are not read from the factory default files.

  •  

    We are using an automated pipeline for code distribution, it deploy XML files and plugin DLLs automatically from source code repository, to multiple instances where changes need to be applied

    Is there any way to automate scoped property changes distribution?

  • Scoped properties are read when an XML file is imported. If factory default files are deployed directly (without calling an import API) to the centralized file storage location, an import does not occur and any scoped configuration properties will not be applied.

    When automating page, header, footer deployments, it may be better to use the UI Automation API (  UI Automation ) instead of deploying XML files directly. Since you're already deploying DLLs, one of those could define an installable plugin ( IInstallablePlugin Plugin Type )  that could handle updating the UI.

Reply Children