What is the primary reason for adding a permanent save feature to the transaction?

The primary reason is to prevent users from adding or deleting items from a transaction after it has been officially finalized and a receipt has been generated, thereby avoiding potential fraud or record discrepancies.

What new database column was added to track the finalization status of a transaction?

A new column named 'simpan' (save) was added to the transaction table, using 0 to indicate 'not saved' and 1 to indicate 'permanently saved.'

What PHP script handles the update when a user clicks 'Save Permanently'?

The update logic is handled in `spt.php`, which receives the transaction ID and executes an SQL UPDATE query to set the 'simpan' column to 1 for that specific ID.

Why did the initial attempt to redirect after saving fail to register the save status correctly?

The failure was due to the form submission method. The front-end form was using GET implicitly, while the backend script expected POST data, causing the transaction ID parameter to be lost upon redirection.

How is the system configured to hide the "Add Item" and "Save Permanently" buttons after finalization?

A PHP function `cek_simpan_transaksi` queries the database for the transaction's 'simpan' status, and an IF/ELSE block on the detail page controls the display of these buttons based on whether the returned value is 0 or 1.

What calculation is required for the 'Total' column in the transaction details?

The total price for each line item is calculated by multiplying the item's Weight by its Unit Price (Berat $\times$ Harga Satuan).

#12. Validasi Data dan Form Input Part 1

Transaction Finalization and Immutability
📌 Implemented a "Permanent Save" (Simpan Permanen) feature to finalize transactions, which prevents further edits or deletions to prevent potential misappropriation of garments.
⚙️ A new `simpan` column (with values 0 or 1) was added to the `transaksi` table to track the finalization status (0 for pending, 1 for permanent).
🔄 Upon clicking "Permanent Save," a script updates the `simpan` status from 0 to 1, invalidating any further modification attempts on that transaction.

User Interface and Conditional Display
🖥️ The logic now checks the `simpan` status using a custom function (`cek_simpan_transaksi`) based on the transaction ID (`$_GET['q']`).
🚫 If the transaction is finalized (`simpan = 1`), the "Add Item" and "Save" buttons are hidden, and a "Print Receipt" (Cetak Nota) button is displayed instead.
🖨️ A "Print Receipt" link is conditionally shown when the transaction is finalized, directing the user to the report display page.

Detail Calculation and Display Logic
🔢 Line item total is now dynamically calculated as Weight × Unit Price within the loop.
💰 The Grand Total is calculated by summing the line item totals across all records in the transaction using a running variable (`$GT`) initialized to 0.
🏷️ Item names (e.g., Nama Jenis Cucian) and currency formatting (Indonesian Rupiah) were integrated into the display for better reporting.

Key Points & Insights
➡️ Method Consistency is Crucial: When submitting the permanent save form, ensure the HTTP method (e.g., `POST`) in the front-end matches how the receiving script (`simpanpermanen_transaksi.php`) attempts to capture the data (`$_POST`).
➡️ Data Integrity via Status Flags: Using a database flag (like `simpan = 1`) is essential for enforcing business rules, such as making completed transactions immutable (non-deletable/non-editable).
➡️ Dynamic Reporting Display: Leverage conditional PHP logic within the HTML structure to dynamically show or hide interface elements (buttons, input fields) based on real-time database status checks.

📸 Video summarized with SummaryTube.com on Nov 20, 2025, 00:57 UTC

#12. Validasi Data dan Form Input Part 1

Loading Similar Videos...

Recently Summarized Videos

📜Transcript

📄Video Description

Loading Similar Videos...

Recently Summarized Videos

Get the Chrome Extension