Who's On?

	Membership:
	Latest: Raju
	Past 24 Hours: 0
	Prev. 24 Hours: 1
	Overall: 5205

	People Online:
	Visitors: 233
	Members: 0
	Total: 233

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1369
Roger French	1315
mark.cook	1244

IPA User Action node not executing

5 Replies

0 Subscribed to this topic

52 Subscribed to this forum

Sort:

Author

Messages

Michael J

New Member

Posts: 3

9/20/2013 2:05 PM

I am executing a lawson delivered Process Flow, ChangeRelToOrg and the flow gets to the user action, reject, approve or return. The user will select an action, but the flow does not execute the node. The proceed action will commence when "any one recipient takes an action". The work assignment ID is HR administrator
we are running IPA version 10.0.4.0.5739
Any suggestions

Woozy

Veteran Member

Posts: 709

9/23/2013 1:33 PM

Hi Michael - Is the system generating an error? Something like "user xxxxx is not in task yyyyyy"? Are they taking action from the Landmark Inbasket, or some other way (like the email link)?

Michael J

New Member

Posts: 3

9/23/2013 5:19 PM

thank you for the response. no error is generated and the user will execute the action from the landmark inbasket.

Woozy

Veteran Member

Posts: 709

9/23/2013 5:43 PM

Odd. Your other flows are running, and other action updates are working correctly? Does this happen with a specific person or workunit, or for all ChangeRelToOrg process actors and workunits?

The WU log just remains as if no action has been taken?

Is this happening in PROD or in DEV?

Michael J

New Member

Posts: 3

9/23/2013 6:39 PM

thank you for your continued support,

any flow with an user action does not execute after the user has performed an action. we are in development mode and just installed a new release of Landmark 10.0.4.0 CU4 and IPA, 10.0.4.0..5739. the WU log shows "waiting for action by user"
it is happening with lawson installed flows or ones we developed

Woozy

Veteran Member

Posts: 709

9/23/2013 6:55 PM

It sounds like something goofy is going on with Async. Generally when Async stops working then new workunits don't start either - they stay in "Ready" status. Have you tried recycling services? At least LPS and Async - but I'd do everything.

I don't think I can help much beyond this. We're under Managed Services, so when we have issues like this we turn it over to AMS to resolve.

Sorry I couldn't help more. Good Luck