why Param.Name syntax is not supported for certain button actions ? I noticed it for Create Work, Set Value Actions. while it works for Run activity etc.
Harness -> Section with a button. Define Create Work action on click of button.
For Create Work, you give a class name and flow name.If the flow is parameterized, you would see the parameter showing up in the rule form and to populate that if you use Param.Name logic the section itself fails with jsp gragment error. sometimes it doesn't allow you to save the section itself.
The flow needs an input to start with. The input comes from an external application thru IAC.
The screenshots mentioned in the subsequent comments depict my configuration. I just attached the button action I tried too if it helps.
Th weirdest thing is the section and button save perfectly fine and the error is thrown at runtime saying :
com.pega.pegarules.pub.PRRuntimeException: Error including section 'xxxxx' on page 'pyDisplayHarness' of class 'xx-xxx'.
... 88 more
com.pega.pegarules.pub.PRRuntimeException: Section 'xxxxxx' execution error on page 'pyDisplayHarness' of class 'xx-xxx'. : The page or property Param is read-only, and cannot be modified. Calling method: PageDirectoryImpl.getPage Details: reserved page named 'Param' does not exist and cannot be created
... 90 more
com.pega.pegarules.pub.clipboard.ReadOnlyException: The page or property Param is read-only, and cannot be modified. Calling method: PageDirectoryImpl.getPage Details: reserved page named 'Param' does not exist and cannot be created
I see that we get a run time error (in PegaRULES log) when we have a section configured as you described for 'Create Work' action. And the work object doesn't display this section at all
Error snippet, com.pega.pegarules.pub.clipboard.ReadOnlyException: The page or property param is read-only, and cannot be modified. Calling method: PageDirectoryImpl.getPage Details: reserved page named 'param' does not exist and cannot be created
Please go through screen shots of design and error file and confirm this is exactly the behavior you are reporting in this post.
Once confirmed we can raise an SR for this to get an explanation/solution for this behavior.