Let Users Edit Business Documents with Context-Bound References
An order-editing page may show an order and several lines. The user changes a quantity, removes one line, and clicks Save. The server must distinguish that intent from a missing row that was never loaded, an old version of the order, or a row reference copied from another user's page.
TeaQL's optional Secure Document Reference module makes that round trip explicit. Here, a document is an editable view of a business object graph; it does not mean a PDF or Word file. The application opens a document for a particular actor and purpose, sends its editable body and opaque credentials to the client, and accepts a returned edit only within that document's scope.
