Conflict management
In a single requirements database, changes that are made to the same requirement by different users do not cause a conflict. Requirements applications enforce online transactions and locks to handle concurrent changes.
During requirements exchange, conflicts are not detected when changes are committed by individual partners. Instead, they are detected when those changes are synchronized and applied by each partner.
For example, imagine two partners who try to update a requirement status attribute to two different values. The first partner successfully synchronizes the update to the master requirements database. When the next partner synchronizes his update to the replicated requirements database and sends a snapshot to the master partner, a conflict occurs because the current state of the requirement status attribute is different from what the synchronization engine was expecting.
Conflict detection
In Windchill Requirements Connector conflicts are detected by analyzing differences between requirements passed to the exchange partners and residing in the master requirements database.
Windchill Requirements Connector logs all conflicts in the audit trail in the form of a conflict view. Explained in more detailed
here
Parent topic