Deployment — Concepts and terms

A working Pega Platform application often corresponds to the contents of one or a few rulesets. The rules in these rulesets collectively provide the logic, the properties, the flows, the HTML forms, the computations, and all other ingredients of the "package."

Deploying minor versions and patches

Because ruleset versions and other access control features isolate developers from users, you can often develop your application on the same Pega Platform server that supports production users.

If you have updated an application already in production use, you can deploy the updated application to users of the system by:

For example, if production users previously access the ALPHA:03-04-07 ruleset version, they can be "upgraded" to use ALPHA:03-05-02 by changing the access group they use.

This roll-out can be gradual. Some users can continue to use lower-numbered versions, while others use more recent versions.

Copying a ruleset to another system

If your development and testing occurs on a Pega Platform system different from your application production, you can keep them synchronized as often as you want.

Use the archive tools to copy one or a few ruleset versions from one Pega Platform system to another. This is quick and simple to use, does not depend on the operating system or database product supporting the two systems, and can be completed without stopping either system.

Deploying a product

Use a Product rule to deploy a completed application on a separate Pega Platform system. See About Product rules .


After your application is mature, you may want to consolidate multiple versions of its ruleset into one new version, retaining only the newest and best versions of rules that have changed over time. Use the Skim function to create a new major version containing the best (highest) versions.