Scribd
Upload
41 views12 pages

BI Notification Report Template Guide

This document provides definitions and instructions for modifying a report layout subtemplate file in Microsoft Word. Any changes should be made to a copy of the file rather than the original. The document also contains snippets of code for common elements like logos, action buttons, footers, and report metadata that can be incorporated into templates.

Uploaded by

trivenicat
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
41 views12 pages

BI Notification Report Template Guide

This document provides definitions and instructions for modifying a report layout subtemplate file in Microsoft Word. Any changes should be made to a copy of the file rather than the original. The document also contains snippets of code for common elements like logos, action buttons, footers, and report metadata that can be incorporated into templates.

Uploaded by

trivenicat
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd

This subtemplate consists of various definitions, each containing a block of

formatting or commands that can be called from report layout templates for workflow
notifications.

Do not make changes directly to the RTF subtemplate file under Shared Folders/Common
Content/Templates folder in the business intelligence (BI) catalog. Any changes made directly to
the predefined subtemplate are overwritten during release updates.
Instead make a copy of that subtemplate, put the copy under Shared Folders/Custom/Common
Content/Templates in BI catalog, and modify the RTF file from the copy.

Do not modify any hyperlinks in this subtemplate [Link] saving a local copy of this file,
disable the Update links on save option in Microsoft Word.
1. Click File >Options >Advanced.
2. In the General section, click Web Options and open the Files tab.
3. Deselect the Update links on save check box.
The exact steps can vary depending on your version of Microsoft Word.
Internal Use
Do not edit, move or remove this part.
Common XSL Attributes Common Task Attributes
Logo
Place your logo in the blank space below, between the conditional form fields IS_ONLINE and
END_IS_ONLINE. Remove the conditional form fields LOGO_C and LOGO_EC.
<?template:FusionHeaderLogo?>LOGO_CIS_ONLINE

TS

END_IS_ONLINELOGO_EC<?end template?>
Your image must not be wider than 200 pixels. Do not adjust the size in Microsoft Word; the
image may not render properly in email.

The following example shows a logo in an appropriate size and location.


<?template:FusionOracleLogo?>C

TS

EC<?end template?>
Action Buttons
<?template:FusionApproveRejectLinks?><?
param:actionLink1Text;string(‘Approve’)?><?
param:actionLink1href;string(‘[Link]
param:actionLink1Style;string(‘Positive’)?><?
param:actionLink2Text;string(‘Reject’)?><?
param:actionLink2href;string(‘[Link]
param:actionLink2Style;string(‘Negative’)?><?
param:forceDisplayButtons;string(‘false’)?>C C

displayActionLink displayActionLink

ECC

TS
TSSubmit Info

ECEC<?end template?>

<?template:FusionActionLinks?><?
param:actionLink1Text;string(‘Approve’)?><?
param:actionLink1href;string(‘[Link]
param:actionLink1Style;string(‘Positive’)?><?
param:actionLink2Text;string(‘Reject’)?><?
param:actionLink2href;string(‘[Link]
param:actionLink2Style;string(‘Negative’)?><?
param:actionLink3Text;string(‘Request Information’)?><?
param:actionLink3href;string(‘[Link]
param:actionLink3Style;string(‘Neutral’)?><?
param:forceDisplayButtons;string(‘false’)?>C C

displayActionLink displayActionLink displayActionLink

ECC

TS TSSubmit Info

ECEC<?end template?>

<?template:FusionAction?><?param:actionLink1Text;string(‘Approve’)?><?
param:actionLink1href;string(‘[Link]
param:actionLink1Style;string(‘Positive’)?><?
param:forceDisplayButtons;string(‘false’)?>C C
TS
displayActionLink
ECC
TS
TSSubmit Info
ECEC<?end template?>
<?template:FusionActionButton?><?
param:actionLink1Text;string(‘Approve’)?><?
param:actionLink1href;string(‘[Link]
param:actionLink1Style;string(‘Positive’)?>CC
TS<?$actionLink1Text?>
ECC
TSReject
ECC
TSApprove
ECC
TSRequest Info
ECEC
CC
TS<?$actionLink1Text?>
ECC
TSReject
ECC
TSApprove
ECC
TSRequest Info
ECEC
CC
TS<?$actionLink1Text?>
ECC

TSReject
ECC
TSApprove
ECC

TSRequest Info
ECEC<?end template?>
Table Footer
Data models can be defined to limit the number of records displayed in the report output. If the
limit is exceeded, the table footer provides a link to the transaction details page.

<?template:FusionTableFooter?><?param:pMaxRowsToBeDisplayed;-1?><?
param:pTotalCount;-1?><?param:pTransactionDetails;string(‘’)?><?
param:pTblStyle;string(‘’)?><?param:pRenderAsLinks;string(‘true’)?>DTF
C ONE to X of Y itemsECC ONE to X of Y itemsEC
C ONE to X of Y itemsECC ONE to X of Y itemsEC
EC<?end template?>
Approvals
<?template:FusionHistoryRegion?>
TSORA_BIP_TOKEN_HISTORY_REGION_BIP_TOKEN
<?end template?>
Notification Footer Links
<?template:FusionFooterLinks?><?
param:footerLink1Text;string(‘Transaction details’)?><?
param:footerLink1href;.//BINDTRANSACTIONDETAILSLINK?><?
param:footerLink1RenderInOnline;string(‘false’)?><?
param:footerLink2Text;string(‘In-app notification’)?><?
param:footerLink2href;.//BINDWORKLISTURLLINK?><?
param:footerLink2RenderInOnline;string(‘false’)?>testIsOnline
TSC callFooterLinkTemplateEC callFooterLinkTemplate
EC<?end template?>
<?template:FusionRightFooterLink?><?param:footerLink1Text;string(‘’)?
><?param:footerLink1href;string(‘’)?><?param:
footerLinkRenderInOnline;string(‘false’)?> C C C <?$footerLink1Text?>ECC
Transaction detailsECC In-app notificationECECC C <?$footerLink1Text?>ECC Transaction
detailsECC In-app notificationECECEC<?end template?>
<?template:FusionLeftFooterLink?><?param:footerLink1Text;string(‘’)?
><?param:footerLink1href;string(‘’)?><?param:
footerLinkRenderInOnline;string(‘false’)?> C C C <?$footerLink1Text?> ECC
Transaction detailsECC In-app notificationECECC C <?$footerLink1Text?> ECC Transaction
detailsECC In-app notificationECECEC<?end template?>
Report Metadata

TS<?template:FusionNotificationReportName?><?param:reportName;.//
REPORT_NAME?>C <?$reportName?>EC<?end template?>
<?template:FusionNotificationReportPath?><?param:reportPath;.//
REPORT_PATH?>C <?$reportPath?>EC<?end template?>
Information Requested
<?template:FusionRequestInfoComment?>C
TSChkRequestInfoBINDREQUESTERNAME requested informationEC
ChkSubmitInfoBINDREQUESTERNAME submitted informationEC
REQUESTERCOMMENT
EC<?end template?>
Definitions for Backward Compatibility
Do not use the following definitions, which are included in this subtemplate for backward
compatibility purposes only.

Logo
Place your logo in the blank space below, between the definition statements.
<?template:FusionLogo?>

TS

<?end template?>
Your image must not be wider than 200 pixels. Do not adjust the size in Microsoft Word; the
image may not render properly in email.

Action Buttons
<?template:FusionApproveReject?>
ORA_BIP_APPROVE_START
T TSApprove TSReject
S
ORA_BIP_APPROVE_END
<?end template?>

<?template:FusionRequestInfo?>
ORA_BIP_APPROVE_START

TSApprove TSReject
TS TSRequest Info

ORA_BIP_APPROVE_END
ORA_BIP_SUBMIT_START

TS TSSubmit Info
ORA_BIP_SUBMIT_END
<?end template?>

Footer Links
<?template:FusionFooter?>
TSC Transaction detailsEC In-app notification
<?end template?>

Report Metadata
TS<?template:FusionReportName?> <?REPORT_NAME?> <?end template?>
<?template:FusionReportPath?> <?REPORT_PATH?> <?end template?>

Common questions

Powered by AI

When defining custom templates for workflow notifications in the BI catalog, it's crucial to consider how these templates will be organized under the Shared Folders/Custom hierarchy to prevent overwriting by updates. The templates must also be designed to align with the existing format and style guidelines specified for workflow notifications, ensuring that they integrate seamlessly. Custom templates should allow for easy modification and updates while maintaining functionality and compatibility with the overall workflow system .

Metadata templates in report notifications provide a structured way to manage and reference report-specific information such as the report name and path. By using these templates, the document ensures that critical metadata is consistently applied and easily accessible across various notifications. This approach not only aids in maintaining uniformity and reducing errors but also simplifies the process of updating and managing report-related data by centralizing metadata management within defined templates .

Logos should be placed in the designated space between the conditional form fields 'IS_ONLINE' and 'END_IS_ONLINE' within a subtemplate file. It is important to remove any other conditional form fields such as 'LOGO_C' and 'LOGO_EC' to ensure the image is displayed correctly. This placement is critical to maintain the proper structure of the template and ensure the logo appears correctly when the subtemplate is used .

To modify an RTF subtemplate for workflow notifications without altering the original file under Shared Folders/Common Content/Templates, a user should first make a copy of the subtemplate. This copy should then be saved under Shared Folders/Custom/Common Content/Templates in the BI catalog. Direct modifications to the predefined subtemplate will be overwritten during release updates, thus the copy provides a safeguard against such changes .

Hyperlink management in RTF templates for workflow notifications is critical as it directly affects how users interact with and navigate through notifications. Properly defined hyperlinks can lead users to the appropriate actions or information with ease, enhancing the overall user experience. On the other hand, misconfigured hyperlinks can lead to errors or misdirection, hampering efficiency. Ensuring that hyperlinks are correctly set up, maintained, and updated is essential for effective communication and operation within workflow notifications .

Data models should be configured to define a maximum number of records that appear in the report output. When this threshold is exceeded, the table footer plays a vital role by providing a link to the transaction details page, allowing users to access full data beyond what is displayed. This helps in managing large datasets effectively within reports, ensuring users can access complete information without burdening the report layout with excessive data .

Backward compatibility definitions are included in the RTF subtemplate to support older systems and integrations that may require them. However, they are not intended for current use, as relying on outdated definitions can cause issues with the update process or create inconsistencies in the template's operation. By not using these outdated definitions, users can ensure that their templates remain aligned with the latest standards and practices, promoting better performance and compatibility with current systems .

Action buttons in the document serve to streamline user interactions within workflow notifications by providing quick and direct options for users to respond to tasks such as approving, rejecting, or requesting information. They are created using specific templates that take parameters such as text, hyperlinks, and styles, ensuring that the buttons are properly integrated and styled within the notification framework. This enhances efficiency by embedding actionable items directly into the notifications, reducing the need for additional steps to complete these tasks .

Disabling the 'Update links on save' option in Microsoft Word is important to prevent automatic changes or updates to hyperlinks and formatting when a local copy of the RTF file is saved. This ensures that the document's integrity and reference links remain intact, especially when modifications are made for workflow notifications .

The document advises that logos should not be wider than 200 pixels to ensure proper rendering in email. It also cautions against adjusting the size of the image within Microsoft Word as this might lead to improper rendering .

You might also like