HI
Sr Pega Developer
Han IT Staffing
- Location not stated
- Senior
- 10 months ago
- AI
- SOAP
- SQL
10 months ago
Location: Whippany, New Jersey- Hybrid
Duration: Contract
- Here's a concise overview of key concepts for a Pega Developer working with Case Management, Dispute Framework, Integrations, Locks, and Error Handling.
- Case Types: Represent business transactions (e.g., loan processing, dispute resolution).
- Stages & Steps: Define the lifecycle of a case using visual flows.
- Sub-cases: Enable modularization and reuse of logic.
- Routing & SLA: Assign tasks based on roles, urgency, and deadlines.
- Dynamic Case Management: Supports ad-hoc tasks and real-time decisioning.
- Used in financial services to manage chargebacks, fraud claims, and transaction disputes.
- Offers:
- Pre-built workflows for Visa/Client dispute rules
- Straight-through processing using AI and automation
- Audit trails and compliance tracking
- Integrates with core banking systems and external networks (e.g., card processors).
- Connectors: REST, SOAP, MQ, File, SQL, etc., to call external systems.
- Services: Expose Pega APIs to external consumers.
- Data Pages: Load data from external sources on demand.
- Error Handling: Use Connection Problem Flow and response status checks to manage failures in connectors.
Locks
- Case locking ensures only one user can update a case at a time.
- Default behavior: Lock acquired when a case is opened for assignment.
- Optimistic locking: Used for high-volume, read-heavy scenarios.
- Lock timeouts and manual release can be configured to avoid deadlocks.
Error Handling
- Flow-level: Use Problem Flows to recover from runtime issues like missing data or broken rules.
- Activity-level: Use Step Status Fail, Jump, and Transition logic.
- Integration-level: Configure Connection Problem Flow and Error Handlers on connectors.
- Global Exception Handling:
Sr Pega Developer · Han IT Staffing