Discover how to add or edit embedded data using actions with full control. Apply pre/post processing for smarter interactions, validate entries instantly, and refresh forms dynamically. Perfect for complex workflows requiring accuracy and automation.
@MarcCheong Hi, is functionally limited to only for embedded reference? are we able to use from landing pages with list view and insights, when we create a new record to check the record already present and avoid duplicates records and all?
If you configure an Embedded Data list of record field to appear as a table that is editable in a modal dialog box, you can now source the content of that modal from either a View or an Action. Because User Actions support pre- and post-processing and refresh condition, when you use them in an embedded table, you can define validations that can help your users avoid inputting incorrect data.
Creating new data instances from a list view, this is not part of this feature. I don’t believe there is a way to execute your business outcome exactly like outlined above - you’d likely need to do somethings with keys to avoid duplicates, like you would of done in UI Kit when delegating data… However, its not an area I’ve explore in depth. I’d suggest starting a new Conversation on UX Expert Circle, see if we can find someone in the community with experience in this area
Hi @MarcCheong , I have tried using TOP for prepopulating embedded data list. Which is working. However, I am trying to add a post processing activity, which will check if same email id will be entered for multiple rows of embedded list.It will throw error. As per the documentation, from the post processing activity, we can put reference like TOP.ApplicantList where ApplicantList is the embedded data list created on work page.I am not able to save the activity with this reference.I have done show page on TOP so that I can see content of TOP at runtime and it shows my whole pyworkpage within TOP including the embedded field.But when I am trying to looping through it, it is not allowing me to the reference.
I do not know why specifically it won’t allow looping - that may be worth raising a ticket to Pega Support to understand why.
As for the need to validate - could you not just use a validation rule on the case flow action? I know that would work. You might be able to do it inside the embedded data’s flow action, but you may also hit the issue with “TOP” again (i have not tested this).
Putting the validation in the modal might also cause UX issues. If I can not see the other items in my list, and you’re telling me this email is already in the list, i need to cancel out of the modal just to verify that. Having it on the case, where i can see all my rows could be a nicer UX?
Hi Marc, Thanks for responding .I have used validate rule inside embedded data list flow action.I mean, I have used user action instead of view inside Embedded data list and in that user action I have used validate rule, that is working fine.Though it doesn’t have TOP reference.But in the same user action, I have used a pre processing data transform where I have used TOP reference to prepopulate data from workpage.That is working fine.Only for looping in post processing specially where I have to refer the list through TOP refrence, it’s failing.Lets see if anyone else has faced similar issue.
