I decided to implement this as a Fluid page and using the Fluid Attachment Framework, which was implemented as part of Image 25, and there are a couple of write ups on the feature:
- Oracle: Fluid Attachments for PeopleSoft HCM (contains a link to a doc id which references a red paper).
- Kovaion: Fluid Attachments Framework in PeopleSoft
Implementing this was fairly easy, and the only issues I had were:
- The subpage which was inserted into the run control page was the first item, and saving the page in Application Designer gave an error "More than one data record in scroll".
- Once I changed this to not be the first page item, i.e. I moved it down to the bottom in the page order, the error went away.
- My page was navigated to by way of another page and the Transfer function, and I originally didn't register it as a portal content reference. This caused one of the queries related to security to not return a value, and give a null exception error.
- I registered the component and made it hidden.
- As referenced in the red paper, there are two component scoped Rowsets which need to be declared and initialized, otherwise errors occur.
- Ensure that these objects are initialized prior to calling the event.
- Originally I had my run control record as level 0 (it had OPRID and RUN_CNTL_ID and the required subrecord). But then when saving the page, the SEQ_NBR on the subrecord is a key and caused a NULL insert error.
- The solution was to just use PRCSRUNCNTL as the level 0 record, and then the level 1 record is the custom run control record (with the attachment sub record).
- The 'Maintain Definitions' page needed to have the 'All values' checkbox selected for the Context Keys.
