PeopleSoft Fluid Attachments Framework
The Fluid Attachment feature has been upgraded to support fluid and responsive design. This article goes into detail about this feature.
Join the DZone community and get the full member experience.Join For Free
The Fluid Attachment feature has been upgraded to support fluid and responsive design. Administrators can now configure attachments, notes, and links for transactions on Fluid pages in a way that works seamlessly across desktop, tablet, and mobile devices. Users are able to upload attachments from their desktop, mobile device, or third-party online storage services when using Fluid for self-service transactions. This attachment feature is supported on both desktops and smartphones. The Attachment Functionality enables users to attach documents, links, and notes to various delivered transactions, such as approvals, billing statements, name changes, address changes, and more.
Implement Fluid Attachment Framework
To implement the Fluid Attachment Framework for a bolt-on module, you can follow the steps outlined below:
- Create a custom record specifically for handling attachments. This record should include a Sub Record (HR_ATT_DD_SBR) that allows for the inclusion of component keys and line or header levels as per the specific needs of the business.
- Insert the subpage (HR_ATTCH_FL_SBF) at Level 0 on the Fluid Transaction Page. This subpage will serve as the user interface for managing attachments within the bolt-on module.
- Implement the necessary PeopleCode logic either in the Postbuild or Page Activate event. This code will be responsible for initiating the attachment processing functionality and handling any associated actions or validations.
- Add the necessary Peoplecode on the Postbuild or Page Activate event.
* ——- Begin : Fluid Attachment Functionality ————- * / /*Initialize parameters for calling attachment constructor*/ Local array of string &CKeys = CreateArray(“Your Context Keys”); /*This array would contain the Context key values*/ Local array of string &Store_Keys_Array = CreateArray(“Your Store Keys”); /*This array would contain the Store key values*//*Initialize component rowsets*/ &Lvl1 = GetLevel0()(1).GetRowset(Scroll.HR_ATT_KEYS_S); &RS_DocDefns = GetLevel0()(1).GetRowset(Scroll.HR_ATTACH_FLU); /*Calling attachment constructor*/ &call_attachment = create HR_ATTACHMENT_FLU:Attachment_Fluid(“Your owner ID”, “Your sub ID”, “Your Config ID”, %Date, &CKeys, %UserId, %Component, “”, &Store_Keys_Array, False); /* ——- End : Fluid Attachment Functionality ————- */
SavePostChange to save the
/* ——- Begin : Fluid Attachment Functionality ————- *//* Calling Save*/ &call_attachment.Attachment_SaveProcessing(); /* ——- End : Fluid Attachment Functionality ————- */
Following these steps, you can successfully integrate the Fluid Attachment Framework into your bolt-on module, enabling efficient attachment management within the fluid transaction environment.
Set Up HCM > Common Definitions> Attachments > Define Authorization
Use the Define Authorization page (HR_ATT_AUTH) to enter and maintain attachment authorization IDs that specify the user access level for attachments.
Define Authorization Entries Page
Use the Define Authorization Entries page (HR_ATT_AUTH_ENT) to associate attachment authorizations with user roles.
- Set Up HCM > Common Definitions > Attachments > Define Authorization Entries > Define Authorization Entries
Define Attachments Page
- Set Up HCM > Common Definitions > Attachments > Define Attachments > Define Attachments
Published at DZone with permission of Chandra Rawat. See the original article here.
Opinions expressed by DZone contributors are their own.