In the development being done on PeopleSoft uses, PeopleTools ATT is a component this gives user the capability to upload, file, and manage files in application components. This capability is important and useful for organizations who want to add supporting documentation, images, or other files to transactions, employee records, or cases.
Users will need the ability to attach receipts to an expense report, include scanned documents for HR forms, and provide reference files when completing a project. PeopleTools ATT provides that ability. We will cover what PeopleTools ATT is, how it works, best practice configuration, security considerations, and what the developers can do with it in this guide.
What Is PeopleTools ATT?
PeopelTools ATT, denotes the Attachments (Att) field type in PeopleSoft’s Application Designer. This field type contains binary files which are intended to reside in the system and are normally associated with a BLOB (binary large object) column in the database. It is commonly associated with a subrecord like ATTACH_DETAIL allowing for tracking attachment metadata (file name, file size, file date of upload).
The primary intent of this field type is to allow users to attach files directly to application data. This keeps documents “in order”, keeps them readily accessible and links them to the right records for auditing and reporting.
Why PeopleTools ATT Matters
Attachments are more than just files they are an integral part of digital record keeping. With PeopleTools ATT, organizations can:
- Keep related documents linked to relevant records for easy retrieval.
- Improve workflow efficiency by avoiding separate file sharing systems.
- Maintain compliance by storing records securely within the PeopleSoft environment.
- Support integration with other modules and external systems for document exchange.
When configured correctly, PeopleTools ATT saves time, ensures data consistency, and enhances collaboration.
Storage Options for Attachments
When configuring PeopleTools ATT, there are two storage types, Database and File System:
Database Storage (BLOB)
• Pros: Centralized storage, backed up with the database, database permissions
• Cons: Size of the database can grow considerably, performance may be impacted
File System Storage
• Pros: Database is not burdened with additional storage, for large files may be quicker, easier to manage when you are dealing with a very large data set.
• Cons: Intended file server must be correctly set up as secure, backup will need to be handled separately, permissions at the OS level must be managed.
Some organizations employ a hybrid model– the database for smaller files and the file system for larger attachments.
Configuring PeopleTools ATT Step by Step
Define Attachment Authorization IDs
Assign specific IDs to control who can view, add, or delete attachments. Link these IDs to security roles.
Create Attachment Configuration IDs
Define rules for file size limits, allowed extensions, and visibility.
Set Repository Paths (for File Storage)
Use dynamic placeholders like %OPRID% (operator ID) or %DBNAME% (database name) to organize files automatically.
Choose Storage Method
Select database or file system storage depending on performance and management needs.
Add the ATT Field in Application Designer
Include the Attachment field type in the relevant record or subrecord (e.g., ATTACH_DETAIL)
Develop PeopleCode Logic (Optional)
Use PeopleCode APIs to programmatically upload, download, or process attachments.
Test Upload and Retrieval
Ensure files upload, download, and delete correctly for all authorized users.
Monitor Usage and Apply Retention Policies
Prevent storage from growing unnecessarily by deleting outdated files or archiving them.
Best Practices for Security and Performance
• To constrain file formats: There are specific file types we want to allow, i.e. (pdf, jpeg, png, docx..)
• To constrain file size: Disallow large uploads that risk slowing our system down.
• To implement role based access: Always map Attachment Authorization Id’s to role authorities.
• To constrain file system paths: If we use file storage; make sure to set permissions on directories so they are restricted.
• To ensure flexibility in storage: Routinely monitor database or file server usage and apply changes to retention policies when required.
• To archive files: Move attachments that are of an old version to archived storage for better performance.
Using PeopleTools ATT with PeopleCode
Developers can take advantage of PeopleCode to enhance attachment handling:
• Upload Automation: Automatically add attachments from integrated systems or email inputs.
• Custom Validation: Check file type or size before upload to ensure compliance with rules.
• Dynamic Retrieval: Fetch and display attachments on related transactions or reports.
• Integration: Send and receive attachments via Integration Broker to connect with external applications.
By combining PeopleTools ATT with PeopleCode, you can create customized file handling workflows that fit specific business needs.
Quick Setup Checklist
Choose storage method: Database or File System.
• Define and assign Attachment Authorization IDs.
• Create Attachment Configuration IDs with proper rules.
• Configure repository paths (use metastrings if needed).
• Add ATT field in the appropriate record/subrecord.
• Set up PeopleCode for automation or integration.
• Test uploads, downloads, and deletions.
• Apply retention and cleanup policies.
FAQs
What is PeopleTools ATT?
It’s the Attachment (Att) field type in PeopleSoft used to store binary files, typically in a database BLOB or in a secure file system, linked directly to application records.
Which storage method is better for attachments?
Database storage is easier to secure and back up, while file system storage handles large files more efficiently. A hybrid approach often works best.
How do I control who can see attachments?
Use Attachment Authorization IDs and map them to user roles for precise access control.
Can attachments be handled programmatically?
Yes, PeopleCode offers APIs to upload, download, and manage attachments as part of custom processes.
Read also: Geekzilla Podcast The Ultimate Guide to Culture, Tech, and Fandom
Conclusion
PeopleTools ATT is the backbone of attachment handling in PeopleSoft, enabling secure and organized storage of files within the application. By understanding its capabilities, choosing the right storage method, and applying best practices for configuration, security, and performance, you can create a robust attachment framework that serves both users and administrators effectively.
With proper setup including Authorization IDs, Configuration IDs, dynamic repository paths, and optional PeopleCode automation your PeopleSoft system can manage attachments efficiently for years to come. For any new PeopleSoft project, configuring PeopleTools ATT correctly should be a top priority.
