Data Syntax

Content may contain "markers" that indicate places where data will be substituted for the markers. The marker is expressed as an HTML custom tag: <comms-data/> that contains a JSON object named "$Data". The JSON $Data object has an Id attribute.

The Id attribute is the name of the Field defined in the Assembly Template.

Example: <comms-data>$Data{"Id":"PolicyHolder"}</comms-data>

Presentation Formatting

Data in the source file may not be formatted in the desired presentation format. The data "markers" may contain an optional "format" attribute which will adjust the incoming data to match the desired presentation format.

Example:

<comms-data>$Data {"Id":"PolicyExpiry","Type":"Date","Format":"MM-dd-yyyy"}</comms-data>

Date Formatting

• Data

  JSON does not support a date type. Data must be provided as a string value. It must be in the format of yyyy-MM-dd following the ISO standard where the first four characters are year followed by a dash followed by 2-digit month followed by a dash followed by 2-digit day. If the incoming 'date' is not in this pattern the subsequent 'format' attribute will be ignored and the data will be displayed as provided.

• Masking Characters

The following existing numeric masks will also apply in the same manner as previously described when mingled with date masks.

Examples

If date value in incoming data is 2021-01-23 the output for each format example is as follows:

DateTime Format

DateTime

Communication Cloud Service supports "DateTime" type field. The input date timestamp feed must follow the ISO standard data format as shown in below table so that the Communication Cloud Service can apply the time formatting.

Following is the syntax to define time formatting functionality within a <comms-data> tag:

Syntax

<comms-data>$Data{"Id":"RequestDateTimeStamp", "Type":"DateTime", "Format":"yyyy-MM-dd-'T'-HH-mm-ss-SSS z"}</comms-data>

Masking Characters

DateTime format

Examples

Following are some of the examples to illustrate how Communication Cloud Service formats the time data according to the defined configuration and the way how input is passed to the service:

Examples of DateTime

{
	"$$Id": "SamplePackage",
	"Fields": [{
			"Name": "InputTimeStamp",
			"Path": "$.InputTimeStamp"
		}]
} 

Content: <comms-data>$Data{"Id":"InputTimeStamp", "Type":"DateTime", "Format":"MMM dd yyy HH' hrs 'mm' mins 'ss' seconds'"}</comms-data> 
Preview Data: { "InputTimeStamp":"2024-04-17T04:22:58.175Z" } 
Output: Apr 17 2024 04 hrs 22 mins 58 seconds

Content: <comms-data>$Data{"Id":"InputTimeStamp", "Type":"DateTime", "Format":"MMM dd yyyy'T'HH:mm VV", "TimeZone":"Libya"}
Preview Data: { "InputTimeStamp":"2024-04-17T04:22:58.175Z" } 
Output: Apr 17 2024T06:22 Libya

Content: <comms-data>$Data{"Id":"InputTimeStamp", "Type":"DateTime", "Format":"yyyy-MM-dd'T'HH:mm:ss.SSSz"}</comms-data>  
Preview Data: { "InputTimeStamp":"2024-04-17T04:22:58Z" } 
Output: 2024-04-17T04:22:58.000Z