Skip to end of banner
Go to start of banner

UI Page Structure and Terminology

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The EmpowerID web user interface is made up of the pages within the UI container role as well as the user interfaces provided by the microservices applications (e.g. IT Shop, My Identity, etc.). The user interface within the UI container role adheres to a defined structure which is helpful to understand when supporting the EmpowerID platform and communicating with EmpowerID support staff.

Overview

  • The pages in the UI container role are a responsive design web application built using Microsoft ASP.NET MVC and HTML5

  • The user interface is themeable/brandable and can be branded and styled using CSS and JavaScript

  • Out of the box pages can be “overridden” with custom pages by copying your custom page of the same name into a mirrored folder structure called “Overrides”

  • Pages can be classified based on a few specific templates that are repeated for different types of objects (e.g. People, Groups, etc.)

Navigation Sidebar

  • The Sidebar is how you navigate the pages of the EmpowerID Web site and search for people and other types of resources.

  • The sidebar is “security trimmed” which means that the number of sections and links in the sidebar that a user can see will differ according to the amount of access your organization has given them.

  • The sidebar also contains the Global Search control

Find Pages

  • Each type of object in the EmpowerID system has a Find page that lists the objects of that type stored or referenced in the Identity Warehouse

  • The URL for Find pages is: https://%yourserver%/ui#Common/Find/%ObjectName%

  • On the server Find pages are located under %InstallFolder%\EmpowerID\Web Sites\EmpowerID.Web.PortableAreas.Common\Views\ObjectTypeSearch

  • Find pages typically contain one or more tabs listing objects of that type

  • Find pages can optionally also include a Tree pane of locations on the left and an action pane of workflows and page actions on the right

View One Pages

  • Viewone pages are what display a single instance of any object. For example, when clicking on the link for a group in the Find Group page the next page to load is the Viewone page for that group

  • Viewone pages are typically read-only and are used to display information about an object and any related data

  • More than one Viewone page can exist for a specific type of object in order to show only relevant fields in cases where a single type might have many subtypes – e.g. Account for AD versus Account for Office 365

  • The specific Viewone page to be loaded is defined by logic on the SQL view and configured in what is called ResourceTypeFormIdentitifiers that define each subtype and the Viewone and Editone to load

  • Viewone pages are located:

    • %InstallPAth%Root\UI\Web Sites\EmpowerID.Web\EmpowerID.Web.PortableAreas.Common\Views\ViewOne\Details

Edit One Pages

  • Editone pages are what display a single editable instance of any object. For example, when clicking on the link for a group in the group’s Viewone page, the next page to load is the Editone page for that group

  • More than one Editone page can exist for a specific type of object in order to show only relevant fields in cases where a single type might have many subtypes – e.g. Account for AD versus Account for Office 365

  • The specific Editone page to be loaded is defined by logic on the SQL view and configured in what are called ResourceTypeFormIdentitifiers that define each subtype and the Viewone and Editone to load

  • Editone pages are located:

    • %INSTALLPATH%\Root\UI\Web Sites\EmpowerID.Web\EmpowerID.Web.PortableAreas.Common\Views\EditOne

  • Each Editone page will send its edited data to one or more workflows for processing

  • No labels