Search
Saturday, October 31, 2009
Create Popup using Peoplecode
How to create Popups in peoplesoft applications using Peoplecode:
1. Create the content that you want to show in the Pop up (SRB_HTML_EXEC)
2. Create another HTML as below (SRB_HTML_MASTER)
href="#" onclick="window.open('%BIND(:1)','whatevername','width =400,height=400')
HelpLink
3. Create a web library (WEBLIB) and create an iscript with in Field Formula Event
Function iscript_dev
&HTML = GetHTMLText(HTML.SRB_HTML_EXEC);
%Response.Write(&HTML);
End-Function;
4. Add HTMLAREA to the page on which you want to click to get the popup.
5. Add Record Field FIFO peoplecode to the above field as below. Code this as a function.
Function CallFunc(&u)
&suburl = &u;
&url = GenerateScriptContentURL(%Portal, %Node, Record.WEBLIB_SRB, Field.SRB_ISCRIPT, "FieldFormula", &suburl);
SRB_WRK.HTMLAREA.Value = GetHTMLText(HTML.SRB_HTML_MASTER, &url);
End-Function
6. Now call the above function from RowInit peoplecode of Component Record of HTMLAREA (Html Area is added to the page in step#4 above):
CallFunc("iscript_dev")
Thursday, July 30, 2009
Peoplesoft Integration between Oracle and SQL server
There has been a notion floating around that integration cannot be achieved between peoplesoft versions running on separate database platforms using Integration Broker (although Peoplesoft is designed to be platform independent). I procrastinated long enough before I tried the integration with the following set of environments. It works just fine.
FSCM: App Rel 8.4, Tools 8.45, DB Oracle 9i, app server on AIX 5.3 (unix)
HRMS: App Rel 9.0, Tools 8.49, DB SQL Server 2005, app server on Win'2003 server
Messages: PERSON_BASIC_SYNC, WORKFORCE_SYNC
Points to keep in mind here, though, as the Financials Release is lagging behind HRMS:
Convert the service operation version in the source from INTERNAL to the one that is used in the target. In the above example, Financials uses VERSION1 of PERSON_BASIC_SYNC.
External Alias Naming in the routing parameters should match the version of the target message.
But otherwise it is pretty straightforward.
FSCM: App Rel 8.4, Tools 8.45, DB Oracle 9i, app server on AIX 5.3 (unix)
HRMS: App Rel 9.0, Tools 8.49, DB SQL Server 2005, app server on Win'2003 server
Messages: PERSON_BASIC_SYNC, WORKFORCE_SYNC
Points to keep in mind here, though, as the Financials Release is lagging behind HRMS:
Convert the service operation version in the source from INTERNAL to the one that is used in the target. In the above example, Financials uses VERSION1 of PERSON_BASIC_SYNC.
External Alias Naming in the routing parameters should match the version of the target message.
But otherwise it is pretty straightforward.
Subscribe to:
Comments (Atom)