An OpenEdge ABL implementation for Submit

Using JSDOs to create mobile and web clients : Accessing standard CRUD and Submit operations : Submit operation example : An OpenEdge ABL implementation for Submit

The signature of the ABL routine associated with a submit operation must have a single INPUT-OUTPUT parameter for a DATASET or DATASET-HANDLE.

For an OpenEdge Data Object resource, the signature of the ABL routine that implements a Submit operation must have a single INPUT-OUTPUT parameter for a DATASET or DATASET-HANDLE.

The following example shows a SubmitOrderEntry( ) method that might be associated with Data Object Submit operations:

The following example shows a SubmitdsCustomer( ) method that might implement the Data Object Submit operation for the ProDataSet resource, dsCustomer:

METHOD PUBLIC VOID SubmitdsCustomer(INPUT-OUTPUT DATASET dsCustomer):

DEFINE VAR hDataSet AS HANDLE NO-UNDO.
hDataSet = DATASET dsCustomer:HANDLE.

SUPER:SubmitData(DATASET-HANDLE hDataSet BY-REFERENCE).

END METHOD.

This implementation simply calls an overload of the SubmitData( ) method defined in the OpenEdge.BusinessLogic.BusinessEntity super class, which OpenEdge provides as an aid for implementing Data Object resources that support before-imaging. The invoked SubmitData( ) method provides a default implementation to create, update, or delete one or more records in the server database from the changed temp-table records in the ProDataSet input to SubmitdsCustomer( ).