ProcessMaker Developers Documentation
processmaker.comKnowledge CenterProcessMaker University
Guides
Guides
  • Getting Started
    • Installing ProcessMaker
  • Authentication
    • Creating a Client Application
    • Getting an Access Token
    • Getting a Refresh Token
  • Working with the API
    • Starting a Request via REST API
    • Starting a Request via Web Hook
  • Embedding Forms
    • Starting a Request via Anonymous Web Entry
    • Participating in a Workflow via Intermediate Web Entry (Anonymous)
    • Participating in a workflow via Intermediate Web Entry (Authenticated)
    • Angular Inbox Tutorial
      • Part 0: Overview
      • Part 1: Hello World
      • Part 2: Services & Dependencies
      • Part 3: Components
      • Part 4: The Inbox
      • Part 5: The Screen & Form Elements
  • Script Task Examples
    • PHP
  • Packages
    • ProcessMaker Platform Packages
      • Actions By Email Package
      • Advanced Screens Package
      • Advanced User Package
      • Auth Package
      • C# Package
      • Collections Package
      • Comments Package
      • Conversational Forms Package
      • Data Connector Package
      • Decision Tables Package
      • Documentation Package
      • DocuSign Package
      • Dynamic UI Package
      • File Manager Package
      • Google Places Package
      • IDP Package
      • Java Package
      • PDF Generator Package
      • PM Blocks Package
      • Process Optimization Package
      • Python Package
      • R Package
      • Saved Searches Package
      • Send Email Package
      • Signature Package
      • Slack Notification Package
      • Translations Package
      • Versioning Package
      • Vocabularies Package
      • Web Entry Package
    • Custom Packages
      • The Package Skeleton
      • Creating Your First ProcessMaker Package
Powered by GitBook
On this page
  1. Packages
  2. ProcessMaker Platform Packages

Versioning Package

Manage and maintain multiple versions of your Processes, Screens and Scripts.

PreviousTranslations PackageNextVocabularies Package

Last updated 1 year ago

Overview

Use the Versioning package to manage and maintain multiple versions of your Processes, Scripts and Screens. A version is a set of changes made to a ProcessMaker Platform asset at a particular time by a Process Designer. Versioning maintains a record of all named and unnamed changes to that asset. Versioning information is useful both for auditing and historical data maintenance purposes. The saved versions display in a tabular format when viewing version history for an asset from where they can be edited and/or marked as the Current Version according to your business needs.

The latest saved version of a ProcessMaker Platform asset is automatically designated as the current version and is used in new Requests. Version changes are not reflected in Requests which were in-progress or already completed when that asset version changed.

The Versioning package has the following attributes:

  • When the Versioning package is installed, versioning is available for Processes, Scripts and Screens.

  • Every new version is saved with the following information:

    • Date: The date and time when a Process Designer saved that version.

    • Name: The name of this version as entered by a Process Designer.

    • Description: A description of the changes in this version as entered by a Process Designer.

    • Saved by: The name of the Process Designer who saved this version.

  • Although multiple versions of each ProcessMaker Platform asset can be saved, only one version can be marked as the current version.

  • Any existing version of a ProcessMaker Platform asset can become the current version when configuring that asset.

See the following topics regarding how to use versioning in Processes:

  • Save a version: of a Process in the Process Modeler.

  • View and configure Version History: of a Process in Process Modeler.

See the following topics regarding how to use versioning in Scripts:

See the following topics regarding how to use versioning in Screens:

Save a version: of a Script in the Script Editor.

View and configure Version History: of a Script in Script Editor.

Save a version: of a Screen in the Screen Builder.

View and configure Version History: of a Screen in Screen Builder.

Save a version
View and configure version history
Save a version
Save a version
View and configure version history
View and configure version history