The Erase History command removes the record of all existing changes to the current project in the database. When collaborating with a distributed team where GENESYS Server is not available, tracking merge history allows team members to work in parallel and then integrate their changes. Erasing the merge history marks the starting point for tracking modifications to the project. GENESYS then transparently tracks all changes and then can export the change file using the Export command, enabling the team to easily merge their work.
Typically, erasing merge history is best handled as an option set during export when the design manager distributes baseline files to the design team. However, it can be handled manually using this command.
NOTE: |
What permissions are required to erase merge history? To erase merge history, you must have Project Administrator permissions. |