Format of the Unica Insights Reports

List report styles

Use the styles included with the global report style sheet, GlobalReportStyles.css, to format list reports. The following table shows formatting from the GlobalStyleSheet.css style sheet for list reports.

<chartPalette>
<chartColor value="#6B80BE"/>
<chartColor value="#DDBB4D"/>
<chartColor value="#9CAC61"/>
<chartColor value="#78BF79"/>
<chartColor value="#7D5AA6"/>
<chartColor value="#efc100"/>
<chartColor value="#aeb8b8"/>
<chartColor value="#4178be"/>
</chartPalette>

Additionally, when you create a new list report, use the following guidelines to match existing reports:

• Use List Headers (not List Footers) to display summarization at the object level.
• Manually right-justify any numbers that are displayed in List Headers. Unlike List Footers, List Headers are not separated into the outer component and summary component, which use a right-justified style by default. When you summarize information into a List Header, you must complete the extra step and right-justify the values.
• Optionally, add 2px solid Grey borders to group columns.

The following example shows a list report that does not use the global styles:

Date formats for English versions

If you use a globalized version of the HCL Unica reports package, you see a different date format in your list reports depending on which locale you use. Unica Insights list reports use the date style medium.

The following table shows the date formats for list reports for all available locales.

Unica Insights list reports date formats for globalized versions

Crosstab report styles

Use the styles included with the global report style sheet, GlobalReportStyles.css, to format crosstab reports.

The following table shows formatting from the GlobalStyleSheet.css style sheet for crosstab reports:

Additionally, when you create a new list report, use the following guidelines to match the existing reports.

• Use 2px grey borders to separate summarization from measures.
• Use 2 px grey borders to group logical column groupings.
• As a general guideline, avoid summarizing both columns and rows in the same report.

The following example shows a crosstab report that uses the global styles and has 1.5 px borders that are applied to show column groupings.

Chart styles

Use the styles included with the global report style sheet, GlobalReportStyles.css, to format charts.

The following table shows formatting from the GlobalStyleSheet.css style sheet for charts:

Charts obtain the following formatting from the GlobalStyleSheet.css.

Additionally, when you create a new chart, use the following guidelines to match the existing chart reports.

• Use the default width, unless there is more than one chart on the report. When you include multiple charts in a single report, set the chart width to 750px.
• To use gradients and color palettes, copy and paste the strings from the table in “Global report styles” into the XML report specification.
• As a general guideline, select the chart type based on the data that you expect to be returned.
  • Use line graphs as the chart type only when you can guarantee the report retrieves continuous data.
  • If there are multiple series, a stacked bar works better than a non-stacked bar.
  • As a best practice, use percentages only when the total percentage equals 100%. Pie charts tend to confuse people when the values do not add up to 100%.
• If there are only two series on a chart and you display both the Y1 and Y2 axes, as a best practice you must match the colors to the first two palette colors for the axis labels.

The following example shows a chart that uses the global styles and has additional formatting applied.

Chart styles

Use the styles included with the global report style sheet, GlobalReportStyles.css, to format charts.

The following table shows formatting from the GlobalStyleSheet.css style sheet for charts:

Charts obtain the following formatting from the GlobalStyleSheet.css.

Additionally, when you create a new chart, use the following guidelines to match the existing chart reports.

• Use the default width, unless there is more than one chart on the report. When you include multiple charts in a single report, set the chart width to 750px.
• To use gradients and color palettes, copy and paste the strings from the table in “Global report styles” into the XML report specification.
• As a general guideline, select the chart type based on the data that you expect to be returned.
  • Use line graphs as the chart type only when you can guarantee the report retrieves continuous data.
  • If there are multiple series, a stacked bar works better than a non-stacked bar.
  • As a best practice, use percentages only when the total percentage equals 100%. Pie charts tend to confuse people when the values do not add up to 100%.
• If there are only two series on a chart and you display both the Y1 and Y2 axes, as a best practice you must match the colors to the first two palette colors for the axis labels.

The following example shows a chart that uses the global styles and has additional formatting applied.

Date formats for English version

If you use a globalized version of the HCL Unica reports package, you see a different date format in your chart reports depending on which locale you use. Unica Insights chart reports use the date style short.

The following table shows the date formats for chart reports for English locale.

Unica Insights chart reports date formats for English version

Dashboard report styles

Dashboard reports use the global styles with some manual formatting.

Use the following guidelines to make sure that reports that are displayed in the Dashboard fit properly in Dashboard portlets.