Copy the Supplied Processing Sequences Before Use
The sets of Processing Sequences supplied with LANSA Composer for processing inbound and outbound transaction document flows:
- Have names beginning with TXDOC_ ;
- Are supplied with their flag set to .
The latter point means you may not change these definitions, although you may open them in mode and/or print their definitions. There is no supported means to turn off this flag such that you can modify the Processing Sequences.
This is deliberately so. The supplied Processing Sequences may be updated and replaced with later versions of LANSA Composer. If LANSA Composer allowed you to change them, then your changes would be lost when you upgrade to a new version.
If you intend to use these Processing Sequences, and particularly if you wish to modify them, you are strongly advised to make your own copies and use or modify the copies. When doing so, please refer to the following notes.
Copying the Supplied Processing Sequences
The supplied inbound and outbound processes are designed to be modular - that is, they are broken down into more than one Processing Sequence with the main Processing Sequence (TXDOC_INBOUND or TXDOC_OUTBOUND) calling the subsidiary Processing Sequences as required.
If you copy the Processing Sequences, you will need to modify any references to subsidiary Processing Sequences to make sure that your copies are called. This may involve one or other of the following:
1. Modifying a Document Type definition
The Document Type definition includes a reference to the Processing Sequence that processes transaction documents of the type. For example, as supplied, the 'EDI' document type is configured to use Processing Sequence TXDOC_IEDI010 to processing inbound transaction documents, or TXDOC_OEDI010 to processing outbound transaction documents.
The supplied TXDOC_INBOUND and TXDOC_OUTBOUND Processing Sequences uses these values to determine which Processing Sequence to execute for a transaction document file.
If you have copied supplied Processing Sequences that are specified in a Document Type definition (EDI or another type), then you should modify the Document Type definition to call your copied version.
For more information on modifying the Document Type definition, refer to Document Type Maintenance.
2. Modifying references within the Processing Sequence definition
In other cases, references to called Processing Sequences are embedded directly in the calling Processing Sequence.
For example, for an EDI document, the supplied TXDOC_IEDI010 Processing Sequence calls TXDOC_IEDI020 which in turn may call TXDOC_IEDI090.
In these instances, you need to open your copy of the Processing Sequence in the and directly change the reference to the Processing Sequence.
For more information on editing a Processing Sequence, refer to Use the Processing Sequence Editor.