Skip to main content

Dynamic Password Protected report output (Part 2)

This post is in continuation of Password protected report output (Part 1) post where we discussed about generating the static password protected output. In this post we will go through steps to have dynamic password protected report output. This is a common requirement when a company send offer letter, payslips, appraisal letter etc in HCM. We might have also similar requirement when we send some bills to users.

Let's go through the required steps to enable the password protected report output.

1) Create a SQL Data Model which should have one column password like below query have NID

:

 

Note: We can have combination of one or more than one column as password.

2) Create a report for which we have to create a RTF template.

While creating the RTF template we need to setup word properties to enable the password for PDF.

Please follow the navigation: File > Info > Advance Properties > Custom


3) Add the below two properties:

Name

Value

xdo-pdf-security

true

xdo-pdf-open-password

{/DATA_DS/G_1/NID}


4) Upload the RTF template 

Now we will run the report for one employee and check the report output:



4) Enter the NID of employee the Document will open as :



Thanks for your time. I hope this will be helpful.

Labels:

Comments

Post a Comment

Popular posts from this blog

Loading External Bank Account Using HDL

There are general requirements for loading the External Bank Account for employees during the project implementation which will be used either for expenses or Payroll.  Let's go through the pre-requisite and steps for loading the External bank account using HDL Pre-Requisite: There is pre-requisite to generate party id before loading the External Bank Account.  1) We need to run the " Synchronize Person Records "  scheduled process by entering the details: This process should generate the Party Id for employee which have been migrated using HDL. 2) If Party Id is still not generated even after running the above process then run the " Maintain Party and Location Current Record Information " This process should generate the Party Id for employee which have been migrated using HDL. Once the Party Id is generated run Load the External Bank Account HDL file. Below is sample ExternalBankAccount.dat file: METADATA|ExternalBankAccount|BankNumber|BankName|BankBranchNumbe...
Post a Comment
Read more

Supported Keys in Oracle Fusion HCM Data Loader(HDL)

Today we will go through the few concepts of HCM Data Loader (HDL). HDL is data loading tool for Oracle fusion HCM. It helps us to do bulk loads during implementation projects or also for on going work. HDL works on predefined template provided by  Oracle.  Keys supported by HDL: 1) Source Key: Source Key is combination of  Source System Id and Source System Owner.  It can be used for both  Create  and  Update.      Source System Id: It is key to represent record uniquely. It can be one column or concatenation of column.      Source System Owner: It generally represents the source of data. We add the source name in Lookup type:   HRC_SOURCE_SYSTEM_OWNER. 2) User Key: These are columns available at object level which are user friendly.  It can be one column or combination of column. e.g Job Code and Set Code are user keys for Job. I t can be used for both  Create  and  Update. 3)  GUID...
Post a Comment
Read more