Scribd
Upload
9 views12 pages

Workflow Notification Template Guide

This document provides guidelines for modifying RTF subtemplates used in workflow notifications within a business intelligence catalog. Users are instructed to create copies of the subtemplate for customization to avoid losing changes during updates and to follow specific steps to prevent hyperlink updates in Microsoft Word. Additionally, it includes instructions for placing logos, creating action buttons, and defining report metadata, along with backward compatibility definitions.

Uploaded by

Bablu Chetan
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
9 views12 pages

Workflow Notification Template Guide

This document provides guidelines for modifying RTF subtemplates used in workflow notifications within a business intelligence catalog. Users are instructed to create copies of the subtemplate for customization to avoid losing changes during updates and to follow specific steps to prevent hyperlink updates in Microsoft Word. Additionally, it includes instructions for placing logos, creating action buttons, and defining report metadata, along with backward compatibility definitions.

Uploaded by

Bablu Chetan
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

It is important not to modify hyperlinks in the subtemplate file because changes to these can affect the functionality of the template, potentially disrupting the workflow notifications. Maintaining the hyperlinks as specified ensures that all actions and links behave as intended .

To prevent unintentional overwriting during release updates when modifying an RTF subtemplate in the BI catalog, a copy of the predefined subtemplate should be made and placed under Shared Folders/Custom/Common Content/Templates. Modifications should then be made to this copy rather than the original file. It is also important to deselect the 'Update links on save' checkbox in Microsoft Word before saving a local copy to avoid issues with hyperlinks .

Transaction details are linked within the table footer by defining data models that limit the number of records displayed in the report output. If the limit is exceeded, a link is provided to access the transaction details page, which enables users to view comprehensive information without cluttering the report output .

For deploying conditional logos in BI catalog subtemplates, the logos should be placed between specific conditional form fields such as IS_ONLINE and END_IS_ONLINE. It's crucial to remove conditional form fields like LOGO_C and LOGO_EC and adhere to image size constraints, ensuring the visual integrity of logos in different environments .

To configure action buttons like 'Approve' or 'Reject' in workflow notifications, parameters such as actionLink1Text, actionLink1href, and actionLink1Style should be set in the subtemplate. For 'Approve', the parameter string would be set to 'Approve' with an associated mailto link. The styling is set to 'Positive' for 'Approve' and 'Negative' for 'Reject' .

Handling backward compatibility involves avoiding the use of certain definitions included in the subtemplate. This is important as it ensures the template continues to function as intended across different software versions, preventing disruptions from deprecated functions or incompatible code .

Disabling the 'Update links on save' option in Microsoft Word helps prevent automatic updates to links within the document, ensuring that the hyperlinks and associated formatting included in the subtemplate are preserved without alteration when saving locally .

Report metadata tags like FusionNotificationReportName and FusionNotificationReportPath serve the purpose of dynamically loading the report name and path into notifications. These tags ensure that specific report details are consistently and accurately included in the notification, aiding in tracking and reference .

Images should be placed between the conditional form fields IS_ONLINE and END_IS_ONLINE in the subtemplate, with a maximum width of 200 pixels to ensure proper rendering in emails. The image size should not be adjusted using Microsoft Word to avoid rendering issues .

Footer links within the subtemplate should be managed by defining parameters such as footerLink1Text and footerLink1href to ensure clarity and usability. These links should be rendered appropriately in online settings, controlled via parameters such as footerLinkRenderInOnline, thus maintaining consistency across different outputs .

You might also like