> For the complete documentation index, see [llms.txt](https://doc.sysdevmobile.com/kalipso5/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-database/commit-transaction.md).

# Commit Transaction

Commit specified transaction on local database.

Action available for the following operating systems:

![](/files/-MAlQBZuuTnc6hyzKSVQ)

### Parameters

* **Name** *\<string> -* The name of the commit transaction. If this parameter is leave empty, system will commit all pending transactions.

{% hint style="info" %}
This action should be used in conjuction with Begin *Transaction* action.
{% endhint %}

{% hint style="info" %}
Actions taken between *Begin Transaction* and *Commit Transaction* are executed in an atomic way.
{% endhint %}

{% hint style="info" %}
Works only with local database tables, this includes databases in the Offline and Local tree. This action does not work with online Databases.
{% endhint %}

{% hint style="info" %}
See chapter [Database ](broken://pages/-M9xeS95S1XRS69Ow17-)for more information.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-database/commit-transaction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.