If the subset is not already checked out, the logic required to create the expansion conflict report is the same as the logic described in the section on download. The differences are that the conflict report is created rather than the transaction file and a rollback is executed so that checkout information for objects is not saved in the encyclopedia. Because a rollback is performed, the potential for contention is greater when creating this report than when downloading.
If the subset is checked out or if the report is run on the entire model, the program uses the existing expansion and no additional expansion is performed. Contention is minimized because no additional expansion is performed.
|
Copyright © 2013 CA.
All rights reserved.
|
|