Generate output and Attachments

Each attachment can be configured to be:

  • Static or personalized – static means that the content is the same for each user receiving the message. Personalized means that the attachment is specific to each user receiving the message.
  • Optional or compulsory – an optional attachment may be selected for some messages. and can be skipped for other messages processed using the same Outbound Profile.
  • Archived or not – specifies whether the attachment is to be archived.

Here is important information about attachments:

  • The attachment that gets attached is the file whose name is equal to the AttachNameX value in the DIJ. If this attachment is set to optional in the Outbound Profile and the AttachNameX value in the DIJ is left blank, no attachment is used. If the value is blank and the attachment is not set to be optional, an error occurs.
  • For static attachments, all Outbound Profiles expect to find one or more files in the attachment folder matching the AttachNameX values in the DIJ.
  • For personalized attachments, a real-time Outbound Profile expects a single file in the attachment folder.
  • If the attachment is configured as optional, the attachment can be skipped if the AttachNameX value in the DIJ is also blank. If an attachment is compulsory, an error occurs if the required attachment is missing.
  • For personalized PDF attachments, either a single compound PDF file or an individual PDF file must exist for each message.
    • For a single compound PDF file, the main part of the filename must be identical to that of the DIJ being processed and the order of documents in the compound PDF file MUST match the order of the message descriptions in the DIJ.
    • In the case of individual PDF files, if the PDF file to be attached to the first message described in the DIJ is main_part_of_DIJ_filename_0000001.PDF, the remaining PDF files must be named incrementally. The numbering in the individual PDF filenames must match the order of the message descriptions in the DIJ being processed. By default, this will always be the case provided that the compound or split PDF and DIJ are generated by the same Generate job. Additional content verification based on Document Instance ID can be configured in an Outbound Profile to guarantee that the correct content is always attached to a given message.