This page is no longer current.

Please visit the Worksoft Customer Portal for the latest content.

This article refers to the standalone Content Merge tool available in 8.5.0 and later versions of Certify. However, it is also applicable to the Content Merge option under the Tools menu in Certify 8.4.1 as well. 

Warning: Content Merge is an administrator only tool. Only Certify users who are members of the Administrator group will be able to use this tool.

NOTE: Starting with Certify 9.0, Content Merge is only available as a separate, standalone tool and the above Warning does not apply.

If this is your first time running Content Merge, please read the online help on the topic of Content Merge carefully.


Supported Certify version requirements for Content Merge

Content Merge is supported for all released versions of Worksoft Certify 9.0.2.

For Worksoft Certify 9.0.1, please use version and up.

For Worksoft Certify 9.0.0, please use version and up.

NOTE: The following versions of Certify are no longer supported. Please see the Worksoft product life cycle article for details.

For Worksoft Certify 8.7.0, please use version and up. (Please note that the Selection pane will be disabled in this version).

For Worksoft Certify 8.6.0 and up, Content merge is supported in all patches as a Standalone tool. (For Worksoft Certify 8.6.0, please use patch and up.

For Worksoft Certify 8.5.0, Content merge is supported in patch and up as a Standalone tool.

For Worksoft Certify 8.4.1, please use patch and up.

For Worksoft Certify 8.3.2, please use patch and up.


Database Prerequisite Steps for successful Content Merge

Before you use the Content Merge tool, you must do the following for both the source and target Certify databases:

1. Back up the Certify database.

2. Run the Database Validation tool on the Certify database. (Please see details below.)

3. Confirm that there are no issues present in the Database Validation log files.


Steps for successful Content Merge

1. For best performance of the Standalone Content merge tool, run the Content merge on a machine which has a 64-bit OS (i.e. Windows 7 x64 or Windows 2008 Server R2) with a minimum of 4 Gb of installed memory.

2. Use Content merge on only one machine at one time. Please do not attempt to use content merge on more than one machine (pointing to the same Certify database) simultaneously.

3. Please note that only the map windows and objects used by the selected processes will be merged.

4. For older versions of Certify, you may be required to add application versions back to the project after content merge. This is done by going to the Project Editor to edit the project and select the appropriate application versions.

5. Recommended for large projects:

a. Select a small Process subfolder (one containing very few processes) to merge.

NOTE: Don't select anything else , the needed dependencies will be automatically checked (with one exception - see #4 in Existing limitations of Content Merge below).

b. If the small merge goes well, select the rest of the processes to merge (one subfolder at a time).


Existing limitations of Content Merge

The existing limitations of the Content Merge tool are:

1. The source and target Certify databases must not report any issues after running the latest Database Validation tool.

2. The source and destination databases must have identical Interface Class Library (ICL) data.

3. There cannot be two entities with the same name in both projects which are of different type.

4. When you select a process or process folder to merge, Content Merge will select any recordsets and variables required by the selected process unless the recordset names themselves are provided via a variable. If you select a process in the source project which uses a variable in the recordset name field, you must explicitly select the corresponding recordsets which are used by that process in the source project. If you do not explicitly select the corresponding recordsets, Content Merge will not be able to determine that the recordsets are required by the selected process during run time and the recordsets will not be merged.


Contacting Support for issues with Content Merge

If there is a problem during Content Merge, please file a Support case with the following information:

a. Certify version and build level

b. Names of the source and target databases being merged.

c. Names of the project and process folder(s) or individual processes being merged (both source and destination)

d. A screen capture of the Content Merge dialog showing the selected process folders, variables, layouts, etc.

e . A screen capture of the error message (preferably in a JPG or PNG file) showing additional details (if available).

f.  The certify log file from C:\Users\<username>\AppData\Roaming\Worksoft\log-file.txt on Windows 7 and newer.

g. The Content Merge log file from C:\Users\<username>\AppData\Roaming\Worksoft\ContentMerge.log on Windows 7 and newer.

h.   Run the database validation in C:\Program Files\Worksoft\Certify\Client\DatabaseValidation.exe and attach the log file found in C:\Temp\DatabaseValidation.log . (Please see the instructions for running the Database Validation from the command line below.)

i. If possible, please provide the most recent copy of the database backup. If the merge is done between two different databases, then we'll need backup files from both databases. (We'll need database backup files that are an exact match of the one where you are currently having issues since the ICL data issue might have occurred recently).


Instructions for running the Database Validation for content merge (for Certify 8.5.0 and up):

Make sure you have permissions to write to the C:\Temp folder, then do the following:

1. Open a Command Prompt. 
2. CD to the C:\Program Files\Worksoft\Certify\Client\ folder. 
3. Type in DatabaseValidation.exe {servername} {databasename} {sausername} {sapassword} where {servername} is the name of your database server, 
{databasename} is the name of your Certify database, 
{sausername} is the login id for a user with SA permissions on the database, 
{sapassword} is the password for {sausername} 
Example: C:\Program Files\Worksoft\Certify\Client\DatabaseValidation.exe SRV_CERTIFY1, Certify, sa, sapa$$w0rd 
4. Once the Database Validation completes, it will produce a log file in the C:\Temp folder named "DatabaseValidation.log".  If you run into any issues, please attach this log file to the support case. Also, make sure and rename the log file after running the Database Validation tool against the first database, otherwise it will get overwritten when you run the Database Validation tool against the second database. 

The source and target Certify databases must not report any issues after running the latest Database Validation tool.