Hi Dinesh,

May I know the reason why you went for Parameter display type: Section ?
If you have defined those in the above Parameter field you can use inside the code with the below code.

JAVA : StringUtils.crossScriptingFilter(tools.getParamValue("myParameter")) - CSF filter for better security.
JSP : <pega:reference name="Param.myParameter" />

Hi Durai Sankar,

In my POC I have to configure more than 40 properties based on four scenarios. for each scenario I have to collect only 10 properties.
there will be four radio button if we click first radio button, section will display properties according to the first scenario

developer should configure properties based on their scenario only.

for this validation requirement only i have selected in Parameter display type: Section

Got it Dhinesh.

We can't use (RH_1.pySections(1).pySectionBody(1).pyTable.pyRows(1).pyCells(1)) as it is a Pega generated page for processing section at compile time. It may not be available at runtime.

For using Parameter display type: Section, We have to load custom param section on a Page property, and then we have to access from the clipboard.

Example : OOTB Chart control is implemented like this method.

They initialized .pyHTMLParams page using custom code, loaded param fields section on .pyHTMLParams property and accessed the value using the below code in their control.

tools.getPrimaryPage().getPage(".pyHTMLParams").getString(".reportParameters")

Go through Chart control for more clarity.

I hope it helps! Let us know if you have any questions while implementing the above.