Some Oracle Fusion HCM features look small in the release notes, but their real value becomes clear when you connect them to the actual business problem. This is one such feature.

Earlier, when an employee updated passport details, visa information, marital status, national identifiers, or other personal information, they can attach a supporting document as part of the transaction. But in most cases, that attachment mainly helped during approval. Once the transaction was completed, the document was not retained in a way that helped for future reference.

That created a product gap.

To handle this, customers usually followed one of two approaches. In the first approach, the employee updated the personal information on the page, completed the transaction, and then separately went to Document Records to upload the same supporting document again. In the second approach, customers used Document Records as the starting point and built a custom loopback solution to move the information into the relevant personal information section.

Both approaches worked, but neither was ideal.

With Oracle 26B, this gap is addressed in a much better way. Oracle has expanded Document Records integration so that supporting documents can now be retained directly from more Personal Details and Identification Info sections. This means the document can stay connected to the business process in a much more meaningful way.

What has changed?

Oracle has expanded this integration to the following sections:

Personal Details

• Demographic Info
• National Identifiers
• Biographical Info

Identification Info

• Citizenship
• Passports
• Visas and Permits
• Driver’s Licenses

This is the real improvement. The attachment is no longer just an approval-time file. It can now be retained through Document Records for future reference.

Why this matters

This enhancement can make a big difference for customers who need supporting documents to remain available along with updates such as:

• Passport renewal
• Visa updates
• Citizenship changes
• Marital status changes
• National identifier updates

Earlier, even if the document was attached during the transaction, customers often had to do extra work later to retain it properly. Now Oracle brings that process much closer together.

How it works

The Document Records region is not visible by default. It must be enabled through a page property in VB Studio.

Once enabled, the user can:

1. Update the relevant personal or identification information
2. Enter a document name
3. Upload one or more attachments

Oracle then creates the Document Record using the configured document type, and the attachments are stored there. Users can later open the Document Records action from the section and preview or download the retained files.

This gives a much cleaner user experience compared to the older manual or custom approaches.

Important points to remember

1. Document type setup matters

The document type selected in the page property should be chosen carefully. Once used, it is better not to keep changing it, because older records created under a different document type may no longer appear in that section.

2. Only basic document retention is supported

This integration is meant for simple attachment retention. If the customer expects advanced document features, the standalone Document Records page is still the better option.

3. Effective-dated behaviour is important

For effective-dated sections, if an attachment is added to one row, it can appear across other effective-dated rows of that object. If it is removed, it is removed completely.

4. Approval attachments and retained documents are different

When approvals are enabled, users may see two attachment regions. One is for the retained Document Record. The other is only for the approval transaction and is not retained after approval.

5. Security must be in place

Users need the required Document Records privilege to see and use this region.

Why customers will like this feature

This update can reduce duplicate effort for employees and HR teams. It can also reduce the need for some custom loopback solutions that were built only to make sure supporting documents were retained properly.

That is why this is more than just another page enhancement. It closes a long-standing functional gap in a very practical way.

Conclusion

Oracle 26B has improved the way supporting documents are handled during personal information updates.

Earlier, attachments were often useful only during approval, which forced customers into manual re-upload steps or custom solutions. Now, with Document Records integration expanded to more Personal Details and Identification Info sections, Oracle has made the process much more complete.

It is a small-looking enhancement, but for many customers, it can create a big impact.