About Active Pages
Active Pages are Magentrix's framework for building custom UI inside the portal. Each Active Page is a record administrators create at Setup > Develop > Pages; the actual page markup, components, and code are authored in the in-portal IDE that opens when you edit the record.
This page is the administrator's overview — what an Active Page is, how its records are organized, who can edit them, and how access is granted. The development reference, component library, and all code-level documentation live in the Developer Guide.
Where Active Pages Live
Active Pages have two entry points, and they do different things:
- Setup > Develop > Pages — the administrative list. From here you create new records, edit page metadata (Label, Description, Type, Version, attached Controller), configure sharing, clone, and delete. This entry point does NOT open the code editor.
- The IDE at /sys/ide — the in-portal code editor where developers author markup, components, JavaScript, CSS, and code-behind. Open it directly, or click the Open in IDE button on any Active Page's detail view. Most developers work entirely in the IDE rather than navigating through Setup pages. The IDE itself is documented in the Developer Guide.
Use the Setup pages when an administrator needs to manage records (visibility, sharing, deletion). Use the IDE for everything related to authoring or modifying page content.
Active Page Types
| Type | What It Is |
|---|
| Active Page | A standalone page rendered at its own URL. Can have a Controller (an Active Class) attached to handle requests, model binding, and persistence. |
| Active Template | A reusable layout fragment included from other Active Pages. Used for shared headers, footers, and partial views. |
| Active Content | A content fragment, typically used inside Engagement Pages or other host containers. |
Versions
Each Active Page is associated with a version of the Active Pages framework: 2.0, 3.0, 4.0, or 5.0. The version determines which components and conventions are available. Newer versions have richer component libraries and improved rendering. Existing pages remain at the version they were created on; new pages should use the latest available version unless a specific reason calls for an older one. Component availability per version is documented in the Developer Guide.
Mobile and Tablet Variants
An Active Page record stores up to three content variants:
- Content — the default desktop markup.
- Mobile Content — an optional override served on mobile devices.
- Tablet Content — an optional override served on tablets.
If a variant is empty, the desktop Content is served on that device class. Variants are created and edited from the IDE; this overview only notes their existence.
Active Page and Active Class Together
Most Active Pages have a Controller, which is an Active Class attached via the page's Controller field. The Controller handles incoming requests, prepares data for the page, and processes form submissions. An Active Page can also exist without a Controller for purely presentational content. See Controllers Overview in the Developer Guide for the technical relationship.
Use Cases
- Custom self-service flows. Build a portal flow that doesn't fit the standard entity layout — for example, a multi-step deal registration wizard, a partner application form, or a guided onboarding experience.
- Custom dashboards. Compose data from multiple entities into a single screen tailored to a specific audience.
- Embedded widgets. Build an Active Page once, then embed it in an Engagement Page through the Active Pages widget so the same content appears on a landing page.
- External-facing landing pages. An Active Page can serve unauthenticated visitors when shared with the Guest Role.
Permissions and Sharing
- Only administrators can create, delete, or share Active Pages.
- An Active Page is visible to a portal user only when it is shared with one of their Roles or User Groups, or with the Guest Role (which opens it to all authenticated users in addition to anonymous visitors).
- Sharing supports Roles, User Groups, and specific people. Group-based sharing was added so admins can grant access by segment without assigning new Roles.
- For the full sharing model and the exact behavior of Guest Role and Group sharing, see Sharing Active Pages and Classes.
Where to Go Next
About Active Classes >>