Pega Knowledge sharing

In real Pega projects, iterating over Page Lists is something you do almost daily — to read data, apply validations, or update records. However, the moment the requirement changes to removing pages from a Page List based on a condition, things often go wrong. I’ve seen many entry-level developers get stuck here. Let’s break down the clean and Pega-recommended way to handle this scenario. Understanding the Problem A Page List is an ordered collection of pages, for example: .Participants () .Transactions() Each page usually represents a business entity. Now imagine a requirement like: Remove participants whose Age < 18 Remove transactions where Amount = 0 This is where conditional removal becomes important. ❌ Common Mistake (Don’t Do This) Many developers try to remove pages while looping forward through the Page List. Example: Loop from index 1 → N Remove page at index 2 Index shifts → next page gets skipped This leads to: Skipped records Partial cleanup Hard-to-debug issues 👉 Ne...

  If you’ve spent enough time in enterprise IT, you’ve probably heard this line: “It’s just another application with workflows.” That assumption usually lasts until the system goes live — and starts running for months or years. That’s when the difference between BPM applications and traditional enterprise applications becomes very real. 1. Traditional apps execute transactions. BPM apps manage work. Most enterprise applications are built around a simple idea: User does something System processes it Transaction completes That works well when everything happens quickly and predictably. BPM applications are built for a different reality: Work that pauses and resumes Decisions that depend on humans Cases that evolve over time Think of onboarding , claims , compliance reviews , or service requests . A case might: Start today Wait a week for documents Move back due to rework Escalate because an SLA is breached In BPM, this isn’t an edge case. This is the normal path. 2. State isn’t ...

Let’s look at what actually happens inside real enterprise systems . The real challenges organizations face: • Long-running business processes that span days, months, or even years • Frequent changes to business logic driven by dynamic markets and regulations • Reliable integration with multiple external systems — each with its own latency and failure patterns How Pega addresses these concerns explicitly: • Case life cycles model long-running work without custom state management • Business rules and decisions are externalized and versioned • Integrations are orchestrated at the process level, not hard-wired into services In enterprise systems, speed of change matters more than theoretical flexibility. Most organizations don’t struggle to build systems. They struggle to change them safely . Real enterprise value comes from: • Implementing business or regulatory changes quickly • Predictable behavior across releases • Minimizing regression in systems that are always live Th...