Skip to content

Scripting

The basic version of versiondog supports the most commonly used automation systems and devices. However, most companies use a mix of technologies, and some devices may fall outside the standard scope of versiondog.

In many cases, a short assessment is enough to determine whether a device can be integrated using a custom script. Experience shows that newer devices can often be retrofitted with minimal effort. In contrast, integration options for older devices are more limited.

Today, many manufacturers provide their own tools for backing up device data. These tools are typically not automated and often require advanced user knowledge. This is where versiondog adds value: with scripting, backup processes can be streamlined and automated.

In practice, manufacturer-provided tools are frequently integrated into the upload process and extended through scripting within versiondog.

Info

When you use the scripting feature, versiondog can't verify the authenticity of software that runs outside the versiondog system. You must verify the authenticity of such software before use.

Functionality

Scripts are bound to events in versiondog, i.e. an action in the software triggers the execution of the script. These events are divided into server and client events.

Events on the server

  • After a Check-In on the server
  • After a Check-Out from the server
  • Before and/or after a comparison
  • After executing a job
  • Before and/or after a backup job

Events on the client

  • Before and/or after checking for changes
  • Before and/or after a comparison
  • Before starting an editor
  • Before and/or after restoration of a version (e.g. before and/or after a Check-Out)

React to an event

Scripting must generally be activated in the Global settings module, as it is not selected in the default settings. If such a trigger is triggered after activation, versiondog checks whether a script is assigned to this trigger and executes it accordingly.

Script creation

A script can be created using many different tools and programming languages. The simplest option is to use a text editor, which is included in every Windows installation. The most complex and also most expensive option is to use a development environment such as Microsoft Visual Studio. The options available for script development depend largely on the tool used. The most common tools, which are usually completely sufficient in practice, are:

  • a custom scripting language from versiondog
  • batch files from the Windows world
  • Powershell as a development environment

Almost all (special) scripting tasks can be solved with these tools.

Related topics