Hi @TanyaS58,

Handling a change in the circumstance from a property like customer id to timezone in Pega, especially when it's already in production, requires a careful approach to ensure smooth transitions and maintain system integrity. Here’s a step-by-step guide on how to handle this:

Step 1: Understand Existing Circumstances

Before making any changes, review the existing circumstances based on customer id to understand how they are implemented and used throughout the application.

Step 2: Plan the Transition

Planning the transition involves determining how the new circumstances based on timezone will be integrated and how to phase out the old circumstances based on customer id.

Step 3: Create New Circumstance Definitions

Create new circumstance definitions based on the timezone property.

1. Identify the Rules to Circumstance:

   • Determine which rules need to be circumstanced based on timezone.

2. Create Circumstanced Versions:

   • For each rule, create a new circumstanced version based on timezone.

Example:

• Rule to Circumstance: YourRule
• Base Rule: YourRule
• Circumstance Property: Timezone

Steps:

1. Open the Rule: Open YourRule.
2. Create Circumstance: In the rule form, select Actions > Circumstance > Template.
3. Define Template: Create a new circumstance template with Timezone as the circumstance property.
4. Save Circumstanced Rule: Save the rule with the new circumstance template.

Step 4: Update Case Types and Workflows

Update the case types and workflows to ensure they utilize the new circumstances based on timezone.

1. Review Case Types: Identify where the old customer id circumstances were used.
2. Update References: Update these references to use the new timezone circumstances.

Step 5: Migrate Data and Cases

If there are existing cases that depend on the old circumstances, plan a migration strategy.

1. Identify Affected Cases: Identify cases that are currently using the old customer id circumstances.
2. Data Migration: Write scripts or use Pega utilities to update these cases to the new circumstances based on timezone.

Step 6: Testing

Thoroughly test the changes in a development or staging environment before deploying to production.

1. Unit Testing: Test individual rules to ensure they behave correctly with the new circumstances.
2. Integration Testing: Test the entire process flow to ensure there are no breaks.
3. User Acceptance Testing (UAT): Have end-users test the application to ensure it meets business requirements.

Step 7: Deployment to Production

Deploy the changes to production following your organization's deployment process.

1. Schedule Downtime (if necessary): Schedule a maintenance window if the changes require downtime.
2. Deploy Changes: Deploy the new rules and circumstances to production.
3. Monitor Post-Deployment: Monitor the system post-deployment to ensure everything is functioning correctly.

Step 8: Communicate Changes

Communicate the changes to all relevant stakeholders, including any changes to how the system should be used or understood.

Example Scenario

Before:

• Circumstance Property: customer id
• Circumstance Rule: YourRule_custID

After:

• Circumstance Property: timezone
• Circumstance Rule: YourRule_timezone

Steps:

1. Identify Rules: YourRule circumstanced by customer id.
2. Create New Circumstanced Rules:
   • Open YourRule.
   • Create a new circumstance based on timezone.
3. Update Workflow:
   • Ensure all references to YourRule_custID are updated to YourRule_timezone.
4. Migrate Data:
   • Update existing cases from customer id circumstances to timezone.
5. Test:
   • Perform unit, integration, and UAT testing.
6. Deploy:
   • Deploy changes to production.
7. Monitor:
   • Monitor system performance and behavior post-deployment.

Summary

By carefully planning and executing these steps, you can transition from circumstances based on customer id to those based on timezone smoothly, ensuring minimal disruption and maintaining the integrity of your Pega application.