Skip to main content

Versioning applications - expanding on Version Control in Pigment

  • July 27, 2026
  • 1 reply
  • 18 views

Forum|alt.badge.img+1

Expanding on the Version Control in Pigment | Community idea, we’d like to raise the following issue : 

  • During a planning cycle, we are required for new versions to implement changes to the structure of the application (be it new formulas with new metrics or event changes to formulas, blocks creations...) that require a new version of the application : the existing one must be kept with all existing figures, while a new one is used to bear the changes
  • We often work on this new version with paradigm changes and are required to go back to the previous application version to change some assumptions and compare how they perform back to the newest version
  • These different application versions are required to be kept for audit purposes

As of it is not possible to perform all this in a single application (we create a clone of the application). The idea would be to be able within the same application to be able to create a copy of the application (a bit like a snapshot), with the ability to still change this application figures inputs, so a bit like a snapshot but with the ability to use it like a live application, or to be able to “unlock” a snapshot or a previous version of the application that we took before committing to further changes.

1 reply

Julien
Employee
Forum|alt.badge.img+10
  • Employee
  • July 27, 2026

Hi ​@DSA, Applications clones seem to be exactly what you describe (identical copies like Snapshots, but live so you can still edit anything you want in the model or the data). You mentioned you are using Application duplicates (clones), are there limitations with them that prevent you from implementing the workflows you describe?