Implementing further comparison and save related settings

Configure the settings:

Configure the sections Compare these files, Ignore these files during the comparison and Detection of changes.
for saving the files in the areas Save these files, Ignore these files and Settings for saving.

The following settings can be made in the columns of all areas.

Image: Component type module, Compare these files, Columns

Column Specification:

Click on a cell and enter the desired value.

In the case of data types, you can use the placeholder * (for example, *.txt).

File names can also be set out (for example, info.txt).

When splitting file names, the placeholder * can be used for several characters and the placeholder ? for one character (for example, *_info_???.txt).

Files and file types that have not been specified to be compared and saved, will not be compared and saved. If no files are being compared, you can only create new versions with the option Version without difference. If no files are saved, you will not be able to create new versions.

Column Comparator:

Click in a cell.
A dropdown menu will appear.
Select the desired comparator (the pre-selection jumps to the letter that you enter).

Column Subdirectories:

Click on a cell and activate the drop down menu.
Select the option Include or Don't include.

If directory structures are not saved, check the checkbox Ignore empty directories located under Settings for savings.

In the case of contradictory rules, these files will not be compared /saved.

Examples:

Affected files	Action
	Compare	Save
All TXT files	Under Compare these files, enter *.txt. Include subdirectories	Undersave these files, enter *.txt. Include subdirectories.
No TXT file	Under Ignore these files during comparison, enter *.txt. Include subdirectories.	Under Ignore these files, enter *.txt. Include subdirectories.
Only TXT files from root directory/ None from sub directories	Under Compare these files enter *.txt Do NOT include subdirectories.	Under Save these files, enter *.txt. DO NOT include subdirectories.
Only TXT files from subdirectory/ None from root directory	Under Compare these files, enter .txt. Include subdirectories. Under Ignore these files during comparison* enter *.txt DO NOT include subdirectories.	UnderSave these files, enter .txt. Include subdirectories. Under Ignore these files* enter *.txt DO NOT include subdirectories.
All files from the subdirectory “UVZ”	Under Compare these files, enter UVZ\*.	Under Save these files, enter UVZ\*.
No files from the subdirectory “UVZ”	Under Ingore these files during comparison, enter UVZ\*.	Under Ignore these files, enter UVZ\*.

Should I select in AdminClient > Component type editor > Detect changes via the timestamp or checksum? How will this affect the system performance? Do I need to consider the file size?

For efficient use of resources, before a detail comparison takes place, versiondog finds out which files were changed using the option selected:

By timestamp needs less time as the time stamps can be read very quickly. There is however the risk, even if unlikely, that two files could have different content but the same time stamp.

By checksum is slower as it is requires much more time to create checksums. The advantage is that the file content is examined and every difference results in another checksum.

Potential scenarios

Scenario 1:

The component type, that you are currently editing, is normally used for components with large files that are only rarely changed. In this scenario: By timestamp offers the best solution.

Scenario 2:

The component type, that you are currently editing, is normally used for components with small files that are regularly changed. In this scenario: By checksum offers additional security with a relatively low loss of performance.

To FAQ list