Iterative Development helps the developer to see the changes by just a refresh of the page in the integrated Server.
This makes the portal application development easy and rapid development.
Disadvantages of enabling this is that the application will run slowly as all the performance optimization settings will all be disabled. The ‘Delete Customization Before every run‘ is to be checked if we plan to enable the iterative Development option.
By default the iterator will refresh when the user first enters the page. But sometimes you need to control the refresh action of the iterator for some reason.
There are three optional iterator properties Refresh, RefreshCondition,and RefreshAfter which will control the refreshing of the iterator accordingly.
ChangeEventPolicy property in the iterator controls the behavior of the refresh action. It has three properties
none – by default, iterator refreshes according to the refreshcondition specified
push – asynchronous data change in the model layer will be pushed automatically.. used in BAM and Active Data Components
ppr – this will decide on when to refreshes the components bound to the iterator. If the current row of the iterator is changed and when the ppr is occurred the iterator will get refreshed to reflect the changed data