PFlow Initial User email notification not generating

In the processflow file in Designer, in the User Action node, check to make sure the Notify check box is checked. This tells processflow to send the inbasket email notifications. Also check your email server, RD30 records to make sure the email addresses are there for the approvers.

Thank you for that tip but we seem to have all those setups in place correctly. This flow has been working fine for the last 3 years and now just this past week we are having issues with this initial email notification and can't seem to find out why.

Do you see any errors in the WorkUnit logs? So the requisition approvals are showing up in the Inbasket but the email isn't being sent? And you have escalation on for Reminder emails and those are being sent?

I see no errors in the Workunit logs. That is correct the requisition approvals are showing up in the Inbasket but the initial email is not being sent. Yes we do have escalation on for Reminder emails which are being generated and sent without an issue. Thanks

If it wouldn't bother you, if you email me your flow file I'll look at it to see if anything obvious shows up. Also one of your WorkUnit logs.

I see no errors in the Workunit logs. That is correct the requisition approvals are showing up in the Inbasket but the initial email is not being sent. Yes we do have escalation on for Reminder emails which are being generated and sent without an issue. Thanks

Thanks for trying to help me out. Please find attached the flows the and the workunit log for a workunit.

You mean this flow has been in version 9 for the last three years? Nothing has been changed lately to the flow?
Do you have the correct email server used by bpm? Do you have new approvers? Are they correctly setup in
WFUSERCAT? Did you check the metrics if you can see their task and wf-id?

When you look at the log the following line should show email addresses but doesn't:
The following email users of tasks will be notified about this user action:

This means that ProcessFlow can't find matching Users/Tasks for (in this case) the Level3 approver. What value do you see on the WorkUnit in menu.do (ProcessFlow Admin) in the Category field?
Your log shows this value is blank: oCatKey(Type=String) =

In your flow NashMain.xml the WorkObject is missing the Category Key value which should be "Req Loc" and that seems to be why this is missing in your NONSTKREQ.xml flow. I'm just guessing, but it appears that ProcessFlow can't match the approver since this value is missing. Put that value on your WorkObject so it passes to the new flow and see if it makes a difference.

David,
Thanks for your valuable input. I have attached 2 new workunit logs that were generated today relating to the 2 flows I sent to you earlier today. On the NashMain.xml flow I see an error which is as follows:

Executing WorkObject Activity WorkObject3560.....

ErrorLog in Process : NashMain_V04 Workunit : 93876, ActivityType=WO, ActivityName=WorkObject3560, ActivityId=WO30 Date:02/03/2009 Time:15:48:10

Exception while evaluating expression: ReqLoc_Name = GetReqLoc_NAME;

ReferenceError: "GetReqLoc_NAME" is not defined. (threadScript#1)
I have also attached the screen shots in the Process Flow Admin for these workunits and the Workobject setup in the other document. Thanks

David,
I also looked at a few other workunits that were generated today and they do not have the error with the Work Object that I sent to you in my earlier email. Thanks

In the logs and screen shots you can see that the original WorkUnit for requisition approvals had the value for Req Loc but the 2nd WorkUnit didn't. You are not passing that value in your WorkObject. Please update your WorkObject to pass this value and let me know if that resolves your issue.

The GetReqLoc_NAME error seems to have occured because the GetReqLoc query didn't process any records. You also had the following errors for the same reason:
Exception while evaluating expression: GetReqLoc_PROCESS_TYPE == "@K"
ReferenceError: "GetReqLoc_PROCESS_TYPE" is not defined. (threadScript#1)

You could run WorkUnit 93876 within the ProcessFlow Designer to see why the query didn't work correctly in this case.

We experienced the same problem late last year following an "update". We updated the server and process flow for the new environment (designer was upgraded and so was the process flow engine ). Lawson acknowledged the problem and opened a PT (179174). A patch for this problem exists. Here's some correspondence as of Dec. 10, 2008

"This patch is now available. You will find it on the System Foundation/Lawson Core Technology patch page for your OS, in the 9.0.0.5 area. As of today, the primary PT for this patch is listed as 179278 (and if you click on the description field, you will see PT 179174 as one of the PTs included inside.) Since the ProcessFlow patches change frequently, if you download it tomorrow, it may show a different primary PT. But the patch will always be easy to find since the patch page for LSF will always have one, and only one ProcessFlow patch. So if you look at the descriptions, you'll always be able to find it. "

I tried all the suggestions given but had no success. What is really weird is that today I have been notified by the end users of another flow which we use to approve Job Requistions that it is not generating the initial user email notification. When I go to the Workunit Queue Message Definition and Workunit Queue Messages under the Inbasket Information in PF Admin I do see that the initial email notification message has been generated . It therefore makes me think that there is something else that is going on the Production server that is causing this issue. The flows are not the issue.We have the same flows on our Test server and they are generating the initial email notifications like they should.

mbaliga, did you get your issue resolved? if yes, how was it resolved?
Thanks

I remembered when we migrated to LSF9 we have to create a bogus mail server so that executives or users will not get any email during testing of their requisition flow. We the developers are the only ones who knows where the location of the mails. You can setup a bogus email server using bpm.properties
(see pfserv pfconfig).

Make sure your Mail_From is defined  with an email address.  It does not have to be a valid email address but it does have to be in the email address format (a@b.com). If you are 8.0 it is in RD00, if you are 9.0 it will be on the bpm/menu.do form under Interface Definition