Hi Experts ,
We are exploring the functionality of the PegaExtension_CheckBoxTrigger DX Component in the Constellation UX Gallery using the Community Edition. I’ve attached the configuration details along with the error we’re encountering. Could you please help us understand the cause of this issue?
@Unnikrishnan T N I see that the property is not marked primary (storybook - Storybook), you may want to do that first.
Looking at you screenshots, it is not directly clear where the issue is, check the network tab and see if there are any issues there. That will help you understand where it is coming from
@Ronald de Lignie,
Thanks for the response ,
I tried by making that field also as Primary still same issue
I dont see any error in network tab.@Ronald de Lignie,
@Unnikrishnan T NDoes it work in the Computerland application?
@Ronald de Lignie ,
Thanks for pointing it out , I checked the computer land application and configured our app accordingly.
Attached are the screenshot from both applications. The savable data page input payload is going as null in both occasions.
@Unnikrishnan T Nyour payload seems incorrect. It generally is ‘dataViewParameters’ instead of ‘data’. But in your app screenshot I can see 2 refresh calls, so the base-functionality seems to work
@Ronald de Lignie
Thanks for responding to the query .
First refresh was one because of a previous action and we have a D_Page trigger followed by refresh in my case .
in ComputerLand Application also you see , null payload goes . D_Page is of type savableamd API status enabled
@Unnikrishnan T N
I have configured it in same way as its mentioned in Computer land application and CheckboxTrigger Component | pegasystems/constellation-ui-gallery | DeepWiki
But still I dont see the expected payload trasnferred , any help would be appreciated . If its working for anyone could you please share configuration details.
Thanks in advance .
I have further debugged same by creating same componenet in my side , I dont see the dataInfo in
const data: any = (window as any).PCore.getStore().getState().data?.[context]?.dataInfo?.content;( I have attached screenshot ) , but I checked it in ‘caseInfo.content’ where I could able to see the ListEntry via pageReference( attached it ) , Could you please check once . If the d_page call and bodyData is in expected format.
I found the the implementation and how its working . Its from the context of list data set not from primary page context as I have seen the code was written in CheckBoxTrigger accordingly , ourusecase was to do the similar from a work page embed context. But current component was built for list data record . We will try a different implementation for our requirement .
