The capability to do Stack Changes for a Configured Structure has been available for awhile, but there seems to be a miss on how to actually implement. I've encountered many customers' deployment where one of their biggest heartache is Stack Changes for a Configured Structure that is locked under Change Control. Since the customers were not aware of how to do Stack Changes, they incur a lot productivity loss by doing change and approval one at a time. The customers' goal is to be able to move fast by planning ahead several Model Version revisions. They want to allow for concurrent updates so that engineers don't have to wait to take turn making and applying changes.

The example below explains in using Change Dependencies to streamline performance of business needs for Stack Changes.

Initial data setting:

• "Physical Product00001764 revision A" with Evolution Effectivity of "Model Version Full Car Assembly-A to Infinity".
• Change Action named "CA-83754613-00000052" with Applicability defined as "Model Version Full Car Assembly-B to Infinity"
• Change Action named "CA-83754613-00000053" with Applicability defined as "Model Version Full Car Assembly-C to Infinity".

In the image below, you can see that I'm replacing "Physical Product00001764" revision A with B using Change Action named "CA-83754613-00000052" and concurrently replacing revision B with C using Change Action named "CA-83754613-00000053".  The goal is to have:

• "Physical Product00001764 revision A" available for "Model Version revision A" evolution as shown in row 1's "Projected Evolution" column.
• "Physical Product00001764 revision B" available for "Model Version revision B" evolution as shown in row 2's "Projected Evolution" column.
• "Physical Product00001764 revision C" available for "Model Version revision C to infinity" evolution as shown in row 3's "Projected Evolution" column.

You cannot achieve the above stacking changes without using dependencies.  Please refer to the following link for similar guidance:  https://r1132100503382-eu1-3dswym.3dexperience.3ds.com/#community:38/post:udykfVZqQ2iSiZxrn4vR_w

Using "dependencies", we can achieve the Stack Changes function as shown in the very first image above.  You can validate the two Change Actions below against the "Current Evolution" column of very first image above:

• Change Action titled "Replace A with B" (with Name "CA-83754613-00000052") has a downstream Change Action titled "Replace B with C" (with Name "CA-83754613-00000053"). 
• Or you can read it the other way that Change Action titled "Replace B with C" (with Name "CA-83754613-00000053") has an upstream Change Action titled "Replace A with B" (with Name "CA-83754613-00000052").