Hello, I would like to know how the "Evolve Instance" functionality works. For that, I performed the following test:

1. I inserted 5 Installations nodes under a Manufacturing Assembly. All these Installation nodes were inserted working under a ChA 1, with applicability from January 1st to Infinite, so that they inherited this effectivity due to I added Configuration Model, set the Criteria by Date and activated the Change Required for the parent (Manuf Assy)
2. Then, I completed the ChA 1 and created ChA 2, with applicability from February 1st to Infinite.
3. I evolved the PPCMI 1.1 instance and then tried to save it --> It worked
4. Then, I tried to set the PPCMI 1.2 as Input for the PPCMI 2.1 --> It worked
5. Then, I tried to set the PPCMI 3.1 as the Input for PPCMI 2.1 . However, this time, when I performed the action of changing the precedences, the tool automatically evolved the PPCMI 2.1. Then I tried to save, but I was unable to do so. Therefore, I manually evolved the PPCMI 3.1, whose instance is still controlled by the ChA 1 and then tried to set the PPCMI 3.2 as the Input for PPCMI 2.2  --> Now it worked.
6. By setting the PPCMI 4.1 as precedence for PPCMI 3.2, the tool does not allow you to save. Because of that, I manually evolved PPCMI 4.1 and then set the new PPCMI 4.2 as the input for PPCMI 3.2 --> Now, it works
7. The same thing mentioned in the step above happened with PPCMI 5.1.

Conclusions: The logic behind the "instance evolution" remains unclear due to inconsistent tool behavior. Specifically, I observed that step 4 was completed without any manual evolution, yet the tool automatically evolved PPCMI 2.1 during a subsequent action. Furthermore, this automatic evolution did not occur in later steps, making the process unpredictable.