I use custom PA52 Portal Pages for display execs in the Portal Inbasket. In our current production ENV 8.0.3.7 / Apps 8.0.3.11 / EMSS 8.0.3.8, they are and have been working properly for over 4 years. My test box LSF9 ENV 9.0.0.3 / Apps 8.0.3.11 / EMSS 8.0.3.5406 / CBL 9.0.0.113 the custom pages do not complete the inquire or are fed incorect data for the inquire. When the page is open it is fed the header fields and does an inquire to display the PA record. When it is opened in LSF9, it displays the Company, Employee, and Action Code, but the Action NBR and Effective Date are not displayed, as if it could not find the record. If I hit the Next button, the PA52 will display the action. The OLD version of EMSS that is in our 8.0.3.7 ENV does not require me to have the Forms Field Definitions changed on the PA52's and J-PA52's as per several HR/PR CTP's have as manual steps. The newer version of EMSS that we have on the LSF9 box does require these changes. I've tried it both before and after the changes with the same non functioning result. Are there any changes in how Portal and/or getting javascript to auto inquire on the PA52 in LSF9? The java script used on the Portal page is below.


function tvlt_OnInit()
{
var pStorage = new PortalStorage()
pStorage.addElement("PCT-COMPANY",page.parameters.COMPANY)
pStorage.addElement("PCT-EMPLOYEE",page.parameters.EMPLOYEE)
pStorage.addElement("PCT-ACTION-CODE",page.parameters.ACTION)
pStorage.addElement("PCT-EFFECT-DATE",FormatLawsonDateToStandard(page.parameters.EFFECT_DATE))
pStorage.addElement("PCT-ACTION-NBR",page.parameters.ACTION_NBR)
page.setObjectValues("PFFULLPA52.1",pStorage)

return true;

}

function FormatLawsonDateToStandard(sDate)
{
//Returns Lawson date (yyyymmdd) as Standard Date string (mm/dd/yyy)
var s = ""
alert("Lawson Date is "+sDate)
alert("Company = "+page.parameters.COMPANY)
alert("Employee = "+page.parameters.EMPLOYEE)
alert("Action = "+page.parameters.ACTION)
alert("Action NBR = "+page.parameters.ACTION_NBR)
if (sDate != "")
{s = sDate.slice(4,6) + "/" + sDate.slice(6,8) + "/" + sDate.slice(0,4)}
else
{s = ""}
alert("Formated date = "+s)
return s

}

I finally got this to work. The migrated custom PA52's DO NOT function as the LSF9 Design Studio would indicate. The migration process and LPS leave out that there are XML coding changes behind the scenes, such as new and/or changed XML parameters for LSF9. The migration process only checks for minor syntax changes in custom scripts, not major coding changes that DS will add for you while creating a form/page from scratch. After going round/round, calling GSC, and not getting much help, I finally created them from scratch with the exact same settings as the 8.0.3.7 version and it worked as it should. If you have custom Portal Forms and/or Pages, it is almost required that you recreate them from scratch to ensure that will work as expected in LSF9. They don't like to mention it up front before they get your signature on the consulting contracts.