I have a question based on the "Update set batching" SN documentation (Washington link). A section says the following:
When you preview or commit the base update set, you preview or commit the entire batch. The system determines the processing order, and checks for collisions, based on the dates the changes were recorded, and on their sequential ancestry. Their ancestries are the specific instances in which the changes in the update sets took place.
I have a question based on this:
Let's say I have a parent update set (no customer updates), which has two child update sets 1.1 and 1.2. Let's say I created a business rule in 1.2, but updated it in 1.1.
When I commit this update set in another instance, does batching know to get the business rule version in update set 1.1, since that's the most recent version?
