Difference between revisions of "Multipage"
From SAP Enable Now Wiki
| (One intermediate revision by the same user not shown) | |||
| Line 6: | Line 6: | ||
==Purpose== | ==Purpose== | ||
| − | By default, the | + | By default, the Carousel will be re-loaded (effectively re-started) every time the user navigates to a new page (screen) in the application. This can cause problems with applications that typically navigate through several screens in a single task, especially with Guided Tours that span these screens. If the '''multipage''' parameter is set to '''true''' then the Carousel is not automatically reloaded on page change. (But see the '''[[multipageTimeout]]''' parameter.) |
Note that this parameter is set automatically by applications that require it. You should not need to manually set it. | Note that this parameter is set automatically by applications that require it. You should not need to manually set it. | ||
Latest revision as of 13:02, 18 February 2024
Scope
SAP Companion parameter, specified either in the URL or in the SAP Companion parameters in the linked application.
Purpose
By default, the Carousel will be re-loaded (effectively re-started) every time the user navigates to a new page (screen) in the application. This can cause problems with applications that typically navigate through several screens in a single task, especially with Guided Tours that span these screens. If the multipage parameter is set to true then the Carousel is not automatically reloaded on page change. (But see the multipageTimeout parameter.)
Note that this parameter is set automatically by applications that require it. You should not need to manually set it.
Usage
Specified as:
multipage=[true|false]
