File name default classes
This table shows the default classes for the file name settings. Access these properties through the File Names tab in .
EC default classes | Definition |
---|---|
MEC_Prefix |
The File name result: |
MEC_Infix |
The File name result: Note: The parenthesis must be included in the file name
field.
If the indicator |
MEC_Suffix |
The File name result: |
MEC_InfixManifest |
The When you set up the send object, the manifest item name is case sensitve and must be enclosed in parenthesis. The manifest item name, including the parentheses, is replaced by the manifest item's value at runtime. If the manifest item does not exist, an empty string ("") is used as value. You can use one or more manifest items in a file name. If the generated file name is blank, an error will be generated. File name format: Note: If you specify a dash character for the file
extension in the send object setting, it will create files without extension.
|
Here is an example setting for MEC_InfixManifest
:
UUID.xml
|
Generated File name:
The manifest's UUID is used. |
Prefix_cmn:agreement_UUID_Suffix.xml
|
Generated File name:
The name of the agreement is Test_20. |
com:fileName
|
Generated File name:
The generated file extension is included in the manifest item value and the generated file name is equal to the received file's name. |
If you put this Java code into a user-defined function in a map: You must do these:
The result file name will be: " You can now set the complete file name or part of the file name from a map. |