We are using Pega v8.4.4
Multi select control isn’t working on a Model dialog window, where as same configuration is working fine in normal section.
Steps to Reproduce
- Drag & Drop a table in section
- Configure a page list property in general tab.
- Add a link in one of the column and add Local action. Select Modal dialogue and provide flow action details.
- Open the section referred in flow action and configure a Multi select list control.
- Create page list property
- Drag & Drop in that section
- Select control as “MultiSelectList”
- Give the source as a Data Page for smart prompt.
Hi Rajasekhar,
Table layout needs to configure as optimized, to support native controls like multiselect.
Thanks,
Sreedevi
@Sreedevi9193 . Thanks. Optimized configuration is read only. we need Editable view.
@RajasekharU0829 :
Below is the difference in rendering between templatized and non-templatized control:
Templatized control renders on client side. On screen load the metadata is send by the server later on the specific content is getting load. In non-template control, the whole data is getting loaded on the server side and the result is shown on the screen.
In the multiselect control on the grid the section that is getting loaded is non-template and the multiselect control is templatized control. On screen load, the section getting loads the whole script with data whereas the multiselect control loads only the metadata and on second refresh it loads the data related to that previously loaded metadata.
This is the reason why the template control is not getting loaded in the non-template section.
Advanced parameter sections are rendering as non-template causing new controls like multiselect not to render. "
As this is by design, we would not able to achieve your requirements.
Enhancement request raised.
@RajasekharU0829
please share the INC/enhancement request ID for adding it to the post for future reference.
Thank you!