PIA_KEYSTRUCT object. It looks like this object contains key/value pairs for each level 0 search key, primary and alternate. What can you do with this? I'm not sure yet. I've been thinking about it for a couple of weeks. My two main questions:
- Can I use this to create new developer tools (bookmarklets, etc)?
- Can I use this to empower users?
For now, the only example I can show you is how to open a query and pass in the
PIA_KEYSTRUCT values as query bind parameters. This example passes the Role Administration component's
window.open("/psc/portal/EMPLOYEE/EMPL/q/?ICAction=ICQryNameURL=PUBLIC.PT_SEC_ROLE_CLASS&BIND1=" + escape(frames['TargetContent'].PIA_KEYSTRUCT.ROLENAME))
- Enhance the Ctrl-J page by adding the level 0 search keys
- Simplify the Pagelet Wizard link creation process
about this. I am not sure if you have come across a feature called Context Manager in
PeopleSoft Enterprise Portal.
Let me briefly explain this functionality. When you navigate to a cref, say a hrms cref
that lists the company names, it will be nice if you can show a brief history of the
company, stock code symbol, yearly turnover etc, that helps the user to know something
about the company on hand. This is what Context Manager is doing.
It just uses the component level 0 search and alt search keys to identify the target page
keys and show relevent information in the form of template pagelet in left navigation
Template pagelets are usually to be written by the admin user who decides what kind of
information to show in the left frame. Admin user writes his template pagelet code such
that it reads this PIA_KEYSTRUCT variable (this variable will contain company name/id on
company name cref)use this level 0 key values to find/query the company information table
in hrms to get some relevent information of the company (selected on the target frame)
and show this info as a template pagelet in the left frame. This template pagelet can be
a simple iscript function. Once you complete your template pagelet code, then define it
under PeopleTools> Portal> Structure and Content> Portal Objects> Template Pagelets and
provide appropriate permission to this iscript function.
Once your templatepagelet is registered in the Portal Registry, it will be available for
Context Manager feature to use. Once important thing to remember is that, this Context
Manager feature uses a different template called Dynamic template that reloads the left
frame with the relevent information pertaining to the target frame level 0 keys and it
repeats the same whenever a new level 0 key is selected on the target frame. NOTE: If you
are using Context Manager functionality, you donot need to read the PIA_KEYSTRUCT
variable from the PIA html. Context Manager framework reads it and gives it in the form
of an App class method result. Context Manager App class is EPPLN_TEMPLATE_PAGELET:TPRequest and methods GetTCKey and GetTCKeyValue.
You can find more detailed information on the PeopleSoft Enterprise Portal peoplebooks.
Hope it helps.
Are you aware of any method to control/maintain the operators (=, between, <=, etc) on a component search page when a user selects 'Return to Search'? I have code that preserves non-key search values, but the operators always get set back to whatever the default is for the field type.
@Brady, I am not aware of a delivered method for controlling the comparison operator. I have some ideas though. If my idea is simple, I'll post the response here. If it is complex, I'll post it in my regular blog and include a link here.
I haven't written or tested a solution for this. These are just some pointers to help you if you are interested in writing a solution.
I suspect PIA_KEYSTRUCT is a key element of how popup pages work. I haven't run a full trace but I bet that string is passed into that popup modal.
Post a Comment