Fluid Attachment in newer PeopleSoft versions (9.2+ using Tools 8.55+)

-

 

In newer PeopleSoft versions (9.2+ using Tools 8.55+), the Fluid Attachments Framework has been significantly enhanced for easier configuration and mobile-friendly use. Here’s a full overview tailored to the latest version:

🧩 1. Core Framework Pages & Setup

In the latest Fluid-compatible releases, configuration is done entirely through delivered setup pages (no custom code needed unless advanced):

  1. Define Authorization (HR_ATT_AUTH): Create attachment authorization IDs to control access.

  2. Define Authorization Entries (HR_ATT_AUTH_ENT): Map attachment IDs to roles and access levels.

  3. Define Attachments Configuration (HR_ATT_CNFG): Specify available document types, URL links, notes, and attachments for each configuration ID.

  4. Configure Keys – Header/Store (HR_ATT_KEYS_HDR / _S / _C): Set which record fields act as context keys that group attachments by transaction (e.g. employee ID, transaction number).

  5. Maintain Definitions (HR_ATT_DEFN): Manage configuration effective dates and scopes. Oracle Support+10Oracle Docs+10DZone+10

🔧 2. Enabling Fluid Attachment UI

Delivered Fluid pages (like approvals, job data, name change, expenses, travel, payment requests) now already support attachments once enabled via configuration pages. For example:

  • In Person and Job Installation, toggling "Enable Fluid Attachments" makes the Attachments section appear in Fluid Add/Modify employee pages ScribdOracle Docs.

  • In Fluid Approvals and transactional pages (e.g. Payment Requests, Travel Authorization, GL Journals), attachments can now be included—though there are known issues to note (e.g., missing buttons until revisiting steps, behavior quirks during Save‑For‑Later flows) .

📱 3. Developer’s Implementation (Optional Custom Bolt-ons)

For custom Fluid components, you can still use the delivered Fluid Attachment class (HR_ATTACHMENT_FLU:Attachment_Fluid) to embed attachment UI:

peoplecode
Local array of string &CKeys = CreateArray("KEY1", ...);
Local array of string &StoreKeys = CreateArray("STORE_KEY1", ...);
&call_attach = Create HR_ATTACHMENT_FLU:Attachment_Fluid(
  "OWNER_ID","SUB_ID","CONFIG_ID", %Date, &CKeys, %UserId, %Component, "", &StoreKeys, False
);

/* Save */
&call_attach.Attachment_SaveProcessing();

You must also include the delivered subpage HR_ATTCH_FL_SBF at Level 0 in your Fluid page and add this logic in PostBuild/PageActivate events Oracle Support+5DZone+5PeopleSoftBlogger (DP Labs)+5.

✅ 4. Summary of New Version Highlights

  • End-to-end setup is done through PeopleSoft pages—no custom code needed unless you're building bolt‑ons.

  • Support for mobile responsiveness, notes, file-upload, and URL attachments.

  • Security-managed via delivered authorization framework.

  • Common delivered attachment UI & classes for both standard and custom Fluid pages.

  • Beware of some known product bugs that may require patching (MYSRs related to visibility in multi-step flows) Oracle Docs.

🛠 Next Steps

  • Navigate to Set Up HCM > Common Definitions > Attachments and complete pages HR_ATT_AUTH → HR_ATT_CNFG → HR_ATT_KEYS_HDR/_S/_C.

  • If using Add/Modify PeopleSoft delivered Fluid pages, ensure “Enable Fluid Attachments” is ticked in Person/Job installation.

  • If using custom Fluid components, insert the HR_ATTCH_FL_SBF subpage and add the PeopleCode above.

  • Test using both desktop and mobile, especially edge cases: save‑for‑later, approval flows, canceling edits.

Let me know if you'd like a walkthrough of the configuration pages, sample configurations for a specific transaction, or an example bolt‑on implementation!

Comments

Post a Comment

Popular posts from this blog

PeopleSoft Meta Tables

-
Application Engine Meta Data PSAEAPPLDEFN AE header record; 1 row per app engine PSAEAPPLSTATE AE state records (shows which one is the default) PSAEAPPLTEMPTBL AE temp tables assigned PSAESECTDEFN AE sections: public or private PSAESECTDTLDEFN AE section: descriptions, market, DB Type, EFFDT, EFF_STATUS, and auto commit PSAESTEPDEFN AE steps within section: description, market, DB Type, EFFDT, EFF_STATUS PSAESTMTDEFN AE actions within AE step: Step type (SQL, Do Select, etc.) with SQLID. PSAESTEPMSGDEFN AE message (parameters in each step) AEREQUESTPARM AE request parameters table behind the AE run control page. Find All Records Referenced in App Engine 1. Find the Temp Records (TAO) that are used: SELECT RECNAME FROM PSAEAPPLTEMPTBL WHERE AE_APPLID = 'MY_APP_PROGRAM_NAME' 2. If there are records, find the number of instances: SELECT TEMPTBLINSTANCES FROM PSAEAPPLDEFN WHERE AE_APPLID = 'MY_APP_PROGRAM_NAME...
Read more

Peoplesoft Application Package, Application Class and Application Method Implementation

-
Application Classes in PeopleSoft Defining and Importing packages or classes in PeopleCode <Pacakge name>:<Subpacakge name>:<…>:<Class name or wild card> Class Extensions represents the “is-a” relationship.   When a class extends another class, it’s called a subclass of that class. No Multiple inheritances or Concept of interface in Application classes. Instance variables in the class are accessible in all the objects of that class. Application programs generally pass parameters by value, which is not the same as for existing functions. Parameter passing with object data types is by reference. When the objects are passed to method and it reassign the object with new object it will not reflected in the calling method. Application Programs use the out specifier to pass a parameter by reference. Method increment (&Value as number out); rem passed by reference.   Create is the key word used to create the class object.  ...
Read more

Peoplesoft Application Package - Application Class/Application Package peoplecode and Calling them anywhere

-
Peoplesoft Application Package - Define Application Class and Calling Application class and Application Class Method from any Peoplecode event:  Step 1: Create New Application Package - MYPACKAGE Step2: Add a new application class in it. - MyClass Step 3: Defining Class and methods inside (Public or Private) 1. We can define classes here 2. We can define methods here 3. We can define Class Property Code to write inside a class to define class and its method: class MyClass method MyMethod (&smyInput as String, &nmyInput as Number) returns string; private method MyPrivateMethod (&sInput as String) returns boolean; property string &sVar; property number &nVar; end-class; method MyMethod /*+Method Body+*/ returns &sVar; end-method; method MyPrivateMethod  /*+Method Body+*/ returns &bVar; end-method; Code to write call a class and run its method: import MYPACKAGE:MyClass; Local string &sGetMethodData; Local MYPACKAGE:MyClass &oClassObjectVar...
Read more