COOL RECORD EDIT PRO VERSION HISTORY PRO

COOL RECORD EDIT PRO VERSION HISTORY PRO

The Repository Service manages communication between Studio or Studio Pro and other supporting services (for example, Team Server). Tags are supported by Studio Pro Git ( BYO and Team Server) from Mendix version 9.8.0. Revision: this is added automatically and is the revision number of the commit.Patch: used to identify a fix to an error in a previously-released app.Minor: used to identify new functionality which augments the main function of the app.Major: used to identify significant new functionality, a new user interface, or other important change.It is specified by the developer and has four parts: 2.11 TagĪ Tag is a way of identifying a commit in addition to the revision number. Studio cannot be used to develop the app if it is not enabled for any development lines.įor app templates created via the Developer Portal, the main line of a new app will be Studio enabled. Changes made to other development lines will not be available in Studio. All changes will be linked to the selected branch and committed as revisions to that branch. This means that a developer can make changes to the app through Studio and share changes with the team. You may enable Studio for one of the development lines. See the Branches section below for more information on how branch lines can be used. 2.9.2 Branch LineĪ branch line is a way of making an independent set of changes which can be tested away from the main line. Simple apps, and apps which do not require a high degree of collaboration, may only have a main line. The main line is the initial development line for the app and is usually kept as the version which will be deployed to the production environment.

There are two types of development lines: the main line and branch lines. 2.9 Development Lineĭevelopment of an app is done in a development line where a set of related changes is made. If there are not conflicts, the changes are then sent to the repository to make a new revision. If Studio is enabled for this development line, the process first ensures that the Studio working copy is stored as a new revision and merged into the working copy of Studio Pro. In SVN these actions are always done together. When using Git, it is possible to store the committed data in a local repository, but not yet push it to the central repository. 2.8 Commit/PushĬommitting is the action, invoked in Studio Pro, of creating a set of changes and sending/pushing all your changes to the repository and making a new revision. If Studio is enabled for this development line, the process first ensures that the Studio working copy is stored as a new revision. Updating is the action, invoked in Studio Pro, which gets the latest revision of the current development line from the repository and merges the differences into the current working copy. When a conflict occurs, a developer has to intervene to decide how it should be resolved before it can be committed to the Team Server as a new revision. A document is moved or deleted in the revision but has been changed in a different way in the working copy.The properties of a widget are changed in the revision and the working copy but to different settings.This happens when the same document has been changed in a Studio Pro working copy and a committed revision and these changes cannot be reconciled. 2.6 ConflictĪ conflict occurs when two versions of the app cannot be combined automatically. If any of the differences cannot be applied, then there is a conflict. See the Merging Branches section for more information.

Merging is the action of taking one revision of an app and applying the differences which have been made in a different revision. Only one developer at a time can edit this. This model is held locally, on each computer where development work is taking place.įor Studio, there is one additional working copy, held in the cloud. For Studio Pro, there is one working copy for each development line of the app.

A Studio Pro working copy is updated from a Studio working copyĪ working copy is the version of your app which is currently being worked on in Studio Pro or Studio.

A new revision is created from Studio Pro in two circumstances: 2.3 RevisionĪ revision is the version of your app at a moment in time, stored on the Team Server.Įach revision of your app is given a unique alphanumeric identifier which enables you to find it in future. This repository contains all the committed revisions for the Branches of the app. Within the Team Server each app is stored in a repository. For more information, see the Team Roles section App Roles. To commit to the Team Server you will need to have a role in the app which allows you to edit the app.

If you commit a revision of an app, it is stored on the Team Server.

Team Server is where all the committed versions of Mendix apps are stored. Git is in Beta since Mendix 9.6.0, you can enable Beta features in Studio Pro Preferences.

Cool record edit pro version history