Different ways to version maps and processes

There are a couple different ways to keep track of the different map versions; it depending on what you want as the end results.

1. If user only wants the map objects and no processes from the original project in the new project, creating a new application version and copying over the windows one by one is one way of making a copy of their application version.

2. If user wants a new project with all the map objects in all the application versions in a project along with all of the processes using the map objects, they could would use Project copy. The user will end up with two projects, two application versions and twice as many processes, requirements, variables and recordsets.

3. If user wants a new project which shares the same application version and a few selected processes in a new project in the same database, we recommend that they use Content merge and select those processes for the merge.

4. If user wants to add only the map objects used by selected processes in the original project stored in a different database (assuming that the destination project does not yet have all the map objects), you would use content merge and select those processes for the merge.

Note about Content merge: For older versions of Certify (before Certify 8.5.0) when merging very large databases, the content merge can take up to 36 hours. We recommend that large merge is performed during the weekend since it is best to not make changes during the Project copy or Content merge. Content merge best practice article can be found in the Worksoft Community server KB (Content merge ).

5. If user wants an exact copy of all of existing projects with all of the results, the best method is to use a database back up.

6. Last method - suitable for custom development project or testing by a software vendor:

 

 

o    Project 1 that has processes that test Application Version 1 in a single database.

o   A new release/version needs to be tested. The user creates a Project 2 to test Application Version 2 in the same database.

o   Create Application Version 2 which only has screens that are different from AppVer1.  So AppVer2 contains the differences between Application Version 2 from Application Version 1.

o   Project 2 is used to test Application Version 2.  Project 2 starts of as a copy of Project 1 (created via content merge).  So initially processes in Project 2 are using maps objects in AppVer1.

o   When the encounters a screen that is different, it is recommend that the user learns it and imports the new map objects into Application Version 2.  Then they modify the Project 2 process to use the imported screen.

o   Over time, screens are imported into Application Version 2 and Project 2 processes are modified to use Application Version 2. 

o   For unchanged screens, Project 2 process still use Application Version 1 maps.  These process are still identical to those in Project 1

If you would like our Profession Services team to help you with setting this up, please let your Sales rep or Account manager know. We'd be happy to work with you on finding the best version control strategy.