Recommended Free Tools
PeopleSoft’s Fluid Attachments Framework lets application transactions present files, URLs, and notes tied to application data. Implementing it involves more than adding an upload control: administrators configure authorization, attachment definitions and context keys, while developers connect the framework to the transaction and add custom logic where needed. Repository transfers and security are configured separately in PeopleTools.
What the Fluid Attachments Framework does
Oracle describes the attachment feature as enabling users to attach files, notes, and URLs to a PeopleSoft application. In the Fluid framework, administrators configure which attachment behaviors are available for application transactions and which roles may use them.
- Files: Previously created electronic files may be made available for users to download. Document definitions support uploading files associated with a particular row of application data.
- URLs: A link can point to a site or dynamic file.
- Notes: Users can create free-form text through attachment pages.
The exact controls are transaction-specific. A page may provide different buttons and fields from another transaction, so a shared framework does not mean identical user interfaces. See Oracle’s HCM 9.2 PBR 44 guide.
How administrators configure it
Oracle’s HCM 9.2 PBR 29 setup guide lays out a sequence that connects access rules, attachment types, application data, and the transaction’s implementation.
#1 Best Overall
- Define authorization IDs and entries. Specify permitted view and edit behavior, and which attachment object types are available to roles.
- Define attachment configuration IDs. Create configurations for common attachments, URLs, or document definitions, and identify the roles that can see them.
- Map application fields to context keys. The key configuration connects transaction data to the attachment configuration that applies. For document definitions, also configure store keys and a store record so uploaded files can be associated with the relevant application-data row.
- Maintain the definitions. The framework uses context keys to retrieve valid configuration IDs; it uses the definition ID and effective date to select the attachment from the database.
- Implement the framework in the application. Oracle documents use of the delivered
HR_ATTACHMENTSapplication package.Attachment_Dataconstructs entries such as labels, configuration IDs, and group boxes;Attachment_UImanages the attachment interface.
Refer to Oracle’s HCM 9.2 PBR 29 setup guide for the setup details.
What application developers must handle
The framework covers add and update operations for key fields and fields in the common HR_ATT_DD_SBR subrecord in the store record. It does not automatically handle every custom field that an application may add to that record. Oracle’s HCM 9.2 PBR 53 guide says additional non-key store-record fields require application-specific logic. That boundary matters when designing a document definition: identify any extra fields the transaction needs to maintain and implement their behavior in the application.
Rank #2
Source: Oracle HCM 9.2 PBR 53 guide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Repository and transfer choices
Attachment storage is a PeopleTools configuration concern, distinct from the HCM transaction’s attachment definitions. PeopleTools 8.63 documents these repository possibilities:
- FTP, FTPS, and SFTP
- HTTP and HTTPS
- Database records
- Oracle Content and Experience Cloud
- Oracle Cloud Infrastructure (OCI) Object Storage
Setup depends on the chosen protocol. URL Identifiers are mandatory for FTPS, SFTP, HTTP, and HTTPS. HTTP/HTTPS transfers require an available repository and configured URL properties. Oracle’s HTTPS examples include certificate and host/peer verification settings. OCI Object Storage requires an HTTPS URL and repository properties including bucket, tenancy and user identifiers, and API signing key information. Consult PeopleTools 8.63 URL Maintenance for release-specific setup and security requirements; protect credentials and follow the guidance for the deployed environment.
If attachments should be recognized as storage locations by the Search Framework, PeopleTools also provides an Attachment URL ID List to select the URL definitions it recognizes. See Creating the Attachment URL ID List.
Quick Recap
Rank #4
Plan the implementation around these boundaries
- Access: Define view/edit behavior and role visibility for each attachment type rather than assuming that a transaction’s users should all have the same access.
- Data association: Confirm the context-key mapping and, for document definitions, the store-key and store-record mapping to the intended application row.
- Custom fields: List non-key store-record fields that need application-specific add/update handling.
- Repository security: Choose a repository and configure its protocol-specific identifiers, properties, credentials, and certificates as applicable.
- Page behavior: Check the actual transaction page for its available controls and any file-type restrictions. Oracle notes that URL properties for
HR_ATTACHMENT_FLUcan restrict file types uploaded to or downloaded by the framework.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
