Question

Param.Name syntax in button action

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.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

Pega
December 19, 2016 - 8:23pm

Hi,

Why do you want your flow to be parameterized?

Can you upload a screenshot of your Parameters tab of your section which contains the button?

December 23, 2016 - 5:17pm
Response to SusanLiu

Hi,

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 : 

Caused by:
com.pega.pegarules.pub.PRRuntimeException: Error including section 'xxxxx' on page 'pyDisplayHarness' of  class 'xx-xxx'.
    at com.pega.pegarules.session.internal.mgmt.autostreams.AutoStreamRuleRuntime.getSectionStream(AutoStreamRuleRuntime.java:158)
    at com.pegarules.generated.html_harness.ra_stream_xxxx_464447dea53e6762bd758f08bcad355e.includeSectionBody_1(ra_stream_xxxxx_464447dea53e6762bd758f08bcad355e.java:3204)
    at com.pegarules.generated.html_harness.ra_stream_xxxxx_464447dea53e6762bd758f08bcad355e.generatePegaHarnessDiv_6(ra_stream_xxxxxx_464447dea53e6762bd758f08bcad355e.java:1988)
    ... 88 more
Caused by:
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
    at com.pegarules.generated.html_section.ra_stream_xxxxx_1db3d8bbc9b0d2d21e3e9ffab83a9373.execute(ra_stream_xxxxx_1db3d8bbc9b0d2d21e3e9ffab83a9373.java:105)
    at com.pega.pegarules.session.internal.mgmt.Executable.getStream(Executable.java:4033)
    at com.pega.pegarules.session.internal.mgmt.autostreams.AutoStreamRuleRuntime.getSectionStream(AutoStreamRuleRuntime.java:149)
    ... 90 more
Caused by:
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

 

Pega
December 20, 2016 - 4:04pm

Hi Ravi,

I have checked this on a Pega V72ml2 system.

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.

December 21, 2016 - 8:12am
Response to SaiDeepak

Yeah, that's exactly  is the behavior. Thank you for capturing screenshots.

 

Pega
December 21, 2016 - 2:04pm
Response to RaviR054

Please go ahead and raise an SR. And you can mention this post in the SR for reference.

Mod
December 22, 2016 - 1:46am

Hi Ravi,

Please let us know the SR number once you get a chance to create it. That way we can track it and follow-up this discussion with the resolution.

Regards,
Lochan  |  Community Moderator  |  Pegasystems Inc.

Lochana | Community Moderator | Pegasystems Inc.