I would like to understand the internal workings of a Savable Data Page in Pega. Specifically, I’m interested in how the persistence operations (such as insert or update) are executed. I attempted to use Tracer to capture the underlying SQL statements triggered during the save operation, but I wasn’t able to trace or identify them. Could you explain how Savable Data Pages handle database interactions under the hood, and how one can effectively trace or debug these operations?
1 Like
Hi @SaiC17448934,
A Savable Data Page in Pega allows data to be persisted (create/update/delete) using a defined save plan (data transform, connector, or activity). Internally, it executes the logic configured in the Save options of the data page rule. To trace the operation, enable Tracer settings like DB Query, Data Page Load/Save, and Activities. For deeper visibility into SQLs, increase logging for com.pega.pegarules.data.internal.access to DEBUG. This is the Pega-recommended, declarative way to separate data access logic from UI and process.
1 Like