Support Article
Action buttons don't work on a web node
SA-2044
Summary
After following IAC documentation and creating a whitelist of May Start activities to prepare for switching the server to a web node, clicking on any application button with an on-click action will result in a failure message. The following entry in the Alert Security log may also be seen:
"Activity 'HLQ-VS-AS-SelfSvc-Work-Reg.Add' was not allowed to run in WEB node because <it is not in the allowed activities list/its pyInputMayStart property is not set/it requires authentication>"
and
"Activity 'HLQ-VS-AS-SelfSvc-Work-PersDat.ProcessAction' was not allowed to run in WEB node because <it is not in the allowed activities list/its pyInputMayStart property is not set/it requires authentication>"
and
"Activity 'HLQ-VS-AS-SelfSvc-Work-PersDat.ProcessAction' was not allowed to run in WEB node because <it is not in the allowed activities list/its pyInputMayStart property is not set/it requires authentication>"
This can occur even though the out-of-the-box activities "Add" and "ProcessAction" are in the May Start list. They are listed in parent classes i.e.
1. "ProcessAction" is in baseclass and
2. "Add" is in Work-Cover
2. "Add" is in Work-Cover
I tried to add HLQ-VS-AS-SelfSvc-Work-PersDat.ProcessAction to the list but that made no difference. I also tried to generate the may start list without class name but the same problem was still occurring.
Error Messages
Activity 'HLQ-VS-AS-SelfSvc-Work-PersDat.ProcessAction' is not allowed to run in a WEB node because <it is not in the allowed activities list/its pyInputMayStart property is not set/it requires authentication>
Steps to Reproduce
Expose an application with buttons that have actions associated with it e.g. Add New Work and log into it using IAC connecting to a web node.
Root Cause
Known issue when using the externalized prconfig.xml. The PRPC web node does not function and experiences the same maystart.xml reference issue you have reported.
Resolution
Including the maystart.xml entries inside prconfig.xml. If using an externalised prconfig.xml on a Tomcat deployment, removal and regeneration of the PegaTemp directory contents should address the problem.
Please note that when switching the nodetype of PRPC, the PRGenJava and PRGenClasses direcories in PegaTemp should be deleted. This should be done to ensure all activities are being regenerated with the correct flag of “Allowed to run in web mode”.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.