savable data page , does really save without transaction only with this savable data page?

General
, , ,
1

with the savable data page , does really save without transaction calls like (commit , submit cases or complete assignment)

when use savable data page just savable , it saves and commit to db

please can you clarify and confirm this best use case to use for this

2

Hi @RaviG0023

In Pega, a Savable Data Page can be used to save data to the database without explicitly calling actions like Commit, Submit, or Complete Assignment.

Key Points to Confirm:

  1. Auto-Commit Behavior:

    • When using a Savable Data Page directly in a flow action or data transform, Pega automatically commits the changes to the database.

    • You don’t need to call Commit explicitly.

  2. Best Use Cases:

    • Form Submissions: Ideal when saving form data in a flow action.

    • Integration Scenarios: When data needs to be saved without managing explicit commit logic.

    • Background Processing: Used in job schedulers or queue processors to persist data without requiring manual commits.

  3. Transaction Management:

    • Pega manages transactions implicitly with Savable Data Pages. If any exception occurs, the transaction will be rolled back.

  4. Conditional Saves:

    • You can configure conditional save logic using when rules to ensure only valid data is saved.