When the agent is set to use MultiForwardingUDR
input, it accepts input of the UDR type MultiForwardingUDR
declared in the package FNT. The declaration follows:
Code Block | ||
---|---|---|
| ||
internal MultiForwardingUDR { // Entire file content byte[] content; // Target filename and directory FNTUDR fntSpecification; }; |
The content of the MultiForwardingUDR will be stored at the path that you have set in the fntSpecification
field. Use the APL functions fntAddString
and fntAddDirDelimiter
to set the value of this field. For further information about these functions, see 16. FNTUDR Functions in APL Reference Guide.
When the files are received they are written to temp files in the DR_TMP_DIR
directory situated in the root output folder. The files are moved to their final destination when an end batch message is received. A runtime error will occur if any of the fields have a null value or if the path is invalid on the target file system.
A UDR of the type MultiForwardingUDR which has a target filename that is not identical to its precedent is saved in a new output file.
Note |
---|
Note!MultiforwardingUDR’s with their own specific target filenames will be saved into their specific output files. UDRs with filename A will be saved to filename A and UDRs with filename B will be saved to filename B regardless of precedence. |
Non-existing directories will be created if the Create Non-Existing Directories check box under the Filename Template tab is checked. If not checked, a runtime error will occur if a previously unknown directory exists in the FNTUDR of an incoming MultiForwardingUDR
. Every configuration option referring to bytearray input is ignored when MultiForwardingUDR
s are expected.
Info | |||||||
---|---|---|---|---|---|---|---|
Example - APL code to send MultiForwardingUDRsThis example shows the APL code used in an Analysis agent connected to a forwarding agent expecting input of type
The Analysis agent mentioned previous in the example will send two |