Transaction Document Support

Transaction Document Support

LANSA Composer's supplied Transaction Document Processing Framework has been extended to better cover the inbound and outbound transport operations:

• For inbound transport, the supplied "model" processing sequences (*) have been extended to include a call to a new TXDOC_RCV processing sequence for receiving transaction document files.  That processing sequence, in turn, is set up to delegate to a processing sequence (modeled as TXDOC_RCV_TP) that is specific to the Trading Partner.

• For outbound transport, the supplied "model" processing sequences (*) have been extended to include a call to a new TXDOC_SEND processing sequence for sending transaction document files.  That processing sequence, in turn, is set up to delegate to a processing sequence (modeled as TXDOC_SEND_TP) that is specific to the Trading Partner.

• Trading partner support has been extended to permit the trading partner specific receive and send processing sequences to be specified individually for each trading partner and new trading partner built-in variables are provided for accessing these values.

 

Together, these changes make the Transaction Document Processing Framework, as supplied, a better fit for accommodating the varied transports associated with a range of trading partners, and should reduce the need to modify the framework solution for this purpose.

(*) The changes are to the supplied processing sequences.  Existing implementations will most usually have copied the supplied processing sequences and modified them to suit the specific implementation.  In this case, the existing implementation may need to be revised to take advantage of this new support.

 

Other changes related to transaction document support include:

• The LANSA Composer Document Manager provides a Resend button for a completed outbound transaction document envelope.  When clicked, the completed transaction document file will be sent again to the trading partner by means of executing a Processing Sequence identified by a new system setting.  By default, the supplied TXDOC_SEND processing sequence is used, which in turn delegates to the processing sequence specified for the Trading Partner, if any.

• New *txdoc.* built-in variables provide access to transaction document envelope attributes in a Processing Sequence.

• A new application program interface (API) to replicate the functionality of TXDOC_REGISTER and TXDOC_STATUS customer application code.