Details

    • Improvement
    • Resolution: Won't Do
    • Major
    • xCM 6.1.0
    • xCM 6.0.0
    • None

    Description

      Scenario :
      --------------
      Create a page Rubrique
      Create 3 sub pages page 1, page 2, page 3.
      Publish All
      Change manually the order of the 3 pages or with the automatic ranking the behavior should be :
      Rubrique page worflow status become red and all sub pages still green

      With the 18633 build the behavior is : (1 out of 2 is ok)
      ---------------------------------------------------
      Change manually the order of the 3 pages :
      Rubrique page worflow status become red and all sub pages too

      Change with the automatic ranking :
      It's the right behaviour, rubrique become red and sub page still green

      With the 18785 build the behavior is : (none is ok)
      ----------------------------------------------------
      Change manually the order of the 3 pages :
      All the pages become red including rubrique

      Change with the automatic ranking :
      All the pages still green

      TestRail: Results

        Attachments

          Activity

            [JAHIA-2464] Sort and worflow Status

            Discussed in pm-dm (https://jahia.slack.com/archives/CNRFEDYHX/p1728046393480479), closing, as Inactive, all issues that were last updated before January 2023 (22 months ago).
            Please re-open if necessary

            fgerthoffert@jahia.com Francois Gerthoffert added a comment - Discussed in pm-dm ( https://jahia.slack.com/archives/CNRFEDYHX/p1728046393480479 ), closing, as Inactive, all issues that were last updated before January 2023 (22 months ago). Please re-open if necessary

            Currently the handling is as follows:

            1) The container list gets into the "staging" state after you click on the "OK" button - there is no detection, if anything was or was not changed

            2) For manual sort, the rank is a part of a field value, i.e. when the sorting is changed, a new version of the field value (in stanging) is created. It is not possible to update the rank in the live version (as the changes will be applied immediately).

            I would postpone it to the time point, when the container list properties will also support workflow (if we will do it, otherwise I will work on a possible solutions).

            shyrkov Sergiy Shyrkov (Inactive) added a comment - Currently the handling is as follows: 1) The container list gets into the "staging" state after you click on the "OK" button - there is no detection, if anything was or was not changed 2) For manual sort, the rank is a part of a field value, i.e. when the sorting is changed, a new version of the field value (in stanging) is created. It is not possible to update the rank in the live version (as the changes will be applied immediately). I would postpone it to the time point, when the container list properties will also support workflow (if we will do it, otherwise I will work on a possible solutions).

            Having discussed this behavior with Stephane, the best would be that:

            _ For an automatic sort, everything stay green as it is immediately applied to live mode. It would also be nice to display a message in engine when an automatic sort is selected to inform the editor that changes will be immediately applied to live mode
            _ For a manual sort, only the container list (i.e. the mother page in current example) become red status, so that we don't have to validate each child page in case of subpages sorting, what can force to validate some content we don not want to.

            dsaulnier_old Damien Saulnier added a comment - Having discussed this behavior with Stephane, the best would be that: _ For an automatic sort, everything stay green as it is immediately applied to live mode. It would also be nice to display a message in engine when an automatic sort is selected to inform the editor that changes will be immediately applied to live mode _ For a manual sort, only the container list (i.e. the mother page in current example) become red status, so that we don't have to validate each child page in case of subpages sorting, what can force to validate some content we don not want to.

            If another behaviour is desired, we need to elaborate it as an improvement (please open a separate JIRA issue in this case)

            shyrkov Sergiy Shyrkov (Inactive) added a comment - If another behaviour is desired, we need to elaborate it as an improvement (please open a separate JIRA issue in this case)

            The bahaviour described in the MIN-372, is currectly (according to actual Jahia design and implementation) is the correct one, i.e.:

            1) using automatic sorting

            • the sorting is stored in the container properties.
            • changing sorting (automatic) --> changes the workflow status of the container list (parent page in case of a navigation link container list)
            • sorting order is the same in live and edit mode --> changes are immediatelly visible

            2) using manual sorting

            • sorting (rank) is store in each container
            • the workflow status of each container and of the container list is changed (parent and child pages in case of a navigation link container list)
            • sorting order is applied to live mode only after approving the modifications
            shyrkov Sergiy Shyrkov (Inactive) added a comment - The bahaviour described in the MIN-372, is currectly (according to actual Jahia design and implementation) is the correct one, i.e.: 1) using automatic sorting the sorting is stored in the container properties. changing sorting (automatic) --> changes the workflow status of the container list (parent page in case of a navigation link container list) sorting order is the same in live and edit mode --> changes are immediatelly visible 2) using manual sorting sorting (rank) is store in each container the workflow status of each container and of the container list is changed (parent and child pages in case of a navigation link container list) sorting order is applied to live mode only after approving the modifications

            I have corrected one issue, that was a side-effect of JAHIA-2380 fix

            shyrkov Sergiy Shyrkov (Inactive) added a comment - I have corrected one issue, that was a side-effect of JAHIA-2380 fix

            On the current nightly build (18785) the workflow status is not changed (parent and child pages) either using manual sort nor an automatic sort.

            There is a known issue in Jahia (a design issue). The container sorting is stored as properties and does not get any workflow status (there is no difference between live and edit mode), so the container and container list workflow status do not get changed when changing the sorting.

            shyrkov Sergiy Shyrkov (Inactive) added a comment - On the current nightly build (18785) the workflow status is not changed (parent and child pages) either using manual sort nor an automatic sort. There is a known issue in Jahia (a design issue). The container sorting is stored as properties and does not get any workflow status (there is no difference between live and edit mode), so the container and container list workflow status do not get changed when changing the sorting.

            People

              shyrkov Sergiy Shyrkov (Inactive)
              srouaud_old Stéphanie Rouaud (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                TestRail: Runs

                  TestRail: Cases

                    Packages

                      Version Package
                      xCM 6.1.0