Workunit not appearing in Inbasket

Is this IPA? If so, then you might not have the User, Task, Filter set up correctly or you may not have defined the oWorkCat value in the flow. Both this and oCatValue have to be defined in IPA. The flow and user setup must match or the Inbasket won't display.

Thanks David. Not IPA - Process Flow.
Regardless of how the category filter is set up, shouldn't it work the same, running in designer or on the server?

Check the WorkUnit Queue before and after you rerun the flow in the PF Designer to see what's different.

windows NT id is what messed me up. I was getting the buyer login from table behind PO04. On the screen it shows DOMAIN\USERID, but in the table BUYER it is saved as NT000000nn. The NT id does not tie to the PF admin user or the resource manager ID.
When Process flow tried to assign a WU to the inbasket of user NT00000nn, it failed.

So I now do an AGS on PO04 instead of DME on BUYER, do some string manipulation to get the proper ID and all is well.

Still don't understand why it worked from the Designer though.

Thanks David for your suggestions.

I've had the same issue with something working through the designer, and not with the flow. I believe, though am absolutely cannot prove, that the issue is the user running the command. I think that when you are running through the designer you are logged into everything as whatever ID you login to the designer. In my case this was the default Lawson ID. When it runs through IPA I think it's running as whatever ID owns the service (in Windows) or the demon (in UNIX). That ID may or may not have the same permissions as when logged into the designer.

As I said though, I could not conclusively prove that to be the case. I'd welcome another opinion, or for someone to think up a way to prove that theory one way or the other.

Just a note on the IPA side. I have the opposite problem, where Designer doesn't work but Server does. My impression is that the IPA designer assumes the login name is the actorID, but we use AD Alias for the login (SSOPV2 Identity) and have an ActorID that (usually) matches the EmployeeID. When debugging something in designer, I have to manually modify the actor value in order for things to work correctly. For example, if I follow a UserAction node with a lookup to find the approver name, I have to use the debugger to modify the {nodename}_users[0] and {nodename}_authUsers[0] values from the login username to the actorID.

It seems like it should work the same as the server, but it doesn't (much to my annoyance).

Good Luck.