Hello Alex,
The trick is to pull the event outside of your collection. You can try it by
- (cleaner, but harder to implement, and I'm not sure the collection mashup parameters are updated bi-directionally, so it might not work) Changing a mashup parameter from within your collection widget and "subscribing" to the changes in the outer mashup via an Expression or Validator bound to the collection data source.
- (quick, reliable, but a bit dirty) Changing a Session variable from within your collection widget, and "subscribing" to the changes in the outer mashup via an Expression or Validator, bound to that session variable. Session is a good and simple mechanism for propagating events through the mashups hierarchy, for good or for worse.
To clarify option (2), the control flow will be the following: [Button click inside collection] --triggers--> [Expression, which generates a random number or the current timestamp in milliseconds] --output--> [Session variable "buttonClicked"] --triggers--> [Expression in the outer mashup, which is configured to fire on data change] --OnChange event triggers--> [Navigation widget in the outer mashup, which displays your popup].
/ Constantine
