Page Overloading can achieved by specifying Device and/or Priority. When a user logs in with roles that allow access to multiple pages with the same MOP then Device and Priority are used to determine which of these pages is to be used. If a particular Device matches the current device then that page is favored. If multiple pages with the same (or no) Device are available then Priority is used to disambiguate with the highest Priority number favored.
Assembly: EAP.Core (in EAP.Core.dll) Version: 220.127.116.11 (18.104.22.168)
[SerializableAttribute] public class PageInfo : IEAPBase, ICloneable, ICacheable
<SerializableAttribute> Public Class PageInfo Implements IEAPBase, ICloneable, ICacheable
If you need to set page-instance-specific properties you can use the GetClonedPageInfo()()()() method, available on most pages, to relatively efficiently obtain a cloned PageInfo object for the page (it will return the existing PageInfo object if already a clone else if not already a clone, it will clone the PageInfo, set it on the page, and return it).