Let a Customer Edit an Order Without Losing the Save Boundary
A customer opens an order with two lines. They change the Blue cup quantity from 2 to 5 and click Save. The connection drops before the response arrives.
Should the client save again? What if another user edited the order while the page was open? What if the customer removes a line from the submitted JSON?
Our protected order-editing guide
walks through these cases using a downloadable Java/SQLite example. It starts
with the open and submit operations, then shows what the application must do
behind them. The example uses the source preview of the optional
SecureDocumentReferenceModule.
