HR Applications and multiple Self-Service transactions (Name Change, Address Change, and Absence Request) necessitate the need of a proof/document to validate the records of the Employees. Attachment functionality was released as a part of PUM 25 and major enhancements followed in subsequent images.
Attachment Functionality can be used to attach Documents, Links and Notes for the delivered transactions like Approvals, Billing Statements, Name Change, Address Change etc.
- Digitizing documents increases HR efficiency and provides more security.
- Consistent and seamless user experience across devices such as Tablets, Smartphones and Laptops
- Able to control visibility using Role security.
- Easily configurable and extendable to bolt on modules with minimal technical effort.
- Business can configure to delete or archive the document
Implement Fluid Attachment Framework for Bolt-On
- Create a custom record for attachment – Should include Sub Record (HR_ATT_DD_SBR) along with component keys, line or header level as per business need.
- Insert the subpage (HR_ATTCH_FL_SBF) at Level 0 on the Fluid Transaction Page.
- Add necessary PeopleCode on the Postbuild or Page Activate event to initiate attachment processing.
- Add PeopleCode to save the attachment in your custom record use SavePostChangePeopleCode.
Steps to configure Fluid Attachment Functionality
- Set Up HCM > Common Definitions>Attachments > Define Authorization
Configure security details (Edit or View Authorization) and delete options. Select edit checkboxes to enable the user to create, update, or delete attachments and view to enable users to view attachments.
Mark as deleted enable to the user to track the deleted attachments. When an object is deleted, it appears in the scroll area list of existing attachments when they are deleted but the status column are grayed out.
Delete from database enable the users to immediately delete the attachment from the database. You will get a confirmation before deleting it.
- Set Up HCM > Common Definitions> Attachments > Define Authorization Entries
Authorization IDs created in previous step are tagged to entry ID and roles. Multiple Authorization IDs can be tagged to a single entry ID. Authorization IDs defined whether tagged role has edit access or view access only. It has worked like as a security feature for attachments.
- Set Up HCM > Common Definitions> Attachments > Define Attachments
This setup page allows to define type of attachment to be used on component (Attachment, URL and Document Definition). Select Document Definition to create an entry that enables users to create their own attachments for a specific row of application data.
**Note – For now, only Document Definition type is supported as part of the support given to Fluid Interface for Desktop and Only one Entry id within a Configuration id is supported by the Fluid Attachment Framework.
- Set Up HCM > Common Definitions> Attachments > Configure Keys.
Configure keys option gives overall information in terms of key structure and table details to save attachments.
Select Object Owner Id to the application in which a common component is used.
Configured context keys by which attachments are partitioned for an application.
Configure Store Keys to store the values in attachment record.
- Set Up HCM > Common Definitions> Attachments > Maintain Definitions
Maintain Definitions page to specify the attachment types available to an application. The context keys are determined by the Configure Keys component and are used to retrieve a list of valid Configuration IDs.
The context keys are not displayed first, enter the Sequence Number and then the context keys automatically display.
* Group Box column above has no relevance for Fluid Attachment Framework.
Business Use Case:
PeopleSoft has delivered functionality for HR/Administrator to capture Name change and Address change for employees.
Customer specific bolt on ESS functionalities like Passport Additions, Prior Work Experience was configured to have the Attachment framework with a Workflow approval to HR Shared Services. With this Bolton functionality, employees were able to submit requests with proper documents attached for approval. Approvers can take necessary action without delay with instant access to proof/document.
Fluid attachment framework along with Page Composer was used to achieve the mentioned use case.
PeopleSoft Technical Consultant