Hey,
did you also add a "Page event mapping"?
I got it working on my side, here's all the stuff I have, hope it helps.
An EVAM Definition with a Data Source and a View Config Bundle:
The View Config Bundle has a View Config:
I made a new View Template, which looks like this:
The "my_event" event is a a new Declarative Action for the View Config I made:
Which looks like this:
The client action is a custom one I made:
The "Action Payload Mappings" record was automatically created iirc.
My Page in UI Builder looks like this:
It has a Data Set Component an EVAM Data Resource, which uses the definition above and a simple Client Script, which logs something to the browser console.
(The "Playbook 1" component is not important, it was for a PoC.)
The Events tab on the Page Body element looks like this:
I added the "Random event name" as a new Handled Event. Then I added an Event Mapping for this new Handled Event.
The mapping maps the execution of the Client Script to the Handled Event.
And then for the last manual step, I went into the Data Set Component's configuration to edit the "declarative action mappings":
The mapping shows that the Declarative Action "my_event" (label "My Event :-)"), which an EVAM Card is configured to fire via the View Template, is mapped to the Handled Event "Random event name" of the Page.
One last thing that UIB did automatically:
The Declarative Action "my_event" automatically got a "UX-addon Event Mapping" at some point:
If I read the data correctly, it must have happened when configuring the declarative action mapping for the Data Set:
Result:
This is my test Page:
And this is the firing Client Script, happily logging something to the browser console:
Conclusion:
The whole chain of things is - in my opinion - outrageously complicated and error prone.
If you slip up even a tiny bit, you're left completely stranded without proper documentation or help or debugging capabilities.
Best regards,
Aaron
