We modified the time entry form, when users click on the update button at the tim entry forms, supervisors will receive email noticications. It worked when we use LAUA secuity. But it doesn't work when I'm working the new Lawson security. The new security is working fine on the time entry forms but the process flow just didn't kick off for notification. I don't understand why it is related to process flow?
We modified the "timentryperiodwindow.js" , to trigger a process flow: function UpdateClicked_Period() { perform.reset() showWaitAlert(getSeaPhrase("UPDATING_PERIOD_TE","TE")) if(arguments.length>0 && arguments[0]=="Submitted") UpdateTimeCard("Period", "Submitted") else UpdateTimeCard("Period") // When users click on Update button at Time Entry form, supervisor will receive email notification // about what Pay Period has been updated. AGS call will create Workunit for Process Flow to send email. var SEATime="http://lawsontest.tra.local:81/cgi-lawson/ags.exe?_PDL=TEST9&_TKN=WFWK.1&_EVT=ADD&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Add&SERVICE=TimeEntryUpdate&WORK-TITLE=Time%20Entry%20Update&VARIABLE-NAME1=TEEmployee&VARIABLE-VALUE1="+Employee.EmployeeNbr+"&VARIABLE-NAME2=TEStartDate&VARIABLE-VALUE2="+TimeCard.StartDate+"&VARIABLE-NAME3=TEEndDate&VARIABLE-VALUE3="+TimeCard.EndDate+"&PRODUCTLINE=logan&_DELIM=%09&_OUT=TEXT&EOT=TRUE"; var updatewin=window.open(SEATime); updatewin.close(); }
We modified the "timentryperiodwindow.js" , to trigger a process flow:
function UpdateClicked_Period()
{
perform.reset()
showWaitAlert(getSeaPhrase("UPDATING_PERIOD_TE","TE"))
if(arguments.length>0 && arguments[0]=="Submitted")
UpdateTimeCard("Period", "Submitted")
else
UpdateTimeCard("Period")
// When users click on Update button at Time Entry form, supervisor will receive email notification
// about what Pay Period has been updated. AGS call will create Workunit for Process Flow to send email.
var SEATime="http://lawsontest.tra.local:81/cgi-lawson/ags.exe?_PDL=TEST9&_TKN=WFWK.1&_EVT=ADD&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Add&SERVICE=TimeEntryUpdate&WORK-TITLE=Time%20Entry%20Update&VARIABLE-NAME1=TEEmployee&VARIABLE-VALUE1="+Employee.EmployeeNbr+"&VARIABLE-NAME2=TEStartDate&VARIABLE-VALUE2="+TimeCard.StartDate+"&VARIABLE-NAME3=TEEndDate&VARIABLE-VALUE3="+TimeCard.EndDate+"&PRODUCTLINE=logan&_DELIM=%09&_OUT=TEXT&EOT=TRUE";
var updatewin=window.open(SEATime);
updatewin.close();
}
Did you add WFWK.1 access to the users security in LS for the application product line? It is not automatic. Bear in mind if your portal is wide open (ie they can transfer to programs by entering in the search box), that in theory any user can create a workunit to kick off any flow.
Because WFWK was moved from LOGAN to the application product line this security "hole" is caused. It is for this reason that I tend not to use WFWK anymore and actually will create a custom 4GL form instead that has the COBOL trigger logic in it, this way it can be controlled which trigger can be called, you can also set the $NOTKXFER on the screen definition for WFWK.scr and that would lock it down from the search box.
What would the "Transaction Servlet" look like in the url?
Would this be right?
http://lawsontest.tra.local:81/servlet/Router/Transaction/Erp?_PDL=TEST9&_TKN=WFWK.1&_EVT=ADD&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Add&SERVICE=TimeEntryUpdate&WORK-TITLE=Time%20Entry%20Update&VARIABLE-NAME1=TEEmployee&VARIABLE-VALUE1="+Employee.EmployeeNbr+"&VARIABLE-NAME2=TEStartDate&VARIABLE-VALUE2="+TimeCard.StartDate+"&VARIABLE-NAME3=TEEndDate&VARIABLE-VALUE3="+TimeCard.EndDate+"&PRODUCTLINE=logan&_DELIM=%09&_OUT=TEXT&EOT=TRUE