InfiniteERP Wiki - User contributions [en]

JRXML Local Verification

2026-09-16T15:28:11Z

Wikiadmin:

Halaman ini menjelaskan cara menguji file JRXML '''di laptop''' — compile dan render PDF tanpa men-deploy ke server InfiniteERP. Wajib dilakukan sebelum JRXML baru/diubah dipasang di server.

== Kenapa Verifikasi Lokal ==

* Kesalahan JRXML (ekspresi tidak valid, field tidak dideklarasikan, class salah) baru ketahuan saat compile — bukan dari membaca XML.
* Menguji di server berarti menyentuh sistem produksi; di laptop cukup 1 perintah Java.
* Klaim "compatible" harus dibuktikan dengan hasil compile terhadap '''versi library yang sama dengan server''' (6.0.0), bukan versi lain.

== Classpath (Terbukti Jalan) ==

Unduh dari Maven Central, taruh dalam satu folder (misal <code>lib6/</code>):

{| class="wikitable"
! Jar !! Fungsi
|-
| <code>jasperreports-6.0.0.jar</code> || Engine report — versi sama dengan server
|-
| <code>jasperreports-fonts-6.0.0.jar</code> || Font extension — sama dengan server
|-
| <code>commons-digester-2.1.jar</code>, <code>commons-collections-3.2.2.jar</code>, <code>commons-beanutils-1.9.4.jar</code>, <code>commons-logging-1.2.jar</code> || Dependensi parsing
|-
| <code>ecj-4.4.2.jar</code> || Compiler ekspresi (JDT)
|-
| <code>itextpdf-5.5.13.3.jar</code> || Export PDF (JR 6.x memakai package <code>com.itextpdf</code>)
|-
| <code>itext-pdfa-5.5.13.3.jar</code> || '''Wajib''' — <code>PdfAWriter</code> dipisah ke jar ini
|}

Jebakan versi yang sudah ditemukan:

* JR 6.x '''tidak''' memakai iText lawas <code>com.lowagie</code> (itu milik JR 5.x). Tanpa <code>itextpdf</code>, export gagal: <code>NoClassDefFoundError: com/itextpdf/text/DocumentException</code>.
* Tanpa <code>itext-pdfa</code>, export gagal: <code>NoClassDefFoundError: com/itextpdf/text/pdf/PdfAWriter</code>.
* Teruji jalan di '''Java 17'''.

== Langkah ==

=== 1. Compile ===

<syntaxhighlight lang="java">
JasperReport rep = JasperCompileManager.compileReport("report.jrxml");
</syntaxhighlight>

Compile sukses = JRXML valid dan kompatibel dengan JR 6.0.0.

=== 2. Fill dengan data dummy ===

Report ber-query SQL tidak butuh database untuk diuji — lewatkan datasource map:

<syntaxhighlight lang="java">
Map<String,Object> row = new HashMap<>();
row.put("bpnmae", "PT CONTOH PELANGGAN");
row.put("pricestd", new BigDecimal("5000000"));
// ... isi semua field sesuai deklarasi <field> di JRXML

Map<String,Object> params = new HashMap<>();
params.put("IMAGE_DIR", "/path/ke/folder/gambar");

JasperPrint print = JasperFillManager.fillReport(rep, params,
new JRMapCollectionDataSource(java.util.Collections.singletonList(row)));
</syntaxhighlight>

Catatan: ImageIO membaca gambar '''berdasarkan konten''', bukan ekstensi — file PNG bernama <code>.jpg</code> tetap ter-render (berguna untuk placeholder).

=== 3. Export PDF ===

<syntaxhighlight lang="java">
JRPdfExporter exporter = new JRPdfExporter();
exporter.setParameter(JRExporterParameter.JASPER_PRINT, print);
exporter.setParameter(JRExporterParameter.OUTPUT_FILE_NAME, "sample.pdf");
exporter.exportReport();
</syntaxhighlight>

Jalankan: <code>java -cp ".:lib6/*" NamaVerifier</code>

=== 4. Cek hasil ===

* Buka PDF dan periksa visual: overlap, teks terpotong, alignment angka.
* Untuk elemen grafis kritis (accent bar, latar blok), bisa dicek deterministik: konversi PDF ke PNG lalu baca warna piksel pada koordinat yang diharapkan. Cara ini terbukti menangkap bug outline hitam pada <code><rectangle></code> (lihat [[JRXML Best Practices]]).

== Tool CLI: jrxmlcheck ==

Untuk pengguna non-programmer tersedia tool CLI '''jrxmlcheck''' — satu perintah, tanpa menulis Java.

=== Unduh & Pasang ===

# Unduh '''[[Media:Jrxmlcheck.zip|Jrxmlcheck.zip]]''' (5 KB; halaman berkas: [[:File:Jrxmlcheck.zip]]).
# Ekstrak: <code>unzip Jrxmlcheck.zip</code> — terbentuk folder <code>cli/</code>.
# Beri izin eksekusi (sekali saja): <code>chmod +x cli/jrxmlcheck</code>
# Prasyarat: Java/JDK terpasang (teruji di Java 17), dan internet saat '''pertama''' dijalankan karena library JasperReports 6.0.0 diunduh otomatis dari Maven Central.

=== Cara Pakai ===

<pre>./cli/jrxmlcheck compile laporan.jrxml # cek valid & kompatibel JR 6.0.0
./cli/jrxmlcheck preview laporan.jrxml # buat PDF contoh, data otomatis
./cli/jrxmlcheck preview laporan.jrxml --images ./images # pakai folder gambar (logo/stempel/ttd)
./cli/jrxmlcheck preview laporan.jrxml --data data.txt # data sendiri, format: namafield=nilai</pre>

* Mode <code>preview</code> membaca deklarasi <code><field></code> di JRXML lalu membuat data contoh otomatis — langsung jalan tanpa menyiapkan apa pun. Jumlah baris contoh diatur dengan <code>--rows N</code>.
* Mode <code>audit</code> — pemeriksaan menyeluruh sebelum deploy:
** '''Font''' — setiap <code>fontName</code> dicek terhadap isi <code>jasperreports-fonts-6.0.0.jar</code> (DejaVu Sans/Serif/Sans Mono + SansSerif/Serif/Monospaced). Font lain akan disubstitusi diam-diam di server → layout bergeser.
** '''Path absolut''' pada <code>imageExpression</code> (mis. <code>/home/zaien_aji/...</code>) — harus diganti parameter seperti <code>$P{IMAGE_DIR}</code>.
** '''Geometri''' — elemen yang keluar batas band atau lebar kolom (tidak akan tercetak utuh).
** '''Variabel mati''' (variableExpression kosong) dan '''field/parameter tidak terpakai'''.
** '''Jejak Jaspersoft Studio''' (<code>splitType</code>, property <code>com.jaspersoft.studio.*</code>) — jadi peringatan bila diaudit dengan <code>--target ireport</code>.
** '''Elemen teks bertumpuk''' — dua elemen teks yang kotaknya beririsan >50% dari kotak terkecil (irisan tipis antar kolom kiri/kanan diabaikan karena umum & aman; teks di dalam kotak latar dan stempel-di-atas-tanda-tangan juga diabaikan — gambar bertumpuk hanya dicatat sebagai info).
** '''Atribut PDF lawas''' (<code>pdfFontName</code>, <code>pdfEncoding</code>, <code>isPdfEmbedded</code>) — deprecated, migrasikan ke font extension.
** '''Encoding file''' — JRXML wajib UTF-8 valid; file Latin-1/Windows-1252 ditolak sebelum compile dengan pesan yang menunjuk cara memperbaikinya (karakter <code>•</code>, <code>·</code> rawan rusak).
** <code>--strict</code>: exit code 1 bila ada peringatan — cocok untuk gerbang CI sebelum deploy.

* File data sendiri: teks biasa, satu <code>namafield=nilai</code> per baris, baris <code>#</code> untuk komentar.
* Pesan error diringkas ke penyebab utama beserta daftar penyebab umum (field tidak dideklarasikan, salah ketik nama field, class field salah, ekspresi bukan Java valid).
* PDF hasil terbuka otomatis di macOS (nonaktifkan dengan <code>--no-open</code>); nama file diatur dengan <code>--out</code>.
* Petunjuk lengkap juga tersedia di <code>README.txt</code> dalam paket.

=== Validasi query ke database (--jdbc) ===

Menjalankan query JRXML ke '''PostgreSQL sungguhan''' — persis alur produksi:

<pre>./cli/jrxmlcheck audit laporan.jrxml \
--jdbc jdbc:postgresql://HOST:5432/NAMA_DB --dbuser USER
# password: --dbpass PASS atau lebih aman env JRXMLCHECK_DBPASS
# override parameter: --param DOCUMENT_ID=XXX (boleh berulang)</pre>

Yang diverifikasi:

# Query dieksekusi lewat <code>fillReport(connection)</code> — parameter default ikut dievaluasi JasperReports, jadi kesalahan nama tabel/kolom langsung ketahuan dengan pesan asli PostgreSQL.
# '''Probe kolom''': <code>ResultSetMetaData</code> hasil query dicocokkan dengan deklarasi <code><field></code> — tetap bekerja walau hasil query '''0 baris''' (kasus alias salah yang tidak ketahuan saat fill biasa).
# Gambar tidak perlu disiapkan: placeholder otomatis dibuat untuk nama file yang dirujuk <code>imageExpression</code> (bisa dioverride dengan <code>--images</code>).
# Kolom query yang tidak dideklarasikan hanya dicatat sebagai INFO.

Driver PostgreSQL (42.7.3) ikut terunduh otomatis oleh wrapper. Teruji end-to-end memakai PostgreSQL 16 dengan skema mini ala Openbravo (c_invoice dkk).

== Hasil yang Pernah Diverifikasi ==

* <code>sales_invoice_SSD.jrxml</code> (asli, iReport 5.6): compile OK di JR 5.6.0 dan 6.0.0
* Versi perbaikan (parameter <code>IMAGE_DIR</code>, variable mati dihapus): compile + render OK
* Layout modern tanpa border penuh: compile + render OK, cek piksel lolos

[[Category:Development ERP]]

JRXML Best Practices

2026-09-16T15:27:46Z

Wikiadmin:

Halaman ini merangkum aturan dan jebakan yang ditemukan saat menulis/memperbaiki JRXML untuk InfiniteERP (runtime JasperReports 6.0.0). Latar belakang versi ada di halaman [[JasperReports]].

== Aturan Kompatibilitas ==

* Namespace root: <code><nowiki>http://jasperreports.sourceforge.net/jasperreports</nowiki></code> (jangan ganti ke namespace <code>jaspersoft.com</code> — itu gaya file baru Studio, dan tidak konsisten dengan report existing).
* Ekspresi ditulis sebagai '''Java valid''', bukan gaya Groovy. Contoh: <code>new Integer($V{No_Urut}.intValue()+1)</code>.
* Deklarasikan '''semua''' field yang dipakai di <code><field></code> dengan class Java yang benar:
** Uang/numerik: <code>java.math.BigDecimal</code>
** Tanggal: <code>java.sql.Timestamp</code>
** String: <code>java.lang.String</code>
* Font: pakai logical font (<code>SansSerif</code>, <code>Serif</code>, <code>Monospaced</code>) kecuali ada font extension jar di server.

== Jebakan yang Sudah Ditemukan ==

=== 1. Path absolut untuk gambar ===

Report existing me-hardcode path seperti:
<pre><imageExpression><![CDATA["/home/zaien_aji/appl/sahila/modules/.../ssd_logo.png"]]></imageExpression></pre>
Ini gagal render di mesin/user lain. '''Solusi''': parameter direktori gambar:
<pre><parameter name="IMAGE_DIR" class="java.lang.String" isForPrompting="false">
<defaultValueExpression><![CDATA["."]]></defaultValueExpression>
</parameter>
...
<imageExpression><![CDATA[$P{IMAGE_DIR} + "/ssd_logo.png"]]></imageExpression></pre>

=== 2. Rectangle selalu ber-outline hitam ===

Elemen <code><rectangle></code> '''selalu digambar dengan garis tepi 1pt berwarna <code>forecolor</code>''' (default hitam), di samping fill <code>backcolor</code>. Untuk balok warna bersih (accent bar, latar blok total), samakan keduanya:
<pre><reportElement mode="Opaque" x="0" y="84" width="565" height="3"
forecolor="#224435" backcolor="#224435" .../></pre>
Jika hanya <code>backcolor</code> yang di-set, balok tipis (height 1–3) akan terlihat kehitaman karena tercampur border.

=== 3. Variable mati sisa template ===

Variable dengan <code>calculation="Sum"</code>/<code>Average</code> tetapi <code><variableExpression></code> kosong adalah sisa template iReport — tidak dipakai dan aman dihapus.

=== 4. Atribut versi baru di file lama ===

Atribut seperti <code>splitType</code> pada <code><band></code> (milik JR 6.x) bisa muncul di file lama karena pernah dibuka di Jaspersoft Studio. Compile tetap OK (parser mengabaikannya), tetapi iReport 5.6 dapat mengacaukannya saat edit-save. Untuk file yang masih dirawat di iReport, hapus atribut tersebut.

== Pola Kalkulasi ==

Report existing melakukan kalkulasi di '''SQL (PostgreSQL)''', bukan di ekspresi report:

* Pajak: <code>ci.grandtotal - ci.totallines as pajak</code>
* Terbilang: fungsi custom database <code>terbilang(grandtotal)</code>
* Format tanggal Indonesia: <code>CASE EXTRACT(MONTH FROM ...)</code> + <code>to_char</code>

Ikuti pola yang sama kecuali ada alasan memindahkannya ke report — query mengambil langsung dari skema Openbravo/ADempiere (<code>c_invoice</code>, <code>c_invoiceline</code>, <code>c_bpartner</code>, dst).

== Trik Layout ==

=== Satu sel, dua baris (nama produk + deskripsi) ===

Buat dua text field bertumpuk di kolom yang sama; hilangkan border yang bertemu agar terlihat seperti satu sel:

* Elemen atas: <code><bottomPen lineWidth="0.0"/></code>
* Elemen bawah: <code><topPen lineWidth="0.0"/></code>

=== Tabel tanpa border penuh (gaya modern) ===

* Header kolom: hanya <code><bottomPen lineWidth="1.0" lineColor="#224435"/></code>
* Baris detail: hanya <code><bottomPen lineWidth="0.5" lineColor="#E0E0E0"/></code> di setiap sel (menjadi separator tipis antar-baris)
* Penekanan total: balok <code><rectangle></code> berlatar warna muda, bukan kotak border

== Setelah Menulis: Verifikasi ==

Jangan menganggap JRXML benar hanya dari membaca XML. Compile (dan bila perlu render) secara lokal — lihat [[JRXML Local Verification]].

[[Category:Development ERP]]

JasperReports

2026-09-16T15:27:35Z

Wikiadmin:

'''JasperReports''' adalah library reporting Java yang dipakai InfiniteERP (Openbravo) untuk mencetak dokumen (invoice, kuitansi, dan report lain) dari file template '''JRXML'''.

== Versi Library di Server ==

Berdasarkan pemeriksaan source code Openbravo, runtime report memakai:

* <code>jasperreports-6.0.0.jar</code>
* <code>jasperreports-fonts-6.0.0.jar</code>
* iText 5.5.x (package <code>com.itextpdf</code>) untuk export PDF — bukan iText lawas <code>com.lowagie</code> yang dipakai JasperReports 5.x

== Tool Desain ==

{| class="wikitable"
! Tool !! Library JasperReports bawaan !! Keterangan
|-
| iReport 5.6.0 || 5.6.0 || Legacy, sudah tidak dikembangkan
|-
| Jaspersoft Studio CE 6.21.x || 6.21.x || Tool desain aktif berbasis Eclipse
|}

File JRXML existing (contoh: <code>sales_invoice_SSD.jrxml</code>) dibuat dengan iReport 5.6, lalu sempat disentuh Jaspersoft Studio (terlihat dari property <code>com.jaspersoft.studio.*</code> dan atribut <code>splitType</code> di dalamnya).

== Kompatibilitas JRXML (Sudah Diuji) ==

Pengujian dilakukan dengan meng-compile JRXML memakai <code>jasperreports-6.0.0.jar</code> persis seperti di server:

{| class="wikitable"
! File JRXML !! Compile di JR 6.0.0 !! Export PDF
|-
| Asli (output iReport 5.6, ada <code>splitType</code>) || OK || —
|-
| Versi perbaikan (clean-up) || OK || OK
|-
| Layout baru (modern) || OK || OK
|}

Kesimpulan:

* Namespace lawas <code><nowiki>http://jasperreports.sourceforge.net/jasperreports</nowiki></code> '''sepenuhnya kompatibel''' dengan JR 6.0.0 — tidak perlu diubah.
* Parser JR 6.0.0 (bahkan 5.6.0) '''toleran''' terhadap atribut yang tidak dikenal; atribut asing diabaikan saat compile.
* Risiko sesungguhnya bukan di runtime, melainkan di '''editor''': iReport 5.6 dapat menghapus/mengacaukan atribut versi baru saat file di-edit lalu di-save.

== Mengedit dengan Jaspersoft Studio CE ==

Jaspersoft Studio Community Edition dapat diunduh di: [https://community.jaspersoft.com/download-jaspersoft/community-edition/jaspersoft-studio_6.21.2 Download Jaspersoft Studio CE 6.21.x]

Karena Studio 6.21.x membawa library JasperReports 6.21.x (lebih baru dari runtime server 6.0.0), perhatikan:

# Setelah mengedit, '''selalu compile ulang JRXML terhadap JR 6.0.0''' (lihat [[JRXML Local Verification]]) sebelum deploy — jangan mengandalkan preview Studio.
# Hindari memakai komponen/fitur yang hanya ada di versi baru (misal elemen <code><part></code>) kecuali runtime server memang di-upgrade.
# Property <code>com.jaspersoft.studio.*</code> yang ditulis Studio aman — diabaikan oleh runtime.
# Simpan file dengan encoding UTF-8 dan pertahankan namespace lawas agar tetap konsisten dengan report existing.

=== Setting Compatibility ke JasperReports 6.0.0 (Dokumentasi Resmi) ===

Jaspersoft Studio secara default memakai library versi bawaannya (Studio 6.21.x → JasperReports 6.21.x) untuk '''menyimpan JRXML''' dan '''meng-compile report'''. Karena runtime server InfiniteERP adalah JR 6.0.0, atur compatibility agar keduanya memakai 6.0.0:

# Buka '''Window > Preferences''' (di macOS: '''Jaspersoft Studio > Preferences''').
# Pilih '''Jaspersoft Studio > Compatibility'''.
# Pada bagian '''Source .jrxml Version''', pilih '''6.0.0''' di menu ''Version'' — JRXML akan disimpan dalam format versi tersebut.
# Centang '''Don't save Jaspersoft Studio properties''' — property khusus Studio (info layout, dimensi px/mm, data adapter terakhir dipakai) tidak ikut tersimpan ke JRXML.
# Pada bagian '''Compiler Settings''', pilih '''6.0.0''' di menu ''Version'' — report di-compile memakai JR 6.0.0.
# Jika 6.0.0 belum tersedia di menu, klik '''Manage JasperReports Versions''':
#* '''Add From Path''' — jika jar JR 6.0.0 sudah ada di lokal; arahkan ke direktori berisi JasperReports Library dan Studio akan memverifikasinya.
#* '''Add From URL''' — unduh dari SourceForge (https://sourceforge.net/projects/jasperreports/) atau URL lain; Studio mengunduh, memverifikasi jar, lalu menambahkannya ke menu.

Catatan dari dokumentasi resmi:

* Fitur report yang bergantung pada versi JasperReports lebih baru '''tidak akan tersedia''' saat memakai versi lebih lama.
* Pengaturan Compatibility ini ditujukan untuk report yang dipakai di aplikasi sendiri berbasis JasperReports Library (persis kasus Openbravo/InfiniteERP). Jika targetnya JasperReports Server, versi diatur di ''connection settings'' server.

Sumber resmi: [https://community.jaspersoft.com/documentation/jaspersoft%C2%AE-studio/tibco-jaspersoft-studio-user-guide/v621/setting-compatibility-earlier-versions/ TIBCO Jaspersoft Studio User Guide — Setting Compatibility with Earlier Versions of JasperReports Library] ([https://web.archive.org/web/20250804124055/https://community.jaspersoft.com/documentation/jaspersoft%C2%AE-studio/tibco-jaspersoft-studio-user-guide/v621/setting-compatibility-earlier-versions/ arsip Wayback, 4 Agustus 2025])

== Praktik dan Verifikasi ==

* [[JRXML Best Practices]] — aturan penulisan JRXML, jebakan umum, dan polanya
* [[JRXML Local Verification]] — cara compile + render JRXML di laptop tanpa server

[[Category:Development ERP]]

JRXML Local Verification

2026-09-16T11:35:17Z

Wikiadmin: Audit v4: validasi query --jdbc + cek encoding UTF-8

File:Jrxmlcheck.zip

2026-09-16T11:35:16Z

Wikiadmin: Wikiadmin uploaded a new version of File:Jrxmlcheck.zip

Tool CLI jrxmlcheck v1: compile & preview JRXML (JR 6.0.0)

JRXML Local Verification

2026-09-16T11:17:09Z

Wikiadmin: Audit v3: cek overlap teks & atribut PDF lawas

Halaman ini menjelaskan cara menguji file JRXML '''di laptop''' — compile dan render PDF tanpa men-deploy ke server InfiniteERP. Wajib dilakukan sebelum JRXML baru/diubah dipasang di server.

== Kenapa Verifikasi Lokal ==

* Kesalahan JRXML (ekspresi tidak valid, field tidak dideklarasikan, class salah) baru ketahuan saat compile — bukan dari membaca XML.
* Menguji di server berarti menyentuh sistem produksi; di laptop cukup 1 perintah Java.
* Klaim "compatible" harus dibuktikan dengan hasil compile terhadap '''versi library yang sama dengan server''' (6.0.0), bukan versi lain.

== Classpath (Terbukti Jalan) ==

Unduh dari Maven Central, taruh dalam satu folder (misal <code>lib6/</code>):

{| class="wikitable"
! Jar !! Fungsi
|-
| <code>jasperreports-6.0.0.jar</code> || Engine report — versi sama dengan server
|-
| <code>jasperreports-fonts-6.0.0.jar</code> || Font extension — sama dengan server
|-
| <code>commons-digester-2.1.jar</code>, <code>commons-collections-3.2.2.jar</code>, <code>commons-beanutils-1.9.4.jar</code>, <code>commons-logging-1.2.jar</code> || Dependensi parsing
|-
| <code>ecj-4.4.2.jar</code> || Compiler ekspresi (JDT)
|-
| <code>itextpdf-5.5.13.3.jar</code> || Export PDF (JR 6.x memakai package <code>com.itextpdf</code>)
|-
| <code>itext-pdfa-5.5.13.3.jar</code> || '''Wajib''' — <code>PdfAWriter</code> dipisah ke jar ini
|}

Jebakan versi yang sudah ditemukan:

* JR 6.x '''tidak''' memakai iText lawas <code>com.lowagie</code> (itu milik JR 5.x). Tanpa <code>itextpdf</code>, export gagal: <code>NoClassDefFoundError: com/itextpdf/text/DocumentException</code>.
* Tanpa <code>itext-pdfa</code>, export gagal: <code>NoClassDefFoundError: com/itextpdf/text/pdf/PdfAWriter</code>.
* Teruji jalan di '''Java 17'''.

== Langkah ==

=== 1. Compile ===

<syntaxhighlight lang="java">
JasperReport rep = JasperCompileManager.compileReport("report.jrxml");
</syntaxhighlight>

Compile sukses = JRXML valid dan kompatibel dengan JR 6.0.0.

=== 2. Fill dengan data dummy ===

Report ber-query SQL tidak butuh database untuk diuji — lewatkan datasource map:

<syntaxhighlight lang="java">
Map<String,Object> row = new HashMap<>();
row.put("bpnmae", "PT CONTOH PELANGGAN");
row.put("pricestd", new BigDecimal("5000000"));
// ... isi semua field sesuai deklarasi <field> di JRXML

Map<String,Object> params = new HashMap<>();
params.put("IMAGE_DIR", "/path/ke/folder/gambar");

JasperPrint print = JasperFillManager.fillReport(rep, params,
new JRMapCollectionDataSource(java.util.Collections.singletonList(row)));
</syntaxhighlight>

Catatan: ImageIO membaca gambar '''berdasarkan konten''', bukan ekstensi — file PNG bernama <code>.jpg</code> tetap ter-render (berguna untuk placeholder).

=== 3. Export PDF ===

<syntaxhighlight lang="java">
JRPdfExporter exporter = new JRPdfExporter();
exporter.setParameter(JRExporterParameter.JASPER_PRINT, print);
exporter.setParameter(JRExporterParameter.OUTPUT_FILE_NAME, "sample.pdf");
exporter.exportReport();
</syntaxhighlight>

Jalankan: <code>java -cp ".:lib6/*" NamaVerifier</code>

=== 4. Cek hasil ===

* Buka PDF dan periksa visual: overlap, teks terpotong, alignment angka.
* Untuk elemen grafis kritis (accent bar, latar blok), bisa dicek deterministik: konversi PDF ke PNG lalu baca warna piksel pada koordinat yang diharapkan. Cara ini terbukti menangkap bug outline hitam pada <code><rectangle></code> (lihat [[JRXML Best Practices]]).

== Tool CLI: jrxmlcheck ==

Untuk pengguna non-programmer tersedia tool CLI '''jrxmlcheck''' — satu perintah, tanpa menulis Java.

=== Unduh & Pasang ===

# Unduh '''[[Media:Jrxmlcheck.zip|Jrxmlcheck.zip]]''' (5 KB; halaman berkas: [[:File:Jrxmlcheck.zip]]).
# Ekstrak: <code>unzip Jrxmlcheck.zip</code> — terbentuk folder <code>cli/</code>.
# Beri izin eksekusi (sekali saja): <code>chmod +x cli/jrxmlcheck</code>
# Prasyarat: Java/JDK terpasang (teruji di Java 17), dan internet saat '''pertama''' dijalankan karena library JasperReports 6.0.0 diunduh otomatis dari Maven Central.

=== Cara Pakai ===

<pre>./cli/jrxmlcheck compile laporan.jrxml # cek valid & kompatibel JR 6.0.0
./cli/jrxmlcheck preview laporan.jrxml # buat PDF contoh, data otomatis
./cli/jrxmlcheck preview laporan.jrxml --images ./images # pakai folder gambar (logo/stempel/ttd)
./cli/jrxmlcheck preview laporan.jrxml --data data.txt # data sendiri, format: namafield=nilai</pre>

* Mode <code>preview</code> membaca deklarasi <code><field></code> di JRXML lalu membuat data contoh otomatis — langsung jalan tanpa menyiapkan apa pun. Jumlah baris contoh diatur dengan <code>--rows N</code>.
* Mode <code>audit</code> — pemeriksaan menyeluruh sebelum deploy:
** '''Font''' — setiap <code>fontName</code> dicek terhadap isi <code>jasperreports-fonts-6.0.0.jar</code> (DejaVu Sans/Serif/Sans Mono + SansSerif/Serif/Monospaced). Font lain akan disubstitusi diam-diam di server → layout bergeser.
** '''Path absolut''' pada <code>imageExpression</code> (mis. <code>/home/zaien_aji/...</code>) — harus diganti parameter seperti <code>$P{IMAGE_DIR}</code>.
** '''Geometri''' — elemen yang keluar batas band atau lebar kolom (tidak akan tercetak utuh).
** '''Variabel mati''' (variableExpression kosong) dan '''field/parameter tidak terpakai'''.
** '''Jejak Jaspersoft Studio''' (<code>splitType</code>, property <code>com.jaspersoft.studio.*</code>) — jadi peringatan bila diaudit dengan <code>--target ireport</code>.
** '''Elemen teks bertumpuk''' — dua elemen teks yang kotaknya beririsan >50% dari kotak terkecil (irisan tipis antar kolom kiri/kanan diabaikan karena umum & aman; teks di dalam kotak latar dan stempel-di-atas-tanda-tangan juga diabaikan — gambar bertumpuk hanya dicatat sebagai info).
** '''Atribut PDF lawas''' (<code>pdfFontName</code>, <code>pdfEncoding</code>, <code>isPdfEmbedded</code>) — deprecated, migrasikan ke font extension.
** <code>--strict</code>: exit code 1 bila ada peringatan — cocok untuk gerbang CI sebelum deploy.
* File data sendiri: teks biasa, satu <code>namafield=nilai</code> per baris, baris <code>#</code> untuk komentar.
* Pesan error diringkas ke penyebab utama beserta daftar penyebab umum (field tidak dideklarasikan, salah ketik nama field, class field salah, ekspresi bukan Java valid).
* PDF hasil terbuka otomatis di macOS (nonaktifkan dengan <code>--no-open</code>); nama file diatur dengan <code>--out</code>.
* Petunjuk lengkap juga tersedia di <code>README.txt</code> dalam paket.

== Hasil yang Pernah Diverifikasi ==

* <code>sales_invoice_SSD.jrxml</code> (asli, iReport 5.6): compile OK di JR 5.6.0 dan 6.0.0
* Versi perbaikan (parameter <code>IMAGE_DIR</code>, variable mati dihapus): compile + render OK
* Layout modern tanpa border penuh: compile + render OK, cek piksel lolos

[[Category:Development]]

File:Jrxmlcheck.zip

2026-09-16T11:17:08Z

Wikiadmin: Wikiadmin uploaded a new version of File:Jrxmlcheck.zip

Tool CLI jrxmlcheck v1: compile & preview JRXML (JR 6.0.0)

JRXML Local Verification

2026-09-16T11:08:37Z

Wikiadmin: Dokumentasi mode audit jrxmlcheck v2

Halaman ini menjelaskan cara menguji file JRXML '''di laptop''' — compile dan render PDF tanpa men-deploy ke server InfiniteERP. Wajib dilakukan sebelum JRXML baru/diubah dipasang di server.

== Kenapa Verifikasi Lokal ==

* Kesalahan JRXML (ekspresi tidak valid, field tidak dideklarasikan, class salah) baru ketahuan saat compile — bukan dari membaca XML.
* Menguji di server berarti menyentuh sistem produksi; di laptop cukup 1 perintah Java.
* Klaim "compatible" harus dibuktikan dengan hasil compile terhadap '''versi library yang sama dengan server''' (6.0.0), bukan versi lain.

== Classpath (Terbukti Jalan) ==

Unduh dari Maven Central, taruh dalam satu folder (misal <code>lib6/</code>):

{| class="wikitable"
! Jar !! Fungsi
|-
| <code>jasperreports-6.0.0.jar</code> || Engine report — versi sama dengan server
|-
| <code>jasperreports-fonts-6.0.0.jar</code> || Font extension — sama dengan server
|-
| <code>commons-digester-2.1.jar</code>, <code>commons-collections-3.2.2.jar</code>, <code>commons-beanutils-1.9.4.jar</code>, <code>commons-logging-1.2.jar</code> || Dependensi parsing
|-
| <code>ecj-4.4.2.jar</code> || Compiler ekspresi (JDT)
|-
| <code>itextpdf-5.5.13.3.jar</code> || Export PDF (JR 6.x memakai package <code>com.itextpdf</code>)
|-
| <code>itext-pdfa-5.5.13.3.jar</code> || '''Wajib''' — <code>PdfAWriter</code> dipisah ke jar ini
|}

Jebakan versi yang sudah ditemukan:

* JR 6.x '''tidak''' memakai iText lawas <code>com.lowagie</code> (itu milik JR 5.x). Tanpa <code>itextpdf</code>, export gagal: <code>NoClassDefFoundError: com/itextpdf/text/DocumentException</code>.
* Tanpa <code>itext-pdfa</code>, export gagal: <code>NoClassDefFoundError: com/itextpdf/text/pdf/PdfAWriter</code>.
* Teruji jalan di '''Java 17'''.

== Langkah ==

=== 1. Compile ===

<syntaxhighlight lang="java">
JasperReport rep = JasperCompileManager.compileReport("report.jrxml");
</syntaxhighlight>

Compile sukses = JRXML valid dan kompatibel dengan JR 6.0.0.

=== 2. Fill dengan data dummy ===

Report ber-query SQL tidak butuh database untuk diuji — lewatkan datasource map:

<syntaxhighlight lang="java">
Map<String,Object> row = new HashMap<>();
row.put("bpnmae", "PT CONTOH PELANGGAN");
row.put("pricestd", new BigDecimal("5000000"));
// ... isi semua field sesuai deklarasi <field> di JRXML

Map<String,Object> params = new HashMap<>();
params.put("IMAGE_DIR", "/path/ke/folder/gambar");

JasperPrint print = JasperFillManager.fillReport(rep, params,
new JRMapCollectionDataSource(java.util.Collections.singletonList(row)));
</syntaxhighlight>

Catatan: ImageIO membaca gambar '''berdasarkan konten''', bukan ekstensi — file PNG bernama <code>.jpg</code> tetap ter-render (berguna untuk placeholder).

=== 3. Export PDF ===

<syntaxhighlight lang="java">
JRPdfExporter exporter = new JRPdfExporter();
exporter.setParameter(JRExporterParameter.JASPER_PRINT, print);
exporter.setParameter(JRExporterParameter.OUTPUT_FILE_NAME, "sample.pdf");
exporter.exportReport();
</syntaxhighlight>

Jalankan: <code>java -cp ".:lib6/*" NamaVerifier</code>

=== 4. Cek hasil ===

* Buka PDF dan periksa visual: overlap, teks terpotong, alignment angka.
* Untuk elemen grafis kritis (accent bar, latar blok), bisa dicek deterministik: konversi PDF ke PNG lalu baca warna piksel pada koordinat yang diharapkan. Cara ini terbukti menangkap bug outline hitam pada <code><rectangle></code> (lihat [[JRXML Best Practices]]).

== Tool CLI: jrxmlcheck ==

Untuk pengguna non-programmer tersedia tool CLI '''jrxmlcheck''' — satu perintah, tanpa menulis Java.

=== Unduh & Pasang ===

# Unduh '''[[Media:Jrxmlcheck.zip|Jrxmlcheck.zip]]''' (5 KB; halaman berkas: [[:File:Jrxmlcheck.zip]]).
# Ekstrak: <code>unzip Jrxmlcheck.zip</code> — terbentuk folder <code>cli/</code>.
# Beri izin eksekusi (sekali saja): <code>chmod +x cli/jrxmlcheck</code>
# Prasyarat: Java/JDK terpasang (teruji di Java 17), dan internet saat '''pertama''' dijalankan karena library JasperReports 6.0.0 diunduh otomatis dari Maven Central.

=== Cara Pakai ===

<pre>./cli/jrxmlcheck compile laporan.jrxml # cek valid & kompatibel JR 6.0.0
./cli/jrxmlcheck preview laporan.jrxml # buat PDF contoh, data otomatis
./cli/jrxmlcheck preview laporan.jrxml --images ./images # pakai folder gambar (logo/stempel/ttd)
./cli/jrxmlcheck preview laporan.jrxml --data data.txt # data sendiri, format: namafield=nilai</pre>

* Mode <code>preview</code> membaca deklarasi <code><field></code> di JRXML lalu membuat data contoh otomatis — langsung jalan tanpa menyiapkan apa pun. Jumlah baris contoh diatur dengan <code>--rows N</code>.
* Mode <code>audit</code> — pemeriksaan menyeluruh sebelum deploy:
** '''Font''' — setiap <code>fontName</code> dicek terhadap isi <code>jasperreports-fonts-6.0.0.jar</code> (DejaVu Sans/Serif/Sans Mono + SansSerif/Serif/Monospaced). Font lain akan disubstitusi diam-diam di server → layout bergeser.
** '''Path absolut''' pada <code>imageExpression</code> (mis. <code>/home/zaien_aji/...</code>) — harus diganti parameter seperti <code>$P{IMAGE_DIR}</code>.
** '''Geometri''' — elemen yang keluar batas band atau lebar kolom (tidak akan tercetak utuh).
** '''Variabel mati''' (variableExpression kosong) dan '''field/parameter tidak terpakai'''.
** '''Jejak Jaspersoft Studio''' (<code>splitType</code>, property <code>com.jaspersoft.studio.*</code>) — jadi peringatan bila diaudit dengan <code>--target ireport</code>.
** <code>--strict</code>: exit code 1 bila ada peringatan — cocok untuk gerbang CI sebelum deploy.
* File data sendiri: teks biasa, satu <code>namafield=nilai</code> per baris, baris <code>#</code> untuk komentar.
* Pesan error diringkas ke penyebab utama beserta daftar penyebab umum (field tidak dideklarasikan, salah ketik nama field, class field salah, ekspresi bukan Java valid).
* PDF hasil terbuka otomatis di macOS (nonaktifkan dengan <code>--no-open</code>); nama file diatur dengan <code>--out</code>.
* Petunjuk lengkap juga tersedia di <code>README.txt</code> dalam paket.

== Hasil yang Pernah Diverifikasi ==

* <code>sales_invoice_SSD.jrxml</code> (asli, iReport 5.6): compile OK di JR 5.6.0 dan 6.0.0
* Versi perbaikan (parameter <code>IMAGE_DIR</code>, variable mati dihapus): compile + render OK
* Layout modern tanpa border penuh: compile + render OK, cek piksel lolos

[[Category:Development]]

File:Jrxmlcheck.zip

2026-09-16T11:08:36Z

Wikiadmin: Wikiadmin uploaded a new version of File:Jrxmlcheck.zip

Tool CLI jrxmlcheck v1: compile & preview JRXML (JR 6.0.0)

JRXML Local Verification

2026-09-16T10:55:04Z

Wikiadmin: Tool jrxmlcheck: ganti referensi path lokal menjadi link unduh Media:Jrxmlcheck.zip + petunjuk pasang

File:Jrxmlcheck.zip

2026-09-16T10:53:33Z

Wikiadmin: Tool CLI jrxmlcheck v1: compile & preview JRXML (JR 6.0.0)

Tool CLI jrxmlcheck v1: compile & preview JRXML (JR 6.0.0)

JRXML Local Verification

2026-09-16T10:39:13Z

Wikiadmin: Tambah dokumentasi tool CLI jrxmlcheck

JasperReports

2026-09-16T10:25:52Z

Wikiadmin: Tambah prosedur resmi Setting Compatibility Jaspersoft Studio ke JR 6.0.0 + sumber

JRXML Best Practices

2026-09-16T10:15:26Z

Wikiadmin: Dokumentasi

JRXML Local Verification

2026-09-16T10:15:26Z

Wikiadmin: Dokumentasi

JasperReports

2026-09-16T10:15:24Z

Wikiadmin: Dokumentasi

Getting started with Openbravo/id

2026-08-29T02:34:37Z

Wikiadmin: test

{{Languages}}

== Getting started with Openbravo (Bahasa Indonesia) ==

Stub.

Release Notes

2026-08-28T12:20:14Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

== Introduction ==
This page documents the official Openbravo quarterly Platform Releases, including the release notes and maturity status.

Additional Release status and schedules information are available following [[ERP/Release_Life_Cycle | this link]].

== Openbravo Business Suite releases ==

{| align="center" width="100%"
!Release Notes
!Date
!Version
![http://wiki.openbravo.com/wiki/Modules_Management#Maturity_Status Maturity Status] (*)

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q4.1| 3.0PR21Q4.1]]
|width="10%" |16/11/2021
|width="10%" |3.0.214101
|width="10%" |QAA

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q4| 3.0PR21Q4]]
|width="10%" |28/10/2021
|width="10%" |3.0.214003
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q3.5| 3.0PR21Q3.5]]
|width="10%" |16/11/2021
|width="10%" |3.0.213501
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q3.4| 3.0PR21Q3.4]]
|width="10%" |27/10/2021
|width="10%" |3.0.213401
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q3.3| 3.0PR21Q3.3]]
|width="10%" |20/10/2021
|width="10%" |3.0.213301
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q3.2| 3.0PR21Q3.2]]
|width="10%" |15/09/2021
|width="10%" |3.0.213201
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q3.1| 3.0PR21Q3.1]]
|width="10%" |31/08/2021
|width="10%" |3.0.213101
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q3| 3.0PR21Q3]]
|width="10%" |03/08/2021
|width="10%" |3.0.213003
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q2.4| 3.0PR21Q2.4]]
|width="10%" |20/10/2021
|width="10%" |3.0.212401
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q2.3| 3.0PR21Q2.3]]
|width="10%" |15/09/2021
|width="10%" |3.0.212301
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q2.2| 3.0PR21Q2.2]]
|width="10%" |31/08/2021
|width="10%" |3.0.212201
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q2.1| 3.0PR21Q2.1]]
|width="10%" |29/07/2021
|width="10%" |3.0.212101
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q2| 3.0PR21Q2]]
|width="10%" |11/06/2021
|width="10%" |3.0.212003
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q1.3| 3.0PR21Q1.3]]
|width="10%" |09/06/2021
|width="10%" |3.0.211301
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q1.2| 3.0PR21Q1.2]]
|width="10%" |31/05/2021
|width="10%" |3.0.211202
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q1.1| 3.0PR21Q1.1]]
|width="10%" |08/04/2021
|width="10%" |3.0.211101
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR21Q1| 3.0PR21Q1]]
|width="10%" |04/03/2021
|width="10%" |3.0.211004
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q4.4| 3.0PR20Q4.4]]
|width="10%" |31/05/2021
|width="10%" |3.0.204402
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q4.3| 3.0PR20Q4.3]]
|width="10%" |06/04/2021
|width="10%" |3.0.204301
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q4.2| 3.0PR20Q4.2]]
|width="10%" |02/03/2021
|width="10%" |3.0.204201
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q4.1| 3.0PR20Q4.1]]
|width="10%" |21/01/2021
|width="10%" |3.0.204101
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q4| 3.0PR20Q4]]
|width="10%" |03/12/2020
|width="10%" |3.0.204003
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q3.4| 3.0PR20Q3.4]]
|width="10%" |26/02/2021
|width="10%" |3.0.203401
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q3.3| 3.0PR20Q3.3]]
|width="10%" |21/01/2021
|width="10%" |3.0.203301
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q3.2| 3.0PR20Q3.2]]
|width="10%" |02/12/2020
|width="10%" |3.0.203201
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q3.1| 3.0PR20Q3.1]]
|width="10%" |22/09/2020
|width="10%" |3.0.203101
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q3| 3.0PR20Q3]]
|width="10%" |10/08/2020
|width="10%" |3.0.203002
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q2.2| 3.0PR20Q2.2]]
|width="10%" |23/09/2020
|width="10%" |3.0.202201
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q2.1| 3.0PR20Q2.1]]
|width="10%" |03/08/2020
|width="10%" |3.0.202101
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q2| 3.0PR20Q2]]
|width="10%" |04/06/2020
|width="10%" |3.0.37242
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q1.3| 3.0PR20Q1.3]]
|width="10%" |04/08/2020
|width="10%" |3.0.201301
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q1.2| 3.0PR20Q1.2]]
|width="10%" |04/06/2020
|width="10%" |3.0.36908
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q1.1| 3.0PR20Q1.1]]
|width="10%" |30/04/2020
|width="10%" |3.0.36902
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR20Q1 | 3.0PR20Q1]]
|width="10%" |18/03/2020
|width="10%" |3.0.36897
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q4.4 | 3.0PR19Q4.4]]
|width="10%" |28/04/2020
|width="10%" |3.0.36580
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q4.3 | 3.0PR19Q4.3]]
|width="10%" |12/03/2020
|width="10%" |3.0.36577
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q4.2 | 3.0PR19Q4.2]]
|width="10%" |25/02/2020
|width="10%" |3.0.36576
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q4.1 | 3.0PR19Q4.1]]
|width="10%" |06/01/2020
|width="10%" |3.0.36568
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q4 | 3.0PR19Q4]]
|width="10%" |12/12/2019
|width="10%" |3.0.36563
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q3.4 | 3.0PR19Q3.4]]
|width="10%" |20/02/2020
|width="10%" |3.0.36257
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q3.3 | 3.0PR19Q3.3]]
|width="10%" |02/01/2020
|width="10%" |3.0.36249
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q3.2 | 3.0PR19Q3.2]]
|width="10%" |08/11/2019
|width="10%" |3.0.36241
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q3.1 | 3.0PR19Q3.1]]
|width="10%" |30/09/2019
|width="10%" |3.0.36238
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q3 | 3.0PR19Q3]]
|width="10%" |22/08/2019
|width="10%" |3.0.36231
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q2.3 | 3.0PR19Q2.3]]
|width="10%" |30/09/2019
|width="10%" |3.0.35659
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q2.2 | 3.0PR19Q2.2]]
|width="10%" |08/08/2019
|width="10%" |3.0.35653
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q2.1 | 3.0PR19Q2.1]]
|width="10%" |22/07/2019
|width="10%" |3.0.35650
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q2 | 3.0PR19Q2]]
|width="10%" |21/05/2019
|width="10%" |3.0.35625
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q1.2 | 3.0PR19Q1.2]]
|width="10%" |15/07/2019
|width="10%" |3.0.35359
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q1.1 | 3.0PR19Q1.1]]
|width="10%" |08/05/2019
|width="10%" |3.0.35341
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR19Q1 | 3.0PR19Q1]]
|width="10%" |27/03/2019
|width="10%" |3.0.35325
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q4.3 | 3.0PR18Q4.3]]
|width="10%" |17/04/2019
|width="10%" |3.0.34866
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q4.2 | 3.0PR18Q4.2]]
|width="10%" |01/03/2019
|width="10%" |3.0.34861
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q4.1 | 3.0PR18Q4.1]]
|width="10%" |27/12/2018
|width="10%" |3.0.34849
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q4 | 3.0PR18Q4]]
|width="10%" |12/12/2018
|width="10%" |3.0.34846
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q3.5 | 3.0PR18Q3.5]]
|width="10%" |26/02/2019
|width="10%" |3.0.3432
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q3.4 | 3.0PR18Q3.4]]
|width="10%" |27/12/2018
|width="10%" |3.0.34302
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q3.3 | 3.0PR18Q3.3]]
|width="10%" |28/11/2018
|width="10%" |3.0.34292
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q3.2 | 3.0PR18Q3.2]]
|width="10%" |31/10/2018
|width="10%" |3.0.34284
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q3.1 | 3.0PR18Q3.1]]
|width="10%" |27/09/2018
|width="10%" |3.0.34272
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q3 | 3.0PR18Q3]]
|width="10%" |08/08/2018
|width="10%" |3.0.34267
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q2.3 | 3.0PR18Q2.3]]
|width="10%" |30/10/2018
|width="10%" |3.0.33814
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q2.2 | 3.0PR18Q2.2]]
|width="10%" |22/08/2018
|width="10%" |3.0.33803
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q2.1 | 3.0PR18Q2.1]]
|width="10%" |12/07/2018
|width="10%" |3.0.33797
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q2 | 3.0PR18Q2]]
|width="10%" |09/05/2018
|width="10%" |3.0.33777
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q1.3 | 3.0PR18Q1.3]]
|width="10%" |17/05/2018
|width="10%" |3.0.33196
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q1.2 | 3.0PR18Q1.2]]
|width="10%" |24/04/2018
|width="10%" |3.0.33194
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q1.1 | 3.0PR18Q1.1]]
|width="10%" |26/03/2018
|width="10%" |3.0.33192
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR18Q1 | 3.0PR18Q1]]
|width="10%" |21/02/2018
|width="10%" |3.0.33184
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q4.2 | 3.0PR17Q4.2]]
|width="10%" |23/03/2018
|width="10%" |3.0.32891
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q4.1 | 3.0PR17Q4.1]]
|width="10%" |20/02/2018
|width="10%" |3.0.32880
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q4 | 3.0PR17Q4]]
|width="10%" |29/12/2017
|width="10%" |3.0.32857
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q3.3 | 3.0PR17Q3.3]]
|width="10%" |01/02/2018
|width="10%" |3.0.32432
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q3.2 | 3.0PR17Q3.2]]
|width="10%" |28/12/2017
|width="10%" |3.0.32425
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q3.1 | 3.0PR17Q3.1]]
|width="10%" |07/11/2017
|width="10%" |3.0.32416
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q3 | 3.0PR17Q3]]
|width="10%" |21/09/2017
|width="10%" |3.0.32403
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q2.4 | 3.0PR17Q2.4]]
|width="10%" |06/11/2017
|width="10%" |3.0.31816
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q2.3 | 3.0PR17Q2.3]]
|width="10%" |14/09/2017
|width="10%" |3.0.31811
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q2.2 | 3.0PR17Q2.2]]
|width="10%" |10/08/2017
|width="10%" |3.0.31802
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q2.1 | 3.0PR17Q2.1]]
|width="10%" |28/06/2017
|width="10%" |3.0.31796
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q2 | 3.0PR17Q2]]
|width="10%" |18/04/2017
|width="10%" |3.0.31787
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q1.3 | 3.0PR17Q1.3]]
|width="10%" |23/06/2017
|width="10%" |3.0.31116
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q1.2 | 3.0PR17Q1.2]]
|width="10%" |23/06/2017
|width="10%" |3.0.31111
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q1.1 | 3.0PR17Q1.1]]
|width="10%" |05/05/2017
|width="10%" |3.0.31101
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR17Q1 | 3.0PR17Q1]]
|width="10%" |15/03/2017
|width="10%" |3.0.31087
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q4.4 | 3.0PR16Q4.4]]
|width="10%" |09/03/2017
|width="10%" |3.0.30460
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q4.3 | 3.0PR16Q4.3]]
|width="10%" |09/03/2017
|width="10%" |3.0.30460
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q4.2 | 3.0PR16Q4.2]]
|width="10%" |24/01/2017
|width="10%" |3.0.30447
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q4.1 | 3.0PR16Q4.1]]
|width="10%" |23/01/2017
|width="10%" |3.0.30445
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q4 | 3.0PR16Q4]]
|width="10%" |16/12/2016
|width="10%" |3.0.30440
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q3.5 | 3.0PR16Q3.5]]
|width="10%" |27/01/2017
|width="10%" |3.0.29799
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q3.4 | 3.0PR16Q3.4]]
|width="10%" |18/01/2017
|width="10%" |3.0.29789
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q3.3 | 3.0PR16Q3.3]]
|width="10%" |23/11/2016
|width="10%" |3.0.29786
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q3.2 | 3.0PR16Q3.2]]
|width="10%" |13/10/2016
|width="10%" |3.0.29751
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q3.1 | 3.0PR16Q3.1]]
|width="10%" |01/09/2016
|width="10%" |3.0.29734
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q3 | 3.0PR16Q3]]
|width="10%" |11/08/2016
|width="10%" |3.0.29727
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q2.4 | 3.0PR16Q2.4]]
|width="10%" |18/11/2016
|width="10%" |3.0.28902
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q2.3 | 3.0PR16Q2.3]]
|width="10%" |04/10/2016
|width="10%" |3.0.28899
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q2.2 | 3.0PR16Q2.2]]
|width="10%" |26/08/2016
|width="10%" |3.0.28883
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q2.1 | 3.0PR16Q2.1]]
|width="10%" |11/07/2016
|width="10%" |3.0.28873
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q2 | 3.0PR16Q2]]
|width="10%" |16/06/2016
|width="10%" |3.0.28860
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q1.3 | 3.0PR16Q1.3]]
|width="10%" |07/06/2016
|width="10%" |3.0.28231
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q1.2 | 3.0PR16Q1.2]]
|width="10%" |26/05/2016
|width="10%" |3.0.28226
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q1.1 | 3.0PR16Q1.1]]
|width="10%" |29/04/2016
|width="10%" |3.0.28220
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR16Q1 | 3.0PR16Q1]]
|width="10%" |15/03/2016
|width="10%" |3.0.28207
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q4.6 | 3.0PR15Q4.6]]
|width="10%" |27/04/2016
|width="10%" |3.0.27708
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q4.5 | 3.0PR15Q4.5]]
|width="10%" |18/03/2016
|width="10%" |3.0.27703
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q4.4 | 3.0PR15Q4.4]]
|width="10%" |01/03/2016
|width="10%" |3.0.27695
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q4.3 | 3.0PR15Q4.3]]
|width="10%" |15/02/2016
|width="10%" |3.0.27688
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q4.2 | 3.0PR15Q4.2]]
|width="10%" |25/01/2016
|width="10%" |3.0.27681
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q4.1 | 3.0PR15Q4.1]]
|width="10%" |16/12/2015
|width="10%" |3.0.27665
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q4 | 3.0PR15Q4]]
|width="10%" |23/11/2015
|width="10%" |3.0.27657
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q3.5 | 3.0PR15Q3.5]]
|width="10%" |22/01/2016
|width="10%" |3.0.27124
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q3.4 | 3.0PR15Q3.4]]
|width="10%" |10/12/2015
|width="10%" |3.0.27112
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q3.3 | 3.0PR15Q3.3]]
|width="10%" |03/11/2015
|width="10%" |3.0.27099
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q3.2 | 3.0PR15Q3.2]]
|width="10%" |27/10/2015
|width="10%" |3.0.27096
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q3.1 | 3.0PR15Q3.1]]
|width="10%" |8/9/2015
|width="10%" |3.0.27080
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q3 | 3.0PR15Q3]]
|width="10%" |18/08/2015
|width="10%" |3.0.27073
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q2.6 | 3.0PR15Q2.6]]
|width="10%" |26/10/2015
|width="10%" |3.0.26471
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q2.5 | 3.0PR15Q2.5]]
|width="10%" |18/09/2015
|width="10%" |3.0.26460
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q2.4 | 3.0PR15Q2.4]]
|width="10%" |26/08/2015
|width="10%" |3.0.26456
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q2.3 | 3.0PR15Q2.3]]
|width="10%" |29/07/2015
|width="10%" |3.0.26448
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q2.2 | 3.0PR15Q2.2]]
|width="10%" |22/06/2015
|width="10%" |3.0.26430
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q2.1 | 3.0PR15Q2.1]]
|width="10%" |21/05/2015
|width="10%" |3.0.26407
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q2 | 3.0PR15Q2]]
|width="10%" |06/05/2015
|width="10%" |3.0.26393
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q1.5 | 3.0PR15Q1.5]]
|width="10%" |19/06/2015
|width="10%" |3.0.25877
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q1.4 | 3.0PR15Q1.4]]
|width="10%" |21/05/2015
|width="10%" |3.0.25852
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q1.3 | 3.0PR15Q1.3]]
|width="10%" |17/04/2015
|width="10%" |3.0.25819
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q1.2 | 3.0PR15Q1.2]]
|width="10%" |01/04/2015
|width="10%" |3.0.25793
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q1.1 | 3.0PR15Q1.1]]
|width="10%" |20/02/2015
|width="10%" |3.0.25735
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR15Q1 | 3.0PR15Q1]]
|width="10%" |2/02/2015
|width="10%" |3.0.25704
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q4 | 3.0PR14Q4]]
|width="10%" |30/12/2014
|width="10%" |3.0.25161
|width="10%" |QAA

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3.8 | 3.0PR14Q3.8]]
|width="10%" |24/03/2015
|width="10%" |3.0.24112
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3.7 | 3.0PR14Q3.7]]
|width="10%" |24/02/2015
|width="10%" |3.0.24089
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3.6 | 3.0PR14Q3.6]]
|width="10%" |05/02/2015
|width="10%" |3.0.24075
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3.5 | 3.0PR14Q3.5]]
|width="10%" |15/01/2015
|width="10%" |3.0.24063
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3.4 | 3.0PR14Q3.4]]
|width="10%" |05/12/2014
|width="10%" |3.0.24052
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3.3 | 3.0PR14Q3.3]]
|width="10%" |14/11/2014
|width="10%" |3.0.24041
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3.2 | 3.0PR14Q3.2]]
|width="10%" |24/10/2014
|width="10%" |3.0.24034
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3.1 | 3.0PR14Q3.1]]
|width="10%" |05/09/2014
|width="10%" |3.0.24019
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q3 | 3.0PR14Q3]]
|width="10%" |06/08/2014
|width="10%" |3.0.24005
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q2.6 | 3.0PR14Q2.6]]
|width="10%" |01/10/2014
|width="10%" |3.0.22943
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q2.5 | 3.0PR14Q2.5]]
|width="10%" |04/08/2014
|width="10%" |3.0.22936
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q2.4 | 3.0PR14Q2.4]]
|width="10%" |18/07/2014
|width="10%" |3.0.22925
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q2.3 | 3.0PR14Q2.3]]
|width="10%" |27/06/2014
|width="10%" |3.0.22913
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q2.2 | 3.0PR14Q2.2]]
|width="10%" |19/06/2014
|width="10%" |3.0.22896
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q2.1 | 3.0PR14Q2.1]]
|width="10%" |22/05/2014
|width="10%" |3.0.22859
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0PR14Q2 | 3.0PR14Q2]]
|width="10%" |07/05/2014
|width="10%" |3.0.22845
|width="10%" |C
|}

'''(*)''': Maturity Levels Legend:
* CS : Confirmed Stable
* QAA : QA Approved
* C : Cancelled

== Maintenance packs ==

Before changing the release cycle to be quarterly we released monthly ''Maintenance Packs''.

{| align="center" width="100%"
!Release Notes
!Date
!Version
![http://wiki.openbravo.com/wiki/Modules_Management#Maturity_Status Maturity Status] (*)

|- align="center"
|width="10%" |[[Release_Notes/3.0MP31.4 | 3.0MP31.4]]
|width="10%" |11/06/2014
|width="10%" |3.0.21811
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP31.3 | 3.0MP31.3]]
|width="10%" |14/05/2014
|width="10%" |3.0.21803
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP31.2 | 3.0MP31.2]]
|width="10%" |28/02/2014
|width="10%" |3.0.21792
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP31.1 | 3.0MP31.1]]
|width="10%" |15/02/2014
|width="10%" |3.0.21782
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP31 | 3.0MP31]]
|width="10%" |18/01/2014
|width="10%" |3.0.21766
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP30.3 | 3.0MP30.3]]
|width="10%" |13/02/2014
|width="10%" |3.0.21573
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP30.2 | 3.0MP30.2]]
|width="10%" |28/01/2014
|width="10%" |3.0.21560
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP30.1 | 3.0MP30.1]]
|width="10%" |09/01/2014
|width="10%" |3.0.21549
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP30 | 3.0MP30]]
|width="10%" |18/12/2013
|width="10%" |3.0.21543
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP29.4 | 3.0MP29.4]]
|width="10%" |20/01/2014
|width="10%" |3.0.21451
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP29.3 | 3.0MP29.3]]
|width="10%" |10/01/2014
|width="10%" |3.0.21444
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP29.2 | 3.0MP29.2]]
|width="10%" |30/12/2013
|width="10%" |3.0.21440
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP29.1 | 3.0MP29.1]]
|width="10%" |21/11/2013
|width="10%" |3.0.21423
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP29 | 3.0MP29]]
|width="10%" |19/11/2013
|width="10%" |3.0.21419
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP28.5 | 3.0MP28.5]]
|width="10%" |24/12/2013
|width="10%" |3.0.21285
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP28.4 | 3.0MP28.4]]
|width="10%" |19/12/2013
|width="10%" |3.0.21283
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP28.3 | 3.0MP28.3]]
|width="10%" |04/12/2013
|width="10%" |3.0.21275
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP28.2 | 3.0MP28.2]]
|width="10%" |22/10/2013
|width="10%" |3.0.21255
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP28.1 | 3.0MP28.1]]
|width="10%" |18/10/2013
|width="10%" |3.0.21253
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP28 | 3.0MP28]]
|width="10%" |15/10/2013
|width="10%" |3.0.21251
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP27.1 | 3.0MP27.1]]
|width="10%" |25/10/2013
|width="10%" |3.0.21096
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP27 | 3.0MP27]]
|width="10%" |18/09/2013
|width="10%" |3.0.21083
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP26.4 | 3.0MP26.4]]
|width="10%" |21/10/2013
|width="10%" |3.0.20857
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP26.3 | 3.0MP26.3]]
|width="10%" |10/10/2013
|width="10%" |3.0.20852
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP26.2 | 3.0MP26.2]]
|width="10%" |06/09/2013
|width="10%" |3.0.20842
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP26.1 | 3.0MP26.1]]
|width="10%" |27/08/2013
|width="10%" |3.0.20838
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP26 | 3.0MP26]]
|width="10%" |27/08/2013
|width="10%" |3.0.20833
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP25.2 | 3.0MP25.2]]
|width="10%" |05/09/2013
|width="10%" |3.0.20698
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP25.1 | 3.0MP25.1]]
|width="10%" |16/07/2013
|width="10%" |3.0.20695
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP25 | 3.0MP25]]
|width="10%" |16/07/2013
|width="10%" |3.0.20689
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP24.2 | 3.0MP24.2]]
|width="10%" |17/07/2013
|width="10%" |3.0.20531
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP24.1 | 3.0MP24.1]]
|width="10%" |28/06/2013
|width="10%" |3.0.20527
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP24 | 3.0MP24]]
|width="10%" |20/06/2013
|width="10%" |3.0.20523
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP23.2 | 3.0MP23.2]]
|width="10%" |10/07/2013
|width="10%" |3.0.20281
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP23.1 | 3.0MP23.1]]
|width="10%" |26/06/2013
|width="10%" |3.0.20278
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP23 | 3.0MP23]]
|width="10%" |21/05/2013
|width="10%" |3.0.20267
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP22.3 | 3.0MP22.3]]
|width="10%" |22/05/2013
|width="10%" |3.0.20088
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP22.2 | 3.0MP22.2]]
|width="10%" |02/05/2013
|width="10%" |3.0.20079
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP22.1 | 3.0MP22.1]]
|width="10%" |17/04/2013
|width="10%" |3.0.20067
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP22 | 3.0MP22]]
|width="10%" |15/04/2013
|width="10%" |3.0.20065
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP21.1 | 3.0MP21.1]]
|width="10%" |17/05/2013
|width="10%" |3.0.19883
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP21 | 3.0MP21]]
|width="10%" |22/03/2013
|width="10%" |3.0.19865
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP20 | 3.0MP20]]
|width="10%" |19/02/2013
|width="10%" |3.0.19641
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP19.4 | 3.0MP19.4]]
|width="10%" |20/02/2013
|width="10%" |3.0.19251
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP19.3 | 3.0 MP19.3]]
|width="10%" |31/01/2013
|width="10%" |3.0.19241
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP19.2 | 3.0 MP19.2]]
|width="10%" |24/01/2013
|width="10%" |3.0.19233
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP19.1 | 3.0 MP19.1]]
|width="10%" |21/01/2013
|width="10%" |3.0.19229
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP19 | 3.0 MP19]]
|width="10%" |21/01/2013
|width="10%" |3.0.19226
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP18.5 | 3.0MP18.5]]
|width="10%" |15/02/2013
|width="10%" |3.0.19042
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP18.4 | 3.0MP18.4]]
|width="10%" |28/01/2013
|width="10%" |3.0.19037
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP18.3 | 3.0MP18.3]]
|width="10%" |22/01/2013
|width="10%" |3.0.19035
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP18.2 | 3.0 MP18.2]]
|width="10%" |12/01/2013
|width="10%" |3.0.19028
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP18.1 | 3.0 MP18.1]]
|width="10%" |27/12/2012
|width="10%" |3.0.19016
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP18 | 3.0 MP18]]
|width="10%" |17/12/2012
|width="10%" |3.0.19013
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP17.3 | 3.0 MP17.3]]
|width="10%" |15/01/2012
|width="10%" |3.0.18540
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP17.2 | 3.0 MP17.2]]
|width="10%" |24/12/2012
|width="10%" |3.0.18537
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP17.1 | 3.0 MP17.1]]
|width="10%" |09/12/2012
|width="10%" |3.0.18529
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP17 | 3.0 MP17]]
|width="10%" |15/11/2012
|width="10%" |3.0.18521
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP16.3 | 3.0 MP16.3]]
|width="10%" |29/11/2012
|width="10%" |3.0.18151
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP16.2 | 3.0 MP16.2]]
|width="10%" |22/11/2012
|width="10%" |3.0.18145
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP16.1 | 3.0 MP16.1]]
|width="10%" |02/11/2012
|width="10%" |3.0.18142
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP16 | 3.0 MP16]]
|width="10%" |10/10/2012
|width="10%" |3.0.18129
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP15.2 | 3.0 MP15.2]]
|width="10%" |01/11/2012
|width="10%" |3.0.17898
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP15.1 | 3.0 MP15.1]]
|width="10%" |05/10/2012
|width="10%" |3.0.17889
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP15 | 3.0 MP15]]
|width="10%" |25/09/2012
|width="10%" |3.0.17885
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP14.2 | 3.0 MP14.2]]
|width="10%" |26/10/2012
|width="10%" |3.0.17646
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP14.1 | 3.0 MP14.1]]
|width="10%" |03/10/2012
|width="10%" |3.0.17641
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP14 | 3.0 MP14]]
|width="10%" |06/09/2012
|width="10%" |3.0.17628
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP13.2 | 3.0 MP13.2]]
|width="10%" |01/10/2012
|width="10%" |3.0.17529
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP13.1 | 3.0 MP13.1]]
|width="10%" |12/09/2012
|width="10%" |3.0.17522
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP13 | 3.0 MP13]]
|width="10%" |20/07/2012
|width="10%" |3.0.17503
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP12.2 | 3.0 MP12.2]]
|width="10%" |16/08/2012
|width="10%" |3.0.16768
|width="10%" |QA

|- align="center"
|width="10%" |[[Release_Notes/3.0MP12.1 | 3.0 MP12.1]]
|width="10%" |09/07/2012
|width="10%" |3.0.16758
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP12 | 3.0 MP12]]
|width="10%" |26/06/2012
|width="10%" |3.0.16746
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP11.1 | 3.0 MP11.1]]
|width="10%" |28/06/2012
|width="10%" |3.0.16288
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP11 | 3.0 MP11]]
|width="10%" |22/05/2012
|width="10%" |3.0.16285
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP10.3 | 3.0 MP10.3]]
|width="10%" |28/05/2012
|width="10%" |3.0.16029
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP10.2 | 3.0 MP10.2]]
|width="10%" |14/05/2012
|width="10%" |3.0.16027
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP10.1 | 3.0 MP10.1]]
|width="10%" |16/04/2012
|width="10%" |3.0.16017
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP10 | 3.0 MP10]]
|width="10%" |N/A
|width="10%" |3.0.16012
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP9.3 | 3.0 MP9.3]]
|width="10%" |24/05/2012
|width="10%" |3.0.15736
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP9.2 | 3.0 MP9.2]]
|width="10%" |09/05/2012
|width="10%" |3.0.15734
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP9.1 | 3.0 MP9.1]]
|width="10%" |24/04/2012
|width="10%" |3.0.15727
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP9 | 3.0 MP9]]
|width="10%" |02/04/2012
|width="10%" |3.0.15716
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP8.4 | 3.0 MP8.4]]
|width="10%" |02/05/2012
|width="10%" |3.0.15320
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP8.3 | 3.0 MP8.3]]
|width="10%" |20/04/2012
|width="10%" |3.0.15318
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP8.2 | 3.0 MP8.2]]
|width="10%" |05/04/2012
|width="10%" |3.0.15313
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP8.1 | 3.0 MP8.1]]
|width="10%" |06/03/2012
|width="10%" |3.0.15303
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP8 | 3.0 MP8]]
|width="10%" |22/02/2012
|width="10%" |3.0.15300
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP7.3 | 3.0 MP7.3]]
|width="10%" |16/02/2012
|width="10%" |3.0.15075
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP7.2 | 3.0 MP7.2]]
|width="10%" |08/02/2012
|width="10%" |3.0.15073
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP7.1 | 3.0 MP7.1]]
|width="10%" |13/01/2012
|width="10%" |3.0.15070
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP7 | 3.0 MP7]]
|width="10%" |13/01/2012
|width="10%" |3.0.15068
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP6.2 | 3.0 MP6.2]]
|width="10%" |08/02/2012
|width="10%" |3.0.14833
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP6.1 | 3.0 MP6.1]]
|width="10%" |04/01/2012
|width="10%" |3.0.14830
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP6 | 3.0 MP6]]
|width="10%" |12/12/2011
|width="10%" |3.0.14822
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP5.3 | 3.0 MP5.3]]
|width="10%" |14/12/2011
|width="10%" |3.0.14221
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP5.2 | 3.0 MP5.2]]
|width="10%" |07/12/2011
|width="10%" |3.0.14219
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP5.1 | 3.0 MP5.1]]
|width="10%" |21/11/2011
|width="10%" |3.0.14203
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP5 | 3.0 MP5]]
|width="10%" |12/11/2011
|width="10%" |3.0.14195
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP4.2 | 3.0 MP4.2]]
|width="10%" |16/11/2011
|width="10%" |3.0.13970
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP4.1 | 3.0 MP4.1]]
|width="10%" |22/10/2011
|width="10%" |3.0.13968
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP4 | 3.0 MP4]]
|width="10%" |15/10/2011
|width="10%" |3.0.13966
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP3.2 | 3.0 MP3.2]]
|width="10%" |15/11/2011
|width="10%" |3.0.13703
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP3.1 | 3.0 MP3.1]]
|width="10%" |19/10/2011
|width="10%" |3.0.13701
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP3 | 3.0 MP3]]
|width="10%" |29/09/2011
|width="10%" |3.0.13698
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP2.4 | 3.0 MP2.4]]
|width="10%" |16/10/2011
|width="10%" |3.0.13468
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP2.3 | 3.0 MP2.3]]
|width="10%" |29/09/2011
|width="10%" |3.0.13465
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP2.2 | 3.0 MP2.2]]
|width="10%" |14/09/2011
|width="10%" |3.0.13459
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP2.1 | 3.0 MP2.1]]
|width="10%" |06/09/2011
|width="10%" |3.0.13453
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP2 | 3.0 MP2]]
|width="10%" |16/08/2011
|width="10%" |3.0.13451
|width="10%" |C

|- align="center"
|width="10%" |[[Release_Notes/3.0MP1 | 3.0 MP1]]
|width="10%" |15/07/2011
|width="10%" |3.0.13118
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP0.1 | 3.0 MP0.1]]
|width="10%" |29/06/2011
|width="10%" |3.0.12782
|width="10%" |CS

|- align="center"
|width="10%" |[[Release_Notes/3.0MP0 | 3.0 MP0]]
|width="10%" |15/06/2011
|width="10%" |3.0.12774
|width="10%" |C

|}

'''(*)''': Maturity Levels Legend:
* CS : Confirmed Stable
* QA : QA Approved
* C : Cancelled

== Early Adopter Releases ==
{| align="center" width="100%"
!Release
!Date
!Release Notes

|- align="center"
|width="10%" |3.0 RC7
|width="10%" |20/05/2011
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC7 | 3.0 RC7]]

|- align="center"
|width="10%" |3.0 RC6.1
|width="10%" |24/04/2011
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC6.1 | 3.0 RC6.1]]

|- align="center"
|width="10%" |3.0 RC6
|width="10%" |21/04/2011
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC6 | 3.0 RC6]]

|- align="center"
|width="10%" |3.0 RC5.1
|width="10%" |01/04/2011
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC5.1 | 3.0 RC5.1]]

|- align="center"
|width="10%" |3.0 RC5
|width="10%" |22/03/2011
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC5 | 3.0 RC5]]

|- align="center"
|width="10%" |3.0 RC4
|width="10%" |23/02/2011
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC4 | 3.0 RC4]]

|- align="center"
|width="10%" |3.0 RC3
|width="10%" |30/11/2010
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC3 | 3.0 RC3]]

|- align="center"
|width="10%" |3.0 RC2
|width="10%" |17/09/2010
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC2 | 3.0 RC2]]

|- align="center"
|width="10%" |3.0 RC1
|width="10%" |16/07/2010
|width="10%" |[[ERP/3.0/Release_Notes/3.0RC1| 3.0 RC1]]

|}

== Older release notes ==

* [[ERP/2.50/ReleaseNotes | Openbravo 2.50]]
* [http://archive.wiki.openbravo.com/wiki/ERP/2.40/Release_History Openbravo 2.40]

== Feedback ==

Do you want to contribute? To get involved with Openbravo see our [[Contributor's_Guide | Contributor's guide]].

[[Category:Release Notes ERP]]
[[Category:General Information]]

Release Notes/id

2026-08-28T12:20:13Z

Wikiadmin: Create ID subpage stub (scaffold) for Release Notes

{{Languages}}

== Release Notes (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Release Notes|Release Notes]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

How To/id

2026-08-28T12:20:12Z

Wikiadmin: Create ID subpage stub (scaffold) for How To

{{Languages}}

== How To (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[How To|How To]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

How To

2026-08-28T12:20:12Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

Below is a list of "How To" documents aimed at describing ways in which business objectives can be met using Openbravo.<br>If you want to review development related How To documents please visit this [http://wiki.openbravo.com/wiki/Category:HowTo link].

[[How to configure InfiniteERP high level? | How to configure InfiniteERP high level?]]

[[How to initialize Opening Balance in InfiniteERP | How to initialize Opening Balance in InfiniteERP]]

[[How_to_initialize_financial_balances_in_Openbravo | How to initialize financial balances in Openbravo ]]

[[How to Adjust Customer Account Balances Using Credit Memos]]

[[How_to_Transfer_Funds_Between_Financial_Accounts | How to Transfer Funds Between Financial Accounts]]

[[How_to_Set_Up_Discounts_for_Early_Payment | How to Set Up Discounts for Early Payment]]

[[How_to_Use_Volume_Discounts | How To Use Volume Discounts]]

[[How_to_Manage_Prepaid_Invoices_in_Receivables | How to Manage Prepaid Invoices in Receivables]]

[[How_to_Manage_Prepaid_Invoices_in_Payables | How to Manage Prepaid Invoices in Payables]]

[[How_to_manage_payroll_accounting_and_payment | How to Manage Payroll Accounting and Payment]]

[[How_to_Manage_Attributes_And_Attribute_Sets | How to Manage Attributes and Attributes Sets]]

[[How_to_manage_VAT_settlement_and_payment | How to Manage VAT settlement and payment]]

[[How_to_manage_deferred_revenue_and_expenses| How to Manage Deferred Revenue and Expenses]]

[[How_to_manage_payments_in_other_currencies_than_the_financial_account_currency| How to Manage Payments in other currencies than the financial account currency]]

[[How_Price_Including_Taxes_are_Calculated| How Prices Including Taxes are calculated]]

[[How_to_Configure_an_Attachment_Method|How to Configure an Attachment Method]]

[[How_to_manage_Cancel_and_Replace_process|How to manage "Cancel and Replace" process]]

[[How_to_manage_Alternative_Unit_of_Measure_AUM|How to manage Alternative Units of Measure (AUM)]]

[[How_to_Property_Configure_Costing_Functionality|How to Properly Configure Costing Functionality]]

[[Category:User_Guide]]

User Interface Introduction

2026-08-28T12:20:11Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

{{BackTo|User Guide}}

== Introduction ==
The Openbravo 3 user interface is optimized for productivity. It is characterized by the following attributes:
*Multiple tabs that allow to have multiple documents open at the same time
*Master-detail views: Parent and child record information is shown in the same view
*In-grid editing: It is possible to modify field values directly in the grid
*Column filtering: Filter fields on top of the grid allow for real-time filtering while typing the keyword
*Application menu: A multilevel fly-out menu to discover and access all functional areas
*Quick menus allow for fast access to existing documents and creation of new documents
*Sessions: user and profile/role settings can be accessed via the top navigation
*Help can be accessed via the top navigation and help content will be opened on separate tabs

===Login===
You access Openbravo through a Web browser.

{|width="100%"
|-|- valign="top"

[[Image:WIK_Logon.png|thumbnail|right|150px|View larger]]

1. ''Enter your Openbravo URL into the address bar of the browser.''

The login window opens up.

In case the login page is not being not displayed, please verify the correctness of the URL, or contact your system administrator.
|}
{|width="100%"
|-|- valign="top"
2. ''Enter your user name and password.''

The user name and password are assigned by the system administrator. If you don´t know your user name and password contact your system administrator.
|}

{|width="100%"
|-|- valign="top"
|3. ''Click login''

The Openbravo Home page shows up.

===Google Account Association===

You have the ability to log into an Openbravo instance using your Google Account by clicking the G-button that is shown on the login screen below the login button.
There are two ways to use the Google Accounts authentication service:

* Link an existing Openbravo user name with a Google Account
* Configure an instance to allow any user with a Google Account to log into the application. If no Openbravo user is linked to that Google Account, a new one is created with default properties.

Learn more about Google Account association in the [http://wiki.openbravo.com/wiki/Configuration_Manual/Google_Integration Configuration Manual]

== Screen Areas ==
[[Image:WIK PartsOfScreen.png|thumbnail|right|150px|View larger]]
The Openbravo 3 screen consists of the following components:

*Top navigation
*Main (1st level) tabs
*Toolbar
*Message area
*Status bar
*Header level (form or grid)
*Sections
*Child (2nd level) tabs
*Column filters
*Child grid
*Grandchild (3rd level) tabs

== Top Navigation ==

[[Image:top-nav.png]]

The top navigation offers the following menus or functionalities:

*Quick Menus
**Create New
**Launch
*Application Menu
*Alerts
*Log out
*User Preferences
*Help

=== Quick Menus ===
[[Image:quickmenu-buttons.png]]

Via the quick menus you can quickly launch new documents or jump to existing documents.
*Create New: a new document of a specific type is created on a new tab in form view
*Launch: a grid for a specific document type is opened on a new tab

Both QuickCreate and QuickLaunch work in the same way using auto-suggest based on the typed input. By simply entering the first couple of letters of the name of the document type, you will be offered suggestions for the type of document you are looking for.

[[Image:WIK_Quick.png]]

=== Application Menu ===
The Openbravo 3 application menu uses the same taxonomy as the 2.x versions, only the presentation has changed. Folders are replaced by expandable menus but its contents remain the same.

[[Image:WIK_AppMenu.png|thumbnail|right|150px|View larger]]

''The contents of the Application Menu depends on the user's role. For example, one user can have various roles and see different things with each. Users and roles are usually created and maintained by the client's Administrator.

=== Alerts ===
[[Image:WIK_Alerts.png|thumbnail|right|150px|View larger]]
[[Image:WIK_Alerticon.png]]

An alert is a notification that informs or warns its recipients about a critical or very important situation that has arisen. With one click you can see and edit all your active alerts.

The number of new alerts is shown in the top navigation as ''Alerts (n)''. Clicking this link will take you to the Alerts Management tab. This tab shows four sections, each one representing a status or stage in the alert life cycle:

*'''New alerts''': alerts that you have not marked as read/acknowledged and that are not ignored nor solved
*'''Pending alerts''': alerts that you have marked as read/pending because you don´t want to see them in the new section anymore. You would do this for example when you or your colleague have taken care of the problem but this has not been updated in the system. A typical example is: Stock of product x dropped below critical level. You just placed a new order by phone but it will still take a day to receive the orders.
*'''Ignored alerts''': alerts that you do not want to see back again. By placing them in the Ignore section, it means that they are now exceptions to the alert rule.
*'''Solved alerts''': alerts are automatically moved to the solved section when the system notices that the alerts threshold seized to be violated. Note that you cannot mark alerts as solved yourself.

In the Notes column, you can add a comment. You would typically do it when moving a New alert to (for example) the Acknowledged/read section. You can move alerts to a different section and clicking one of the buttons in the top right of the grid.
The Record column contains clickable links. They let you open the (problematic) record on a new tab for further investigation.

[[ERP/2.50/User_Manual/General_Setup#Alert | More about Alerts]]

=== Help & About ===
The last item in the top navigation is the Help menu. It also contains an About item. Help content is opened on a new tab.

=== User Preferences ===
Click the user name in the top navigation to access a user preferences menu. The menu is split in two tabs: Profile and Change Password

[[Image:WIK_Profile.png|thumbnail|right|150px|View larger]]

*See the current role information.
*Change the session options such as role, entity, organization, warehouse, language you want to work with.
*Set your default session options .
*Change password (on the second tab in the menu)

=== Log out ===
[[Image:logout-icon.png]]

This button logs you out of the application. A confirmation dialog lets you confirm.

== Tabs ==
[[Image:WIK_tabs.png|thumbnail|right|150px|View larger]]

Openbravo 3 allows you to have multiple transactions open a the same time on different tabs. You can switch between active tabs, just as you do using a modern internet browser. Tabs can be closed by pressing the X button.

In case of overflow, when the total width of the tabs exceed the available horizontal space, three buttons appear to the right of the last tab that allow you to scroll through the tabs and easily navigate to one.

Starting from version '''3.0PR14Q2''', it is possible to reorder tab position. To do it, drag the tab and drop it in the desired position.

Starting form version '''3.0PR15Q3''', by default only one tab of a window is allowed. Only in case there is a module in development or the window is flagged as ''Thread Safe'' it is possible to have multiple tabs. Since this version there is a new [[Preference]] property '''Allow Multiple Tabs of a Window''' that enables the possibility to open more than one tab of a window. This preference can be configured by user, role and/or window level.

== Levels & Views ==
[[Image:WIK_Levels.png|thumbnail|right|150px|View larger]]
An application window consists of one or more levels: parent, child and sometimes even grandchildren and deeper. They are separated by a horizontal splitter bar. Each level can be displayed in grid or form view.

=== Grid View ===
[[Image:WIK_OpenForm.png|thumbnail|right|150px|View larger]]

The grid view functions as the base view and often as a starting point to filtering and drilling down. The user can open a record in form view on top of the grid. The interaction metaphor that is used is that of a file explorer of an operating system. The grid is the folder with files, a double click opens the record. The record in form view can be closed at any time by clicking the close (X) button in the top right corner of the form.

A record in the grid can be opened via:
*A double click on the row
*Pressing the <ENTER> key on the keyboard
*Clicking the form/document icon on the left hand side of the row

=== Tree Grid View ===

{{(!)| The Tree Grid View is available from '''Openbravo PR14Q2'''}}

[[Image:MenuTreeGridView.png|thumbnail|right|150px|View larger]]

The tree grid view is an alternative to the standard grid view that is available for tabs based on [http://wiki.openbravo.com/wiki/How_to_Define_a_Table_as_a_Tree tables that have been defined as a tree]. The tree grid view shows the tab data hierarchically. When the view is first loaded only the root nodes are shown. The user can then open individual nodes to load its children.

To switch between the standard grid view and the tree grid view the user has to click the Tree toolbar button: [[Image:WIK_button_Tree.png]]

The user can reorder the nodes of the tree, moving a node to another parent or to another position within its original parent. Some restrictions apply when moving a node:
* If the tab is set as read only, the user will not be able to change the position of tree nodes.
* Openbravo PR14Q3: If the tab has the flag "Read Only Tree" checked, the user will not be able to change the position of tree nodes.
* If the tab has a '''Summary Level''' field, then it will not be possible to drop a node to a record whose summary level field is not checked.
* Some trees may define specific restrictions. For instance, it is not possible to move an organization if it is set as ready, or a menu item if it belongs to a module that is not in developement. If the user tries to move one of these nodes, the movement will be reverted and a meaningful message will be shown in the message bar.
* By default the node movement will occur just after it is droped in its new position. To show a confirmation popup before actually moving the node, the OBUIAPP_ConfirmNodeReparent preference should be set.

Openbravo PR14Q3: There are some configurations that can be done at tab level:
* "Show Tree Node Icons": It is only available when the tree is in read only mode and by disabling it the tree icons can be hidden.
* "Default Tree View Logic": It defines if by default the tree view should be shown following a specific logic

When the tree grid view is filtered, not only the records that fulfill the filter criteria will be shown, also its parent nodes, until reaching the root node. This is done in order to show the filtered nodes in its proper context. The font color of the context nodes is grey in order to distinguish them from the nodes that actually fulfill the filter criteria. It is not possible to reorder the tree nodes while it is being filtered, as it some records are hidden the new position of the node could be ambiguous.

It is not possible to create or edit a node using the tree grid view, for that the standard grid view should be used. What it is actually possible is to open a record in form view from the tree grid view. Then the record can be edited in the form view, and when the form view is closed the tree grid view will be shown again.

If a user wants to use the classic tree popup instead of the tree grid view, he can use the '''Use Classic Popup Tree''' preference.

=== Form View ===
[[Image:WIK_CloseForm.png|thumbnail|right|150px|View larger]]

The form view is used for more complex editing of individual records. Normally header records are created in form view because they e.g. a description which usually is too long to enter comfortably in grid view.

The form view can be closed by
*Clicking the close (X) button in the top right of the form.
*Clicking the Save&Close button in the toolbar, this is the button with the floppy disk combined with the X symbol.

=== Form Personalization===

This feature allows you to change the order and visibility of fields, and several other settings:

*assign fields to the status bar and assign fields to existing field groups
*set the colspan or rowspan
*define if a field should be placed on a new row
*the field which will get the first focus

[[Image:WIK_FormPersonalization.png‎]]

More detailed documentation:[[User_Manual/Window_Personalization|Window_Personalization]]

{{(!)|This is a '''Premium''' functionality. [http://www.openbravo.com/product/erp/editions/ Learn more] about the benefits of Openbravo's commercial editions}}

=== Activating, resizing, maximizing and toggling levels ===
[[Image:WIK_3Levels.png|thumbnail|right|150px|View larger]]

Each application window is split in two visible levels. This can be either parent-child or child-grandchild (or even deeper down). The distribution of the height of each level is not fixed as it can be changed by dragging the horizontal splitter bar that divides the two levels.

Only one level can be active at a time. An active level is marked with an orange vertical strip on the left hand side and an orange horizontal strip on top of the tab. You can toggle between active levels simply by clicking in a non-active level. The orange markers will move along.

The standard view is parent-child (also known as header-lines). In case there is a third level available, it will sit at the bottom of the window in collapsed state. In order to expand the third level, you can simply click on its tab. It will then pop out and push the other levels upwards. In this case you will notice that the top level (header) will become collapsed. Here the same interaction principle applies: a single click on the header tab will make it re-appear.

A level can be maximized by double clicking on its tab. Double clicking it again will restore its size to the previous size.

[[Image:WIK_3Levels2.png|thumbnail|right|150px|View larger]]

=== Saving Views ===

Saving Views stores grid and form settings, column filters and even the entire layout of the screen, for example the position of the splitterbar between the header and lines. So imagine that you rearranged your grid and it´s perfectly adapted to your task. You even added some column filters, for example you only want to see invoices that are more than 21 days overdue for organization East Coast. Now you save all this in one go using a name. Now when you need to work on another task that needs other filters and grid or form settings, you can easily retrieve this view later. You can access Saved Views through a pull down menu that sits underneath the Saved Views button in the toolbar.

[[Image:WIK_SavingViews.png]]

A saved view can be set as default and can be deleted. The active view is indicated by a little arrow in front of the view name.

As an administrator you are able to save predefined views on different levels (client, org, role) which are made available to users. As a regular user you can only edit/save views on your own levels and not change views entered by an administrator.

More detailed documentation: [http://wiki.openbravo.com/wiki/User_Manual/Window_Personalization#Saved_and_Named_Views Window_Personalization]

{{(!)|This is a '''Premium''' functionality. [http://www.openbravo.com/product/erp/editions/ Learn more] about the benefits of Openbravo's commercial editions}}

== Advanced Grid Functionality ==
The Openbravo 3 grids let you browse, select, filter and organize high volumes of records with ease. Listed below are the main capabilities of the new grids.
=== Selecting Rows ===
[[Image:WIK_Selecting.png|thumbnail|right|150px|View larger]]
Row(s) in grids can be selected as follows:
*Selecting a single row is simply done by clicking on it. There is no need to tick the checkbox in front of the row.
*Multiple selection is done by either ticking the checkboxes in front of the rows or using CTRL-click or SHIFT-click combinations.
*All records displayed in the grid can be selected using the checkbox in the top left of the grid as far as the number of records is smaller than 100.
In the top left of the grid, two numbers are shown. The first one indicates the number of selected rows, the second one the total number of rows in the grid.

=== Column Filters ===
[[Image:WIK_Filter.png|thumbnail|right|150px|View larger]]
[[Image:WIK_Filter_fk.png|thumbnail|right|150px|View larger]]
On top of the columns in a grid you will find column filters. There are several types of column filters:
*Regular column filters: These are fields that are empty by default but once you start typing the first characters of a search term, the grid will be filtered in real-time.
*Date column filters: Clicking it will launch a dialog where you can set a range, for example ''8 days ago till today''.
*Dropdown reference column filters: filters on references to other data, for example from a sales order to a business partner. You can filter on multiple values (available from MP17), if there are many values to filter on then you can scroll in the dropdown box.
*Dropdown column filters: Filters that contain a limited set of values. Just open the dropdown and select a value. From MP17 you can select more than one value to filter on.

The following symbols can be used in regular column filter fields to create more complex filter expressions. Note that once you start typing a filter expression in a numerical value column, the real-time filtering is switched off and you will need to hit Enter to apply the filter.

{| border="1"
! Symbol
! Filter
! Example
! Which means
|-
| <
| less than (also works for strings)
| <100
| Only show amounts less than 100
|-
| >
| greater than (also works for strings)
| >100
| Only show amounts greater than 100
|-
| !
| not equal (also works for strings)
| !100
| Show everything except amounts that equal 100
|-
| ^
| starts with
| ^H
| Only show values that start with "H"
|-
| [[File:endsWithSymbol.png]]
| ends with
| [[File:endsWithSymbol.png]]H
| Only show values that end with "H"
|-
| !^
| does not start with
| !^H
| Only show values that do not start with "H"
|-
| !@
| does not end with
| !@H
| Only show values that do not end with "H"
|-
| ~
| contains (this is the default for most column filters)
| ~buenas
| Only show values that contain "buenas"
|-
| !~
| does not contain
| !~buenas
| Only show values that do not contain "buenas"
|-
| #
| is Null
| #
| Only show records without a value in this column (works in regular and date column filters)
|-
| !#
| is not Null
| !#
| Only show records with a value in this column (works in regular and date column filters)
|-
| ==
| exact match (for fields where 'contains' is the default)
| ==FV/1
| Only show values that equal exactly "FV/1"
|-
| a...b
| range (between a and b)
| 0...100
| Only show values between 0 and 100.
|-
| or
| OR boolean
| check or cash
| Only show records that contain "check" or "cash". Note if you want to use the term 'or' as a filter value then you should prefix it with a '\'. So to get all records containing the value 'or' filter using this value: \or.
|-
| and
| AND boolean
| check and cash
| Only show records that contain "check" and "cash". Note if you want to use the term 'and' as a filter value then you should prefix it with a '\'. So to get all records containing the value 'and' filter using this value: \and.
|}

Filters can be cleared by clicking the funnel icon in the top right of the grid.

==== Client Filtering ====

{{(!)|This capability is available starting from '''MP28'''}}

When applying column filters in a grid, a new request is done to backend to retrieve the filtered data set. In case of applying a filter more restrictive than the one used to retrieve the previous one and if the complete data set for that previous filter has already been completely retrieved from the client (this is, the number of records matching the filter is equals or smaller than the page size -100 records-), the filtering is done in the browser without the need of doing additional requests. This implies a better performance in these cases saving backend trips.

==== Grid Configuration ====

{{(!)|This capability is available starting from '''MP31'''. It was sponsored through [http://www.agilityerp.com Agility ERP] to enable more efficient user interaction with grids configured against a table with millions of rows. In this case it can make sense to restrict the normal interaction to avoid inefficient queries that result in full table scans.}}

The behaviour of the grid filters can be configured by system administrators at System level (Grid Configuration at System Level window) or Tab and Field level (Grid Configuration at Window/Tab/Field Level). Tab configurations will overwrite system configurations, and field configuration will overwrite tab configurations. Grid configuration also can be configured to determine if a column is sortable or not.

Working with '''high volume''' of data we recommend to deactivate sorting and filtering in some/most columns in backend grids. [http://wiki.openbravo.com/wiki/How_to_configure_high_volume_windows How to configure high volume windows.]

The following parameters can be configured in these windows:
* By Default Allow Sorting: If this property is set to false, columns will not be sortable.
* By Default Allow Filtering: If this property is set to false, column filters will be disabled.
* Text Field Filter Behavior: Defines the operator used on the filter of text columns. Allowed values are equals, iEquals, startsWith, iStartsWith, contains and iContains).
* Threshold to Trigger Filter on Text Field (in ms): By default 500 milliseconds after the last user keystroke on the filter of a text colum, a request to the datasource will be done with the current content of the filter. If the user types at a rate slower than 500 milliseconds, then each time the users enters a string in a text filter it will result in several datasource requests. This parameter can be configured to make this delay higher (values lower than 500 will not be applied).
* Filter On Change: Using this property the user can change the behavior of text filters, so instead of triggering a datasource request some time after the last keystroke of the user, the datasource request will be triggered only when the user presses enter or moves the focus out of the text filter.
* Lazy Filtering on Grid: If this property is set to true, then the filters will not be applied to the grid until the user presses enter or clicks on the check icon under the funnel icon. This allows to define several filters and then do just one request to the datasource. If this property is checked then the user opens a window the initial datasource request will not be done automatically. The user will have to do the datasource request explicitally after he sets the filters he needs. This property also affects when changing the sorting criteria of the grid: when set to true, the sorting will not be performed until the user presses the enter key or the mentioned check icon.
* Allow Filtering Foreign Keys by its Identifier: If this flag is unchecked, then the only way to filter the foreign key columns will be by picking some value from the filter drop down. The query done to fetch data when the filter is set this way is much better than the query done when the column is filtered without using the filter drop down. Even if this flag is unchecked the user will be able to enter text to filter the data shown in the drop down list.
* Unfiltered Foreign Key Combo: If this flag if checked, the filter drop down will show the rows from the referenced table unfiltered by specific rows being referenced in the referencing table. The filters entered by the user in the grid filter editor will be applied. This configuration makes sense if the referenced table does not have that much volume, but loading the foreign key filter drop down takes a lot of time anyway.
* Disable Foreign Key Filter Combo: In some cases the population of the drop down is very slow even using the previous configuration. In that case, it could be useful to use this configuration, that will get rid of the foreign key filter combo, so that the column will be filtered like a standard text column. Use this only if filtering this way outperforms the population of the combo.
* Allow Summary Functions: Determines if the [http://wiki.openbravo.com/wiki/User_Interface_Introduction#Grid_Summaries Summary Functions] can be added into the grid, i.e., the menu entry which allows the entering of this summaries will not be available if this flag is not checked. Besides, in the case of Summary Functions already present in [http://wiki.openbravo.com/wiki/User_Interface_Introduction#Saving_Views Saved Views], they will not be displayed.
* Allow Transactional Filters: If this property is set to true then the [http://wiki.openbravo.com/wiki/Standard_Windows#Transactional_Windows transactional filters] will be enabled. Otherwise, all the transactional filters will be disabled.
* Sequence Number: In case of having multiple configurations for the same level, it determines which one is going to be applied. In these cases the configuration that will be taken into account is the one with the highest sequence number.

{{(!)|The '''Allow Filtering Foreign Keys by its Identifier''' feature (also sponsored through [http://www.agilityerp.com Agility ERP]) is available starting from '''PR14Q4'''}}

{{(!)|The '''Unfiltered Foreign Key Combo''' and the '''Disable Foreign Key Filter Combo''' features are available starting from '''PR15Q3'''}}

{{(!)|The '''Sequence Number''' fields is available starting from '''PR16Q2'''}}

{{(!)|The '''Allow Summary Functions''' feature is available starting from '''PR17Q1'''}}

{{(!)|The '''Allow Transactional Filters''' feature is available starting from '''PR19Q2'''}}

=== Column filtering and sorting configuration ===
{{(!)|The '''Allow Sorting''' and the '''Allow Filtering''' checkboxes are available starting from '''PR16Q2'''}}

Every column in Openbravo is filterable and sortable by default. Every column has two checkbox fields which are called Allow Sorting and Allow Filtering that are checked by default. Those checkboxes can be unchecked to make the columns not sortable or not filterable. This can be configured by system administrators in the ''Tables and Columns'' window and there it can be chosen the column of which one wants to change the default sorting or filtering properties.

These defaults can be overridden by a Grid Configuration. In case sorting or filtering is allowed for a column, its behavior can be overridden by a configuration at any level. But if filtering or sorting is disabled, it can be only be enabled by a configuration at field level.

=== Implicit Filters ===
Some grids, especially those with large data volumes, have preset hidden filters, the so called ''implicit filters''. Typical implicit filters are set to filter out already process transactional documents or documents before a certain date. Implicit filters can be cleared by clicking the funnel icon in the top right of the grid.

=== Filtering in Selector Grids ===
[[Image:WIK_Filterpop.png|thumbnail|right|150px|View larger]]
Selectors make use of modal dialogs containing grids. Selector grids work in the same way as regular grids. Often, they also contain preset implicit filters that can be cleared by clicking the funnel icon. Typical cases where selectors are used are business partner and product selection.

=== Setting Column Visibility ===
[[Image:WIK_Colvis.png|thumbnail|right|150px|View larger]]
Via a right-mouse-click on any column header, a context menu can be invoked. In this menu, you can set the column visibility via the ''Columns'' item by ticking or unticking the column (field) names.

=== Setting Column Order & Widths ===
[[Image:WIK_Colwidth.png|thumbnail|right|150px|View larger]]
Column order and width can simply be modified by dragging the column header or separating split line to another position.

=== Sorting ===
[[Image:WIK_Colsorting.png|thumbnail|right|150px|View larger]]
Columns can be sorted by clicking on a column header. A second click sorts the column in the reverse order. A triangle symbol conveys the current ordering.

==== Client Sorting ====

{{(!)|This capability is available starting from '''MP28'''}}

In the same way to [[#Client_Filtering|Client Filtering]], when the number of records matching current filters is equals or smaller than the page size -100 records-, sorting is directly done in the browser instead of performing additional request to backend.

==== Disable Sorting ====

{{(!)|This capability is available starting from '''MP31'''}}

Sorting can be disabled at System, Tab or Field level by configuring the By Default Allow Sorting parameter in the Grid Configuration at System Level and Grid Configuration at Window/Tab/Field Level windows.

==== Sorting Lazily ====

{{(!)|This capability is available starting from '''MP31'''}}

If the Lazy Filtering on Grid parameter is set to true (for more information about grid configuration click [[#Grid_Filter_Configuration | here]]), then when the user clicks on a field title in order to sort the grid using that field, the sorting will not be applied until the user types Enter on a grid filter or until he clicks on the check icon below the funnel icon. This reduces the number of datasource requests, allowing the user to change the sorting and change several filters and then do only one datasource request.

=== Grouping ===
[[Image:WIK_Grouping_showgrouping.png|thumbnail|right|150px|View larger]]
Records can be grouped by a certain value/column (available from MP17).

[[Image:WIK_Grouping_preference.png|thumbnail|right|150px|View larger]]
Grouping is '''not''' enabled by default. The 'Grouping Enabled' preference should be set.

[[Image:WIK_Grouping_dogroup.png|thumbnail|right|150px|View larger]]
To group click on the column header context menu and select 'Group by...'. The display of grid will now show the records in a grouped manner.

[[Image:WIK_Grouping_datatoolarge.png|thumbnail|150px|View larger]]
If the dataset is too large then grouping is disabled. A message is displayed if a large dataset is grouped. The maximum number of records which can be grouped is also controlled by a preference: 'Maximum Number of Records for Grouping'.

[[Image:WIK_Grouping_ungroup.png|thumbnail|right|150px|View larger]]
To ungroup, click the 'ungroup' option in the column header context menu.

=== Grid Summaries ===
[[Image:WIK_Gummary_summarize.png|thumbnail|right|150px|View larger]]
[[Image:WIK_Gummary_setsummarize.png|thumbnail|right|150px|View larger]]
[[Image:WIK_Gummary_summary_ad.png|thumbnail|right|150px|View larger]]
{{(!)|This capability is available starting from '''MP17'''.}}

The grid allows you to set summary functions for a column. These summary values are shown in a separate row in the bottom of the grid. The summary functions are executed on the server so they operate on the complete dataset which fits into the current filter.

To set a summary function click on the column header context menu and go into the 'Set Summary Function' submenu. Numeric and date fields will have several summary functions, other fields will only have a 'count' summary function.

You can remove the summary row by clicking on the 'Clear Summary Functions' option in the column context menu.

It is also possible to set a summary function in the Application Dictionary (in the Window, Tabs, Field window in the Field tab). This summary function is then enabled by default when opening the target window. See the screenshot on the right on how to set this in the Application Dictionary. Valid summary functions are: avg, count, max, min, sum.

'''Limitations'''
{{(!)|This limitation starting from '''3.0PR17Q1'''.}}

'''Summary functions are not supported''' on tabs defined based on [http://wiki.openbravo.com/wiki/How_to_create_a_HQL_Based_Table HQL Query Tables]. For this reason, since 3.0PR17Q1 the 'Set Summary Function' submenu is not available for this kind of tabs.

{{(!)|This limitation starting from '''3.0PR17Q2'''.}}

As computed columns allow to be defined with any arbitrary sql statement, the risk of underperformance when included in a summary function is much bigger. For this reason '''Summary functions are not supported in [http://wiki.openbravo.com/wiki/How_to_create_a_Computed_Column computed columns]'''.

{{(!)|This limitation starting from '''3.0PR18Q1'''.}}

'''Summary functions are not supported''' on tabs defined based on [http://wiki.openbravo.com/wiki/How_to_Create_a_Table_Based_on_a_User_Defined_Datasource Datasource Tables]. For this reason, since 3.0PR18Q1 the 'Set Summary Function' submenu is not available for this kind of tabs.

=== Freezing Columns ===
[[Image:WIK_Colfreeze.png|thumbnail|right|150px|View larger]]
Freezing columns means that they will be kept in the same position regardless of the position of the horizontal slider bar. Freezing column(s) is typically done when information in the right hand side of the grid (that is accessed via horizontal scrolling) needs to be viewed in the context of columns on the left hand side.

Columns can be frozen via the grid context menu that is invoked via a right mouse click on a column header.

=== Formula Columns ===
[[Image:WIK_Colformula.png|thumbnail|right|150px|View larger]]
A formula column shows the outcome of an equation using values of two or more columns. Via the context menu (right mouse click on column header) the formula dialog is launched. Here, you enter the title of the column and the actual definition. Every column containing numerical values is represented by a capital letter. These letters are used to build the formula. For example:

*A = Total Paid
*B = Outstanding Amount

The formula to sum these two is: A+B

=== Summary Columns ===
[[Image:WIK_Colsummary.png|thumbnail|right|150px|View larger]]
Similar to the formula columns, the summary columns simply combine to non-numerical values into a single string. The columns are represented by capital letters. When building the expression the pound sign (#) needs to be used to identify them as values.

=== Printing ===

With the print button of the toolbar ([[Image:WIK_button_Print.png]]) it is possible to launch a process that generates a report with the information of the records in a grid. By default there exists print processes for a limited set of windows:

* Business Partner
* Requisition
* Goods Shipment
* Goods Receipt
* Sales Order
* Purchase Order
* Sales Invoice
* Purchase Invoice
* Payment In
* Payment Out

==== Direct Print ====
For the windows related to the standard documents (goods shipments/receipts, orders, invoices and payments) it is also possible to configure them for '''direct printing''', i.e, instead of downloading the printed report, the print page of the browser is directly opened with the report information.

To enable this print mode, the [http://wiki.openbravo.com/wiki/Preference#Preferences_Definition '''Direct Print'''] preference should be used and the browser must be configured to directly open the PDF files instead of downloading them. This [https://support.google.com/chrome/answer/6213030?hl=en link] explains how to configure it in Chrome.

Please note that this feature relies on the functionality provided by the browser and not all the [http://wiki.openbravo.com/wiki/System_Requirements#Client:_web_browsers supported browsers] currently support it. For example,
Mozilla Firefox ESR browser does not support it due to this [https://bugzilla.mozilla.org/show_bug.cgi?id=911444 bug]. Refer [https://docs.google.com/spreadsheets/d/1LmCczLBW3NBFIB70X6gQmAlSedvRzg8hWZp1KBzZZk0 here] for a list of browsers where the direct print has been tested.

=== Exporting grid content to a spreadsheet ===

Openbravo 3 allows the user to export grid content to a CSV file (Comma-Separated Values) via a button in the toolbar([[Image:WIK_button_Export.png]]). This file can then be imported in most spreadsheet applications such as Microsoft Excel and OpenOffice.

To configure the export functionality correctly, follow these guidelines:

* The exported file is by default formatted using the iso-8859-1 encoding, which is the standard used in Windows environments and which works correctly with Microsoft Excel. In case any odd characters appear in the spreadsheet after importing a file, such as accented letters, then probably the iso-8859-1 encoding is not the best for your environment. This is probably because you are not using the Windows operating system or you are using a different spreadsheet. In case you are encountering this problem, look into the next section to find out how you can change this.

* Openbravo has a decimal separator character, used to format numbers with decimals in the application. The Export to Spreadsheet functionality uses this character when exporting the file. This character is very important in some spreadsheets because it's used when importing a CSV file to detect whether a field should be treated as a number or not. In case a wrong decimal separator is chosen, numbers will be imported into the spreadsheet appliction as strings and problems will occur when trying to do mathematical operations on them. If you encounter this problem, you should check that your decimal separator is correctly configured in your Openbravo environment. [http://wiki.openbravo.com/wiki/Format.xml Here you can find more information] on how to configure the Format.xml file. If you are still interested in configuring the decimal separator of the exported files differently from the one used in the application, then check the next section to find out how to do it.

* The file uses a specific character (which is the comma by default) to separate each field. This works flawlessly in general but in some spreadsheet applications it might be necessary to use a different one. Check the next section if you want to find out how to do it.

* By default, dates and times are exported in UTC. To set a different time zone, create a ''Local Timezone ID'' preference with a valid value from [http://www.java2s.com/Tutorial/Java/0120__Development/GettingallthetimezonesIDs.htm this list]. This preference can be set at any visibility level from System to User, but not Window.

=== Configuring export parameters in your Openbravo environment ===

You can change the decimal separator, the field separator, and the encoding of the file you get when you use the Export to Spreadsheet functionality in Openbravo if you need them to be different from the default values.

This is done via preferences. After logging in to Openbravo, go to the Preference window and do the following:

* If you want to change the decimal separator: create a new record. Select the "CSV Decimal Separator" in the "Property" field. In the "value" field, type your selected decimal separator (for example, the comma character (,), or the decimal point (.)). Save the record.

* If you want to change the field separator: create a new record. Select the "CSV Field Separator" in the "Property" field. In the "value" field, type your selected field separator. Save the record.

* If you want to change the file encoding: create a new record. Select the "CSV Text Encoding" field in the "Property" field. In the "value" field, type the selected file encoding (for example, UTF-8 should work in most non-Windows non-Excel environments). Save the record.

Since Openbravo 3.0PR14Q4, it also possible to define a header and/or footer text that will be included into any CSV file exported from the grid content. This text can be used, for example, for legal purposes (confidentiality of data, restrictions, etc.). This configuration is done via two new preferences: "CSV Header Message" and "CSV Footer Message" in the same way as described above. In the "value" field you can either specify any plain text or alternatively the search key of a [[Message]] defined into the Application Dictionary. The former will directly include the plain text message into the CSV header or footer, and the latter will include the correspondent message's text, translating it to the user's language if available.

After creating the preference (or preferences), log out of the application. Log in again, and try the Export to Spreadsheet functionality, to see the results.

== Workspace & Widgets ==
[[Image:WIK_Workspace.png|thumbnail|right|150px|View larger]]
The first tab contains the Openbravo Workspace, a customized portal-style home page. This tab cannot be closed as its contents are essential.

Widgets are customizable and the available set will be dependent on role and instance activation status.

To add widgets, simply click the Add Widget>> link in the left column in the workspace and select from the library.

=== Administrate widgets for other clients or roles ===
[[Image:WIK_AdminOthers.png|thumbnail|right|150px|View larger]]

With the appropriate administrative rights, you can pick widgets for others users or clients in your organization. Via the Admin Others >> link on the left hand side of the workspace you can choose for which entity (client), organization or role you want to define a widget set.

On the subsequent page you can then add widgets to this user´s / client´s workspace. Once done, click the Publish button to broadcast the selected widgets to the user(s) in the chosen entity/organization/role. The next time they log in, they will find the newly added widgets on their workspace.

== Toolbar ==
The Toolbar contains two types of buttons: Action buttons (green) and Process buttons (orange). Actions are generic and can be applied to almost all selected records. Processes are record specific and depend on the record status and the active level (header or lines or lower).

[[Image:WIK_Toolbar.png]]

The action buttons perform the following actions:

{|
|[[Image:WIK_button_NewForm.png]]||'''New Form'''||''Create a new record in form view''||
|-
|[[Image:WIK_button_InsertRow.png]]||'''Insert Row'''||''Insert a new row in grid view''||
|-
|[[Image:WIK_button_Save.png]]||'''Save'''||''Save the record''||
|-
|[[Image:WIK_button_SaveClose.png]]||'''Save and Close'''||''Save the record, close the form view and go back to the grid view''||
|-
|[[Image:WIK_button_SaveCloseX.png]]||'''Close'''||''Close the record in form view and go back to the grid view''||
|-
|[[Image:WIK_button_Cancel.png]]||'''Cancel'''||''Refresh the window and revert changes''||
|-
|[[Image:WIK_button_Delete.png]]||'''Delete'''||''Delete the selected record(s)''||
|-
|[[Image:WIK_button_Refresh.png]]||'''Refresh'''||''Refresh the window''||
|-
|[[Image:WIK_button_Export.png]]||'''Export'''||''Export the grid to CSV format''||
|-
|[[Image:WIK_button_Clone.png]]||'''Clone'''||''Clone the selected record(s) - (Only for Sales Orders)''||
|-
|[[Image:WIK_button_Print.png]]||'''Print'''||''Print the selected record(s)''||
|-
|[[Image:WIK_button_Email.png]]||'''Email'''||''Email the selected record(s)''||
|-
|[[Image:WIK_button_Attach.png]]||'''Attach a File'''||''Attach a file to the active record''||
|-
|[[Image:WIK_button_AttachOn.png]]||'''File(s) attached'''||''Attach a file. Status: file(s) attached.''||
|-
|[[Image:WIK_button_Tree.png]]||'''Tree'''||''Rearrange account tree element value''||
|-
|[[Image:WIK_button_URL.png]]||'''Create link'''||''Create a URL to the selected document that can be pasted into email or IM''||
|-
|[[Image:WIK_button_Audit.png]]||'''Audit Trail'''||''Enable audit trail for this window (Basic and Professional Edition only)''||
|-
|[[Image:WIK_button_PersonalizeForm.png]]||'''Personalize Form Layout'''||''Personalize the form layout (Basic and Professional Edition only)''||
|-
|[[Image:WIK_button_SaveView.png]]||'''Save View'''||''Save and retrieve views (Basic and Professional Edition only)''||
|-
|[[Image:WIK_button_Dunning.png]]||'''Dunning'''||''Apply dunning workflow (Commercial Extension Module)''||
|}

== Statusbar ==
[[Image:WIK_Statusbar.png]]

The statusbar conveys the editing status of the document (New, Editing or Saved) together with a user-defined set of read-only attributes. These allow the user to get an overview of the document without having to scan the remainder of the form. The statusbar is only visible in form view. On the right side of the statusbar the following buttons are available:

{|
|[[Image:WIK_button_Next.png ]]||'''Browse to next record'''||
|-
|[[Image:WIK_button_Previous.png ]]||'''Browse to previous record'''||
|-
|[[Image:WIK_button_Max.png ]]||'''Maximize form'''||
|-
|[[Image:WIK_button_Restore.png ]]||'''Restore form to previous size'''||
|-
|[[Image:WIK_button_Close.png ]]||'''Close form (save and return to grid)'''||
|}

== User Messages ==
User Messages are displayed centrally and their function is to inform or warn the user about some occurring situation in the application.
There are four different types of user messages.

{|
|[[Image:WIK_message_Error.png]]||'''Error Message'''||
|-
|[[Image:WIK_message_Success.png]]||'''Success Message'''||
|-
|[[Image:WIK_message_Info.png]]||'''Info Message'''||
|-
|[[Image:WIK_message_Warning.png]]||'''Warning Message'''||
|-
|[[Image:WIK_message_Tip.png]]||'''Tip Message'''||
|}

The messages can be hidden by clicking the little X icon in the top right of the message.

== Sections ==
[[Image:WIK_Sections.png|thumbnail|right|150px|View larger]]
Forms contain sections that group assets such as linked items, notes, attachments and groups of related fields. Sections can be expanded and collapsed by clicking on their header or the ''twisti'' (triangle shaped icon).

=== More Info ===
In this section the less frequently used fields are placed so they won´t bother you in the main part of the form.

=== Audit ===
In this section the fields related to audit are placed. Just as for the More Info section, the reason they were tucked away here is to reduce the visual clutter in the main part of the form.

=== Notes ===
[[Image:WIK_Notes.png|thumbnail|right|150px|View larger]]
In this section you can add notes related to the document. These could be notes to self or to colleagues. The bar on the left hand side is colored gray for your own notes and green for notes added by someone else. This way you can identify in one glimpse which notes aren't yours.

=== Linked Items ===
[[Image:WIK_Linkeditems.png|thumbnail|right|150px|View larger]]
In this section all related documents to the active document are shown. The left column contains the window types with the amount of related documents shown in brackets. By selecting one of the window types to the left, the actual documents appear in the right column. The links are clickable and will launch the document on a new tab.

=== Attachments ===
In this section the attachments to a record are stored. For more information on attachments and the API used to get attachments, refer [http://wiki.openbravo.com/wiki/Attachments here].

Starting from '''3.0MP31''', it is possible to have a description for each attachment.

== Keyboard Shortcuts ==

This list is just a starting point. As it is virtually impossible to find the ideal set of keyboard shortcuts for all platforms and languages it is recommended to modify and create your own. You can do this in the General Setup

User Interface Introduction/id

2026-08-28T12:20:10Z

Wikiadmin: Create ID subpage stub (scaffold) for User Interface Introduction

{{Languages}}

== User Interface Introduction (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[User Interface Introduction|User Interface Introduction]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Client Module/id

2026-08-28T12:20:09Z

Wikiadmin: Create ID subpage stub (scaffold) for Client Module

{{Languages}}

== Client Module (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Client Module|Client Module]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Client Module

2026-08-28T12:20:09Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Introduction =

Halaman ini mencatat dokumentasi penting terkait module-module khusus yang dibuat untuk klien secara khusus dan tidak digunakan untuk klien lainnya. Nama klien menggunakan kode khusus agar tidak ter-ekpose.

= List of client module =

{| class="wikitable sortable"
|-
! Client Code !! Module Name !! Description
|-
| IDL || [[IDL TSM | TSM]] || module untuk menghitung target stock maksimum, menentukan target growth penjualan
|-
| TCI || [[Customer Specific TCI Quality Control | Quality Control]] || module quality control check untuk IPQC dan OQC
|-
| RUS || Example || Example
|-
| TVB || [[TVB]]|| Example
|-
| KFS || Example || Example
|-
| SS || [[Shipping Agency]]|| Shipping Agency
|-
| Infinite || [[infinite]] || Module
|-
| Example || Example || Example
|-
| Example || Example || Example
|}

[[Category:Client_Module]]

Integration/id

2026-08-28T12:20:08Z

Wikiadmin: Create ID subpage stub (scaffold) for Integration

{{Languages}}

== Integration (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Integration|Integration]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Integration

2026-08-28T12:20:08Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Introduction =
In an organization, more than one software application often exists to support a particular aspect of operational requirements. The result is an heterogeneous set of software applications requiring data sharing and integration. An ERP system like [http://www.infinite-erp.co.id InfiniteERP] tries to solve this problem by offering one solution for every operational requirement. <br><br>
[http://www.infinite-erp.co.id InfiniteERP] maintains one shared database for all data, integrated processes among different departments, a consistent interface for every user, and homogeneous reports/score cards that display operational data of the whole organization.

== Integration overview ==
The focus of this integration is to create a system where [http://www.infinite-erp.co.id InfiniteERP] is the central repository of data. Products, categories and orders are maintained and other application or services has the ability to operate with the products catalog downloaded from InfiniteERP and to upload such as orders or other transaction created through Web Services/API. <br><br>

This integration has been developed with webservices. [http://www.infinite-erp.co.id InfiniteERP] has two webservice endpoints called ExternalSales and WebService.

== Devices Integration ==

=== Produk dari Solution ===

Device yang telah di support:
* Solution X100-C
** Firmware Version: Ver 8.0.4.6-20220121
** Firmware Version: Ver 8.0.4.6-20220616
* Solution X606-S
** Ver 8.0.4.5-20200408
** Ver 8.0.4.6-20220704
** Ver 8.0.4.6-20220704

Adalah Mesin Absensi Sidik Jari yang di produksi oleh https://solution.co.id/
Mesin ini memiliki fitur cloud ADMS dimana mesin bisa mengirimkan data absen secara realtime ke server.
Tim InfiniteERP telah berhasil mengembangkan server ADMS mandiri sehingga bisa integrasi langsung dengan module HRIS secara realtime.

==== Document Link from Solution.co.id ====
* SDK OLD Black & White : http://www.mediafire.com/file/k2vq0s06xx4a7d4/SDK_OLD_Black%2526White.rar/file
* New SDK Colour : http://www.mediafire.com/file/hnknf18leiv9qzi/NEW_SDK_Colour.rar/file
* WEB SDK : http://www.mediafire.com/file/0wotxt4fkzhtcoz/WEB_SDK.rar/file
* Push SDK : http://www.mediafire.com/file/tslhandv3utz8fx/pushsdk.rar/file
* New Push SDK : https://www.mediafire.com/file/51l70rzvgax6xr4/New_push-sdk.zip/file

= Roadmap =

Here the list of planned integration with other platform.

{| class="wikitable"
|-
! No !! Application/Services !! Description !! Status
|-
| 1|| [[Projects/Integration Yasmeera Webstore|Yasmeera Webstore]] || Customer specific webstore || '''''Inprogress'''''
|-
| 2|| [[Projects/Integration SabilaMall.co.id | SabilaMall.co.id ]] || Local market place || '''''Inprogress'''''
|-
| 3|| [[Projects/Integration WooCommerce | WooCommerce]] || Open-source eCommerce platform built on WordPress || '''''Inprogress'''''
|-
| 4|| Tokopedia || Market Place || Planned
|-
| 5|| Shopee || Market Place || Planned
|-
| 6|| [[Projects/Integration AuraMuslim.co.id | AuraMuslim.id ]] || Local Market Place || '''''Inprogress'''''
|-
| 7|| [[Projects/Integration Moota.co | Moota.co ]] || Layanan Online Check Mutasi Rekening Bank dalam satu sistem || '''''Inprogress'''''
|}

Others Application

2026-08-28T12:20:07Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

{{WorkInProgress}}

= '''Introduction''' =
InfiniteERP memiliki beberapa aplikasi lain yang mendukung fungsi operasional bisnis, dapat berupa dekstop application ataupun module tambahan berupa aplikasi berbasis web.
Tidak menutup kemungkinan, aplikasi ini didesain secara specific untuk client perusahaan tertentu karena kebutuhan khusus.

= '''Daftar aplikasi pendukung''' =
Daftar semua aplikasi yang dibuat untuk mensupport InfiniteERP:
== '''Attendance Synchronization''' ==
<p>
Aplikasi ini berfungsi untuk menarik data absen karyawan dari mesin absen kemudian di upload ke window [[Attendance Entry | Attendance Entry]].
</p>
Terdapat 2 jenis aplikasi untuk memenuhi kebutuhan pelanggan agar proses otomasi penarikan data absensi karyawan dari mesin dapat dilakukan dengan baik.
# Aplikasi Desktop yang diinstall didalam jaringan komputer pada perusahaan klien.
# Aplikasi server

== Production and Shipping apps ==

== '''Infinte ERP Apps''' ==
===Infinte ERP Apps Content===
# POS
# Shipment
# Inventory

<p>
===InfiniteERP Apps Address===
</p>
*apps for development https://dev-sg1.infinite-erp.co.id/
*app for production https://app-sg1.infinite-erp.co.id/

<p>

===Infinte ERP Apps Setup===
</p>

*Login user erpadmin
**After Login change Organization used to desired Organization
*Go To Menu Administrator
**[[Image:Admnistartor.jpg]]
*Define Organization
**Organization is refer to ERP Organization
*Define Role & User
*Role is not Linked to ERP, only User is linked to ERP
*Please ensure Role at ERP on the user have been granted
[[Image:API_Access.jpg|500px]]
*Define Access related to User
*Done
<br>
'''User Guide'''
* Video setup tutorial link
* https://drive.google.com/file/d/163ryLybqeb0VY_JSv0lmY9mzeHBRi6DI/view?usp=sharing

== '''Manage Infinite Apps ERP at pm2''' ==
===Introduction===
<p> To manage application at pm2 we using software Putty.
<br>Once login, please select '''hostxx.infinite-erp.co.id''' at PuTTy configuration.
<br>
[[Image:puTTy_configuration.jpg]]

<br>Following command is to enter the root
<pre>''sudo su''</pre>

<br>Following command is to know the list application on pm2 in tablet

<pre>pm2 list</pre>

===Start & Stop===
'''To Stop'''
<pre>pm2 stop <name> </pre>
<br>'''To Start'''
<pre>pm2 start <name></pre>
<br>'''Additional command'''
if any error on the status you can check the log
<pre>pm2 logs <name></pre>

===Delete & Add Apps===
<p>'''To Delete'''
<pre>
pm2 delete <name>
</pre>
<br>'''To Add '''
<br> Following are several sequence command to type
<pre>
cd appl←
ls←
cd infinteerp-v2←
ls←
cd dev←
ls←
cd infiniteapps←
ls←
nano pm2-apps-prod.json←
pm2 start pm2-apps-prod.json←
</pre>

<br>Additional command to check database configuration
<pre>nano .env</pre>

== '''Budibase''' ==
===Introduction===
Budibase adalah platform pengembangan yang dirancang untuk kecepatan dan produktivitas. Dengan Budibase, pengembang tidak lagi mengalami pengulangan, siklus pengembangan yang panjang, dan frustrasi. Sebaliknya, pengembang lebih produktif, lebih bahagia, dan dapat menghadirkan aplikasi yang mereka banggakan dalam hitungan menit.
=== Integrasi Infinite ERP dengan Budibase dengan API ===
==== [[Setup API]] ====
Dalam artikel ini akan dijelaskan bagimana mengintegrasikan Infinite ERP dengan budibase menggunakan API, sehingga data dapat di kelola menggunakan aplikasi yang di buat dari budibase.

* Add Source kemudian pilih
* Rest API
* buat Authentication untuk mengakses API Infinite ERP sesuai dengan akun yang telah di buat di infinite ERP
==== [[Membuat Query]] ====
* Kemudian add Query
* Pada bagian ini tentukan endpoint dan metode yang akan digunakan, dalam contoh ini akan menggunakan API Purchase Order infinite ERP dan metode yang digunakan adalah 'get' [[file: budibase1.png|800px]]<br>
# Pilih metode dalam hal ini adalah <pre>get</pre>
# Isikan endpoint dalam hal ini <pre>https://my.infinite-erp.co.id/infinite/org.openbravo.service.json.jsonrest/Order</pre>
# Pilih Authentication
# Pada bagian tab Transformer ganti code dengan code berikut ini <pre>return data.response.data</pre> fungsi ini untuk menampilkan response JSON menjadi schema atau kolom, sihingga data dapat di tampilkan pada table atau data provider budibase
# Pilih Save untuk menyimpan perubahan
==== [[Test API]] ====
# Kemudian klik tombol send untuk mencoba, jika berhasil akan menampilkan result seperti berikut ini [[file: result respons API.png|800px]]<br>
# Berikut ini merupakan tampilan schema yang nantinya akan di tampilkan pada table view [[file: Reponse schema.png|800px]]<br>

=== Membuat aplikasi dengan Budibase ===
==== [[Design]] ====
# Masih di halaman yang sama, pilih tab Design
# Pilih add screen
# Pilih Blank screen, lalu continue
# Pada bagian Screen details, isikan nama screen dan continue lagi
# Pada bagian Autogenerated screens, pilih basic saja kemudian done
==== [[Menambahkan nama menu ke navigation]] ====
[[file: membuat menu baru.png|800px]]<br>
# Pilih Navigation
# Pilih Configure Links
# Add link
# Isikan Nama Menu
# Pilih URL
# Kemudian pilih Save

==== [[Menampilkan data di table View]] ====
* Pastikan aktif pada menu screen yang telah di buat
* Add component
* Pilih Container
* Kemudian add component lagi
* Pilih data provider
* Lalu add component lagi
* Pilih New table
jika di lihat pada susunan component akan tampak seperti pada gambar berikut ini :
[[file: component.png|800px]]<br>

==== [[Custom Kolom table View]] ====
[[file: configure_column.png|800px]]<br>
# Pilih component table
# Configure Columns
# Add All Columns

[[file: configure_columns1.png|800px]]<br>
* Pada bagian ini pengguna dapat menghapus column yang tidak di perlu di tampilkan, cara nya dengan meng click tanda silang.
* Label : Pengguna juga dapat meng edit nama column sesuai dengan yang di inginkan
* Jika sudah click Save

==== [[Filter Data pada Table View]] ====

[[file: define_filter.png|800px]]<br>
* Pilih Data Provider
* Define Filters
* Pilih Column yang akan menjadi parameter lalu
* Isikan Value dan
* Save

Pengguna dapat menambahkan beberapa filter sesuai dengan kebutuhan.
Mirip dengan pengurutan, pemfilteran akan dilakukan di sisi server untuk sumber data SQL dan DB Budibase internal, namun untuk kueri khusus, pemfilteran akan dilakukan di sisi klien. Jadi saat menggunakan kueri khusus, Anda disarankan untuk memberikan filter apa pun dalam kueri.

==== [[Implementasi API Approval]] ====
Pada implementasi API Approval teknik yang digunakan adalah Bindings
Budibase fokus membangun aplikasi yang berpusat pada data - untuk dapat melakukan hal tersebut diperlukan suatu cara untuk memanipulasi data. Untuk melakukan ini, Budibase memiliki kemampuan untuk bind data ke dalam elemen desain atau otomasi apa pun melalui penggunaan sintaks Handlebars atau JavaScript.

===== [[Tips dan Trik]] =====
Penting untuk diingat bahwa Handlebars memungkinkan pernyataan yang cukup rumit, yang dapat menggunakan logika komparatif (terutama dengan pembantu perbandingan kami). Di bawah ini kami telah merinci beberapa tip yang akan membantu Anda memulai dengan sintaks binding dan Handlebars.
</p>

Others Application/id

2026-08-28T12:20:06Z

Wikiadmin: Create ID subpage stub (scaffold) for Others Application

{{Languages}}

== Others Application (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Others Application|Others Application]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Background Processes/id

2026-08-28T12:20:05Z

Wikiadmin: Create ID subpage stub (scaffold) for Background Processes

{{Languages}}

== Background Processes (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Background Processes|Background Processes]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Background Processes

2026-08-28T12:20:05Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Introduction =
InfiniteERP memiliki banyak Background Process didalamnya, yang digunakan untuk melakukan beberapa proses secara terjadwal.<br>
Dalam implementasi ERP dapat ditemukan kebutuhan khusus untuk masing-masing klien yang berbeda maupun customized secara umum yang digunakan oleh semua klien.

= Daftar Background Processes =

== Attendance Processing ==

Adalah proses pengolahan data absen yang diterima di ERP dari mesin absen dan diolah untuk menghitung jam kerja, lembur dan keterlambatan masuk kerja dan aturan lainnya yang dimiliki perusahaan.
Pada proses ini akan membentuk data baru hasil pengolahan yang dapat dilihat di menu window Attendance Entry.

InfiniteERP sudah memiliki ADMS Server yang sudah secara otomatis memiliki kemampuan menerima data absen secara realtime dari mesin produk dari X-Solution.
Selengkapnya dapat ditemukan disini [[Integration#Devices_Integration|Device Integration]]

== MRP Purchase Plan (IDOLMART) ==
== Delete Double Payment Plan SO ==
* Problem
Terjadi double payment plan di Sales Order, sehingga Sales Order tidak dapat di Complete

* Problem Solved
Run background atau process request Delete Double Payment Plan SO untuk men delete dan menyisakan satu record Payment plan saja

== Delete Item Double Sales Order ==
* Problem
Terjadi double item di sales order hasil dari sync POS

* Problem Solved
Run background atau process request Delete Item Double Sales Order untuk men delete dan menyisakan satu record Payment plan saja

== Auto Closed Sales Orders ==
Berfungsi untuk merubah status [[Sales Order | Sales Order]] dari Completed menjadi Closed berdasarkan umur Sales Order dalam hitungan Hari (Days).

=== Use Case Scenario ===

* Perusahaan tidak ingin lagi memproses Sales Order yang sudah diterima meskipun tidak semua Order dapat dipenuhi.
* Dalam hal ini Order Quantity pada Sales Order Lines akan disamakan jumlahnya dengan Delivery Quantity sehingga tidak ada lagi Order yang outstanding atau pending delivery.

=== Parameter Setup ===
Berikut parameter yang harus di setup pada window [[Preference | Preference]] :

{| class="wikitable"
|-
! Attribute !! Data Type !! Value !! Sample Value
|-
| AutoCloseOrderBackground_ageso || Numeric || Number of days || 30
|-
| AutoCloseOrderBackground_docType || ID || Document Type ID || 'AF09244D39B24847928C73AE7692E410'
|-
| AutoCloseOrderBackground_isSo || Yes/No || Y or N || Y
|}

=== Screen Reference ===

==== AutoCloseOrderBackground_docType ====
[[File: AutoCloseSalesOrder_background_1.png| 800px]]

==== AutoCloseOrderBackground_ageso ====
[[File: AutoCloseSalesOrder_background_2.png| 800px]]

==== AutoCloseOrderBackground_isSo ====
[[File: AutoCloseSalesOrder_background_3.png| 800px]]

Customer Specific Windows/id

2026-08-28T12:20:04Z

Wikiadmin: Create ID subpage stub (scaffold) for Customer Specific Windows

{{Languages}}

== Customer Specific Windows (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Customer Specific Windows|Customer Specific Windows]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Customer Specific Windows

2026-08-28T12:20:04Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

== Window ==
* [[Shipment Tracking Entry]]
* [[ROP Sugestion]]
* [[Approval Role]]
* [[Backlog Shipment]]
* [[Employee Salary View]]
* [[Custom SOA Monthly]]
* [[Bank Salary Payment Report]]

== Report ==

[[Payables Aging Schedule Default Org:Payables Aging Schedule Default Org]]

Google Sheets Dev

2026-08-28T12:20:03Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Intoduction =
Terkadang kita perlu melakukan simulasi dan berbagai ujicoba data maupun me-modelkan database ataupun untuk berbagai keperluan lain yang memanfaatkan Google Sheets; Dan halaman ini mencatat berbagai tips & trick serta formula yang biasa digunakan untuk menyelesaikan berbagai masalah di google sheets.

= How to? =

= Tips & Tricks =

Google Sheets Dev/id

2026-08-28T12:20:02Z

Wikiadmin: Create ID subpage stub (scaffold) for Google Sheets Dev

{{Languages}}

== Google Sheets Dev (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Google Sheets Dev|Google Sheets Dev]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

MariaDB/id

2026-08-28T12:20:01Z

Wikiadmin: Create ID subpage stub (scaffold) for MariaDB

{{Languages}}

== MariaDB (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[MariaDB|MariaDB]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

MariaDB

2026-08-28T12:20:01Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Introduction =

= Database Maintenance and Monitoring script =

== Backup & Restore ==

refer to https://mariadb.com/docs/recovery/backup-optimization/

* Take a full backup:
<pre>
sudo mariabackup --backup \
--user=root \
--password=P@ssw0rdINDO7Kali \
--target-dir=/home/backup/db
</pre>
Confirm successful completion of the backup operation.

* The backup must be prepared:
<pre>
sudo mariabackup --prepare \
--target-dir=/home/backup/db
</pre>
Confirm successful completion of the prepare operation.

== Monitor Index status dan size for optimization ==

== Monitor Cache Hit Ratio ==

== Monitoring Database Query Performance ==

== Locks held by Open Transactions ==

== Check Trigger Status ==

= How to =

[[Category:Database_Maintenance]]

PostgreSQL/id

2026-08-28T12:20:00Z

Wikiadmin: Create ID subpage stub (scaffold) for PostgreSQL

{{Languages}}

== PostgreSQL (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[PostgreSQL|PostgreSQL]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

PostgreSQL

2026-08-28T12:20:00Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Introduction =

= Database Development =

== Validation ==

=== Check: Columns with search reference and reference value null ===
Setiap Column yang ada dalam daftar hasil query harus diperbaiki sesuai standard Openbravo Development
<pre>

SELECT AD_COLUMN_ID AS referencekey_id, TABLENAME || ' - ' || COLUMNNAME AS RECORD_ID, 0 AS AD_ROLE_ID, NULL AS AD_USER_ID,
'The column ' || COLUMNNAME || ' in table ' || TABLENAME || ' is referenced as search and doesn''t have an associated reference value while having active updateable fields.' AS DESCRIPTION,
'Y' AS ISACTIVE, 0 AS AD_ORG_ID, 0 AS AD_CLIENT_ID, now() AS CREATED, 0 AS CREATEDBY, now() AS UPDATED, 0 AS UPDATEDBY
FROM AD_COLUMN, AD_TABLE
WHERE AD_REFERENCE_ID = '30'
AND AD_COLUMN.AD_TABLE_ID = AD_TABLE.AD_TABLE_ID
AND AD_REFERENCE_VALUE_ID IS NULL
AND AD_TABLE.ISACTIVE = 'Y'
AND AD_COLUMN.ISACTIVE = 'Y'
AND AD_COLUMN.ISPARENT = 'N'
--AND AD_COLUMN.ISUPDATEABLE = 'Y'
AND EXISTS (SELECT 1
FROM AD_FIELD, aD_TAB, AD_WINDOW
WHERE AD_FIELD.AD_COLUMN_ID = AD_COLUMN.AD_COLUMN_ID
AND AD_FIELD.AD_TAB_ID = AD_TAB.AD_TAB_ID
AND AD_WINDOW.AD_WINDOW_ID = AD_TAB.AD_WINDOW_ID
AND AD_FIELD.ISREADONLY = 'N'
AND AD_TAB.ISREADONLY = 'N'
AND AD_TAB.ISACTIVE = 'Y'
AND AD_FIELD.ISACTIVE = 'Y'
AND AD_WINDOW.ISACTIVE = 'Y'
AND ISDISPLAYED = 'Y')

</pre>

= Database Maintenance and Monitoring script =

== Monitor Index status dan size for optimization ==

Over optimizing is a thing
We always our database to be performant, so in order to do that we keep things in memory/cache (see earlier) and we index things so we don’t have to scan everything on disk.
But there is a trade-off when it comes to indexing your database.
Each index the system has to maintain will slow down your write throughput on the database.
This is fine when you do need to speed up queries, as long as they’re being utilized.
If you added an index years ago, but something within your application changed and you no longer need it best to remove it.
Postgres makes it simply to query for unused indexes so you can easily give yourself back some performance by removing them:

<pre>
/*
* Over optimizing is a thing
We always our database to be performant, so in order to do that we keep things in memory/cache (see earlier) and we index things so we don’t have to scan everything on disk.
But there is a trade-off when it comes to indexing your database.
Each index the system has to maintain will slow down your write throughput on the database.
This is fine when you do need to speed up queries, as long as they’re being utilized.
If you added an index years ago, but something within your application changed and you no longer need it best to remove it.
Postgres makes it simply to query for unused indexes so you can easily give yourself back some performance by removing them:
*/
SELECT
schemaname || '.' || relname AS table,
indexrelname AS index,
pg_size_pretty(pg_relation_size(i.indexrelid)) AS index_size,
idx_scan as index_scans
FROM pg_stat_user_indexes ui
JOIN pg_index i ON ui.indexrelid = i.indexrelid
--WHERE NOT indisunique AND idx_scan < 50 AND pg_relation_size(relid) > 5 * 8192
--where relname = 'ret_gen_tsm_targetomzetline'
where relname in ('ret_gen_tsm_targetomzetgrow','ret_gen_tsm_targetomzetline','ret_tsmrekap_category','ret_gen_tsmtarget_category')
ORDER BY relname asc, pg_relation_size(i.indexrelid) / nullif(idx_scan, 0) DESC NULLS FIRST,
--idx_scan asc,
pg_relation_size(i.indexrelid) desc
;

--drop index ret_gen_tsm_targetomzetline_tag_status_idx;
</pre>

== Monitor Temporary Table ==
<pre>
/*
* We all aware of the temp tables and many times developers are creating temp table for their ad-hoc testing purpose.
* But unfortunately sometimes, they forget to drop unused temp tables, and temp tables keep active in those idle connections.
* It also requires unnecessary utilization of disk space.
*
* DBAs are responsible for identifying unused temp tables and then inform to developers so that they can drop their unused temp tables.
*/

SELECT
n.nspname as SchemaName
,c.relname as RelationName
,CASE c.relkind
WHEN 'r' THEN 'table'
WHEN 'v' THEN 'view'
WHEN 'i' THEN 'index'
WHEN 'S' THEN 'sequence'
WHEN 's' THEN 'special'
END as RelationType
,pg_catalog.pg_get_userbyid(c.relowner) as RelationOwner
,pg_size_pretty(pg_relation_size(n.nspname ||'.'|| c.relname)) as RelationSize
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n
ON n.oid = c.relnamespace
WHERE c.relkind IN ('r','s')
AND (n.nspname !~ '^pg_toast' and nspname like 'pg_temp%')
ORDER BY pg_relation_size(n.nspname ||'.'|| c.relname) DESC
</pre>

== Monitor Dead Tupple ==
<pre>
/*
* Under the covers Postgres is essentially a giant append only log.
* When you write data it appends to the log, when you update data it marks the old record as invalid and writes a new one,
* when you delete data it just marks it invalid. Later Postgres comes through and vacuums those dead records (also known as tuples).
* All those unvacuumed dead tuples are what is known as bloat. Bloat can slow down other writes and create other issues.
* Paying attention to your bloat and when it is getting out of hand can be key for tuning vacuum on your database.
*/

WITH constants AS (
SELECT current_setting('block_size')::numeric AS bs, 23 AS hdr, 4 AS ma
), bloat_info AS (
SELECT
ma,bs,schemaname,tablename,
(datawidth+(hdr+ma-(case when hdr%ma=0 THEN ma ELSE hdr%ma END)))::numeric AS datahdr,
(maxfracsum*(nullhdr+ma-(case when nullhdr%ma=0 THEN ma ELSE nullhdr%ma END))) AS nullhdr2
FROM (
SELECT
schemaname, tablename, hdr, ma, bs,
SUM((1-null_frac)*avg_width) AS datawidth,
MAX(null_frac) AS maxfracsum,
hdr+(
SELECT 1+count(*)/8
FROM pg_stats s2
WHERE null_frac<>0 AND s2.schemaname = s.schemaname AND s2.tablename = s.tablename
) AS nullhdr
FROM pg_stats s, constants
GROUP BY 1,2,3,4,5
) AS foo
), table_bloat AS (
SELECT
schemaname, tablename, cc.relpages, bs,
CEIL((cc.reltuples*((datahdr+ma-
(CASE WHEN datahdr%ma=0 THEN ma ELSE datahdr%ma END))+nullhdr2+4))/(bs-20::float)) AS otta
FROM bloat_info
JOIN pg_class cc ON cc.relname = bloat_info.tablename
JOIN pg_namespace nn ON cc.relnamespace = nn.oid AND nn.nspname = bloat_info.schemaname AND nn.nspname <> 'information_schema'
), index_bloat AS (
SELECT
schemaname, tablename, bs,
COALESCE(c2.relname,'?') AS iname, COALESCE(c2.reltuples,0) AS ituples, COALESCE(c2.relpages,0) AS ipages,
COALESCE(CEIL((c2.reltuples*(datahdr-12))/(bs-20::float)),0) AS iotta -- very rough approximation, assumes all cols
FROM bloat_info
JOIN pg_class cc ON cc.relname = bloat_info.tablename
JOIN pg_namespace nn ON cc.relnamespace = nn.oid AND nn.nspname = bloat_info.schemaname AND nn.nspname <> 'information_schema'
JOIN pg_index i ON indrelid = cc.oid
JOIN pg_class c2 ON c2.oid = i.indexrelid
)
SELECT
type, schemaname, object_name, bloat, pg_size_pretty(raw_waste) as waste
FROM
(SELECT
'table' as type,
schemaname,
tablename as object_name,
ROUND(CASE WHEN otta=0 THEN 0.0 ELSE table_bloat.relpages/otta::numeric END,1) AS bloat,
CASE WHEN relpages < otta THEN '0' ELSE (bs*(table_bloat.relpages-otta)::bigint)::bigint END AS raw_waste
FROM
table_bloat
UNION
SELECT
'index' as type,
schemaname,
tablename || '::' || iname as object_name,
ROUND(CASE WHEN iotta=0 OR ipages=0 THEN 0.0 ELSE ipages/iotta::numeric END,1) AS bloat,
CASE WHEN ipages < iotta THEN '0' ELSE (bs*(ipages-iotta))::bigint END AS raw_waste
FROM
index_bloat) bloat_summary
ORDER BY raw_waste DESC, bloat DESC
</pre>

== Monitor Cache Hit Ratio ==

<pre>
/*
* monitor your cache hit ratio
* URL : https://www.citusdata.com/blog/2019/03/29/health-checks-for-your-postgres-database/
*/
SELECT
sum(heap_blks_read) as heap_read,
sum(heap_blks_hit) as heap_hit,
sum(heap_blks_hit) / (sum(heap_blks_hit) + sum(heap_blks_read)) as ratio
FROM
pg_statio_user_tables;
</pre>

== Monitoring Database Query Performance ==

<pre>
/*
* monitoring your database query performance.
* It records a lot of valuable stats about which queries are run, how fast they return, how many times their run, etc.
* Checking in on this set of queries regularly can tell you where is best to add indexes
* or optimize your application so your query calls may not be so excessive.
* URL : https://www.citusdata.com/blog/2019/03/29/health-checks-for-your-postgres-database/
*
* Jalankan : create extension pg_stat_statements; jika belum pernah dilakukan
*/
SELECT query,
calls,
ceil(total_time) as total_time,
ceil(total_time / calls) as time_per_call,
ceil(stddev_time) as stddev_time,
rows,
rows / calls as rows_per_call,
ceil(100.0 * shared_blks_hit / nullif(shared_blks_hit + shared_blks_read, 0)) AS hit_percent
FROM pg_stat_statements
WHERE query not similar to '%pg_%'
--WHERE query similar to '%omzetline%'
--and calls > 500
--ORDER BY calls desc
--ORDER BY total_time desc
order by time_per_call desc
--ORDER BY rows_per
LIMIT 100;
</pre>

== Locks held by Open Transactions (pg_locks) ==

<pre>
/*
* Script to find information about the Locks held by Open Transactions (pg_locks)
*
* PostgreSQL view pg_locks contains the main information about the all types of lock of Database Server.
* It contains one row per active lockable object.
* This script is very helpful to all PostgreSQL Database Administrators.
*/

SELECT
pl.pid AS ProcessID
,psa.datname AS DatabaseName
,psa.usename AS UserName
,psa.application_name AS ApplicationName
,ps.relname AS ObjectName
,psa.query_start AS QueryStartTime
,psa.state AS QueryState
,psa.query AS SQLQuery
,pl.locktype
,pl.tuple AS TupleNumber
,pl.mode AS LockMode
,pl.granted -- True if lock is held, false if lock is awaited
FROM pg_locks AS pl
LEFT JOIN pg_stat_activity AS psa
ON pl.pid = psa.pid
LEFT JOIN pg_class AS ps
ON pl.relation = ps.oid
</pre>

== Check Trigger Status ==

<pre>
SELECT * FROM pg_trigger
WHERE tgisinternal=false and tgenabled = 'D'

--tgrelid 'public.c_order'::regclass and

-- enable trigger
-- ALTER TABLE m_product ENABLE TRIGGER m_product_trg;

-- Disable trigger
-- ALTER TABLE m_product DISABLE TRIGGER m_product_trg;
</pre>

=== More advance ===

<pre>
-- Check Disabled triggers

select trigger_name as referencekey_id,
null as record_id,
0 as ad_role_id,
null as ad_user_id,
'Constraint '||trigger_name||' on table '||table_name||' is not enabled' as description,
'Y' as isActive,
0 as ad_org_id,
0 as ad_client_id,
now() as created,
0 as createdBy,
now() as updated,
0 as updatedBy
from user_triggers
where status!='ENABLED'

-- enable trigger jika di perlukan

--ALTER TABLE c_orderline ENABLE TRIGGER oez_order_line_addcost;
--ALTER TABLE m_product ENABLE TRIGGER m_product_trg;
--ALTER TABLE c_conversion_rate ENABLE TRIGGER c_conversion_rate_trg;
</pre>

== Monitor LIVE and DEAD Tupples ==

<pre>
SELECT
relname AS ObjectName
,pg_stat_get_live_tuples(c.oid) AS LiveTuples
,pg_stat_get_dead_tuples(c.oid) AS DeadTuples
FROM pg_class c
--where relname like 'c_%'
order by pg_stat_get_dead_tuples(c.oid) desc;
--order by pg_stat_get_live_tuples(c.oid) desc;
</pre>

== Monitor LIVE and DEAD Tupples with AUTO VACUUM ==

<pre>
SELECT
schemaname
,relname
,n_live_tup
,n_dead_tup
,last_autovacuum
FROM pg_stat_all_tables
ORDER BY n_dead_tup
/(n_live_tup
* current_setting('autovacuum_vacuum_scale_factor')::float8
+ current_setting('autovacuum_vacuum_threshold')::float8)
DESC
</pre>

= How to =
== Enabled Trigger secara massal ==
'''Background''': <br>

Dalam kasus tertentu selama compile terkadang terdapat problem sehingga menyebabkan ada beberapa Trigger yang tidak di Enable kembali:
Berikut adalah PostgreSQL command untuk ENABLE semua trigger yang statusnya masih DISABLE:

<pre>
DO $$
DECLARE
r RECORD;
BEGIN
FOR r IN
select
table_name as tablename,
trigger_name as trigger_name
from user_triggers
where status!='ENABLED'
LOOP
EXECUTE 'ALTER TABLE ' || r.tablename || ' ENABLE TRIGGER ' || r.trigger_name;
END LOOP;
END $$;
</pre>

== Terminate Idle Transactions for Postgres version 12 and previous ==

'''Background''':
<br>
since configuration '''idle_in_transaction_session_timeout''' on available at version 13 and above, here is the workaround solutions

In PostgreSQL version 10, you can use a SQL script to identify and terminate idle transactions based on your requirements.

Create below function:
<pre>
CREATE OR REPLACE FUNCTION oez_terminate_idle_sessions(idle_timeout_minutes integer) RETURNS void AS $$
BEGIN
-- Terminate idle sessions that exceed the specified timeout in minutes
PERFORM pg_terminate_backend(pg_stat_activity.pid)
FROM pg_stat_activity
WHERE state = 'idle in transaction' AND now() - pg_stat_activity.query_start > interval '1 minute' * idle_timeout_minutes;
END;
$$ LANGUAGE plpgsql;
</pre>

To use this function, you can call it with your desired idle timeout value. For example, to terminate sessions idle for more than 5 minutes, you can call the function like this:
<pre>
SELECT oez_terminate_idle_sessions(5); -- Terminate idle sessions idle for more than 5 minutes
</pre>

== Convert Integer or numeric to row number==
<pre>
select
generate_series(1,tot_wo) as row
from oez_gen_simple_wo sw
</pre>

[[Category:Database_Maintenance]]

Sistem Informasi Desa

2026-08-28T12:19:59Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Introduction =

Aplikasi yang didesain khusus untuk menampung informasi yang berkaitan dengan administrasi dan informasi publik desa. Aplikasi ini masih dalam tahap pengembanga serta beberapa fitur masih dalam tahap uji coba.

= Persiapan =
Setelah admin mendapatkan akun untuk login ke sistem selanjutnya admin melakukan input Wilayah, untuk level desa wilayah yang di masukkan adalah
* Dusun atau RW (Rukun Warga)
* RT (Rukun Tetangga)<br>
untuk input wilayah silahkan masuk ke menu wilayah
= User Guide =
== Informasi Wilayah ==
=== [[Wilayah]] ===
Halaman ini digunakan untuk mengelola data wilayah administratif yang berada di dalam Desa, pada halaman wilayah ini mencakup
Level Desa terdiri dari :
* Dusun atau RW (Rukun Warga)
* RT (Rukun Tetangga)
<br>
Level Kecamatan terdiri dari :
* Desa atau Dusun
<br>
Level Kabupaten terdiri dari :
* Kecamatan
* Desa

=== [[Pejabat_Wilayah|Pejabat Wilayah]] ===
Halaman ini digunakan untuk mengelola data Pejabat Wilayah atau pemerintahan di dalam instansi yang mencakup Wilayah Desa, Wilayah Kecamatan, Wilayah Kabupaten atau Kota, Wilayah Provinsi, untuk informasi detail nya silahkan klik [[Pejabat_Wilayah|halaman ini]]

== Kependudukan ==
=== [[Data_Penduduk|Data Penduduk]] ===
Pada halaman ini digunakan untuk menyimpan data penduduk desa atau sebagai arsip data penduduk yang nantinya akan dapat di kelola dalam bentuk laporan serta dapat digunakan untuk keperluan data yang lain, seperti penerima bantuan dan lain-lain.

= Informasi Developer =

Berikut informasi yang terdaftar:

== Setting Surat ==
Untuk mengetahui setting membuat surat dari sisi developer, anda bisa lihat [[Setting Surat|disini]].

== Profile Wilayah ==
Untuk update field yang ingin ditampilkan di menu Profile Wilayah, anda bisa lihat [[Langkah-Langkah Update Field Profile Wilayah|disini]].

= Informasi Pengguna =

== Membuat Surat ==
Untuk langkah-langkah membuat surat, anda bisa lihat [[Langkah-Langkah Membuat Surat|disini]].

== Profile Wilayah ==
Bagi anggota koperasi yang belum update nomor rekening dan nama bank, anggota bisa update secara manual [https://dev.barelanglaluanmadani.com/blmblog/form_update_anggota disini] . Untuk langkah-langkah update bank account, anda bisa lihat [[Langkah-Langkah Update Bank Account Koperasi BLM|disini]].

= Self Service =
Test WIKI

= Glosary =
{| class="wikitable"
|-
! No !! Istilah !! Pengertian
|-
| 1|| LEVEL|| Struktur atau turunan mulai dari tingkat terendah ke tinggi dalam bentuk sub
|-
| Example || Example || Example
|-
| Example || Example || Example
|}
=== Tagihan Saya ===
Ini contoh sub heading tagihan saya tes
[[Tagihan Saya|Tagihan Saya]]

Sistem Informasi Desa/id

2026-08-28T12:19:58Z

Wikiadmin: Create ID subpage stub (scaffold) for Sistem Informasi Desa

{{Languages}}

== Sistem Informasi Desa (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Sistem Informasi Desa|Sistem Informasi Desa]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Koperasi Syariah/id

2026-08-28T12:19:57Z

Wikiadmin: Create ID subpage stub (scaffold) for Koperasi Syariah

{{Languages}}

== Koperasi Syariah (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Koperasi Syariah|Koperasi Syariah]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Koperasi Syariah

2026-08-28T12:19:57Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Introduction =

Aplikasi yang di desain khusus untuk Koperasi Syariah menggunakan module InfiniteERP khusus sebagai aplikasi backoffice dan untuk interaksi dengan anggota, mitra dan pengurus dibuatkan khusus aplikasi front end mobile friendly yang semua data tersimpan di backend.

= Daftar Istilah / Glossary =

Daftar nama-nama jenid akad transaksi jual beli pada koperasi syariah:
* Murabahah
* Taqsith
* Istishna

Daftar nama-nama jenis investasi pada koperasi syariah:
* Mudhorobah Muqoyyadah
* Mudhorobah Mutlaqoh

= User Story =

* Anggota atau calon konsumen mengisi formulir pengajuan kredit
* Karyawan koperasi menerima notifikasi terdapat pengajuan kredit.
* Karyawan memastikan kelengkapan data yang diisi dan melakukan approval untuk tingkat lebih lanjut pada level pengurus.
* Setelah persetujuan pengurus, dapat diminta persetujuan pengawas untuk beberapa jenis transaksi khusus atau besaran nilai tertentu
* TBC

= Keanggotaan =

== Pendaftaran Anggota Baru ==
Proses:
# Calon Anggota mengisi formulir hardcopy / online form
# Calon Anggota melakukan pembayaran Iuran Pokok
# Calon Anggota melakukan pembayaran iuran wajib
# Pengurus mencatat informasi anggota di menu Anggota

== Anggota Keluar ==
# Anggota mengisi formulir pengunduran diri
# Pengurus melakukan verifikasi
# Cek jika ada tagihan kredit belum lunas
# Cek total iuran yang harus dikembalikan
# Pengurus melakukan proses pembayaran iuran kepada anggota
# Pengurus update informasi anggota telah keluar dan update tanggal keluar
# Anggota di set Non Active dengan tanggal keluar. Data Anggota akan tetap tersimpan termasuk semua data iuran dan semua transaksi yang pernah dilakukan.

== Update Bank Account ==
Bagi anggota koperasi yang belum update nomor rekening dan nama bank, anggota bisa update secara manual [https://dev.barelanglaluanmadani.com/blmblog/form_update_anggota disini] . Untuk langkah-langkah update bank account, anda bisa lihat [[Langkah-Langkah Update Bank Account Koperasi BLM|disini]].

== Pengajuan Kredit Anggota ==
Bagi anggota koperasi yang belum update nomor rekening dan nama bank, anggota bisa update secara manual [https://dev.barelanglaluanmadani.com/blmblog/form_update_anggota disini]

== Pengajuan Kredit Non-Anggota ==
Bagi anggota koperasi yang belum update nomor rekening dan nama bank, anggota bisa update secara manual [https://dev.barelanglaluanmadani.com/blmblog/form_update_anggota disini]

= Self Service =
Adalah menu halaman layanan mandiri setiap anggota koperasi maupun sebagai konsumen.
=== Perubahan Data Profil Pribadi ===
=== Informasi Keanggotaan ===
=== Riwayat Transaksi ===
Mencakup informasi transaksi pembayaran iuran koperasi dan riwayat transaksi yang pernah terjadi.
=== Tagihan Saya ===
Ini contoh sub heading tagihan saya tes
[[Tagihan Saya|Tagihan Saya]]

= Dashboard =
= Sahila ERP =
Adalah module ERP yang dibuat khusus untuk Manajemen Koperasi Syariah.

== Menu Koperasi Syariah==
=== Pengajuan Kredit ===
Ini adalah module backoffice di ERP dan akan terhubung dengan aplikasi Front End berupa web mobile sehingga bisa di akses oleh Anggota dan calon konsumen.

=== Anggota ===
Berfungsi untuk input pendaftaran anggota baru dan update data anggota seperti jika anggota telah keluar dari anggota koperasi.

=== Setup ===
==== Master Data ====
==== Setup Jangka Waktu Kredit ====
Jangka waktu kredit atau tenor mencakup setting jumlah cicilan dan persentase margin per bulan atau per tahun.
Tenor kredit digunakan oleh pengurus untuk membuat simulasi cicilan yang akan diberikan ke calon konsumen. Tenor Kredit dapat dipilih oleh pengurus pada menu Pengajuan Kredit atau juga secara manual di input dalam skenario khusus.

POS (Point Of Sales)

2026-08-28T12:19:56Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

= Introduction =
InfiniteERP memiliki aplikasi POS yang digunakan untuk beberapa klien industri retail.

= Client Specific =

= Fitur POS =
== [https://pos.idolmart.co.id/#ad_table.html?fm=d244fd83-f816-4d58-9955-a946a074b49d Promo Reguler] ==
Promo yang tidak bersyarat

== Promo Tebus Murah==
TESTING :
<pre>
CCCCC
</pre>

= Troubleshooting =

{{ManualDoc:POS-Troubleshooting}}

Berikut beberapa problem ditemukan dan cara menyelesaikan pada link ini [[:Category:POS-HowTo|POS Troubleshooting How-To]]
== Sales Order Tidak Balance ==
Total Penjualan di Local Pos tidak sama dengan hasil kalkulasi struk di server:

=== 1. Struk dari Local tidak Masuk Ke Server ===
1. Cari struk yang belum masuk ke web di menu [https://pos.idolmart.co.id/#ad_table.html?fm=022300e1-204c-4bd1-9e25-f41fb700249f Loss Bill] atau cek manual di menu [https://pos.idolmart.co.id/#ad_table.html?fm=ce256b8c-2dfc-4bec-9185-1b809caaaa7f bill today]

2. sync manual bill yg tidak masuk dari PC local toko
query : update pos_dsales set issync=false where billno like 'BILL YANG TIDAK MASUK'

=== 2. Struk dari local double di server===
Cek di menu [https://pos.idolmart.co.id/#ad_table.html?fm=3b05a9b3-b0bb-4075-9e7d-8bfd5d54b52e Fail Bill], Delete Struk yg Double

=== 3. SO tidak terbentuk ===
1. cek document so di table pos_dsalessum dan pos_dsalesorder
2. jika document so tidak ditemukan di pos_dsalesorder
jalankan query : SELECT public.proc_pos_dsalesorder_manual_insert('CODE CLIENT','CODE ORG','06-Aug-22','ASP');
3. cek lagi di table pos_dsalesorder
4. jika tidak ada di pos_dsalesorder, cek data struk di table pos_dsalesbilltoday, jika tidak ada pindahkan sementara data dari table pos_dsalesbill ke pos_dsalesbilltoday
query : select * from pos_dsalesorder where documentno like 'BOS88-CASH-2022-08-06';
select * from pos_dsalessum where documentno like 'BOS88-CASH-2022-08-06';

INSERT INTO public.pos_dbilltoday
(isactived, insertdate, insertby, postby, postdate, ad_org_id, billno, billamount, paymentmethodname, membercard, cardno, approvecode, edcno, serialno, billstatus, paycashgiven, pos_mbank_key, pos_dcashierbalance_key,
paygiven, printcount, bankname, pos_medc_key, billcode, point)
SELECT isactived, insertdate, insertby, postby, postdate, ad_org_id, billno, billamount, paymentmethodname, membercard, cardno, approvecode, edcno, serialno, billstatus, paycashgiven, pos_mbank_key,
pos_dcashierbalance_key, paygiven, printcount, bankname, pos_medc_key, billcode, point
FROM public.pos_dbill
where billno like 'BOS88-060822S%' and paymentmethodname like 'CASH'
--delete from pos_dbilltoday where billno like 'BOS88-060822S%' and paymentmethodname like 'CASH';
INSERT INTO public.pos_dbilllinetoday
(isactived, insertdate, insertby, postby, postdate, billno, seqno, sku, qty, price, discount, amount, ad_org_id, discountname)
SELECT isactived, insertdate, insertby, postby, postdate, billno, seqno, sku, qty, price, discount, amount, ad_org_id, discountname
FROM public.pos_dbillline
where billno in (select billno from pos_dbill where billno like 'BOS88-060822S%' and paymentmethodname like 'CASH');

--delete from pos_dbilllinetoday
--where billno in (select billno from pos_dbill where billno like 'BOS88-060822S%' and paymentmethodname like 'CASH');
SELECT public.proc_pos_dsalesorder_manual_insert('D089DFFA729F4A22816BD8838AB0813C','AD05B790FB144FDA9704320962710058','06-Aug-22','ASP');

= [[:Category:POS-HowTo | How-To]] =

POS (Point Of Sales)/id

2026-08-28T12:19:55Z

Wikiadmin: Create ID subpage stub (scaffold) for POS (Point Of Sales)

{{Languages}}

== POS (Point Of Sales) (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[POS (Point Of Sales)|POS (Point Of Sales)]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Retail:Configuration Guide

2026-08-28T08:57:25Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

[http://wiki.openbravo.com/wiki/Retail:Main_Page Back to main page]
== Introduction ==
This document describes how to configure the following specific settings of the [http://www.openbravo.com/retailers/product-features/overview/ InfiniteERP Retail Solutions]:
* Enterprise model
* Store pricing
* Assortment
* Cash Management
* Web POS

For generic documentation about '''InfiniteERP''' configuration please follow the [http://wiki.infinite-erp.co.id/index.php/Quick_Guide Quick Guide].

'''If you are trying out '''InfiniteERP''' Retail Solutions for the first time, you MUST first execute all of the [http://wiki.openbravo.com/wiki/Quick_Guide#Business_setup Business Setup] configuration instructions in the Quick Guide before executing the configuration instructions below.'''

== Installing the InfiniteERP Retail Solutions module ==

{{(!)|The Retail system manages to hit a bug in the PostgreSQL database version as being currently shipped in the Openbravo rPath Appliance which can lead to bad performance of the application. To avoid this for the moment we recommend to use the [[Openbravo_On_Demand_User_Guide | On Demand]] or [[Installation/Ubuntu | Ubuntu]] installation methods}}

The Openbravo for Retail module is the main module of the Openbravo Commerce Suite. To install the module (an Openbravo Subscription to either [http://www.openbravo.com/retailers/editions-and-pricing/ Enterprise or Professional Edition] is required since it is a commercial module, read more about [[Retail:License|Retail License]]):

* Login as System Administrator
* Navigate to '''''General Setup -> Application -> Module Management'''''
* Click the '''''Add Modules''''' tab
* Find the ''Openbravo for Retail'' module within the list of available modules.
* Click on '''Install Now''' and follow the guided installation flow.

== Add Retail Stores to the Organization Model ==

In Openbravo an organization is a business unit within an entity (company). Each entity can have more than one business unit to cover different zones, areas, region, stores...
Openbravo allows the definition of a hierarchical structure of organizations where a parent-child relationship between them can be determined. The result is a n-level organization tree, as follows:

[[Image:OrgTree.png|200px|thumb|center]]

This structure is flexible enough to support any further organizational change and may have unlimited levels, branches and nodes at each level as the situation may demand.

In Organization window there is new group of fields called ''Retail Configuration''. There you can find ''Retail Organization Type'' field where you define whether an organization is a store or a group of stores:

'''Store:'''
* Represents a physical retail store
* Only leaf organizations should be configured as store type
* The POS terminals set up in Openbravo shall be restricted to stores
* Must have an Anonymous Customer (Business Partner defined as Customer, with a default payment method)
* Must have an Anonymous Customer Location
* Must have at least one on-hand warehouse defined in the "Warehouses" tab
* The currency defined is the currency that will be used in all terminals of this store. The currency used can be edited to define retail configurations like the precision used in Web POS terminals.
'''Group:'''
* Represents a grouping of stores (or other groups)

[[Image:RetOrgTypeAss.png|800px|thumb|center]]

== Store Pricing Configuration ==

Item pricing can be managed by store or store group. This allows the retailer to manage multiple pricing for a single item.

In Organization window there is a 'Price List' field inside ''Retail Configuration'' group. Any node of the enterprise model (either group or store) can have a sales price list assigned.

Pricing management rules:
*Prices defined at store level will always overwrite the prices defined at parent level
*If the store does not have any attached price list, the price will be inherited from the parent element (store group) in the organizational structure

In the following example all stores located on Zone 1 will use the prices defined at Zone 1 level, except the Store 11, that is going to have its own price list.

[[Image:PriceListTree.png|400px|thumb|center]]

Before RMP19, only price lists which included the tax were supported. Starting RMP19, pricelists without including taxes are also supported in Retail.

In case a pricelist without taxes is used, the prices shown in the receipt lines will be net prices, and an additional line which includes the total tax will be shown. The total amount of the receipt will still be the gross amount.

== Numerical Precision Configuration ==
The Web POS only supports one single precision, and by default uses the Price Precision of the currency it is working on both for its pricing precision, and for the general precision for all internal calculations. Sometimes, it's necessary when operating the backoffice to define a different Price Precision than the Standard precision, and sometimes this price precision would be wrong in the Web POS. For these cases, the POS Precision column in the currency window exists.

This POS precision prevails against every other precision, so if it is defined, then it is used both for price precision and other calculations. If it's not defined, then the Price Precision is used instead.

== Assortment Configuration ==

Assortment management allows the retailer to determine the product range that will be made available for sale at various stores.

A new window ''Assortment'' is created to provide a new grouping for products.

The window has two processes (buttons) for common operations dealing with assortment:
*Clone: New button is displayed in the toolbar. It will create a copy (clone) of the selected assortment. Newly created assortment is opened in form view in order to let the user modify it if required
*Include all products: The user will be able to include all products at once in the assortment by using this button. Duplicated products in the same assortment are not allowed

[[Image:ProductList.png|800px|thumb|center]]

Organization window has a new optional field Assortment inside ''Retail Configuration'' section. Any node of the enterprise model (either group or store) can have an assortment assigned.

[[Image:ProdListTreeAss.png|400px|thumb|center]]

Assortment management rules:
*If a store has an attached assortment, it can only trade with products defined inside the assortment
*Assortment defined at store level will always overwrite assortment defined at parent level
*If the store does not have any attached assortment, the assortment will be inherited from the parent element (store group) in the organizational structure

'''Notes:'''
* Only products included in the assortment and have a price defined in the price list assigned to the store will be available to sell.
* Starting with '''RR17Q3''', products with attributes are supported in Openbravo Retail. Previous versions only supported products with attributes if they were not mandatory.

=== Assortment At POS Terminal Type Level Configuration ===

{{(!)|Starting from 3.0RR18Q4 this functionality is available}}

On '''3.0RR18Q3''' and previous releases, the only option to set the assortment of products for WebPOS was to define it at Store level (Organization window in the ERP). With this new development, the assortment of products for WebPOS could be defined also at POS Terminal Type level (POS Terminal Type window in the ERP).

WebPOS always needs an assortment of products to be loaded. To get the assorment, WebPOS terminal will look first if there is an assorment at POS Terminal Type level, and, in case it's not defined or set, it will look for the assortment set at Organization level.

== Category Tree Configuration ==

Select menu option: ''Application / Master Data Management / Product setup / Product Category''. Push button to show Tree Grid Visibilty.

[[File:categoryTreeConfigErp.png | 800px]]

* Create new categories as necesary

* Modify a category tree

* Add products to a new categories

'''Remember:''' For a category can have children check Summary Level

== Cash Management Events ==
A cash management event is either a cash deposit or withdrawal in the store, but also the process of cashing up. A store can have several cash management events and they are configured differently depending on the nature of the event (in, out, close).

These events are managed in WebPOS and need to be defined in tab ''Cash Management Event'' in ''Organization'' window.

[[Image:CashManagementEvent.png|800px|thumb|center]]

For each event you need to define the following:
*'''Name''': Name of the event. In "in/out" event type, the name can be seen as the event reason shown in WebPOS to allow the cashier give more detail of the operation (e.g it can be different reasons for withdrawing money from the store, for instance the cash security level is reached in the store, or we need to transfer money from one store to another)
*'''Currency''': Currency of the event
*'''Payment Method''': Payment method associated to this event. In case of cash up, it is necessary to create as different ''close'' events as different payment methods are supported in the store
*'''Event Type''': In, out, close depending on the nature of the event
*'''Financial Account''': The account which will be the destination (or the origin) of the cash movement and it depends again on the nature of the event. For ''in'' case, it is the financial account from where money is going to be extracted (origin). For ''out'' case, it is the financial account from where money is injected (destination). Finally, for ''close'' it is the financial account where money is also going to be injected (destination). '''''Be careful, do not use the same financial account in payment types (payments allowed for a POS Terminal) and for "close" Financial Accounts. Moreover, it is recommended to use a different financial account in payments allowed for a POS Terminal and for the "cash management" events.'''''

== Limit for approvals for count differences in initial cash count and cash up ==
Approval system enhancement for cash up and initial count processes, adding the possibility of specifying differences limits for each payment method before asking for an approval.

=== Global Count Difference Limit ===

Navigate to '''''Organization''''' window and select a organization to configure. On section '''Retail Configuration''' set ''Count Difference Limit'', as shown on following figure:

[[Image:CountDifferenceLimit_Org.png|800px|thumb|center]]

=== Count Difference Limit for the payment methods ===

Navigate to '''''POS Terminal Type''''' window and select a item to configure, in tab '''Payment Method''' select a item to configure. On section '''Cash Up''' set ''Count Difference Limit'' and on section '''Cash Management''' set ''Initial Count Difference Limit'', as shown on following figure:

[[Image:CountDifferenceLimit_POSTermType.png|800px|thumb|center]]

'''Note:''' Before to '''3.0RR16Q2''', null value in this field is the same as the value 0: the approval always is required when there is a difference amount. From '''3.0RR16Q2''' the behavior has changed: if the field is null, then never the approval is required, if the value is 0 and there is a difference amount, the approval is required.

=== Approval Reason ===
Navigate to '''POS Approval Reason''' window and edit/add the reasons, as shown on following figure:

[[Image:CountDifferenceLimit_ApprovalReason.png|800px|thumb|center]]

== Customers default configuration ==

The are some fields we must fill if we want to create new customers in Web POS. These fields will be the default value for customers created in our terminal.
*'''Default invoice term for BPs'''
*'''Default payment term for BPs'''
*'''Default BP Category for BPs'''
*'''Default country for BPs'''
*'''Default organization term for BPs'''
*'''Show Tax ID for BPs Edition''': If checked, this option will show an extra field to insert the Tax ID.
*'''Show BP Category selector for BPs edition''': If checked, this option will show an extra field to select the BP category.
[[Image:customersConfiguration_rmp19.png|800px|thumb|center]]

=== Preferences ===

The following preferences have been created:

* '''OBPOS_retail.disableNewBPButton''', used in WebPOS to disable the New Customer button until a search is performed.
* '''OBPOS_retail.customer_advanced_filters''', used in WebPOS to grant/deny access to the Advanced Filters window on the Customer Search popup.
* '''OBPOS_FilterAlwaysBPByAddress''', used in WebPOS to enable/disable in the filter of business partner always use the location.
* '''OBPOS_NotAllowEditCustomer''', used in WebPOS to allow or not to modify an anonymous customer or its adress(es).

== Grouped products ==

By default, all of the products are grouped in Web POS. It means that when a line representing a product is already in the ticket and more units are added, the line will change the quantity without creating new lines.

If you want to create a new line for each product, "Grouped product" field should be disabled.

This field is located in the header of the product window.

Not grouped products will generate new lines when they are added to the ticket through "Browse", "Search", "Scan". When they are added to the ticket we will be able to change the quantity of each line.

== Non Returnable Products ==
{{(!)|Starting from '''RR17Q2''' below functionality is available }}

By default all of the products are returnables in Web POS. It means that it will always be possible to return them. However, in some cases this should not be the rule and in this field you can deactivate this functionality. It is also possible to fill the value of Overdue Return Days in order to set a maximum period of time to return an item.

This field is located in the header of the product window.

The following pop-up will rise when trying to return a non returnable product as a return line:
[[Image:NormalNonReturnable.png|600px|center]]

The following pop-up will rise when trying to return a non returnable product using verifying returns:
[[Image:VerifiedNonReturnable.png|600px|center]]

== PLM Status ==

{{AvailableFrom|3.0RR18Q3}}

From '''18Q3''' is possible to configure the PLM (Product Lifecycle Management) Status of the products. This status affects to critical flows in which the products are used. Up to now, in the ''Web POS'' the only affected flow is the process of selling them. In the next link is possible to find more information and the different status of the ''PLM Status'':

http://wiki.openbravo.com/wiki/Projects:PLM_Status

=== Configure the PLM Status ===

The products status is configured directly in the '''Product''' window. There, there's a selector to set the current status to it:

[[Image:Plmproduct.png|800px|thumb|center]]

It is also possible to open the status list in a selector, to see which is the impact of each one:

[[Image:Plmselectorproduct.png|800px|thumb|center]]

Here the user can see how a status affect to the different flows. The selector is not modifiable, is read only.

==== PLM Status in the Assortment ====

The PLM Status can also be configured in the '''Assortment''' window, in the '''Product''' tab of the window. Any configuration done here overrides the configuration set in the '''Product''' window, affecting only in the organization for which the assortment is configured. This allows to have a different status for a product in each store. The products that are not configured in the assortment will use the status of the product.

[[Image:Plmassortment.png|800px|thumb|center]]

The PLM Status can also be shown with the selector popup, as in the '''Product''' window.

== Enable cross store for a product ==
Cross store is an utility which allow us to see the detailed stock by bin in our store and also the stock of the product in other warehouses of the organization.

To see the stock detail view the field ''Show stock screen'' shuold be checked in the product window.

In this example we will activate the stock screen for the product ''Base camp duffel 70L''

[[Image:OBPOS_enable_show_stock.png|800px|thumb|center]]

{{(!)|Starting from '''RR16Q2''' below functionality is available }}

It exists the possibility to define which warehouses are going to be part of “Cross Channel Warehouse”.

Definition is done in window “Organization” using “Cross Channel Warehouse” tab and adding the warehouses using button “CC Warehouse”. This warehouses are warehouses not defined as Warehouses on Hand of the Store, and defining them in this tab it will be possible to check the Stock of products in those warehouses from Web POS for the configured Stores.

[[File:CCWarehouse_button.jpg|800px|thumb|center]]

Apart from that using the field “Included Warehouses” in the organization it is possible to
define different logics:

-All excluding defined: Web POS will propose all the warehouses defined in the system except which ones defined as On Hand

-Only those defined: Web POS will propose you only the stock of defined warehouses

[[File:Included_CCWarehouses.jpg|800px|thumb|center]]

After this configuration, Web POS will open the stock window when a product is clicked in order to be added to the ticket.

[[Image:OBPOS_view_cross_store.png|800px|thumb|center]]

==Product Images==
By default, the product images are automatically loaded into the browser local database, so they can be used offline in a convenient way. However, the browser local database has a maximum size limitation in all environments, and in some of them this maximum size can be quite restrictive (specifically, in iOS, the maximum size is restricted to 50 MB).

If this maximum size is not enough for your needs, you can configure the Web POS so that it doesn't save the images into the local database, and instead requests them directly to the server.

The slight downside to using this method is that in when the POS goes offline, images for previously used products will be available, but the images for products not yet used will not (the generic 'box' image will be shown instead). If this downside is not relevant for you, then you can definitely use this method to make it possible to use big amounts of products with images in devices such as the iPad

===How to configure the alternate way to load images===
The first step to configure this alternate way to load images is to create a preference in the system, with property '''Web POS Product Images from server instead of cache''', and with value '''Y'''.

[[Image:OBPOS_image_preference.png|800px|thumb|center]]

This preference will tell the Web POS that it needs to load images from the server directly, instead of loading them from the local database.

To improve the performance of this functionality, and ensure that the server is not overloaded with the image requests, the images are read directly from files in the server, instead of the database. This means that image files need to be generated from the product images in the database. To do this, a process called '''Generate Product Images''' needs to be run.

[[Image:OBPOS_generateimageprocess.png|800px|thumb|center]]

This process receives an assortment as a parameter, and will generate files for all products in the assortment which contain an image. After this process has been run, the Web POS terminals should be able to load all product images without trouble.

==Anonymous Layaways==

{{(!)| This configuration will be available starting from RR16Q2}}

This new functionality provides the functionality to allow or deny the creation of layaways for the anonymous customer of the store/terminal (the anonymous customer is defined either on the POS Terminal window or on the Organization window; the value on POS Terminal window, if it exists, will override the value on Organization window).

Navigate to the [[Organization]] window and check '''Allow anonymous customer layaway''' if you want to allow the creation of layaways for the anonymous customer.

[[File:AnonymousLayawaysConfig.png|thumbnail|center|800px]]

==Allow to void Layaways partially paid==

{{(!)| This configuration will be available starting from RR16Q4}}

This new feature provides the ability to configure the store to allow/deny the layaway voiding process if these have some associated payment.

Navigate to the [[Organization]] window and check '''Allow partially paid layaways to be voided''' if you want to allow the voiding of layaways when there are related payments.

[[File:VoidLayawaysConfig.png|thumbnail|center|800px]]

==Currency Exchange Rate at Store Level==

{{(!)| This configuration will be available starting from RR18Q3}}

This new feature provides the ability to configure currency exchange rates at Store level. Currently Openbravo only allows to define currency exchange rates at * level. With this feature, if any exchange rate is defined for an store, the one defined at * level will be overwritten.

Navigate to the [[Organization]] window and open ''Conversion Rates'' tab. Notice that the tab only will be displayed if the selected organization type is ''Retail Store''.In this window it will be possible to define information:
* Currency
* To Currenty
* Valid From Date
* Valid To Date
* Multiple Rate By: a Multiple rate by which is the rate by which the base amount will be multiplied for to calculate the converted amount.
* Divide Rate By: and a Divide rate by which is the rate by which the base amount will be divided by to calculate the converted amount.

[[File:ExchangeRateAtStoreLevel.png|thumbnail|center|1200px]]

==Currency Rounding at Store Level==
{{(!)| This configuration will be available starting from RR19Q1}}
This new development allows to select rounding for different currencies.

Navigate to the [[Organization]] window and open ''Currency Rounding'' tab. It will be possible to configure:

* Currency
* Rounding To
* Rounding Down Limit

In this example, if change is between 100 and 25, it will be rounded up to 100. However if it is less than 25, it will be rounded down to 0.

[[File:Backroun.png|thumbnail|center|1200px]]

==Maximum Allowed Quantity or Price Configuration==
{{(!)| This configuration will be available starting from RR18Q3}}

===Introduction===
This configuration allows to show a popup if the quantity or price exceeds a value set in two new properties defined:
* Web POS maximum allowed price using keyboard
* Web POS maximum allowed quantity using keyboard

[[File:Retail_wk_config_price.png|thumbnail|center|600px]]
[[File:Retail_wk_config_qty.png|thumbnail|center|600px]]

These preference works as other preferences from Web POS, in terms of configuration, with a small difference: the value set indicates Web POS the value to be exceeded to show a confirmation popup. Once set one or both of these preferences, the functionality starts to be check in Web POS.

===How it works===

Once configured, there are two possible scenarios to take into account:

* Web POS maximum allowed price using keyboard is defined. Two different cases could happen:
** The price to be changed is lower than the value configured. The price is set to the lines selected without any UX difference.<br>[[File:Retail_wk_func_price_before.png|thumbnail|center|600px]]<br>
[[File:Retail_wk_func_price_after.png|thumbnail|center|600px]]
** The price to be changed is equal or greater than the value configured. The price is not set directly and a confirmation popup is shown:
[[File:Retail_wk_func_price_before_exce.png|thumbnail|center|600px]]<br>
[[File:Retail_wk_func_price_after_exce.png|thumbnail|center|600px]]<br>
*** If the user click on Cancel button, the price is not set to any line(s)
[[File:Retail_wk_func_price_after_exce_cancel.png|thumbnail|center|600px]]<br>
*** If the user click on OK button, the price is set to line(s)
[[File:Retail_wk_func_price_after_exce_ok.png|thumbnail|center|600px]]<br>

* Web POS maximum allowed quantity using keyboard is defined. Two different cases could happen:
** The quantity to be changed is lower than the value configured
The quantity is set to the lines selected without any UX difference.
[[File:Retail_wk_func_qty_before.png|thumbnail|center|600px]]
[[File:Retail_wk_func_qty_after.png|thumbnail|center|600px]]
** The quantity to be changed is equal or greater than the value configured
The quantity is not set directly and a confirmation popup is shown:
[[File:Retail_wk_func_qty_before_exce.png|thumbnail|center|600px]]
[[File:Retail_wk_func_qty_after_exce.png|thumbnail|center|600px]]
*** If the user click on Cancel button, the quantity is not set to any line(s)
[[File:Retail_wk_func_qty_after_exce_cancel.png|thumbnail|center|600px]]
*** If the user click on OK button, the quantity is set to line(s)
[[File:Retail_wk_func_qty_after_exce_ok.png|thumbnail|center|600px]]

==Web POS module==
POS Terminals represent the different terminals on each store and need to be configured properly in order to ensure operations are well supported in the backofice (e.g stock is updated in the backoffice when a sale is registered, invoice is created if customer requires it, etc.).

Most of the configuration take place in two windows:
* POS Terminal Type
* POS Terminal

The ''POS Terminal Type'' window contains what can be described as a "POS Terminal Configuration". This is a configuration designed to model a type of POS terminal. Each ''POS Terminal'' can only have one POS Terminal configuration.

It allows a very flexible configuration and an example would be a multi-store company. Each store could be managed differently (e.g have different cash up processes). In this case, different ''Pos Terminal Types'' could be defined for each store. And terminals within same store could share the same ''Pos Terminal Type''.

This two tables are designed to simplify the configuration process for the user: if the user needs to configure 100 terminals, but all of them are basically identical, then the amount of data he will need to insert is quite small, because all POS terminals will point to the same POS Terminal configuration.

In this section, we will first describe how ''POS Terminal Types'' are configured, and then we will describe the ''POS Terminal'' window.

===POS Terminal Type window===
In this window, you basically design a POS Terminal configuration, which will be used by one or many POS terminals. Here you configure relevant information at POS level, but also at payment method level.

[[Image:masterdata.png|800px|thumb|center]]

In the header, you configure the following fields:
* '''Name''': The name of the POS terminal type
* '''Document type''': The document type used for sales orders, note see the [[Retail:Configuration_Guide#Configuring_for_performance|performance section]] for its influence on cashup and ticket creation performance in the backend.
* '''Document type for returns''': The document type for returned receipts
* '''Document type for reconciliations''': The document type used for the reconciliations done when executing the "Cash up" process in the POS
* '''Document type for quotations''': The document type for quotations
* '''Group orders in one invoice''': If checked, then all orders processed in Web POS without an invoice are grouped by Business Partner and an invoice for each group of orders is created in the Cash Up process. If unchecked, one invoice per order will be created. Note see the [[Retail:Configuration_Guide#Configuring_for_performance|performance section]] for its influence on cashup and ticket creation performance in the backend.
* '''Separate invoice for returns''' (Starting from RR18Q1): If selected, separate invoices will be generated during the cashup for sales orders and returns, respectively.
* '''Allow pay on credit''': If checked, all POS terminals of this POS terminal type will be able to pay sales orders as a credit.
* '''Default Payment Method''': Selects the payment method that will be used by default when closing a receipt.
* '''Use external input''': (Previously '''Use barcode scanner''') If checked, the Web POS will take into account that an external input (keyboard or barcode scanner) is going to be used in this POS terminal type. Checking this option and then not connecting an external barcode will cause the virtual keyboard to be shown continuously in some devices (specifically in mobile devices (Android phones and tablets and iOS devices like iPads or iPhones).
* '''Hide virtual keyboard with barcode scanner''': if '''Use external input''' is checked but you are using a barcode scanner in your mobile device which is not detected as en external keyboard, the virtual keyboard will appear very frecuently. Using this flag (enabled by default) it will not happen and the virtual keyboard will not be shown. (This feature does not work in iOS, so the value of this flag is ignored when web POS is running in iOS)
* '''Layaway Orders''' (Starting from RR15Q3): If selected, all new orders are created as layaways. This configuration option allows to create terminals that only creates layaways orders that are not paid in these terminals and must be paid in other terminal.
* '''Use RFID:''' (Starting from RR16Q3) Enables the use of an RFID reader. Also, in order to use the reader, the hardware url has to be set according with [[Retail:Configuration_Guide#POS_Terminal_window | this guide]].
* '''RFID Timeout:''' (Starting from RR16Q3) Set a timeout to Web POS after which a disconnect will be sent to the RFID reader (If this field is not set, the timeout is disabled). This timeout resets every time a product is scanned through the reader.
* '''Use Security Gate:''' (Starting from RR16Q3) This field establish that after every POS sale, the terminal will send the order to the Hardware Manager, and the latter will try to call to its respective sendOrder method. This method has to be implemented in a new Hardware Manager plugin if one wants to use this check. Basically is intended to be used if a communication with a security gate is needed.
* '''Multi Change''' (Starting from RR19Q1): If selected, it will be possible to return change in different currencies. Note see [http://wiki.openbravo.com/wiki/Projects:Multicurrency_Change_&_Rounding/Technical_Functional_Guide this guide] for the rest of the configuration needed.
In addition to these, there are two more fields which define how the masterdata reloading is done:
*'''Time to fully refresh masterdata (in minutes)''': A full refresh is the process of reloading the whole masterdata set (including products, business partners, prices, taxes, ...). This operation is very expensive and time consuming, so it should be done only when really needed (typically, every day). If done with too much frequency, this may tax too much the server, greatly slowing down the operation of POS terminals.
*'''Time to incrementally refresh masterdata (in minutes)''': This process is much lighter than a full refresh, because it only loads records which were changed from the last time a refresh was done. This is much less expensive than a full refresh, but has the disadvantage that if a record was deleted, it will not detect it.

If neither of the fields is defined, then the system will fully refresh all data when the user logs in (and data will not be automatically refreshed until the next log in).

If only the first field is filled, then the system will fully refresh all data in the next login done after of minutes specified in the field.

If both fields are specified, then both incremental will be done each number of minutes as indicated in the field. The full refresh will be done in the next login done after of minutes specified in the field.

==== Payment Method ====

[[Image:PosTerminalTypePaymentMethod.png|800px|thumb|center]]

In the Payment Method tab, you configure the following fields:
* '''Search key''': An identifier string for the payment method.
* '''Name''': The name of the payment method
* '''Payment method''': The Openbravo payment method associated with this POS payment method
* '''Currency''': The currency associated to this payment method in POS
* '''G/L Item for Writeoff''': In case the amount received when paying a ticket differs from what is expected, this G/L Item reflects this difference. '''We strongly recommend using the name of the POS terminal and the Payment method for naming the G/Item in order to avoid problems with matching transactions and bank statements. Example: ''VBS Cash overpayments'''''
* '''G/L Item for Rounding'''(Starting from RR19Q1): In case [http://wiki.openbravo.com/wiki/Retail:Configuration_Guide#Currency_Rounding_at_Store_Level rounding] is activated it is needed to configure this GL Item in order to associate it to rounding cash differences.
* '''Payment Provider''': Dialog that will be used to confirm the payment of a receipt using this payment method, usually the dialogs listed in this field are included by payment gateway modules.
* '''Refund Provider''': Dialog that will be used to confirm the refund of a return order using this payment method, usually the dialogs listed in this field are included by payment gateway modules.
* '''Allow Open Drawer''': If checked, to paid, the cash drawer will be opened
* '''Open drawer before closing ticket''': If checked, when paying a ticket, new step will appear to open drawer before finish paying the ticket.
* '''Cash''': When checked indicates this payment method is a cash method and will show a coins and bank notes panel when selected. To configure a new coins and bank notes panel go the document [[Retail:Developers_Guide/How-to/How_to_create_a_new_coins_and_bank_notes_selector |How to create a new coins and bank notes selector]]. It also indicates that overpayments made with a ''cash'' method will be returned to the customer and the change to return to the customer will be calculated and displayed in the payment panel.
* '''Default Cash Payment Method''': only shown for a cash payment method, when there are multiple cash payment methods one of them can be flagged as the default cash payment method, is used for example when displaying the initial count view in the retail sessions module.
* '''Show coin keypad''': If the payment method is cash you can configure if you want to see the coin keypad checking this field to yes. If unchecked, the basic numeric pad will appear.
* '''Max. Limit Amount''' (Starting from RR15Q1): This amount limits the quantity of money you can use to pay a ticket for that payment method. For example if the tickets is 505€ and the limit for the cash payment method is 500 the system will show a message "The maximum limit (500 €) for this payment method has been exceeded. Payment not allowed"
* '''Overpayment Limit''' (Starting from RR15Q3)(Renamed to Overpayment / Change Limit in RR15Q4.2): This field is visible only for cash payment method that allows overpayment. If it contains a value, the amount of change that can be returned to a customer cannot be greater than the amount of this field, otherwise an error message will be shown to the cashier.
* '''Overpayment / Change Limit''' (Starting from RR15Q4.2): This field is visible for every payment methods and it is used to define the behavior regarding overpayments.
**If this field is empty, overpayments (change in case of payment method has been defined as cash) are allowed.
**If the value set in this field is 0, overpayments (change in case of payment method has been defined as cash) are not allowed.
**If the value set in this field is a number greater than 0, overpayments (change in case of payment method has been defined as cash) will be allowed if the amount of the overpayment (change in case of payment method has been defined as cash) is not greater than this value.
* '''Payment method Category''' (Starting from RR15Q2): This combo allows to group different payment methods in one category. This categorization means that when being in the payment panel instead of seeing all the payment methods the user will see just one. When clicking the button it will show the payment methods that belong to it
* '''Image''' (Starting from RR15Q2): This field makes sense when the payment methods is categorized, that is, when it belongs to a ''Payment Method Category''. When the popup gets opened it will show not only the name of the payment method but an image. Taping the image will select the payment

=====Cash Up =====
* '''Count Payment in Cash Up''': (Starting from RR17Q2) This flag allows to avoid counting a payment method in Cash Up flows. The payment methods that have this flag unchecked are not taken into account when doing a Cash Up in the Web POS, not being possible even to count them. If this flag is unchecked, the other fields that belongs to the '''Cash Up''' group are ignored (are hidden).
* '''Automate movement to Other''': If this field is selected, there will be an additional step during the cash up process for this payment method, which will allow the user to specify how much money should be kept in the main account, and how much will be moved to a secondary account (configured in the ''Cash Management Events'' tab of ''Organization'' window). Hence, if you select this, following checks need to be considered, which are the different options given to the user while cashing up for this payment method:
* '''Keep Fixed amount:''' A fixed amount will be kept in the financial account of the terminal
* '''Amount:''': The amount for the previous option
*'''Allow variable amount''': If checked, the user will be able to input an amount to keep in the financial account of the terminal
* '''Allow not to move''': If checked, the user will be able to keep everything in the financial account of the terminal, so not "moving" money
*'''Allow move everything:''' If checked, the user will be able to move all money to the destination financial account configured in the ''Cash Management Event''
* '''Cash differences''': This G/L Item is used if there are cash differences during cash up (theoretical amount different than the counted one). The created transaction will be associated with it. '''We strongly recommend using the name of the POS terminal and the Payment method for naming the G/Item in order to avoid problems with matching transactions and bank statements. Example: ''VBS Cash differences'''''
* '''Cash deposit/withdrawal''': This G/L Item is the one associated in the transaction added in the financial account in both terminal and backoffice after cash up processed is processed. So it is important a G/L Item is configured here. '''We strongly recommend using the name of the POS terminal and the Payment method for naming the G/Item in order to avoid problems with matching transactions and bank statements. Example: ''VBS Cash G/L Item for Cash up'''''
* '''Count Cash''': For payment methods marked as ''Cash'' indicates whether to show or not a cash count step in the cash up process to count the cash amount in the drawer with the help of currency denominations. To activate this option you must configure first ''Coins and Bank notes'' in the ''Currency'' window for the payment method currency.

=====Cash management=====
*'''Allow withdrawals''': If checked, withdrawals can be created associated with this payment method
*'''GLItem for withdrawals''': The G/L Item associated with the transactions created for withdrawals. '''We strongly recommend using the name of the POS terminal and the Payment method for naming the G/Item in order to avoid problems with matching transactions and bank statements. Example: ''VBS Cash withdrawal'''''
*'''Allow deposits''': If checked, deposits can be created associated with this payment method
*'''GLItem for deposits''': The G/L Item associated with the transactions created for deposits. '''We strongly recommend using the name of the POS terminal and the Payment method for naming the G/Item in order to avoid problems with matching transactions and bank statements. Example: ''VBS Cash differences'''''

=====Change Logic=====
{{(!)| This configuration will be available starting from RR19Q1}}
This section applies if [http://wiki.openbravo.com/wiki/Projects:Multicurrency_Change_&_Rounding/Technical_Functional_Guide Multi Change] is enabled
*'''Change less than''': Amount that has to be returned in another currency
*'''Change Payment''': Currency in which change has to be returned if amount is less than selected in "Change less than" field

{{(!)|Starting from '''RR15Q2''' below functionality is available }}

If ''Leave as Credit'' field is set to 'Y' that payment method wont take part on the CashUp process since it is not going to get paid. It won't also have a Financial Account associated.

[[Image:LeaveAsCredit.png|800px|thumb|center]]

==== Hardware URL ====

{{(!)|Starting from '''RR17Q1''' below functionality is available }}

In the tab Hardware URL you can configure a list of Hardware Manager (only for printer devices) to allow the cashier to select a different printer to use in the case he wants to or the current selected printer is not working for any reason. This list of Hardware URL addresses is shared by all the terminals with the same POS Terminal Type and it must be configured using the [[#Hardware Manager window | Hardware Manager window]].

[[Image:posterminaltypeprinters.png|800px|thumb|center]]

==== Terminal for Seller ====

{{AvailableFrom|3.0RR17Q3}}

From '''RR17Q3''', a new concept of terminal have been included. These terminals are '''Terminals for Sellers'''.

'''Terminals for Sellers''' are terminals distributed in different sections of a store. These terminals are only used to create ''layaways'', so are never used to directly buy or return products. An example may be a customer who is in a supermarket, in the fruits section. This customer chooses four apples and asks to a seller to create a layaway with those four apples, which will be paid to a vendor in a normal terminal.

To consider a terminal to be a '''Terminal for Seller''', the terminal needs to belong to a ''Pos Terminal Type'' with an specific configuration:
* The '''Layaway Orders''' field must be checked.
* The ''Pos Terminal Type'' may only contain payment methods that are not counted in the '''Cash Up''' process.
* The roles that are accessing to these terminals should have the ''Web POS action Receipt this Layaway'' property set to 'N'.

As commented before, a '''Terminal for Seller''' should never be used to pay tickets or return products. These terminals don't contain a drawer, so any operation related to a cash movement is not allowed. Due to this reason, '''Terminals for Sellers''' are not allowed to do ''Cash Ups'' or any operation available in the ''Cash Management'' window. The following functionalities are disabled here:
* '''Open Drawer'''
* '''Cash Up'''
* '''Cash Up Partial'''
* '''Cash Management'''
* '''Verified Returns''': The verified return menu entry is disabled, but is not also possible to do any type of return, because the new created tickets will always be layaways

As the ''Cash Up'', ''Cash Up Partial'' and ''Cash Management'' menu entries are disabled, if an user tries to navigate directly to any one of those pages directly by URL, a popup will appear telling that a '''Terminal for Seller''' cannot navigate to that URL.

''Payment methods not counted in the Cash Up process:''

Even if this type of terminal is not considered to work with payments, there are some flows that may need to get money back. Those flows are:
* '''Void Layaway'''
* '''Cancel Layaway'''
* '''Cancel and Replace''' removing products that were previously fully or partially paid

These three situations will be always managed using payment methods that are not counted in the cash up, so which won't need to have a drawer in the terminal.

If the Sessions module is used, Terminals for Sellers are also considered and their behavior particularly when the Store is closed changes a bit. You can find a bit more information [http://wiki.openbravo.com/wiki/Projects:POS_Terminal_Session_Management/User_Guide#Terminal_for_Seller_2 here]

===POS Terminal window===
In this window specific POS terminals can be added. Every POS terminal needs to be added here.

[[Image:PosTerminal.png|800px|thumb|center]]

In the header, the following fields are configured:
* '''Search key''': An identifier for this terminal, it must be unique and it is the one that is going to be used in the URL to access the terminal
* '''Name''': The name of the terminal
* '''Hardware URL''': The URL of the receipt printer, it will be given by the hardware manager, followed by /printer
* '''Scale URL''': The URL of the scale
* '''Order Document No PREFIX''': This prefix is used for the POS order documents generated in ''Sales Order'' window in the backoffice for each ticket of the POS terminal
* '''Order Quotation No Prefix''': This prefix is used for the document number of POS quotations generated in this POS terminal.
* '''POS Terminal type''': The Terminal Type which describes the configuration used by this POS terminal
* '''Default Tab for Web POS''': Ability to define whether the tab for selecting products is Scan (when scanning products is the main action) or the browse
* '''Default customer''': The customer can be configured at store level or at terminal level. In this case it is more restrictive so if it is filled then the system will use this customer instead
* '''Terminal Key Identifier''': When ''Terminal Authentication enabled'' preference is 'Y', this is the code for this POS Terminal configuration. Using for first time a physical device connecting to Web POS we will be able to link the device to this configuration using this code.
* '''Is linked to a physical device''': This field is checked when a physical device is linked to this POS Terminal configuration using Terminal Authentication security.
* '''Unlink device''': This process button allow us to unlink the actual physical device from this configuration. We could lose data not synchronized in the ERP (terminal is offline and exists data to send to the ERP), we need to be sure of this action.
* '''Cache Session Id''': This read only field shows the id which identifies the current cache session id. This id must match with terminal cache session id to allow login.
{{(!)|Starting from '''RR16Q3''' below functionality is available }}
* '''Return No Prefix''': This prefix is used for the document number of POS returns generated in this POS terminal. It's not mandatory, and if it's not set, then return documents will share the sequence with normal sales orders.

[[Image:PaymentCash.png|800px|thumb|center]]

In the payment type, the following information is configured:

* '''Search key''': It is an identifier string for the payment method.
* '''Name''': The name of the payment method
* '''Payment method''': The payment method type defined in the POS Terminal Type, which contains the configuration information for this payment method
* '''Financial account''': The financial account associated with this payment '''''Very important: The financial account must be associated only with this payment. It should not be used in operations generated in backoffice, only transacctions generated in the terminal should be deposited. The Organization of the Financial Account, must be in the Org Access list of the User Role (Only in the Cash Up process)'' '''. POS processes will not work correctly otherwise. (Starting from RR17Q2) The payment methods are not automatically deposited in the financial account. Instead, the '''Automatic Deposit''' field that belongs to the '''Payment Method''' tab in the '''Financial Account''' window is checked to do or not the deposit automatically
* '''Cash management close event''': The cash management close event which should be used when executing the cash up process

'''Very important. Payment methods are secured by Search key value in Role preferences'''. There are three predefined values: ''OBPOS_payment.cash'' for cash payments. ''OBPOS_payment.cash'' payment method is also used to calculate cash change in the payment panel. ''OBPOS_payment.card'' for card payments and ''OBPOS_payment.voucher'' for voucher payments. If you need to add new payments with different ''Search key'' values you need to secure them in order to allow users to use the new payments you create. To do this, as ''System Administrator'' you need to go to the window ''References'', in this window search the record with name ''Property Configuration'' and in the tab ''List Reference'' add a new record with the same Search key as the new payment you need to add. This new record should belong to your own module which should be dependent from the Web POS module. Once it is created you will be able to assign permissions to this new payment in the ''Preferences'' window.

'''Note'''. The search key field in the tab ''List Reference'' must start with the DB prefix of the module you are creating this value, but the search key of the payment method does not need to start with any prefix, so for example if the search key in ''List Reference'' is ''OBPOS_payment.mypayment'' the search key in the payment method to secure can be ''OBPOS_payment.mypayment'' or ''payment.mypayment''.

'''Note'''. When a ticket is created within Web POS, the information related to the payments of this order is stored in Sales Order > Payment plan > payment details

'''Note'''. Do not add payment types if this posterminal has an open cashup. This window is to define configurations before start working in Web POS, if you change the configuration while the terminal is operating you could have errors in the terminal or data inconsistency.

[[Image:cashUpHistory.png|800px|thumb|center]]

In the cash up history, the following information is configured:

* '''Organization''': It is store of the POS Terminal.
* '''User/Contact''': The name of the user who did the cash up.
* '''Cashupdate''': The date when the cash up was done.
* '''Cash Up Report''': This process button, create a pdf report with all the information about the cash up.

In the reconciliation subtab, the following information is configured:

* '''Payment type''': It is payment type which is related to the financial account of the reconciliation.
* '''Reconciliation''': The reconciliation itself.

{{(!)|The functionality described below is available starting from '''15RRQ2'''}}
* '''Override POS Terminal Type Configuration:''' this flag allows to override the configuration of the cash up defined in the POS terminal type – Payment Method.
** '''Automate movement to Other: '''If this field is selected, there will be an additional step during the cash up process for this payment type, which will allow the user to specify how much money should be kept in the main account, and how much will be moved to a secondary account (configured in the Cash Management Events tab of Organization window). Hence, if you select this, following checks need to be considered, which are the different options given to the user while cashing up for this payment method:
** '''Keep Fixed amount: '''A fixed amount will be kept in the financial account of the terminal
** '''Amount: '''The amount for the previous option
** '''Allow variable amount: '''If checked, the user will be able to input an amount to keep in the financial account of the terminal
** '''Allow not to move: '''If checked, the user will be able to keep everything in the financial account of the terminal, so not "moving" money
** '''Allow move everything: '''If checked, the user will be able to move all money to the destination financial account configured in the Cash Management Event
** '''Cash differences: '''This G/L Item is used if there are cash differences during cash up (theoretical amount different than the counted one). The created transaction will be associated with it. '''We strongly recommend using the name of the POS terminal and the Payment method for naming the G/Item in order to avoid problems with matching transactions and bank statements. Example: VBS Cash differences'''
** '''Cash deposit/withdrawal: '''This G/L Item is the one associated in the transaction added in the financial account in both terminal and backoffice after cash up processed is processed. So it is important a G/L Item is configured here. '''We strongly recommend using the name of the POS terminal and the Payment method for naming the G/Item in order to avoid problems with matching transactions and bank statements. Example: VBS Cash G/L Item for Cash up'''
** '''Count Cash: '''For payment type marked as Cash indicates whether to show or not a cash count step in the cash up process to count the cash amount in the drawer with the help of currency denominations. To activate this option you must configure first Coins and Bank notes in the Currency window for the payment type currency.

[[Image:overridePOSTerminalConfiguration.png|800px|thumb|center]]

{{(!)|Starting from '''RR15Q4''' below functionality is available}}

In POS Terminal window you can define a hierarchy of terminals in order to allow to share any payment method you have accross terminals of the same organization.
e.g.- There are 4 terminals in an store but you have only one pinpad.

[[Image:TerminalHierarchyMaster.png|800px|thumb|center]]

More than two levels of hierarchy are not supported. This means that a “master” terminal cannot be slave of any terminal.

[[Image:TerminalHierarchySlave.png|800px|thumb|center]]

A POS terminal can use both standard payment methods and shared payment methods at the same time.

When a POS terminal is defined in the backoffice, another terminal can be specified as its “master”. When this is done, two important changes happen in the POS operation:
* Shared payment methods can be defined. Shared payment methods will not appear in the “slave” terminals when doing the cash up, and will only appear in the “master” terminal. Standard payment methods will appear normally in the cash up of each terminal.
* The cash ups for the “slave” terminals must be done before the cash up in the “master” terminal can be done. The cash ups in the “slave” terminals will not have any real consequence in the backend other than enabling the cash up in the master terminal. The invoices and reconciliations for the payments generated in all the terminals will be created only when the cash up in the “master” terminal is done.
* The Shared Payment Type from the same Payment methods needs to have the same Financial Account associated.

[[Image:PaymentMethodShared.png|800px|thumb|center]]

{{(!)|The functionality described below is available starting from '''RR17Q2'''}}

** '''Refundable: '''For payment type marked as Refundable it will be possible to refund to the Customer on that Payment Method. In the case it is unmarked it will not be possible to add a negative payment with that Payment Method from WebPOS.

** '''Show-Hide Taxes: '''A new button called show Tax Breakdown has been added in the POS Terminal Type screen to show or hide taxes in Web POS.
====Terminal status====

{{(!)|Starting from '''RR18Q2''' below functionality is available}}
Through the terminal window, it is also possible to monitor some key metrics and facts of each terminal in the system.

The information is shown in terminal window header and it is grouped in Terminal Status section.

The user could monitor the following information in Terminal Status section

* Last Full Masterdata Load
** Datetime field with the information of the last time current terminal has completed successfully a full refresh of masterdata. For more information, refer to [http://wiki.openbravo.com/wiki/Retail:Configuration_Guide#POS_Terminal_Type_window Time to fully refresh masterdata section].
* Last Incremental Masterdata Load
** Datetime field with the information of the last time current terminal has completed successfully an incremental refresh of masterdata. [http://wiki.openbravo.com/wiki/Retail:Configuration_Guide#POS_Terminal_Type_window Time to incrementally refresh masterdata section].
* Last Cache Generation
** Datetime field with the information of the last time current terminal has generate cache data. For more information, refer to [http://wiki.openbravo.com/wiki/Retail:Web_POS_User_Guide#The_local_database:_how_the_Web_POS_uses_it_and_when_it.27s_safe_to_clear_the_browser_cache WebPOS cache section].
* Last JS Generation
** Datetime field with the information of the last time current terminal has upload of WebPOS js file. For more information, refer to [http://wiki.openbravo.com/wiki/Openbravo_3_Architecture#ETags.2C_Caching_and_Compressing caching and compression section].

[[Image:Terminal_status.png|800px|thumb|center]]

=====Terminal status extension=====
{{(!)|Starting from '''RR18Q4''' below functionality is available}}
As an extension of previous terminal status values user can monitor, now it is possible to monitor more in detail the current status of a terminal from POS Terminal Window

The information, as before, is shown in POS Terminal window header and it is grouped in Terminal Status section.

The user could monitor the following new information in Terminal Status section

* Last Log In Date
** Datetime field with the information of the last time a user logs in the specific terminal.
* Last Log In User
** Reference field with the information of the last user logged in the terminal.
* Last Performance Check Score
** Score of the last benchmark done in the terminal, refer to [http://wiki.openbravo.com/wiki/Retail:PerformanceTesting POS Terminal Performance Testing].
* Last Synchronized Order
** Datetime field with the information of the last sales order/layaway synchronized to the ERP from the terminal.
* Last Completed Cashup
** Datetime field with the information of the last processed cashup done in the terminal.
* Last Loaded Ticket
** Datetime field with the information of the last completed sales order loaded in the terminal.
* Last Transition To Offline
** Datetime field with the information of the last time the terminal goes offline ('''this information is updated once the terminal goes online again'''), refer to [http://wiki.openbravo.com/wiki/Retail:Web_POS_User_Guide#Offline_Operations Terminal Offline mode].
* Last Transition to Online
** Datetime field with the information of the last time the terminal goes back online.

[[Image:Terminal_status_ext.png|800px|thumb|center]]

In addition, a new sub tab has been created in POS Terminal window called "Terminal Status History".

Terminal Status History records are created once the cash up is synchronized with the ERP and are updated until the current cash up is processed in WebPOS.

The information the user could monitor is

* Cash Up
** The cash up related with this monitor process.
* Number Of Transitions to Online
** Number of times the terminal switches from offline mode to online mode during this cash up.
* Number Of Logclient Errors
** Number of logclient error registered during this cash up.
* Number Of Errors While Importing POS Data
** Number of records in Errors While Importing POS Data registered during this cash up.

[[Image:Terminal_status_ext_history.png|800px|thumb|center]]

===Configuring for performance===
Several settings have consequences for the performance of Web POS in the backend operations: creating orders, invoices and doing cashups. This section gives an overview of some settings.

====Group orders in one invoice - Cashup Performance====
In the POS Terminal Type you can check the group orders in one invoice. If this flag is not checked then each ticket in Web POS will result in a separate invoice in the backend. These invoices are created when doing the cashup.

If shops close at the same time and several shops do the cashup at the same time this can result in the cashups of different shops waiting for each other as they might share the same document sequences for invoices. See the next subsection on document sequences for more information.

In general it is fine/best to check the group orders in one invoice flag. This results in better cashup performance, smaller database sizes and most of the time no separate invoice is needed as there is already a printed ticket for the customer.

====Generate invoice for orders====
Another setting in the POS Terminal Type specifies if a separate invoice should be generated for each order/ticket when the ticket is created. This results in a slighly slower ticket creation in the backend. The Web POS user does not notice this as the backend ticket creation does not block the Web POS user interface. But having a separate invoice for each ticket will result in much more data in the database and more load on the server.

So the advice is to only check this option if it is really needed and in all other cases keep it unchecked.

====Document Type and Sequence Numbers - (Cashup) Performance Consequences====

The document type defines the document sequence which is being used for orders and also defines the document types for invoices and other business documents.

[[Image:POSTerminalTypeDocSequence.png|800px|thumb|center]]

When creating new orders, shipments and invoices the system uses the document sequence to generate a new document number for the business document (order/invoice/shipment). Document numbers need to be unique and also need to be incremented correctly. To ensure this the system will lock the database while creating business documents. If different POS terminals share the same document sequence for a business document then POS actions of these terminals will sometimes wait on eachother (at database level) when new document sequence numbers are created. Especially with large cashups this can result in longer processing times.

'''Therefore the advice is to let different POS Terminals use different document sequences, especially in high volume environments.''' This means that different POS terminals will have to make use of different POS Terminal Types.

====Querying performance====
{{(!)|Starting from '''RR16Q1''' below functionality is available }}
Sometimes we could suffer performance problems when we are searching something in Web POS and it takes time to render all the items or when we have an environment with high volumes. Because of that, we can set this three preference (''Searching in WebPOS limit value for Products, Searching in WebPOS limit value for Customers and Searching in WebPOS limit value for Orders''). We have to put the number of items we would like to show in a search. By default this value is 300, in case you want to show less items, set preferences with your selected value. This feature is available searching Products, Customers and also Orders(Paid orders, layaways, quotations...).

===Synchronized order===

Enabling ''Synchronized Request Order'' we will enable this functionality. From 16Q2.

This functionality makes the transaction be processed on the server completely synchronously. So the WebPOS user interface wait for the confirmation that the record has been successfully processed on one of the servers before it can proceed.
If an error occurs the ticket is not saved on the server and a message is sent to the WebPOS client to show the error.

=== Hardware Manager window ===

{{(!)|Starting from '''RR17Q1''' below functionality is available }}

This window defines the list of Hardware Manager URLs with configured printers that are available for assigning to POS Terminal Types.

See [[#Hardware_URL | Hardware URL ]] for configuring Hardware Managers for each Terminal Type.

For each Hardware Manager record you have to configure the following fields:

* '''Name''': The name that will appear in the dialog to select printer.
* '''Hardware UR'''L: The URL where the Hardware Manager is located. It must be the root location of the Hardware Manager web server.
* '''Has Receipt Printer''': Indicates if the printer can be selected to print receipts.
* '''Has PDF Printer''': Indicates if the printer can be selected to print PDF documents like service documents.
* '''Active''': Indicates whether the printer is active or not.

[[Image:hardwaremanagerwindow.png|800px|thumb|center]]

=== Offline Mode ===

The WebPOS supports offline operation. One of the most important parts of the support for offline operation is being able to save the application sources in a persisted state, so that if the connection is not available, the application can nonetheless be started correctly.

In previous versions of the application, we used the [https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache Application Cache technology] to persist the application sources. This is still supported in current versions, and we expect to keep it for some time. However, starting from '''RR18Q3''' we now also support the persisting of application sources using [https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API Service Workers]. Service Workers are the preferred way to persist the sources nowadays, because they are more flexible and they give greater control to the developer of which resources he wants to cache, and how to manage this cache. However, they are not yet fully available in all browsers, which is the main reason why we are keeping the support for Application Cache as of now.

{{(!)|Starting from '''RR18Q3''' Service Workers are enabled by default. Remember that we need to use HTTPS to make it work properly}}

However, as previously explained, it is possible to switch between Service Workers and Application Cache using the preference "Web POS Use Service Workers for Offline Support". This is a system-admin preference which must be defined using System Administrator role, and only once per system. If it's set to 'Y' (or if it doesn't exist) then Service Workers are enabled, otherwise Application Cache will be used instead.

{{(!)|Starting from '''18Q4''' It is possible to restrict the amount of time the terminal can remain in offline mode}}

This can be configured with the "Web POS Maximum time which the terminal can be offline" preference.

{{(!)|Starting from '''18Q4''' Offline mode has changed slightly, and now it doesn't necessarily require authentication}}

You can use the "Web POS Offline session time expiration" preference to specify how much time will the WebPOS consider a session still valid while being offline. This will slightly change the way the POS behaves is the user refreshes the application while being offline: before, it would always ask for the user to enter credentials to continue, and now it will only ask him to do so if the session is no longer considered valid.

== Security Settings ==
[[Image:windowaccess.png|thumbnail|right|150px|View larger]]
Not every user is supposed to have access to Web POS and not every Web POS user is supposed to have access to Cash Up and Cash Management. You can set access to these windows in the back office as follows.

'''Enabling a role to access Web POS:'''
*Go to the Role window in the back office (''General Setup > Security > Role'')
*Select the role you want to grant access to Web POS to
*Go to the child tab called ''Form Access''
*If it does not exist yet, create a new record and set the ''Special Form'' field to ''Web POS''.
*Save and reload the Web POS for the changes to take effect

'''Setting access to specific functionality:'''

Note roles defined as ''Automatic'' ([[Role#Role|''Manual'']] field is unchecked) have access to all functionality regardless preferences.

*Go to the Preference window in the back office (''General Setup > Application > Preference'')
*Create a new record and select the functionality in the ''Property'' field. For example ''order.discount'' or ''Web POS window Cash Up''.
*Set the value to ''Y'' in the value field to enable access.
*Set the desired visibility in the Visibility section below.
*Save and reload the Web POS for the changes to take effect

The following functionalities are relevant for Web POS users:
*Changing price (''Web POS action Change price'', by default revoked)
*Giving discount (''Web POS action Apply discount'', by default revoked)
*Invoice receipt (''Web POS action Invoice receipt'', by default granted)
*Return receipt (''Web POS action Return receipt'', by default granted)
*Print report in Cash Up (''Web POS action Print cash up'', by default granted)
*Print report in Cash Management (''Web POS action Print cash management'', by default granted)
*Print receipt menu action (''Web POS action Print receipt'', by default revoked)
*Reject a quotation from the menu ('Web POS Quotation rejections', by default granted, available from 3.0RR15Q4)
*Using payment type card (''Web POS payment Card'', by default granted)
*Using payment type cash (''Web POS payment Cash'', by default granted)
*Using payment type voucher (''Web POS payment Voucher'', by default granted)
*Accessing Cash Management (''Web POS window Cash management'', by default revoked)
*Accessing Cash Up (''Web POS window Cash Up'', by default revoked)
*Accessing Point of Sale (''Web POS window Point of Sale'', by default granted)
*Accessing Back Office (''Web POS Back Office'', by default granted)
*Creating [[Retail:Discounts_and_Promotions_Rules#Discretionary_Discounts|Discretionary Discounts]] (''Web POS action Advanced Discounts'', by default granted; together with ''Web POS action Apply discount'')
*Editing ''Firm Quotation'' check when creating order from Quotation (''Web POS Quotation: Editable Firm Check'', default granted, available from RMP27)
*Change profile settings (''Mobile Change Profile'', by default granted, available from RMP30). Allows to change profile settings (role and language)
*Sales with Returns (''Do not allow Sales with return'', by default revoked)
*Switch from positive to return line ('Web POS Show Action Button Return'', by default granted)
*Multi Order (''Web POS Enable Multi Order menu entry'', by default granted)
*Receipt Discounts from Keyboard (''Web POS Open Discounts From Keyboard'', by default granted, available from RMP28)
*Open Drawer button (''Web POS Open drawer from menu'', by default granted, available from RMP29)
*Select a specific warehouse to consume the goods for a specific order line (''Allow to select a warehouse for a specific line order''), by default revoked.
*Enable the functionality to split in shipment lines, lines from orders to be returned. (''Split Lines in Shipments when Returning'', by default disabled, available from RR15Q2)
*Save removed tickets or ticket lines in the backend when the user chooses to delete (Web POS Save Removed Tickets, by default revoked).
*Enable the functionality to have layaways with negative lines if there are no partial payments. (''Allow layaways with negative lines'', by default disabled, available from RR18Q2)

The following functionalities are related to Quotations:
*Create Quotation (''Web POS action create new quotation'', by default revoked)
*Sales Order from Quotation (''Web POS action create sales order from quotation, by default revoked)
*Reactivate Quotation (''Web POS action reactivate quotation'', by default revoked)
*Show Quotation (''Web POS action show quotations'', by default revoked)

Note that access to Cash Up and Cash Management will be disabled by default for new roles.

When the user has no access to specific menu entries these ones will be hidden in the menu

'''Enabling specific terminals for users:'''

Starting Openbravo for Retail RMP20, specific users can be given access to specific POS terminals. This is done through the '''POS Terminal Access''' tab in the '''User''' window.

[[Image:terminalaccess.png|thumbnail|right|150px|View larger]]

The following rules are followed to decide whether a user has access to a terminal or not:
* If a user doesn't have entries in the POS Terminal Access tab, then it can log in all the available POS Terminals (provided that it has access to a role with access to the Web POS form).
* If a user has entries in the POS Terminal Access tab, then it can only access the terminals specified there.

{{(!)|Starting from '''RR17Q4''' below functionality is available }}
Several preferences have been created to be able to show or hide the action buttons related to the products in the order. The default value is to show them.
Some examples of the preferences:
* Web POS Show Action Button Check Stock
* Web POS Show Action Button Delete
* Web POS Show Action Button Description
* Web POS Show Action Button Remove Discount
* Web POS Show Action Button Return
* Web POS Show Action Button Show Related Services
* Web POS Show Action Button Split

=== Approvals ===

{{(!)|This feature is available starting from '''RMP26'''}}

Some actions require of supervisor's approval in order to be accomplished.

When an action requiring of approval is performed a pop up requesting supervisor's credentials is shown and it is not possible to continue till these credentials are provided or the approval is cancelled aborting the action in this way.

In case the user launching the action is a supervisor, no approval is requested to complete it.

==== Supervisor ====

Each action requiring approval can have its own supervisors, thus it is possible for a user to be supervisor of action A but not action's B supervisor.

Each Approvable Action require of a different preference to be set:
* "Approvable Action" Preference with value N at client level. In order to show Approval Modal.
* "Approvable Action" Preference with value Y at user's or role level. In order to give access to this action.

Note that, as opposite as the other security preferences, supervisor preferences require of explicit setting, this means automatic roles are not considered as supervisor unless there is a preference defining it.

====== Approvable Actions ======

Here is the list of actions that can require approval:

* When pressing Total toolbar button, approve Discretionary Discounts. Property '''Web POS Discretionary Discount Approval''' (''OBPOS_approval.discounts''). More information about this action can be found [[Retail:Discounts_and_Promotions_Rules#Approvable_Discounts|here]].
* Open Cash Management window. Property '''Web POS Cash Management window approval''' (''OBPOS_approval.cashmgmt'').
* Open Cash Up window. Property '''Web POS Cash Up window approval''' (''OBPOS_approval.cashup'').
* Open Cash Drawer in Cash Up window. Property '''Web POS Open Drawer approval Cash Up''' (''OBPOS_approval.opendrawer.cashup'').
* Open Cash Drawer in Point of Sale window. Property '''Web POS Open Drawer approval Menu''' (''OBPOS_approval.opendrawer.menu'').
* Remove suspended orders in Cash Up(Step 1) window. Property '''Web POS Remove Receipts Approval in Cash Up''' (''OBPOS_approval.cashupremovereceipts'').
* Remove receipts with Delete button or Loging out. Property '''Web POS Remove Receipts Approval''' (''OBPOS_approval.removereceipts'').
* Remove an order line. Property '''Web POS Delete Line Approval''' (''OBPOS_approval.deleteLine'').
* When pressing Total toolbar button, approve return lines. Property '''Web POS Returns Approval''' (''OBPOS_approval.returns'').
* Set price of a product in a line. Property '''Web POS set Price approval''' (''OBPOS_approval.setPrice'').
* Approve difference between Expected and Counted cash. Property '''Web POS Cash Up Differences Approval''' (''OBPOS_approval.cashupdifferences'').
* Approve menu opening. Property '''Open Menu Approval''' (''OBMOBC_approval.openMenu''). From 17Q2

==== Audit Information ====

Whenever an action is approved by a supervisor, the Sales Order created in the back office keeps track of the supervisor's user as well as the action she approved.

This information can be seen in the ''Approvals'' read only sub tab in ''Sales Order'' window.

==== Offline ====

Approvals can be granted in offline mode. In order to approve an action being in this mode, it is required that the user that has granted to that action has logged in at least one time being online in the terminal

=== Terminal Authentication Security ===

'''A fundamental WebPOS mandatory rule is not to access the same POS Terminal from two or more devices / web browser instances. For the same reason, it is not allowed to access from the same web browser instance to two or more terminals.''' To help avoid this, Openbravo have created the Enhanced Security Authentication.

Starting from RR16Q1 this functionality will be enabled by default thanks to the preference ''Terminal Authentication enabled''.

If someone wants to overwrite the value of the main preference, a new preference for the same property should be created. The value of that new preference will override the value of the original one.

Take into account that this preference should be created for the affected client and it should be visible for Organization "*"

[[File:Term_authentication_preference.jpg|1000px|center]]

Remember that if terminal authentication is enabled, every terminals will share the same URL and then a specific terminal will be linked.
* ''Terminal Authentication enabled'' is 'Y': Access url --> openbravo/web/org.openbravo.retail.posterminal/

If security is not enabled we need to put the terminal searchKey in the URL.
* ''Terminal Authentication enabled'' is 'N': Access url --> openbravo/web/org.openbravo.retail.posterminal/'''?terminal=VBS-1'''

{{(!)|When a new device is used in a terminal, it is '''very important''' to '''clean the browser cache''' in the new device, to prevent corruption data.}}

=== Other Settings ===

The following preferences can be also set.

* ''Quotations are not Firm by default''. When creating an order from a quotation, by default ''Firm'' is checked unless this preference is set to Y.

== Web POS Locale Settings ==

=== Language ===

UI language in Web POS works in a similar way as in ERP: it is defined per session and can be changed, while being online, from ''User > Profile'' dialog.

{{(!)|Topics covered in this section below this line are available starting from '''RMP31'''}}

It is possible to define a default language for Web POS at role level, this default language will be set to user when the role is set as default for Web POS. Additionally it a user can be restricted not to change her defaults by using the ''[[#Security_Settings|Change Profile Settings]]'' preference.

Business Objects such as Product, Product Categories, Taxes, Promotions and Discounts, etc. Are also translated to the same language the UI is set to.

=== Formats ===

==== Date and Numeric ====

Numeric and date formats in Web POS are [[How_to_personalize_Openbravo#Changing_Decimal_Separator | defaulted to the same that in backoffice]].

{{(!)|Topics covered in this section below this line are available starting from '''RMP31'''}}

Starting from ''RMP31'' these formats can be set different to the default ones at Store, Group of Stores or Group of Organization levels. It will be used the most specific one, for example having this Organization tree:

Formats in ''Format.xml'':
date: dd/MM/yyyy
numeric: "." decimal, "," for thousand grouping

Organizations/Stores definition:
*
|- Group 1 (defined date format: MM-dd-yyyy)
| |- Store 1.1
| |- Store 1.2 (defined numeric format: "," decimal, "." for thousand grouping)
|- Group 2 (defined numeric format: "," decimal, "." for thousand grouping)
|- Store 2.1
|- Store 2.2 (defined numeric format: "." decimal, "," for thousand grouping)

The format that would be used in each of the stores would be:
{|border="1"
!Store
!Date Format
!Numeric format (decimal/thousands separator)
|-
|Store 1.1
|MM-dd-yyyy (taken from Group 1)
|./, (taken from Format.xml)
|-
|Store 1.2
|MM-dd-yyyy (taken from Group 1)
|,/. (taken from Store 1.2)
|-
|Store 2.1
|dd/MM/yyyy (taken Format.xml)
|,/. (taken from Group 2)
|-
|Store 2.2
|dd/MM/yyyy (taken Format.xml)
|./, (taken from Store 2.2)
|}

These settings can be configured in ''Organization'' window:

[[Image:WebPOSFormat.png|center|600px]]

Currency Format in Web POS is the same that in backoffice.
It will be used to change the decimals of currency , by default it will be #,##0.00 , the same that priceInform in Format.xml.

{{(!)|Topics covered in this section below this line are available starting from '''3.0RR17Q2'''}}

Starting from ''3.0RR17Q2'' this format can be set different to the default one at #,##0.0 and #,##0.

The value of this field is defined in priceInform in Format.xml.

Formats in ''Format.xml'':
<Number name="priceInform"
decimal="." grouping="," formatOutput="#,##0.00" formatInternal="#0.00"/>

Organizations/Stores definition:
*
|- Group 1 (defined currency format: #,##0)
|- Store 1.1
|- Group 2 (defined currency format: #,##0.0)
|- Store 2.1
|- Group 3 (defined currency format: #,##0.00)
|- Store 3.1

The format that would be used in each of the stores would be:

{|border="1"
!Store
!Currency Format
|-
|Store 1.1
|#,##0
|-
|Store 2.1
|#,##0.0
|-
|Store 3.1
|#,##0.00
|}

These settings can be configured in ''Organization'' window

==== Print Templates ====

Print templates are used to print different reports from Web POS. Default ones can be [[Retail:Developers_Guide/How-to/How_to_create_and_modify_new_receipt_documents_from_other_module|overwritten by others provided by external modules]].

{{(!)|Topics covered in this section below this line are available starting from '''RMP31'''}}

In the same way it is possible to change date and numeric formats at Store/Organization level, templates can be defined at those levels. They are set in ''Organization'' window in Web POS Formats field section. Precedence of these settings works in the same way as described in previous section.

== Do not clean the browser cache - Updating the Client Web POS ==

In normal operations the client side application is automatically updated when updating Web POS modules on the server. However in some cases it makes sense to refresh the client side application explicitly.

One way of refreshing the Openbravo Web POS client is to clean the cache. Then when refreshing the page the Web POS is reloaded from the server. '''But as is noted [[Retail:Web_POS_User_Guide#The_local_database:_how_the_Web_POS_uses_it_and_when_it.27s_safe_to_clear_the_browser_cache|here]] one should be really careful with cleaning the cache during business operations'''.

Therefore this section describes a method which allows you to update the client side application without cleaning the cache.

# In the browser with Web POS go to the following URL: chrome://appcache-internals/
# Find the manifest with the url of the Web POS (most likely there is the only one manifest, see below)
# Press on Remove option for this manifest.
# Close the page, close the browser.
# Start the browser, start the Web POS by going to the original WebPOS URL.

[[Image:WebPOSCleanAppcache.png|center]]

== Hide Cash Up Information to the Cashier ==

{{(!)|Starting from '''RR16Q4''' below functionality is available }}

Since 3.0RR16Q4, it has been implemented a new property configurable from the Preference window named OBPOS_HideCashUpInfoToCashier. This preference allow to hide some critical information to the user in the cash up part.

Follow this [http://wiki.openbravo.com/wiki/Retail:Web_POS_User_Guide#Hide_Cash_Up_Information_to_the_Cashier link] to learn more about this new functionality.

== Configuring Web POS Import Transaction Process ==

{{(!)|Starting from '''RR15Q3''' below functionality is available }}

From the 2015Q3 version of Openbravo Retail transactions which are sent through the server are imported by a separate [[Retail:Web_POS_User_Guide#Backend_Data_Processing:_Data_Import_Entries|process]] using parallel processing. The benefit of this approach is that it makes the Openbravo Retail solution much more stable in very high volume environments (1000 tickets/minute).

The import process will try to process transactions in parallel:
* tickets of different organizations are processed in parallel
* cashups of different organizations are processed in parallel
* business partners of different organizations are processed in parallel

So if there 10 stores, and in each store there are POS systems submitting tickets/cashups and business partners, there will be a total of 30 processes started. They are executed in parallel if there are CPU-processors available.

The parallel processing and even the disabling of this new import process can be controlled through several configuration parameters which can be defined in [[Openbravo.properties|Openbravo.properties]]:

* '''import.disable.process''' (available from RR16Q1 release): default not set/false, if set to true then the import process will not run on this application server, is useful if multiple servers share the same database. In that case only server should be dedicated to process import entries, the one's should have this property set to false.
* '''import.bypass.entry.logic''': default not set/false, if set to the value true then the import framework is not used and requests from WebPOS are processed directly.
* '''import.batch.size''': default is 5000, minimum is 1000, defines the number of import entries read by type of data (Order, Cashup etc.) in each loop of the import process. This can be set to 10000 or 20000 if the server has 16GB of memory or more and there are 8 or 16 processors.
* '''import.number.of.threads''': default is number of processors plus 2, minimum: 4, the number of threads available for the main import thread, archiving thread and the actual processors importing data. It depends on the number of cores in the system and also how many parallel processes are expected. A good value is the number of processor cores in the system (plus 2).
* '''import.max.task.queue.size''': default is 1000, minimum: 50, the number of separate import tasks which are queued, the number of tasks depend on the type of data, the implementation of the data importer, for example in WebPOS there will be a separate order importer for each organization, the same for cashups and business partner imports. If there memory limits and a lot of different stores then this value should be set to a lower value, for example 100.
* '''import.wait.time''': (available from 17Q1), defined in seconds, default is 600 seconds, when there are no actions which trigger an import entry loop the system will wait a specific amount of time before automatically triggerin a read of any current 'Initial' entries. This property defines the wait time between runs/loops of the import entry logic when no other actions happen.

=== Import Entry High Availability ===

{{AvailableFrom|3.0PR18Q2}}

Before '''3.0PR18Q2''' release when working in a clustered environment, it was only supported to run the import process in the same (one) node of the cluster. This was done by setting the '''[http://wiki.openbravo.com/wiki/Retail:Configuration_Guide#Configuring_Web_POS_Import_Transaction_Process import.disable.process]''' property as ''true'' for that node.

Starting from '''3.0PR18Q2''' it is possible to configure the import entry processing as a high available service for the cluster. This means, that in case the node in charge of handling the service fails, eventually another available node of the cluster will take care of processing the import entries, replacing the node that failed.

To enable this feature two properties have to be configured in the [[Openbravo.properties|Openbravo.properties]] file of '''[http://wiki.openbravo.com/wiki/Openbravo.properties#Overriding_properties_per_instance each cluster node]''':

* '''cluster''': defined as '''true''' in all the nodes.
* '''import.disable.process''': defined as '''false''' (or not defined) in every node which it is desired to enable as available for executing the import process.

==== Import Entry Cluster Service Settings ====

Once this feature is enabled, by default, each node in the cluster will check (ping) every 10 seconds if the node in charge of executing the import process is still "alive" or, on the other hand, if it should be replaced with another node of the cluster.

It is possible to change this default time to use a custom value by using the '''Cluster Service Settings''' window.

[[Image:ClusterServiceSettings.png|center|600px]]

In this window a new record should be created with the following values:

* '''Cluster Service''': ''Import Entry Cluster Service''
* '''Timeout (seconds)''': the amount of seconds of the ''ping'' interval

{{(!)|After establishing the new configuration in this window, it will be required to restart every cluster node.}}

==== Cluster Service Management Extension (JMX) ====

This feature also provides a management extension available through [http://wiki.openbravo.com/wiki/Retail:Monitoring_and_Management JMX]. This extension provides:

* The ability of monitoring the status of the import entries service. It is possible to check, for instance, the current cluster node in charge of handling the import entries.

* The ability of disabling the ping service. In case the ping is disabled for the node in charge of handling the import entries service, that node will be automatically deregistered, allowing to promote another node in the cluster to be the responsible of processing the import entries.

== Web POS Multi-Server Architecture ==

{{(!)|Starting from '''RR15Q4''' you can configure a WebPOS client to operate in a multi-server system architecture. As of now, this functionality is only available in the [[Modules_Management#Maturity_Status_in_ERP | QAA maturity status]]. So if you want to try it we recommend to use the latest available at this point QAA release and to get in touch with Openbravo.}}

In the RR15Q4 release the Openbravo Commerce suite takes a first step in allowing a WebPOS client to communicate to multiple servers. The first target architecture to support with this approach consists of store servers and one central server.

The store and central server architecture is described in more detail in the next section. The services and server architecture are defined in the back office system using several windows. These are described in the subsections below.

=== Store and Central Server ===

Openbravo Commerce Suite can be deployed in environments in which stores can run a store server instance locally next to a central server instance hosted in the cloud.

A store server installed locally in the store can provide several benefits:
* in case of [[Retail:Configuration_Guide#Supporting_High_Volume_Master_Data:_Remote_Master_Data_Handling|large master data volumes]], these can be loaded in the store server, WebPOS clients can then load (on-demand) the master data from the store server. This ensures operation of the store in case of high master data volumes in combination with offline situations
* performance and robustness in case of lesser-bandwith internet connections to the store. A store server helps to handle many requests from WebPOS clients on the local network instead of making use of the internet connection of the store.
* many WebPOS clients in a store: when there are many WebPOS clients in a store (hunderds or more) then it can make sense to let the WebPOS clients login on a dedicated store server to balance the load across several servers in the network.

The current solution supports the following architecture:
* One central server instance
* One or more store server instances: one store can only work with one store server, but one store server can handle/operate for multiple stores.

The illustration below demonstrates a possible architecture with store servers hosted in the stores and a central server hosted in the cloud.

[[Image:Multi-Server-Example-Store-Central-Server.png|center|600px]]

For backend replication between servers in the network we have good experience with [http://www.symmetricds.org/ Symmetric DS]. For replication of transactions one can focus on replicating the [[Retail:Web_POS_User_Guide#Backend_Data_Processing:_Data_Import_Entries|data import entries]]. '''The SymmetricDS setup and replication logic for store and central servers will be delivered in a separate module and is targeted for the 16Q1 timeframe.'''

The store and central-server setup can also be used to define a failover mechanism in WebPOS. WebPOS clients will automatically switch from the store server to the central server if the store server is accidentally offline.

=== Base Setup: Enabling Preference & Multi-Server Authentication ===

This section describes several setup steps which need to be done before you can use Openbravo in a multi-server.

'''The enablement of the multi-server-communication functionality is controlled by a preference which by default is not set and therefore disables the multi-server logic'''.

So to enable multi-server-communication behavior for your stores you need to define the preference 'Mobile Multi-Server Architecture Enablement' (see screenshot below) with value Y and 'Selected' checkbox with value Y too. This preference needs to be defined on System level by the System Administrator.

The preference enables multi-server behavior for all WebPOS clients in the system across all clients/organizations/stores. But multi-server behavior will start only if there are Mobile Servers defined, so if you do not define mobile servers (see below) then the multi-server functionality is not operational and the WebPOS clients will work in the standard way.
Also: you can assign servers to stores specifically, so it is possible to test multi-server behavior first for WebPOS systems of specific/selected stores.

[[Image:preferenceMultiServer-OK.png|center|600px]]

Then as a second step, it is needed to enable specific authentication on each of the servers. This to support multi-server login. In each server which can be used from a WebPOS client the following [[Authentication#How_to_configure_the_authentication_manager_in_Openbravo_ERP|authentication manager]] has to be set in Openbravo.properties:

'''Note: the value of the mobile.server.key should be taken from the mobile server definition, see later subsection.'''
<source lang="javascript">authentication.class=org.openbravo.mobile.core.authenticate.MobileKeyAuthenticationManager
mobile.server.key=Central
</source>

Finally, if tickets are send to multiple servers simultaneously from WebPOS then it makes sense that the related documents of the tickets in the different servers have the same document numbers. To make sure this happens set the preference "Use Order Document Number for Related Docs" to Y:

[[Image:Multi-Server-EnablingPreference-SameDocNumber.png|center|600px]]

This section described the first-base setup. The next step is to define the mobile servers, specify which services they provide and assign them to stores/organizations.

==== Mobile Server Authentication ====

The above section specified how to set the authentication manager.

To provide some background information: the mobile server authentication manager uses a symmetric-shared-key logic to authenticate a WebPOS client on several servers withour requiring to relogin.

The key is never send to the WebPOS clients but stored on the server. It is an generated key which is created automatically at first login and then replicated to all store servers.

It is possible to regenerate the authentication key. This should be done in off-hours when none of the stores are operating. To regenerate the authentication key login into the central server backoffice. Goto the role which is linked client for which you want to change the key. Then in quick launch start the 'Recreate Mobile Server Authentication Key' process. You see a popup with an information text, click ok to regenerate the authentication key.

After recreation the new authentication key is replicated to all store servers. '''The tomcat of all the store servers need to be restarted and all users should relogin.'''

==== Test Setup ====

When testing with multiple servers it is often not possible to setup replication logic directly between the central and store servers. This means that the servers will not have a shared key available to them. To force the servers to use the same authentication key you can set the key in the Openbravo.properties file.

To make use of the test key it is mandatory to also set the test.environment property to true.

The following properties have to be set:
<source lang="javascript">test.environment=true
authentication.test.key=uMbsk0ZYPS43uUY6D1KU3A==
</source>

=== Preferences: token age, offline ping ===

For a complete overview of all the relevant multi-server preferences please visit [[Store_and_Multi_Server_Preferences|this page]].

=== Mobile Services ===

The services definition is done by developers and provided by modules. They are available under the System Admin role and shown as a reference here.

[[Image:Multi-Server-Services.png|center|600px]]

A description of the meaning of the fields:
* Module: services are provided by and implemented in modules
* Service: the service name, currently uniqueness of service names is not checked, the service name is used in client side code to call a service
* Routing Type: defines how the transport layer in the Web POS client should call the service:
** Fail Over: mostly used for '''querying''' services, if a call to a server fails for this service then Web POS will automatically try another server which provides the same service
** Transaction: as the name indicates is mostly used for '''transactions''' (such as new tickets/customers). Is similar to fail over, so servers are tried one by one until there is a server which can receive the transaction. The difference with fail over is that the system will store the message in the database and continue retrying until a server is able to receive the transaction. This makes this mode more robust than fail over which stops after all servers have been tried.
** Broadcast: the service request is automatically send (broadcasted) to all servers providing this service. Failed messages are not repeated. This type of request is useful for example for logout.
** Ping: a special service used to detect when a server is back online. Is used in the scenario that a server is offline (detected because another service request fails). In that case the Web POS client will ping the offline server to detect when it is back online
* Default Timeout: Time in seconds defined by default in the module for the request timeout related to the Mobile Service.
* Timeout: Time in seconds defined by the user, which overrides default timeout, for the request timeout related to the Mobile Service.

The service name uses 'contains' to match it with the requests from the client. So a service name of 'org.openbravo.retail.posterminal.master' will handle all the client side requests with 'org.openbravo.retail.posterminal.master' in the requested URL. In this way for example all the master data requests can be mapped to a server.

'''Note: In case of having more than one service for a given Service name, it gets longest name service. Longest name service will be the most similar to Service name. Avoid creating Java classes which contains another Java class name.'''

The following are examples of standard services, see the total list of services in the mobile core and webpos modules:
* org.openbravo.mobile.core.login.ContextInformation: retrieval, provides the current client/organization of the current user (after logging in)
* org.openbravo.retail.posterminal.CustomerAddrLoader: transactional, stores updated and new addresses in the database on the server
* org.openbravo.retail.posterminal.CustomerLoader: transactional, stores updated and new customers in the database on the server
* org.openbravo.retail.posterminal.master.BPLocation: retrieval, retrieves the business partner address from the server
* org.openbravo.retail.posterminal.master.BusinessPartner: retrieval, retrieves the business partners from the server
* org.openbravo.retail.posterminal.master.DiscountFilterBusinessPartner: retrieval, reads the discounts by business partner from the server
* org.openbravo.retail.posterminal.master.Product: retrieval, reads product data from the server
* org.openbravo.retail.posterminal.OrderLoader: transactional, stores new and updated tickets in the database on the server
* org.openbravo.retail.posterminal.PaidReceiptsHeader: retrieval, reads tickets (and layaways and quotations) from the server
* org.openbravo.retail.posterminal.POSLoginHandler: retrieval, login service
* org.openbravo.retail.posterminal.ProcessCashClose: transactional, stores the cashup on the server
* org.openbravo.retail.posterminal.ProcessCashMgmt: transactional, stores the cashup on the server

=== Mobile Server Definition ===

The Mobile Server Definition window allows you to define the servers which are available for WebPOS clients. Servers are used by WebPOS clients for logging in, retrieving master data, sending tickets/cashups and other transactional data.

A distinction is made between a store server and a main server. Store servers are mainly used for a specific store for logging in and querying. Main servers are used to store transactional data. Only transactions send to a Main Server are considered to be synchronized and are considered to be save. '''The 15Q4 release of the Commerce Suite assumes that a WebPOS system has one main server (which can be shared by many WebPOS clients)'''. This main server receives the transactions. In addition there can be several store servers defined for logging in and providing querying services.

A store server can be used for system load distribution or if installed locally in the store can ensure store operation also when the store looses internet connection.

The setup for the rest allows a large degree of flexibility. It is perfectly fine to not have a store server and only main servers. Or to let smaller stores work on a single main server, while a large store has its own store server.

The image below illustrates the definition of a server:

[[Image:Multi-Server-Definition3.png|center|600px]]

A description of the meaning of the fields:
* Name: any unique name is allowed
* Description: additional description for describing the purpose of the server
* Server Type: there are two types:
** Main Server: a main server is often used to store transactional data such as new tickets/updated business partners etc. Only transactions send to a main server are considered to be synchronized and save.
** Store Server: a store server is mainly used for load distribution and if locally maintained to ensure store operations when the store looses internet connection.
* URL: the main url by which the server can be reached, see the examples above/below, should include the webapp context path (openbravo in the examples here)
* Priority: if multiple servers can provide the same service then they are tried in order of priority. This is relevant for failover services which are will be called on the first available server. If a server is not available then the next in line is tried (in increasing order of priority number). '''In a setup with a main server and store server(s) then the store servers normally have a higher priority (lower number) than the central server. This ensures that the WebPOS clients will first access the store server before trying the central server.'''
* All Organizations: if this checkbox is checked then the server is made available to all WebPOS systems and the organizations defined in the 'Organizations by Server' are ignored. If unchecked then the 'Organizations by Server' information is used to determine if a server is to be used by a WebPOS client.
* All Services: if this field is checked then the server is assumed to provide all services. If unchecked then the information in the subtab 'Services by Server' is used to determine what services a server can provide.
* Defined services (from 16Q2): if All Services field is unchecked then we will see this field and we can select ''All excluding defined'' or ''Only those defined''. If ''Only those defined'' is selected then the information in the subtab 'Services by Server' is used to determine what services a server '''can''' provide. If ''All excluding defined'' is selected then the information in the subtab 'Services by Server' is used to determine what services a server '''cannot''' provide.
* Mobile Server Key (from 16Q1): is the unique key for the server, should be set in each server in Openbravo.properties, for example as: mobile.server.key=Central
* Server Status (from 16Q1): gives the current status of the server (offline, online, transitioning). See the [[Retail:Store_Server#Online_.26_Offline_concepts_of_Store_Servers|Store Server]] page for more information on server status handling.
* Reload Status (from 17Q2 when the replication module is installed): defines the status of the initial data reload logic. For more information see [[Retail:Store_Server_Initial_Data_Reload|this]] page.
* Version Status (from 17Q2.1 when the Store Server Retail module is installed): the version status shows if the store and central server have different versions. Field is relevant for [[Retail:Store_Server#Updating_an_Openbravo_Multi-Server_Environment|store server updating]]. The following values can be shown:
** Same as Central: store and central server have the same version for the modules which they have in common
** Different from Central: store and central server have different versions for the modules they have in common
* Version (from 17Q2.1 when the Store Server Retail module is installed): the version is computed from the versions of all the modules installed on the store server. So store servers with different module (versions) will show different overall version numbers. A higher version number means a newer server, this because version numbers can only increase over time. Field is relevant for [[Retail:Store_Server#Updating_an_Openbravo_Multi-Server_Environment|store server updating]].
* Allowed Origin Domains (from 17Q1): a list of comma or new-line separate domain definitions. Each domain value can be a complete domain (including http/https and the port number) or a regular expression. See the screenshot above for examples. See the next section for more information.
* Offline Log/Cause (from 17Q1): if the store server is offline then this field gives information on the reason for being offline. See [[Store_Server_Online_and_Offline_Concepts#Causes_for_staying_offline|here]] for more details.

[[Image:Multi-Server-Definitions.png|center|600px]]

==== Allowed Origin Domains Field - Cross Domain Requests ====

Openbravo Commerce supports doing requests from one WebPOS client to multiple servers in the architecture. The WebPOS client has a url pointing to one host from which it obtains the source code. Requests to other servers (to search for products for example) are therefore so-called [https://en.wikipedia.org/wiki/Cross-origin_resource_sharing cross domain requests]. Cross domain requests are handled specifically in web environments requiring special configuration.

A WebPOS client is only allowed to call the other servers in the environment if the domain of the original url of the WebPOS client (from where it loads the webpage itself) is:
* defined as an Allowed Origin Domain in any of the Mobile Server Definitions
* is the domain of the url of any of the Mobile Server Definitions

For example:
* if you define the store server with an url: http://store1.openbravo.com/openbravo and there is a central server with url: http://central.openbravo.com/openbravo.
* let's say that there is an alias host mystore.openbravo.com pointing to the same server as store1.openbravo.com.
* then a WebPOS client loaded from http://store1.openbravo.com can do requests to central.openbravo.com, this is allowed and supported.
* however a WebPOS client loaded from http://mystore.openbravo.com can not do requests to central.openbravo.com.
* to allow also WebPOS clients loaded from mystore.openbravo.com to call central.openbravo.com you have to add: http://mystore.openbravo.com to the Allowed Origin Domains field of any Mobile Server Definition.

If you don't set the Allowed Origin Domains field then WebPOS clients can only call other servers if they are loaded from the exact url/domain as defined in the mobile server definition of their respective store.

If you try to load the WebPOS from a URL/location which is not defined as the url of a mobile server or allowed origin domain then when loading the client you will get a message as shown below.

[[Image:cors_error_load_webpos.png|center|600px]]

In addition you will see messages like this in the log:
<source lang="bash">XMLHttpRequest cannot load http://store1.openbravo.com:8080/openbravo/org.openbravo.retail.posterminal…ls?terminalName=VBS-1&command=userImages&appName=WebPOS&0.7785557618144872.
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8080' is therefore not allowed access.
</source>

==== Mobile Server Organizations - Stores ====

A server can be linked to all organizations (stores), so it is available for all WebPOS clients, or a server can be assigned to a specific set of organizations (stores).

To flag a server to be available for all organizations, check the 'All Organizations' field in the server definition.

If you want to assign a server to a specific set of organizations/stores then you can use the sub tab 'Organizations by Server'. Make sure the 'All Organizations' checkbox is not checked in the server definition and then add records in the 'Organizations by Server'. Multiple servers can be assigned to multiple organizations and vice versa.

The Openbravo organization structure also plays a role here, so assigning a server to a parent organization automatically makes it available for all the child organizations of that parent organization.

[[Image:Multi-Server-Orgs.png|center|600px]]

==== Mobile Server Services ====

The information in this subtab is used when the 'All Services' checkbox in the Mobile Server definition is not checked.

'Defined services' value will define which services are available for the server. If ''Only those defined'' is selected then the information in the subtab 'Services by Server' is used to determine what services a server '''can''' provide. If ''All excluding defined'' is selected then the information in the subtab 'Services by Server' is used to determine what services a server '''cannot''' provide.

This subtab allows you to specify which services are provided by which server. There is a fair amount of freedom in assigning querying services. You can load products from one server and business partners from another server.

The thing to ensure though is that if users in WebPOS can create new customers and tickets that the tickets and customer are send to the same server. Or that the data between servers is synchronized in a different way. Also the cashup can only be send to a server which also receives or has all the WebPOS orders. This means that either the servers are synchronized in the backend or that all transactions are send to a server. All transactions can also be send to multiple servers.

The example below shows how all transactions services are assigned to a specific main server.

[[Image:Multi-Server-Services-Definitions.png|center|600px]]

==== Modules by Server ====

This subtab is available from 17Q2.1 and only if the Retail Store Server module is installed.

To provide complete visibility of what is installed in your environment you can check the Modules by Server sub tab in the Mobile Server window. It shows the modules installed on the store server with their respective version numbers.

[[Image:StoreServerUpdate_Modules_by_Server.png|center|800px]]

=== Multi Server Configuration: preferences and process ===

==== Preferences ====

{{(!)|This functionality is available from '''RR16Q1'''.}}

Multi server functionality is disabled by default. To make use of this advanced functionality you have to set specific preferences. In addition there are several preferences which control the behavior of multi-server logic. All these preferences are described in [[Store_and_Multi_Server_Preferences|this]] page.

==== Store Server Backoffice ERP access disabled ====

{{(!)|This functionality is available from '''RR16Q3'''.}}

The backoffice user interface is not official supported for the store server. This because the store server architecture assumes that changes in the store server are provided through webservices or symmetric ds replication and not done directly through the user interface.

It is therefore the safest if the backoffice ERP access is disabled. This can be done by setting a preference: '''Restrict ERP Access in Store Server''' to 'Y'.

This preference should be set by the system admin. If you need access to the store server backoffice UI to view current transactions or other diagnostic information then you can temporarily deactivate this preference by logging in with a system admin user/role.

=== Synchronized Transactions in Multi-Server Environments ===

The OB Commerce multi-server functionality is also supported for [[Retail:Configuration_Guide#WebPOS_Synchronized_Transactions|synchronized]] transactions. Synchronized transactions are defined as a fail-over service.

Synchronized transactions in a multi-server environment have specific characteristics. These are described in detail in the [[Synchronized_Transactions_in_Multi-Server_Environments|following]] document.

== Supporting High Volume Master Data: Remote Master Data Handling ==

{{(!)|Starting from '''RR15Q4''' below functionality is available }}

To support high volumes of products, customers and tickets, Openbravo Commerce allows you to work remotely with master data from the WebPOS client. The high volume master data is then not loaded into the WebPOS client database but accesses when needed on a server. The server can be a locally in-store server or a server available in the cloud.

The following data can be handled remotely from WebPOS clients:
* Products
* Customer and Customer Addresses
* Tickets/Orders
* Discounts by Customer

By enabling remote data handling the WebPOS clients are capable of working with millions of products, prices and customers. The remote data handling can be combined with the Openbravo [[Retail:Configuration_Guide#Web_POS_Multi-Server_Architecture|multi-server]] architecture functionality to define (local store) servers which provide product/customer data querying services to WebPOS clients.

By default remote data handling is disabled. The enabling of the remote data functionality is controlled by several preferences which are discussed in the next section.

Note that enabling remote data has as a consequence that it is not possible to operate the WebPOS client in complete offline mode. There are solutions to work with a local [[Retail:Configuration_Guide#Web_POS_Multi-Server_Architecture|store]] server (physically located near the terminals - on the same local network) which can help in these type of specific cases.

=== Remote Data Preferences ===

Several preferences are used to control which data is handled remotely. These are illustrated in the screenshot below. The screenshot below shows that by default the remote-data preferences are set to N. To enable remote data handling you have to define the related preferences and set the value Y. In addition, 'Selected' check-box has to be set as Y too. In the screenshot below this is illustrated.

Note: '''it is important to define the preferences on at least one of client/org/user/role level to ensure that the system will prefer it over the default preferences which are set to N.'''

[[Image:preferencesRemote-OK.png|center|600px]]

==== Use Contains Remote Data Preferences ====

There are also two preference more for remote searching: ''Use contains in Remote Customer search'' and ''Use contains in Remote Product search''. By default, remote queries are done using starts With to filter in order to improve performance of those queries. In case of you need to filter using contains, you can create these preference setting them to 'Y' to have this ability in Web POS for remote models. Non remote models already use contains to filter.

=== Remote Data: Product Categories ===

In case of a high volume of product master data, so when products are accessed remotely then the way product categories are loaded by the WebPOS clients is also changed. The system needs to run an update process in a daily (for example) batch to determine which product categories should be loaded by which WebPOS.

[[Image:Remote-Data-PC-Process.png|center|600px]]

After running the process the product categories which are loaded in the client are displayed in the assortment. Note, the subtab is only visible if there are product categories linked to an assortment.

[[Image:Remote-Data-PC-AssortmentSubtab.png|center|600px]]

=== Remote Master Data Limitations - Future enhancements ===

In the 15Q4 release, the remote data capability also has some limitations, these will be addressed in future releases:
* No client-side product catalog: the Openbravo Commerce WebPOS product catalog functionality will be enhanced in a next release to work with remote product data. In the 15Q4 release it is assumed that the user will find products by scanning or searching for products. In the 16Q4 release a new hierarchical product catalog search will be added.
* No product characteristic support: remote product data can not be combined with product characteristic search. From the '''16Q1''' release onwards product characteristic and brand search is supported also for remote product data.
* No alphabetical search bar in customer search: the alphabetical bar on the left of the customer search is not available when customer data is remote, the search filter text field is there to search for customers.
* No automatic search customer/product when entering search term: with remote product/customer enabled after entering a search term in product/customer search the user has to explicitly tap the search button, with the remote preference set to N the search will automatically happen after 3 characters have been entered.
* Discounts: discounts are mostly all loaded in the client side WebPOS database, only the business partner discount definitions are loaded on demand when a business partner is selected for a ticket. This means that:
** Openbravo Commerce can support 10-thousands of discount definitions on product, product category or business partner category level. They are loaded in the WebPOS client side database.
** But Openbravo Commerce can not support 100-thousands or more discount definitions on product/product category or business partner category level. This would make the WebPOS client too slow.
So in high volume environments it is better to limit the number of discount definitions by defining them on product/BP category level or only for specific business partner.

Default WebPOS layout in case of remote product data (no browse/catalog option):

[[Image:Remote-Data-WebPOS-UI.png|center|600px]]

=== Retail Extension Modules enabled for Remote Data ===

In the subsequent releases many extension modules have been checked for their support of remote product/business partner data. Also automated tests have been added to ensure continuous correct operation with remote data.

This is the current (16Q2 release) list of modules which have been tested with remote data, most are also tested automatically:
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.giftcards.newentities Gift card new entities]
* [https://code.openbravo.com/erp/pmods/org.openbravo.mobile.warehouse.physicalinventory/ Physical inventory]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.complementary Complementary products]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.copystore Copy Store]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.giftcards Gift Card]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.giftcards.printgiftcards Print Giftcard]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.stockcriteria Stock Criteria]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.pricecriteria Price Criteria]
* [https://code.openbravo.com/erp/pmods-branches/org.openbravo.retail.sessions Retail Sessions]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.stockvalidation/ Stock Validation]
* [https://code.openbravo.com/erp/pmods/org.openbravo.financial.multitaxcategory/ Multi Tax Category]
* [https://code.openbravo.com/erp/pmods/org.openbravo.multiupc/ Multi UPC]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.showprodsk/ Show Prod Description]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.taxexempt/ Tax Exempt]
* [https://code.openbravo.com/erp/pmods/org.openbravo.mobile.warehouse/ Mobile Warehouse]
* [http://wiki.openbravo.com/wiki/Retail:Web_POS_User_Guide#Multi_Price_List Multi Price List]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.printlast Print Last Ticket]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.trainingmode Retail Training]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.analytics Retail Analytics]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.levelpricing/ Level Pricing]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.bestsellers/ Best Sellers]

Discount Modules (see limitations section, the remark for discount setup there still applies):
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.discounts Retail Discounts]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.copybestsellers/ Best Sellers]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.copystore Copy Bestsellers]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.discounts.bytotal Discounts by Total]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.discounts.combo Combo Discount]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.discount.twofamiliescombo Two Families Discount]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.activediscountspopup/ Active Discount Popup]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.discounts.bestdeal Best Deal]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.discounts.coupons Coupons]
* [https://code.openbravo.com/erp/pmods/org.openbravo.retail.discounts.discountmatrixmanagement Discount Matrix]

As a next step parallel to the 16Q2/Q3 releases we are adding automated tests on high volume datasets for many of these modules. This section will be updated when the automated tests on high volume data are enabled (probably around 16Q3 timeframe).

[[Category:Retail]]

Retail:Configuration Guide/id

2026-08-28T08:57:24Z

Wikiadmin: Create ID subpage stub (scaffold) for Retail:Configuration Guide

{{Languages}}

== Retail:Configuration Guide (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Retail:Configuration Guide|Retail:Configuration Guide]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Installation

2026-08-28T08:57:23Z

Wikiadmin: Add {{Languages}} switcher (EN) for ID subpage

{{Languages}}

{| style="margin:auto;" cellpadding="0"
|- align="center"
Installation steps: Work from left to right using the clickable links
| <div class="t"><div class="b"><div class="l"><div
class="r"><div class="bl"><div class="br"><div class="tl"><div
class="tr">
<div style="height:25px;display:
table-cell;vertical-align:middle;"><span style="color:#DC6710">[[System_Administration_Guide | System Administration Guide]]</span></div>
</div></div></div></div></div></div></div></div>

| <div class="t"><div class="b"><div class="l"><div
class="r"><div class="bl"><div class="br"><div class="tl"><div
class="tr">
<div style="height:25px;display:
table-cell;vertical-align:middle;"><span style="color:#DC6710">[[System_Requirements | System Requirements]]</span></div>
</div></div></div></div></div></div></div></div>

|

{|
|-

| <div class="t"><div class="b"><div class="l"><div
class="r"><div class="bl"><div class="br"><div class="tl"><div
class="tr">
<div style="height:25px;display:
table-cell;vertical-align:middle;"><span style="color:#DC6710">[[Installation | Installation]]</span></div>
</div></div></div></div></div></div></div></div>

|-

| <div class="t"><div class="b"><div class="l"><div
class="r"><div class="bl"><div class="br"><div class="tl"><div
class="tr">
<div style="height:25px;display:
table-cell;vertical-align:middle;"><span style="color:#DC6710">[[Upgrading_From_2.50 | Upgrading]]</span></div>
</div></div></div></div></div></div></div></div>

|}

|

{|

|-
| <div class="t"><div class="b"><div class="l"><div
class="r"><div class="bl"><div class="br"><div class="tl"><div
class="tr">
<div style="height:25px;display:
table-cell;vertical-align:middle;"><span style="color:#DC6710">[http://landings.openbravo.com/openbravo-cloud '''Openbravo Cloud (recommended)''']</span></div>
</div></div></div></div></div></div></div></div>

|-
| <div class="t"><div class="b"><div class="l"><div
class="r"><div class="bl"><div class="br"><div class="tl"><div
class="tr">
<div style="height:25px;display:
table-cell;vertical-align:middle;"><span style="color:#DC6710">[[Installation/Appliance | '''Appliance''']]

</span>
<span style="color:#489C06">Available in EC2, ISO and VMware</span></div>
</div></div></div></div></div></div></div></div>

|-
| <div class="t"><div class="b"><div class="l"><div
class="r"><div class="bl"><div class="br"><div class="tl"><div
class="tr">
<div style="height:25px;display:
table-cell;vertical-align:middle;"><span style="color:#DC6710">[[Installation/Custom | Custom installation]]</span></div>
</div></div></div></div></div></div></div></div>

|}

| <div class="t"><div class="b"><div class="l"><div
class="r"><div class="bl"><div class="br"><div class="tl"><div
class="tr">
<div style="height:25px;display:
table-cell;vertical-align:middle;"><span style="color:#DC6710">[[Instance_Activation | Activation]]</span></div>
</div></div></div></div></div></div></div></div>

|}

<currentversion type="link">

__NOTOC__

{{(!)|'''The current Openbravo release is #version#'''. Make sure you are installing the latest version.}}

== Deployment options ==

==== Recommended ====
The recommended option is to use the Openbravo Cloud:
* [http://landings.openbravo.com/openbravo-cloud '''Openbravo Cloud''']: A single-tenant Platform-as-a-Service (PaaS) option that enables you to deploy Openbravo on virtual servers in Amazon Web Services

==== Other options available ====
* [[Installation/Appliance|'''Openbravo Appliance''']]:
** '''Amazon EC2''' : intended for production, also can be used for testing.
** '''Iso''' : intended for production servers, can be used in physical servers, virtualization options like (VMware Server, Virtualbox, etc) or any server provider that allows to use your own iso.
** '''Vmware''' : ONLY for testing, uncompress and launch it in your preferred virtualization program (VMware, Virtualbox, etc ) and get an Openbravo running easily.

==== Experts Only ====
* [[Installation/Custom|'''Custom deployment''']]: we don't recommend to use it, please use the appliance in one of the previous options. Custom install is only an option when you know what are you doing and you have very special needs that don't fit in the appliances.

==== Discontinued options ====
* [[Installation/Ubuntu|'''Ubuntu package (ppa)''']] '''(discontinued)''': we don't recommend to use it.

[[Category:Installation]]

</currentversion>

Installation/id

2026-08-28T08:57:22Z

Wikiadmin: Create ID subpage stub (scaffold) for Installation

{{Languages}}

== Installation (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Installation|Installation]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]

Quick Guide/id

2026-08-28T08:57:21Z

Wikiadmin: Create ID subpage stub (scaffold) for Quick Guide

{{Languages}}

== Quick Guide (Bahasa Indonesia) ==

Halaman ini adalah terjemahan Bahasa Indonesia dari [[Quick Guide|Quick Guide]]. Isinya masih dalam pengerjaan (work in progress).

Silakan bantu melengkapi terjemahan mengikuti panduan di [[Starting_Guide_for_Wiki_translators|Starting Guide for Wiki Translators]].

[[Category:WorkInProgress]]