Well… it does not exactly work as it does on Server / Hub - i.e. you can’t have that “next button”.
There are some workarounds though to create a somewhat similar experience.
You can use a Single Selection Widget combined with a Case Switch Node to steer what is visible in a component:
You set up the widget to re-execute on change.
You then connect it to the case switch start node and use the “index” flow variable to drive which port is active.
You then connect the output ports to your widget - you can even connect it to a full component that holds the view you want to make visible e.g. on page 1.
Whatever is connected to an inactive branch will not display and whenever you change the page, your view refreshes showing only what is connected to the now active branch.
Prototype is here:
differentpages.knwf (81.5 KB)