1

FR

Pega Certified Senior System Architect(v8)

• Introduction to customizing a user portal

• Applications often support multiple types of users, such as case workers and
managers.
• Each type of user interacts with the application in a unique manner. For example,
case workers create and process cases, while managers track the progress of
cases.
• Each type of user needs access to tools and features that support their role in case
processing.
User Portals

• User portals provide application users with the tools and options needed to work
with a Pega application. Each portal is tailored to a specific user role.
• A user portal provides a view of the application to the application users.
• Pega provides several default user portals.
• Each portal is customized to the needs of a specific type of user.
User Portals

• While these portals can be used in an application as is, some situations require that
you customize the layout of the portal or the tools presented to the user.

• For example, case workers can use their portal to create new work, complete
existing work, and run reports. Managers can use their portal to monitor cases in
progress and run reports that show case worker and case metrics.
Harnesses

• A harness organizes the structure of a portion of the user display. In Pega, you use
a harness to organize either a work form or a portal.
• Harness records describe the structure of the UI.
• Pega applications commonly use four standard harnesses to organize the content
of user forms.
Customizing a user portal
Customizing a User Portal

• You can customize the default end-user portals provided in Pega to meet many
project requirements. If the requirements are complex enough, you can also create
a custom application portal.

• In Pega, a portal is represented with a portal rule. A portal rule identifies the type of
user expected to use the portal, the harness used to organize the portal contents
and the skin that defines the branding applied to the portal.
Customizing a User Portal

• To configure a Pega portal, you identify the intended user role and portal type,
organize the layout of the portal, customize the branding of the portal, customize the
content and tools available to users, and configure an access group to reference the
portal if necessary.

• Portal records are listed in the User Interface category in both the Records
Explorer and the Create menu.
1. Identifying the intended user role and portal type
• In Pega, you configure a portal for use by either users or developers. User portals
are intended for users who do not routinely need to update rules. Developer portals
are intended for system architects and business architects, who routinely update
rules. User portals require less memory on the user's workstation than developer
portals.

• Pega supports two portal types: composite and custom. Composite portals are
defined by harnesses and sections. Composite portals are cross-browser
compatible and support Microsoft Internet Explorer, Mozilla Firefox, Apple Safari,
and Google Chrome browsers.

• You select the user role and portal type on the Details tab of the portal record.
2. Organizing the layout of the portal

• The organization of the portal affects how the contents of the portal are presented to
the user. The default user portals are organized with a header, a left navigation
pane, and a content pane.

• To change the layout of the portal, you change the screen layout used in the
harness. To modify the content in these sections, you use Live UI to identify and
open the section to configure.
3. Changing the branding of the portal

• You can customize the appearance of a portal by applying a skin. Skins contain
instructions for formatting elements of the user interface, such as text size, font
style, and background color. To customize the appearance of a portal, you choose
between applying the application skin to the portal and configuring a skin for the
portal.

• When you select the application skin, Pega applies the skin for the active
application to the portal. If the user switches applications, Pega applies the skin for
the new application to the portal. If you create a new portal, Pega configures the
portal to default to the application skin.
4. Customizing the content and tools available to users

• You can add or remove content displayed in a portal by updating the sections
referenced in the screen layout. To modify portal content, use Live UI to identify and
open the section to update. To override records provided in the UI-Kit ruleset for
standard portals, copy the record into an application ruleset.
a)Customizing portal menus

• You can add a menu to a portal by using a navigation record. A navigation

• A navigation record contains a list of menu items. For each menu item, you
associate a click event and resulting action, such as logging off or displaying a
harness.
b)Replacing the Pega logo

• You can update the icon displayed in the upper left corner of the portal. Standard
Pega portals display the Pega icon.
• You can update the portal configuration to display a different icon, such as a
company logo.
• To add an image or another non-text file to a Pega application, Pega creates a
binary file record.
• To update the icon displayed in a portal use App Studio, go to Settings > Theme,
and upload a new logo. This instructs Pega to create a binary file to store your
image.
c)Customizing the dashboard content

• You can customize the content displayed on the dashboard of the Case Manager
portal.
• For example, a manager often wants to view the status of cases processed by their
unit or work group. You can configure the Case Manager portal to display one or
more dashboard widgets that provide insight into the status and progress of open
cases.
• Dashboard widgets are organized into two or more slots using a dashboard
template.
5. Configuring an access group to reference the portal

• To provide users with access to a user portal, add the portal to one or more access
groups.
• To add a portal to an access group, list the portal in the Available portals section of
the Definition tab of the access group record.
• For each access group, you select one portal for Pega to use as the default portal.
• Pega presents the default portal to a user when the user first logs in to Pega.
• The remaining portals are available to users from either the Operator menu or
the Launch menu, depending on the portal.
Questions ??
Thank You