SOAP Web Services
Atomic Page Operations
When you publish a page as a SOAP web service, it has a set of default operations that are exposed to consumers of the web service. These operations match the actions a user can perform by interacting with a page using the RoleTailored client. The same page- and table-based business logic is executed. Pages that are backed by virtual tables are not editable through web services. When such pages are published as SOAP web services, the only operations that are available are Read, ReadMultiple, and IsUpdated.
The term entity that is used in the operation signatures describes the data type that is used. The actual entity is defined by the page that is exposed because it contains all controls that are defined on the page. The controls are normally bound to the pages source table. The entity also contains a key that is a special string that uniquely identifies the source table record with a timestamp. This key is used as an argument in many page operations.
All basic page operations are atomic, which means that either all relevant records are affected or no records are affected, even if there was a faulty condition in only one record.