Scribd
Upload
27 views3 pages

Pega Deployment Plan Product Rule

The document outlines a Pega Deployment Plan using the Product rule to bundle application components for deployment. It details the steps to identify what to deploy, create a Product rule, export a ZIP file, import it to target environments, and perform post-import validation. Best practices and an example checklist for components to include in the Product rule are also provided.

Uploaded by

gsravani.pega
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
27 views3 pages

Pega Deployment Plan Product Rule

The document outlines a Pega Deployment Plan using the Product rule to bundle application components for deployment. It details the steps to identify what to deploy, create a Product rule, export a ZIP file, import it to target environments, and perform post-import validation. Best practices and an example checklist for components to include in the Product rule are also provided.

Uploaded by

gsravani.pega
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Pega Deployment Plan Using Product Rule

Overview

The Product rule in Pega is used to bundle application components (rules, data types, data instances) for

deployment across environments.

1. Identify What to Deploy

- Identify rule types (Flows, Data Transforms, Decision Tables, etc.)

- Include relevant classes, rulesets, versions

- Include data instances (e.g., access groups, operators, data types with records if needed)

2. Create Product Rule in Dev

1. Go to Records -> SysAdmin -> Product

2. Click Create

- Provide Name and Version

- Select your Application and Version

3. Under Rulesets, include:

- Relevant rulesets and versions

4. Under Include associated data, check:

- Rule-Admin-Product (for packaging data)

- Classes and Instances (e.g., Data-Admin-Operator-ID, Data-Admin-AuthProfile)

5. Use Preview to verify what is included

3. Export the Product ZIP File

1. Navigate to the Product rule

2. Click Actions -> Export

3. Save the generated .zip file (e.g., MyApp_01_01_01.zip)

4. Import the ZIP to QA/UAT/Prod

1. Log in to target environment (QA, UAT, Prod)


Pega Deployment Plan Using Product Rule

2. Go to Dev Studio -> Configure -> System -> Distribution -> Import

3. Browse and upload the Product ZIP

4. Follow the wizard:

- Preview

- Resolve conflicts

- Confirm instances

5. Complete the import

5. Post-Import Validation

- Validate successful import (check rules, rulesets)

- Clear/refresh rule cache if needed

- Test key use cases

- Run Tracer / Logs for debugging if errors arise

6. Optional: Use Deployment Manager or CI/CD Tools

For automated deployments, use:

- Pega Deployment Manager

- Jenkins + Pega APIs (for enterprises using DevOps pipelines)

Best Practices

- Use patch versions for hotfixes (e.g., 01-01-01 -> 01-01-02)

- Always test in lower environments before UAT/Prod

- Keep Product rule modular for large applications

- Document included data types and configurations

- Backup environments before import

Example Product Rule Checklist

| Component | Include in Product Rule? |

|----------------------------------|---------------------------|
Pega Deployment Plan Using Product Rule

| RuleSets | Yes Yes |

| Access Groups | Yes Yes |

| Operator IDs (Service accounts) | Yes Optional |

| Authentication Profiles | Yes Yes |

| Decision Tables/Strategies | Yes Yes |

| Data Types (with records) | Yes Optional |

| Rules (Flow, Section, DT, etc.) | Yes Yes |

You might also like