Difference between revisions of "MultipageTimeout"
| (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, and instead is only reloaded after the number of seconds specified in the '''multipageTimeout''' parameter. |
==Usage== | ==Usage== | ||
Latest revision as of 21:05, 14 May 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, and instead is only reloaded after the number of seconds specified in the multipageTimeout parameter.
Usage
Specified as:
multipageTimeout={seconds}
where {seconds} is the number of seconds (since it was last loaded) after which the Web Assistant will be reloaded anyway.
