> For the complete documentation index, see [llms.txt](https://docs.salesmania.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salesmania.id/2026-release-notes/app/rilis-app-2.1.3+158-1-oktober-2026.md).

# Rilis App \[2.1.3+158] - 1 Oktober 2026

## Fitur & Peningkatan

1. Tambah tombol scan barcode SKU di halaman Products dan Cari Product (aktif jika opsi SKU di Additional Search Info dicentang lewat Web), serta di kolom SKU pada halaman Tambah/Edit Produk.
2. Halaman Cari Product kini memakai satu kolom pencarian untuk tab Product dan Order History.
3. Pilihan satuan, harga, dan diskon per baris order kini dimuat saat baris dibuka, sehingga kunjungan dengan order banyak lebih ringan.

## Perbaikan Bug

1. Perbaikan halaman Piutang yang menampilkan toast merah untuk pelanggan yang belum terhubung ke Accurate Online.
2. Perbaikan jumlah (qty) produk ribuan di halaman Order yang terpotong.
3. Perbaikan loading yang tidak berhenti saat koneksi mati lalu membuka Database atau kartu kunjungan.
4. Tambah tombol Batal pada pesan izin kamera, dan perbaikan Join Database via QR saat izin kamera ditolak permanen.
5. Perbaikan daftar produk di Cari Product yang tidak kembali menampilkan semua produk saat pencarian dihapus manual.

***

Segera perbarui aplikasi SalesMania ke versi 2.1.3 untuk menikmati fitur terbaru serta peningkatan performa dan kenyamanan penggunaan.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.salesmania.id/2026-release-notes/app/rilis-app-2.1.3+158-1-oktober-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.