P
Peter Judge
Guest
The JSDO component will do the client-side authentication and session management for you. Those things are still controlled by the server. The JSDO still works over standard HTTP and consumes the Data Object Catalog which is a public API of the services; the catalog exposes business resources in a fairly prescriptive manner. The JSDO makes working with data feel closer to ABL (working with datasets/temp-tables) – including knowing how and when to work with the prods: properties. These control the before-imaging (change control) and some error handling of records in temp-tables in a dataset. They are reasonably simple to figure out. In ABL, make sure you have before-tables defined with some change data and call WRITE-JSON() with the write-before-image flag set to TRUE. Basically there end up being up to 3 ‘sections’ in the JSON: one for the data as it is now, one for the data as it was before any changes, and one for errors. Check out the ABL’s TRACKING-CHANGES, MARK-ROW-STATE and of course WRITE-JSON methods in the Help for information about each piece. There’s a short example of using them at community.progress.com/.../37897 I thought there was some description of the JSON we produce from the WRITE-JSON() method at documentation.progress.com/.../reading-and-serializing-json-to-2ffrom-prodatasets.html but sadly not.
Continue reading...
Continue reading...