In the previous section (Registering a Pending Outbound Document) a set of APIS were described for registering a pending outbound transaction document that can then be picked up and processed by the usual outbound processes. This is by far the most common case where you may need to update LANSA Composer's Transaction Document register from your own application code.

However, for more advanced uses, LANSA Composer provides a more general API that is capable of both:

  • Registering a transaction document (whether inbound OR outbound).
  • Updating the status of a registered transaction document.

These two functions correspond directly to the functions of the TXDOC_REGISTER and TXDOC_STATUS activities. (Note that they do not provide the EDI-particular features that are provided by the APIs described in Registering a Pending Outbound Document.)

Note: This section assumes sound knowledge of the applicable LANSA development techniques. Refer to LANSA product documentation for detailed information on application development with LANSA.

LANSA Composer provides the DXXREGDOC re-useable part that provides the interfaces through two methods:

  1. Method dxDocRegister allows the application to register a transaction document and is functionally equivalent to the supplied TXDOC_REGISTER activity.
  2. Method dxDocStatus allows the application to update the status of a specified transaction document and is functionally equivalent to the supplied TXDOC_STATUS activity.
Note: Once you have imported the LANSA Composer development package into your Visual LANSA development environment, you can use the feature help within the Visual LANSA IDE to review the detail of the methods and properties exposed by the DXXREGDOC component.
  • No labels