Ok,
I am working on a flow currently that is a name change flow. It is working correct and flows to a correct inbasket. After approval from the inbasket, it goes to the trigger node, where it calls another flow.
The flow it calls just goes out to PA53 and changes some things and the approval flag.
I can not figure out for the life of me, why this second portion errors out.
Here is the error message (below the dotted line)
Ive rebuilt the lawson transaction node for PA53, checked it etc. I dont know if I have something set wrong with a flow triggering another flow or what
--------------------------------------------------------------------------------------------------------------------------------------------------------
Process: P_MSSNAMCG Activity id: PA53Approval Error code: -1 Information code: -1 Return message: java.lang.NullPointerException at com.lawson.bpm.processflow.workFlow.flowGraph.FgaWorkObject.createWorkObject(FgaWorkObject.java:753) at com.lawson.bpm.processflow.workFlow.flowGraph.FgaWorkObject.startActivity(FgaWorkObject.java:598) at com.lawson.bpm.processflow.workFlow.flowGraph.FgActivity.execute(FgActivity.java:833) at com.lawson.bpm.processflow.workFlow.flowGraph.FgProcess.run(FgProcess.java:2210) at com.lawson.bpm.eprocessserver.grid.ExecuteFlowImpl.executeFlow(ExecuteFlowImpl.java:374) at com.lawson.bpm.eprocessserver.grid.ExecuteFlowImpl.restartFlowForUA(ExecuteFlowImpl.java:154) at com.lawson.bpm.eprocessserver.ProcessFlowEngine.execute(ProcessFlowEngine.java:193) at com.lawson.bpm.eprocessserver.ProcessFlowEngine.reStartProcessAt(ProcessFlowEngine.java:116) at com.lawson.bpm.eprocessserver.KBConnectionDispatch.dispatch(KBConnectionDispatch.java:48) at com.lawson.bpm.eprocessserver.KBConnectionDispatch.run(KBConnectionDispatch.java:37) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Output data: The AGS call to PA53 to update the Approval Flag to Y failed due to the following reason - undefined. Kindly manually make this change using the link below:
_PDL=LAW10&_TKN=PA53.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&PCT-COMPANY=*!Company*&PCT-EMPLOYEE=*!Employee*&PCT-ACTION-TYPE=*!Action_Type*&PCT-ACTION-CODE=*!Action*&PCT-ACTION-NBR=*!Action_Nbr*&PCT-EFFECT-DATE=*!Effect_Date*&PCT-APPROVAL-FLAG=Y&_DELIM=%09&_OUT=XML&_EOT=TRUE
Posted By Tim Cochrane on 08/21/2015 1:30 PM have you tried adding the PA53 AGS directly in the first flow and testing it there...which is where I've always placed the PA53 AGS?? This is my logic...looks just like yours...and it has always worked _PDL=<!--appProdline-->&_TKN=PA53.1&_EVT=CHG&_RTN=MSG&_LFN=ALL&_TDS=IGNORE&FC=Change&PCT-COMPANY=<!--Company-->&PCT-EMPLOYEE=<!--Employee-->&PCT-ACTION-CODE=<!--Action-->&PCT-ACTION-NBR=<!--Action_Nbr-->&PCT-EFFECT-DATE=<!--Effect_Date-->&PCT-ACTION-TYPE=E&FROM-WORKFLOW=Y&PCT-APPROVAL-FLAG=Y&_DELIM=%09&_OUT=XML&_EOT=TRUE
Yes. Tried it yesterday afternoon. I think something is up currently, as once it reaches the PA53 section it locks up.
Ronnie,
Are you using IPA? I am having a different problem with PA53 using IPA. I have a personnel action that triggers PA53 to do the approval. What I am seeing is that PA53 updates the user id to be Lawson instead of the person that created the personnel action. So when I run PA100 it does not find personnel action for the person that created the action. I have you notice this problem? We are running IPA on Windows environment.