You can control certain aspects of the initial state of new views that are added to an analysis and of new objects that are added to a dashboard page.
For example, you can add a default footer to new analyses and set defaults for dashboard sections. You control these aspects by customizing the appropriate XML message files to override the default values that are specified during installation.
This section describes the XML message files to customize to override the view defaults distributed with Oracle BI Presentation Services.
For analyses, the file answerstemplates.xml includes a message named kuiCriteriaDefaultViewElementsWrapper from within kuiAnswersReportPageEditorHead. This message includes two additional messages, kuiCriteriaDefaultViewElements, in which you can define default values, and kuiCriteriaDefaultViewElementsMask, in which masks are defined. The mask XML message is protected and you cannot modify its contents.
The wrapper message adds the combined XML into a JavaScript variable, kuiDefaultViewElementsXML, that is used to apply the new default values.
For dashboards, the file dashboardtemplates.xml includes a message named kuiDashboardDefaultElementsWrapper that adds XML into a JavaScript variable named kuiDefaultDashboardElementsXML for use within the dashboard editor.
The following sections provide examples of customizing default values.
To cause these customizations to take effect, either stop and restart the server for Oracle BI Presentation Services, or click the Reload Files and Metadata link on the Administration page.
You can specify that default headers and footers are displayed on all new analyses.
For example, footers can contain messages such as a confidentiality notice, the company's name, and so on. You can specify a default header or footer by creating an XML message that specifies the text and formatting to apply.
The following XML code example creates a footer that contains the text "Acme Confidential" in bold, red letters.
<?xml version="1.0" encoding="utf-8"?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web.messageSystem">
<WebMessageTable system="Answers" table="ViewDefaults">
<WebMessage name="kuiCriteriaDefaultViewElements" translate="no"><HTML>
<view signature="compoundView" >
<pageProps pageSize="a4">
<pageFooter showOnDashboard="true" show="true">
<zone type="top"><caption>[b]Acme Confidential[/b]</caption>
<displayFormat fontColor="#FF0000"/></zone>
</pageFooter>
</pageProps>
<pageProps pageSize="a4">
<pageFooter showOnDashboard="true" show="true">
<zone position="top">
<caption fmt="html">
<text>[b]Acme Confidential[/b]
</text>
</caption>
<displayFormat>
<formatSpec hAlign="center" fontColor="#FF0000"/>
</displayFormat>
</zone>
</pageFooter>
</pageProps>
</view>
</HTML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
The results of an analysis are displayed when editing views of data. If you prefer that the content designer explicitly asks to view the results, then you can create an XML message that specifies that auto-preview is disabled when new views are created.
The content designer can still click the Display Results link to view the results when editing a view.
Note:
You can add signature entries for various views to the XML code. You can locate the signature value for a view in the XML representation of the analysis. While editing an analysis, see the analysis XML field on the Advanced tab of the Analysis editor. Look for the xsi:type attribute of the <saw:view> element. The signature value is the value without the "saw:" prefix.
The following XML code example disallows the auto-previewing of results when working with a view in Answers.
<?xml version="1.0" encoding="utf-8"?> <WebMessageTables xmlns:sawm="com.siebel.analytics.web.messageSystem"> <WebMessageTable system="Answers" table="ViewDefaults"> <WebMessage name="kuiCriteriaDefaultViewElements" translate="no"><HTML> <view signature="tableView" showToolBar="true" showHeading="true /> <view signature="pivotTableView" autoPreview="false" /> <view signature="titleView" autoPreview="false" /> <view signature="viewSelector" autoPreview="false" /> <view signature="htmlviewnarrativeView" autoPreview="false" /> <view signature="tickerview" autoPreview="false" /> <view signature="htmlview" autoPreview="false" /> <view signature="dvtchart" autoPreview="false" /> <view signature="dvtgauge" autoPreview="false" /> <view signature="dvtfunnel" autoPreview="false" /> <view signature="trellisView" autoPreview="false" /> </HTML> </WebMessage> </WebMessageTable> </WebMessageTables>
The results of a newly formed analysis are displayed as a title view followed by either a table or pivot table in a compound layout.
A table is created if the analysis contains only attribute columns, and a pivot table is created if the analysis contains at least one hierarchical column.
You can create an XML message that specifies that the compound view defaults to a different assemblage of views, such as a narrative followed by a graph. The content designer can still add and rearrange views within the compound layout.
The following XML code example sets the default compound layout to a narrative followed by a graph.
<?xml version="1.0" encoding="utf-8"?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web.messageSystem">
<WebMessageTable system="Answers" table="ViewDefaults">
<WebMessage name="kuiCriteriaDefaultViewElements" translate="no"><HTML>
<view signature="compoundView" >
<cv signature="narrativeView" />
<cv signature="dvtchart" />
</view>
</HTML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
By default, the results of drilling in a dashboard are displayed on a new page, section names are not displayed in the dashboard, and sections can be expanded and collapsed.
You can change these default values by creating an XML message that specifies that new default values for the dashboard section. A content designer who edits the dashboard can still modify this behavior using the options within the dashboard editor.
The following XML code example makes section heads visible, enables drilling, and does not allow sections to collapse.
<?xml version="1.0" encoding="utf-8"?> <WebMessageTables xmlns:sawm="com.siebel.analytics.web.messageSystem"> <WebMessageTable system="Answers" table="ViewDefaults"> <WebMessage name="kuiDashboardDefaultElements" translate="no"><HTML> <element signature="dashboardSection" drillInline="true" showHeading="true" collapsible="false" /> </HTML> </WebMessage> </WebMessageTable> </WebMessageTables>
By default, dashboards are printed without headers or footers and in a portrait orientation.
If you prefer that newly added dashboard pages default to having a custom header and footer and print in landscape orientation, then you can create an XML message that specifies these characteristics. A content designer who edits the dashboard can still modify this behavior using the options within the dashboard editor.
The following XML code example adds a custom header and footer to a dashboard page and specifies landscape orientation.
<?xml version="1.0" encoding="utf-8"?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web.messageSystem">
<WebMessageTable system="Answers" table="ViewDefaults">
<WebMessage name="kuiDashboardDefaultElements" translate="no">
<HTML>
<element signature="dashboardPage" personalSelections="false">
<pageProps orientation="landscape" printRows="all" pageSize="a4">
<pageHeader showOnDashboard="true" show="true">
<zone position="top">
<caption>[b]Acme is Cool[/b]</caption>
<displayFormat>
<formatSpec fontSize="9pt" hAlign="center"
fontColor="#FFFFFF" backgroundColor="#000000"/>
</displayFormat>
</zone>
</pageHeader>
<pageFooter showOnDashboard="true" show="true">
<zone position="top">
<caption>[b]CONFIDENTIAL[/b]</caption>
<displayFormat>
<formatSpec fontSize="7.5pt" hAlign="center"
fontColor="#999999" borderColor="#CC99CC" fontStyle="italic"
borderPosition="all" borderStyle="single"/>
</displayFormat>
</zone>
</pageFooter>
</pageProps>
</element>
</HTML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>