History and Version Increment in ScriptCase

One of the biggest dilemmas of working on development projects is with respect to project versions. One of the most common mistakes is to program on top of some implementation already carried out, and with that, end up overwriting documents. This type of situation can cause serious loss of information and generate a great deal of rework. That's why working with a tool that offers a safe and reliable form of versioning is essential.

Scriptcase offers, in a fast and uncomplicated way, two resources capable of avoiding situations like the ones mentioned above: Version History and Version Increment. Let's see below how each of them works.

Version Increment

To access this feature within our project, we go to the option "Project -> Increment Version", which is located in the top horizontal menu of ScriptCase, as highlighted in the image below:

By accessing this option, we will have the current version in which our project is, the "New Version" field that can be edited for the version we want to increase our project, and finally, the description of this increment, which usually contains the new features that will be added to the project. After defining the necessary information, just click on "Increment":

It is worth noting that the version increment only allows only the latest version of the project to be incremented.

On the next screen, information about our project will be shown, such as the number of applications, fields, events and log, as well as the time it took for this increment to occur. We click on "Open new version of the project", and soon we will be able to start development in the new version:

Version History

To access this feature within our project, let's follow the same path we did above, but now our option of interest is "Project -> Version History":

We'll find all the versions that have been added to the project since the original version, the date and time the version was created, and some options for managing each of these versions, such as: Delete, Status and Edit.

- Delete: this option allows us to permanently delete some version of the project.

- Status: allows us to block the Edit option, so that we can no longer access a certain version.

- Edit: when clicking on this option, we will return to the screen where all the project's applications of that particular version are located. If the lock icon is set to "Closed" in Status for that particular version, this option will be hidden.

Another important point to be mentioned is that if we click on the lock button to close a certain version, and this version is the current version of the project, we are immediately redirected to the screen with all the applications from the previous version to the one that had just been closed.

• Related Articles

• Solving Source Guardian version problem

  In this tutorial, we will show how to solve the problem with Source Guardian version in Scriptcase installations. Select your correspondent operating system to follow the right steps below: Linux Windows MacOS By cryptography incompatibility issues ...

• Request a new license

  Some situations require the reinstallation of Scriptcase, in these cases, the user must generate a new serial on our website to register the tool. Follow the steps below to generate a new serial:  1. Log in to the website The entire process to ...

• Parallel Installation of Scriptcase

  Never delete the directory where you installed your Scriptcase The procedures in this tutorial, explain only how to install the Scriptcase manually. We recommend to create a backup of your scriptcase before proceeding the update, in Options->Settings ...

• Using Languages in Scriptcase

  In Scriptcase you have the option to standardize the language information quickly and uncomplicated. Using the feature you can change LANGUAGES entire textual structure of the project, since this native messages Scriptcase own name to fields and ...

• Updating Scriptcase's PHP

  Currently, the installation of Scriptcase 9.x comes with version 7.0.14 of PHP, unfortunately, this version has a compatibility problem with the new version of authentication of MySQL 8.0, so it is necessary to perform the PHP update so the ...