ShowTable of Contents
Portlet Factory Events
When you use Smart Refresh (new in WPF 7.0) or Partial Page Refresh (or Portal's Client Side Aggregation support) in a model that is firing a Portlet Factory event, only the source portlet user interface (UI) will be refreshed as a result of the action. The event will have been received by the event handler in the target model, but there was nothing to tell it to refresh its page. There are a couple of ways to remedy this.
1) In the action UI builder (for example, the Link or Button builder) that is used to initiate the event, you can change the Post-Action Behavior to Always reload the top-most page after running action. To see this option, you will have to check the Show Advanced Option check box. This setting causes the entire portal page to refresh.
Here is an overview of the steps when using Factory Events with Smart Refresh:
1. In your Event Declaration builder, check the Use Client-Side Delivery option. (Also keep the Fire Event on Server checked.)
2. In the Target model, add an Event Handler and a Client Event Handler builder.
3. The Event Handler action should only process the data passed to the event. This handler must not do any page processing.
4. In the Client Event Handler, you should invoke an action that processes a page. Either directly call the page action, or call an action that does a process page.
Cooperative Portlet builder
When you use the Cooperative Portlet builder where the "type" is set to Property Broker Action
(that is, you are creating your own action UI Button or Link), you will need to set the Post-Action Behavior to Always reload the top-most page after running action
. To see this option, you will have to check the Show Advanced Option
checkbox. This setting causes the entire portal page to refresh. In this use case, if you want to avoid the entire page being refreshed, you must change the Portal page to Client Side Aggregation.