Document Records

Personalization- Frequently
Asked Questions

March 29, 2022 | Version 1.02

Copyright © 2022, Oracle and/or its affiliates
Confidential - Public
PURPOSE STATEMENT
This document addresses the most frequently asked questions for the Document Records personalization options in HCM
Cloud.

DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of
Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software
license and service agreement, which has been executed and with which you agree to comply. This document and
information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without
prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the implementation
and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document
without risking significant destabilization of the code.

DISCLAIMERS FOR PRE-RELEASE, PRE-GA PRODUCTS

The revenue recognition disclaimer on this page is required for any document that addresses future functionality or for
products that are not yet generally available (GA). If you are unsure whether your statement of direction needs the
disclaimer, read the revenue recognition policy. If you have further questions about your content and the disclaimer
requirements, e-mail [email protected].
The testing disclaimer in the copyright section on the last page (highlighted in yellow) is provided by the FCC for hardware
products. It must appear in the copyright section for all pre-release, pre-GA hardware products. Be sure to remove the
yellow highlighting before publishing. When the product becomes GA, update your collateral by removing the disclaimer
from the copyright section. If your product is already GA or if you are writing about a software product, delete the disclaimer
from the copyright section.
Important: If your product is not GA, then you cannot include any regulatory compliance information in the statement of
direction. Regulatory compliance information may be included for GA products only if you have completed all required
safety and emissions testing, and you have received the certificates issued by the testing organization

Note: In the images or examples included in this document regarding: user details, company names,
addresses, emails, and/or telephone numbers represent a fictitious sample of data (based upon made up
data used in a demo environment). Any similarity to actual persons, living or dead, is purely coincidental and
not intended in any manner.

1 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02

Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
TABLE OF CONTENTS
Purpose Statement 1
Disclaimer 1
Disclaimers For Pre-Release, Pre-GA Products 1
Frequently Asked Questions 3
Appendix 6
Appendix 1 - Document Records - Reset Customization of Edit & Delete Buttons 6
Appendix 2 - Document Records - Delete Customization 8

2 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02

Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
FREQUENTLY ASKED QUESTIONS
# QUESTION ANSWER

1 Is it possible to hide the flexfield context when a Yes, it is possible to hide or make the context code read-only when a
document type is selected for creating a document record for a document type is created. However, the context
document record? code will be hidden or read-only for all document types and not just for the
one selected. It is not possible to selectively hide a flexfield context code
using an EL expression.

2 I have multiple flexfield contexts. Can I display Contexts are configured for the single document record flexfield
only one context code for a document type and (PER_DOCUMENTS_OF_RECORD_DFF), and not for individual document
hide the list of other context codes? types.
What can and cannot be done with flexfields is determined by the flexfield
framework. And the framework doesn’t support restricting the list of values
in the context code field. It supports only defaulting of context values in
that LOV.
What is currently possible is to hide or make the context code read-only on
the document record UI. However, if you do this, the context code will be
hidden or read-only for all document types. It is not possible to selectively
hide the flexfield context code using an EL expression.

3 How can the document record flex context be You can use an EL expression to hide document record flex context for
hidden based on a role? specific roles.
For example, to hide the flex context for employees but display it only if the
user has a HR specialist role:
EL expression syntax: #{securitycontext.userinrole[‘role_name1, role
name2, role_name3, ….']}

4 Are the field labels customizable by Document Dynamically changing the labels based on document type isn't available
Type? Example, for passport, could From/To Date out-of-the-box.
be changed to Issue/Expiry Date?
However, customers can explore page composer personalization, using
expression language code, to make these label changes specific to
document types. Doing so will impact the time taken to load the page.

5 Is it possible to identify within an EL that the page No. This is not possible.
is a Document Records page?

6 Is it possible to identify within an EL, the Yes.

document type being selected on the Document
 If you are personalizing the Add Document page, then use
Records page?
#{bindings.DocumentType.attributeValue}

 If you are personalizing the Edit Document page, then use

#{bindings.DocumentType.inputValue}

7 How can I hide the Delete button only on the While in a sandbox, switch to source mode. Click besides the Delete button.
Document Records page? In the structure window, scroll up to find the simplePanel [close] option and
click on the CLOSE option.
Select universalPanel and click Edit properties option.
In the popup for the Primary Action, click on the drop-down option and
select Expression Builder.

3 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02

Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
 # QUESTION ANSWER

Specify the expression as null.

Click on OK and close the properties popup with OK.

8 How do I hide the Delete button when viewing On the document records EDIT page:
document record for someone else?
'#{bindings.PersonId.inputValue}' returns the DOR record owner.
'#{HcmFusePlusBean.userPersonId}' returns the login person .
'#{HcmFusePlusBean.userPersonId ne bindings.PersonId.inputValue}'
returns 'true' if the login person is viewing other person's document record.
So, you can write an EL expression as follows on the Delete button to hide
it:
'#{HcmFusePlusBean.userPersonId ne bindings.PersonId.inputValue}'

9 Can I add worker identification information in the Yes, you can use these values to display worker identification information in
page header for document records flow and the page header:
document delivery preference flow?
BINDING PARAMETER EXPRESSION

Display Name #{bindings.DisplayName.inputValue}

Person Number #{bindings.PersonNumber.inputValue}

Assignment Number #{bindings.AssignmentNumber.inputValue}

Assignment Name #{bindings.AssignmentName.inputValue}

(Business Title)

For a worked example, refer to the following topic in the Employment

chapter of the Implementing Global Human Resources guide: Personalize
the Universal Header for Employment Flows

10 My personalization done on the Add Document The Add Document and Edit Document are two different pages. Hence you
page does not reflect on the Edit Document page. need to personalize both the pages.
Why?

11 Why are the Edit and Delete buttons not being 1. Check for customizations done for the page via Manage
displayed according to the manage/view roles Configurations. Search for those pages. If the page has a download
assigned to the user? option, then the page has customization. You need to verify the
customization done and correct or revert accordingly.

2. Check for security configuration in Document ID 2594767.1

These are the queries to verify the data security privileges for the logged in
user’s session:
select session_cookie from
(select session_cookie from fnd_sessions
where upper(user_name) = upper('<loginUser>')
and last_update_date >= trunc(sysdate)-2
order by last_update_date desc)
where rownum < 2;
SELECT ROLE_NAME, FUNCTION_NAME,

4 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02

Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
 # QUESTION ANSWER

NVL(MAX(DECODE(OBJ_NAME, 'PER_ALL_PEOPLE_F',PREDICATE,
NULL)),'1=2') PERSON_PRED,
NVL(MAX(DECODE(OBJ_NAME,
'HR_DOCUMENTS_OF_RECORD',PREDICATE,'HR_DOCUMENT_DELIVERY_PREFS
',PREDICATE, NULL)),'1=2') DTYPE_PRED
FROM
(SELECT FG.ROLE_NAME, FFF.FUNCTION_NAME, FO.OBJ_NAME
OBJ_NAME,
NVL(FOIS.PREDICATE, decode(instance_type, 'GLOBAL', '1=1',
'1=2')) PREDICATE
FROM FND_GRANTS FG,
FND_OBJECTS FO,
FND_FORM_FUNCTIONS FFF,
FND_MENU_ENTRIES FME,
FND_OBJECT_INSTANCE_SETS FOIS,
FND_SESSIONS S,
FND_SESSION_ROLE_SETS SRS
WHERE FFF.FUNCTION_ID = FME.FUNCTION_ID
AND FG.GRANTEE_KEY = SRS.ROLE_GUID
AND FME.MENU_ID = FG.MENU_ID
AND FO.OBJECT_ID = FFF.OBJECT_ID
AND FO.OBJECT_ID = FG.OBJECT_ID
AND FOIS.INSTANCE_SET_ID(+) = FG.INSTANCE_SET_ID
AND FG.ROLE_NAME = SRS.ROLE_NAME
AND trunc(sysdate) BETWEEN FG.START_DATE AND
NVL(FG.END_DATE, trunc(sysdate)
AND ((FO.OBJ_NAME IN (
'PER_ALL_PEOPLE_F','HR_DOCUMENTS_OF_RECORD')
AND FFF.FUNCTION_NAME LIKE '%PERSON_DOCUMENTATION%') OR
(FO.OBJ_NAME IN (
'PER_ALL_PEOPLE_F','HR_DOCUMENT_DELIVERY_PREFS')
AND FFF.FUNCTION_NAME LIKE '%PERSON_DOCUMENT_DELIVERY%') )
AND FFF.FUNCTION_NAME = 'PER_MANAGE_PERSON_DOCUMENTATION_DATA
AND S.SESSION_ROLE_SET_KEY = SRS.SESSION_ROLE_SET_KEY
AND S.SESSION_COOKIE = '<sessionCookie>' )
GROUP BY ROLE_NAME, FUNCTION_NAME;

12 Why do I get an ADF error when clicking on the If there are any customizations at the ADF central component levels such as
Add button on the Document Records page or universal panel, or any document records related attributes, then it can lead
when clicking on Edit button on the page? to errors for certain users for whom the expression evaluates to false.
Pages:
/oracle/apps/hcm/documentsOfRecord/core/ui/responsive/page/Res
pManageDocumentsOfRecord.jsff
/oracle/apps/hcm/documentsOfRecord/core/ui/responsive/page/Res
pEditDocumentsOfRecord.jsff
/oracle/apps/hcm/documentsOfRecord/core/ui/responsive/page/Res
pCreateDocumentsOfRecord.jsff
/oracle/apps/fnd/applcore/patterns/ui/components/DefaultPanelP
F.jsff
In such cases, the customization of the ADF central component or
document records attributes needs to be corrected or reverted.
For details, refer Appendix 1 (Reset Customization of Edit and Delete
Buttons) and Appendix 2 (Delete Customization).

13 Why are certain customizations done for a specific If there are any customizations at the ADF central component levels such as
button reflecting in other pages (Ex: Organization universal panel, or any document records related attributes, then it can lead
Chart)? to errors for certain users for whom the expression evaluates to false.

5 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02

Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
 # QUESTION ANSWER

Page:
/oracle/apps/fnd/applcore/patterns/ui/components/DefaultPanelP
F.jsff
In such cases, the customization of the ADF central component or
document records attributes needs to be corrected or reverted.
For details, refer Appendix 1 (Reset Customization of Edit and Delete
Buttons) and Appendix 2 (Delete Customization).

APPENDIX

Appendix 1 - Document Records - Reset Customization of Edit & Delete Buttons

1. Create sandbox with Page Composer option, enter the sandbox.
2. Navigate to Document Records - View/Edit page and click Edit Page from Settings and Actions menu.
3. Switch to the Source View and click on Header section (where Delete button is added with customization).
4. In the source section, select the commandToolbarButton: Delete and click the Show Properties popup.

5. If there is customization for the Visible or Show Component (with blue dot) beside it, then click the drop-down
menu beside the field and click Reset.
6. Verify the page and publish the sandbox.

6 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02

Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
7 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02
Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
Appendix 2 - Document Records - Delete Customization
1. Create the sandbox with Page Composer option and enter the sandbox.
2. Navigate to Document Records - View/Edit page and click Edit Page from Settings and Actions menu.
3. Switch to the Source View.
4. Click beside the Delete button, and in the source window shown below scroll completely to the top till the
SimplePanel is found.

5. Click Close beside the simplePanel.

8 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02

Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
 6. Click universalPanel and settings.

7. In the Properties popup, scroll to find the Primary Action and in Expression builder, specify the required condition.

8. If this button is not to be shown for anyone, then set it as false.

9. Click OK, and verify and publish the sandbox.

9 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02

Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
10 DOCUMENT | Document Records Personalization- Frequently Asked Questions | Version 1.02
Copyright © 2022, Oracle and/or its affiliates | Confidential - Public
CONNECT WITH US
Call +1.800.ORACLE1 or visit oracle.com.
Outside North America, find your local office at oracle.com/contact.

blogs.oracle.com facebook.com/oracle twitter.com/oracle

Copyright © 2022, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group. 0120

Document Records Personalization- Frequently Asked Questions

March, 2022
Author: Aliasgar Khambhaty
Contributing Authors: Shweta Ganguly