Uploaded image for project: 'Transactional Activation'
  1. Transactional Activation
  2. MGNLXAA-40

Recursive activation leaves stale content at mgnlSystem

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 1.2.3, 1.3.2
    • None
    • None

    Description

      When you're about to activate a child, so that its parent has to be created by the receive filter explicitly, this child is removed properly when commit/rollback, however the parent stays there. It affects both the situations when you're about to activate the content for the first time, as well as if you're about to update the existing content. This can introduce inconsistencies to any next activations to the same parent tree.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                ochytil Ondrej Chytil
                zdenekskodik Zdenek Skodik
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD