Content Configuration

4 Content Configuration

Content is the visible content that appears in the output. Content Configuration can be graphic or text:

String of text and numbers
Graphics
Variable data

Every Content configuration comprises of a base content and its version. You can create new versions of a Content from existing Content versions. Each Content version must have a unique name for identification which is used for packaging the communication output. You can also control when a content version will be used in a Package Assembly by setting the Active and Inactive dates.

In case of graphics, Communication Cloud Service supports PNG and SVG ( Scalable Vector Graphics) format which you can upload using the user interface. While choosing between PNG and SVG images, you should consider following criteria:

PNG images are pixel based whereas, SVG images are vector images.
You can use PNG images if image has lot of colors.
SVG images are made up of lines and shapes that can be scaled to any size without losing quality. These images have high quality and this file format is useful when you want to re-size images such as logos and icons.

For text type content, syntax can be used to reference variable data and support conditional inclusion logic. The data identifiers used in the referenced tags are defined in the Package Version Configuration’s Assembly Template as Fields.

Additional details on defining the identifiers (Fields) and mapping them to the client’s JSON data file is available in the Assembly Template Reference section. The Content author does not need to be familiar with the data structure or the data mapping in order to use the Fields. The author will need to know the Field’s purpose.

Predefined Fields

The Service provides a collection of predefined fields that provide access to data provided by the Service in addition to any field definitions defined in the Assembly Template. These fields are used in the same manner as user defined fields.