user Action, stuck

what does the log say?

Log says nothing. It still thinks the req is waiting for action.

so in the rich client, in the user action tab - what does it say exactly

This is the last item in the log when the work unit enters the inbasket and it doesn't change after I approved the req.
***

Activity name:Lvl1_InBasket id:1 started @ 10/11/2016 08:53:15.849 AM
UserAction Lvl1_InBasket: Executing UserAction activity
Variables:
vLevel3_Amt(Type=Integer) = 10000
vRequestor_Name(Type=String) = Tammy Bliss
vSysDate(Type=String) = 10/11/2016
vLevel5_Amt(Type=Double) = 250000
vMessage(Type=String) =
vDayOfWeek(Type=Integer) = 2
vTaskLabel(Type=String) = Level 1
vRequestor_email(Type=String) = Bliss@genesishealth.com
vReq_XS_Total(Type=Double) = 3000
vReqNbr(Type=String) = 1466853
vReq_N_Total(Type=Double) = 542.31
vIPAAdminEmail(Type=String) = IPA-Admin@genesishealth.com
GetRequestorInfo_breakFlag(Type=Boolean) = false
vEscalate(Type=Integer) = 0
vLevel6_Amt(Type=Double) = 1000000
vLevel4_Amt(Type=Integer) = 100000
vReminder(Type=Integer) = 0
vLevel1_Amt(Type=Double) = 0
vUser(Type=String) =
Chk_Level1_breakFlag(Type=Boolean) = false
vReqLoc(Type=String) = 7250I
vReqCompany(Type=String) = 0001
vApproverName(Type=String) =
vLevel2_Amt(Type=Double) = 5000
vLawsonTeamEmail(Type=String) =
vRequestor_EmpNbr(Type=String) = 1001779
UserAction Lvl1_InBasket: User list:
UserAction Lvl1_InBasket: CSV user list before variable substitution:
UserAction Lvl1_InBasket: CSV user list after variable substitution:
UserAction Lvl1_InBasket: Task list: ReqLevel1
UserAction Lvl1_InBasket: CSV task list before variable substitution:
UserAction Lvl1_InBasket: CSV task list after variable substitution:
UserAction Lvl1_InBasket: Work routing:
Tasks: ReqLevel1

User Action Reminder #1 message properties before variable substitution:
Cc:
Bcc:
From:
Subject: Requisition # requires action.
Content: This is a reminder that you have a requisition in your InBasket that requires an Action, Requisition Number , from .
If no action is taken within one (1) business day, this will be escalated to the next level.



User Action Reminder #1 message properties after variable substitution:
Cc: null
Bcc: null
From: IPA-Admin@genesishealth.com
Subject: Requisition #1466853 requires action.
Content: This is a reminder that you have a requisition in your InBasket that requires an Action, Requisition Number 1466853, from Tammy Bliss.
If no action is taken within one (1) business day, this will be escalated to the next level.
UserAction Lvl1_InBasket: Created Work Queue record for inbasket user action.

i was referring to thhe work unit details...when you double click on the work unit that seems "stuck"

I should probably clarify a bit. This flow was working in Lawson version 9. This is the first time we've had to continue testing since we completed our upgrade to Lawson v10. Our version of IPA was upgraded from 10.? to Product Version: 10.1.1.30.4710

i have seen instances where after a user action is taken, there is a message that instead of saying "waiting for user acdtion" or "action taken accept", there is another message about "Action taken pending in server" os something very close to that. this message is displayed in the user action tab of the details for a work unit. i was wondering if this message is what you have...

We are testing IPA as well and are experiencing the same issue. When I approve the req in the portal inbasket, the workunit doesn't advance to the next level even though a message pops up saying “Approve Completed Successfully”. It disappears completely. When you look at the workunit details in the Rich Client the User Action tab shows it's still in "Action Awaiting" status at the user action node that I just approved on. I also have actions enabled in the email notification. When I take the approve action there the workunit does advance to the next level.

The work unit status is 'Processing'. The Activity Nodes tab, list the name of the inbasket with the status as 'started' and double clicking on that opens the activity and has 'Disp Status' as 'Action Awaiting'. Any of the log files I see look as if nothing else has happened since the User Action node stated.

Thanks Jon - what you said might explain it better.

and of course if I test anything in the IP Designer it works fine.

This happens when the dispatch call doesn't complete correctly - it's a communication issue between S3 and Landmark. If you search on Infor Xtreme you may find the patch to correct.

I found this KB article which looks similar to what I’m seeing.  We made the change and stopped and restarted "everything" and now the user action nodes are completing and the workunits move on through the next activity nodes!

KB 1521682

Description:

When the lawson user attempts to approve a transaction via the Smart Office or Rich Client, the transaction appropriately disappears from the inbasket, and all the activity nodes following the User Action activity node process successfully.

However, when any user other than lawson approves a transaction via either Smart Office or Rich Client, the transaction appropriately disappears from the inbasket, but none of the activity nodes following the User Action activity nodes process at all. The transaction is stuck in limbo and the transaction cannot complete. Upon taking action, the activity nodes following the action should get executed.

Seeing the following error:

Caused by: com.lawson.security.authen.SecurityAuthenException: com.lawson.security.authen.LawsonUserContextImpl.security.authen.actor_does_not_support_run_as

Resolution:

The user account that starts the GRID services, such as lawson, needs to have the RunAs setting enabled.  View the actor record, account tab of this user, and verify if the runas is enabled or not. If it is not enabled, go to and open the landmark command prompt and run:

secadm actor enablerunas

This will enable the runas for this user, and the LPA service will need to be restarted for this to take effect.

 

Our DBA made the change here:

 

Thank you all. We faced the same issue and the "runas" fix worked for us.