What Really Happens When a Pega Case Is Saved
Introduction Saving a case in Pega may look like a simple user action: a developer or application user changes a field and clicks Save. Behind that single action, however, Pega can perform a sequence of operations involving the UI layer, requestor context, Clipboard, validation, business rules, persistence, database transactions, locking, history, indexes, and integrations. Understanding […]
