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

Automatic Calculation of FTE while HDL Worker Load

Full-time equivalent (FTE) is an important component when we load worker data in Oracle fusion using HCM Data Loader(HDL). F ull-time equivalent (FTE) value gets calculated by diving the assignment normal working hours by standard working hours of employee. You can refer  Loading Worker object using Fusion HCM Data Loader(HDL)   article to see steps to load worker. During the migration, we can either migrate the FTE using the AssignmentWorkMeasure Metadata of Worker file from the legacy system or we can request FTE to be calculated  automatically. We will see how can request FTE to be calculated automatically while doing the Data Migration. We need to include the  following  instruction in Worker.dat file to calculate FTE automatically while loading worker. SET CALCULATE_FTE Y; Worker file will look like as below: Once this file gets loaded the FTE of employee will be automatically calculated. Please see the screenshot of employee from UI We had not pa...
Post a Comment
Read more