Activities for Transaction Document Processing

The supplied transaction document processing framework is typical of many business process integration (BPI) solutions and makes use of a wide variety of the Activities that are supplied with LANSA Composer.

However, there is a subset of the supplied Activities supplied that are very specifically intended for and associated with the transaction document processing framework.  These are Activities that:

• Discover document and content type, including Activities specific to EDI document discovery.

• Establish connections between transaction document files and the Trading Partner and Transformation Maps that should be used to process them.

• Register transaction document files in LANSA Composer's transaction document register and update their status as document processing proceeds.

• Invoke customer-defined processing to import or export transaction document data to or from application database tables.

 

This group of supplied Activities are listed in:

Transaction Document Processing

 

As supplied, the Processing Sequences that implement the transaction document processing framework use most of these Activities.

However, if you either modify the supplied solution or create your own, you are not compelled to use the supplied activities if it is inappropriate, in your particular circumstances to do so.

For example, the supplied TXDOC_INBOUND Processing Sequence uses the DISCOVER_DOC activity to associate a transaction document file extension with the subsidiary Processing Sequence that processes that type of transaction document file.  This provides the maximum flexibility in the supplied solution, but in many cases, with knowledge of your specific organization's requirements, it may be equally valid to make assumptions about the type of transaction document files that you receive from a given Trading Partner.

There are only two Activities that are usually essential to any solution in which you wish to make use of LANSA Composer's transaction document register.  They are the TXDOC_REGISTER and TXDOC_STATUS Activities.  For more information, refer to:

Adapting your own Solution to Use the Transaction Document Register