Difference between revisions of "MultipageTimeout"
(Created page with "__NOTOC__ {{DISPLAYTITLE: multipage}} ==Scope== Web Assistant parameter, specified either in the URL or in the Web Assistant parameters in the linked application. ==Purpose=...") |
|||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | {{DISPLAYTITLE: | + | {{DISPLAYTITLE: multipageTimeout}} |
==Scope== | ==Scope== | ||
Revision as of 10:03, 20 September 2021
Scope
Web Assistant parameter, specified either in the URL or in the Web Assistant parameters in the linked application.
Purpose
By default, the Web Assistant 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 Web Assistant (and Carousel/help) are 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.
