Working with message content

EngageOne™ Content Author is used for creating, maintaining and reviewing messages that provide dynamic content for publications produced by EngageOne™ Designer. This message content for EngageOne™ can be referenced (and shared) by document templates.

Message Content archives are created in EngageOne™ Content Author, and do not come from the same repository as templates and Active Content. Message Content is managed separately from templates and Active Content. Message Content must be imported into a Message Content folder.

Message Content that you import into EngageOne™ Server will not appear in EngageOne™ Designer, EngageOne™ Interactive, or any custom application that uses the editor.

Message Content that you import into EngageOne™ Server is tracked by Message Area IDs. Message Content is created and maintained in a framework set up by the EngageOne™ Content Author administrator. This includes projects and folders to which messages are added, and message areas for which messages are targeted. Message areas represent reserved space in document designs for which messages are scheduled for inclusion. They can be thought of as rectangles that define the maximum size of one or more messages. For more information about Message Content, see the EngageOne™ Content Author User’s Guide.

You can cut and paste Message Content from one Message Content folder to another. You cannot copy Message Content. You can also delete a Message Content if that content is not referenced by an active content or template. Moved or deleted Message Content items are shown in the history log.

If you have any problems creating or generating documents that contain Message Content, navigate to Templates, select the template, and then click the Resources tab. Expand the Message Area to view any missing resources. If there are missing resources, see Working with missing resources.

The following output devices are supported for Message Content:

Note: You must ensure that the device resources used in Message Content match the device resources used in templates. If the resources do not match, the Message Content will display missing resources.
  • AFPDS 240, 300, 600 - bitmap (FOCA) and outline (FOCA Type1)
  • HTML for e-mail (eHTML)
  • IJPDS 240, 300, 600
  • Line data
  • Metacode
  • PCL - bitmap and outline, black/white and color image
  • PDF 72 & 300
  • Postscript 72 & 300 - Type 1 & Type 42 (automatic)

These Designer resource features are not supported for Message Content:

  • Font subsetting for Postscript
  • Open Type Fonts (.otf fonts) using Compact Format compression
  • Windows Image types using AFP Object Containers