USER INTERFACE

1 of 25

Contents

User Interface
Harness
Section
HTML Rule
HTML Property
HTML Fragment
Gadget
Portal
Skin
The Rule Inspector

Duration 2:00 hrs

(All the screenshots are taken from PRPC 5.1)

2 of 25

Extracts from exam Blue Print

Developer Portal
Navigate and use the components of the Developer portal to
display and create rules
Use the navigation panel tabs to access the different parts of the
PegaRULES database or application
User Interface Rules
List and describe the HTML rule types that form the user interface:
Harness
Section
Fragment
HTML Properties

Identify the standard harnesses and their functions

Use the Rules Inspector to identify HTML rules and properties
3 of 25

Extracts from exam Blue Print.

Override default Harness and Section rules to:
Include and remove properties
Add buttons and icons
Alter the display

Understand the benefit of automatically generating HTML and the

Consequences of overriding this feature
Property Display
Use HTML property rules to define field display and input formats
for:
Calendars
Select lists
Currency
4 of 25

Extracts from exam Blue Print.

Validation
Understand the difference between client-side and server-side
validation
Understand how and when validation rules are used
Identify the standard validate rules and their functions
Portals
Understand the components of a portal and where they are defined

5 of 25

User Interface
User Interface consists of several rules which are dynamically
converted to HTML form. This process of conversion is known as
Stream Processing.
User Interface Components:

Harness
Section
HTML Rule
HTML Property
HTML Fragment
Gadget
Portal
Skin
6 of 25

Harness
Are listed in User Interface rule category
Use harness rules to define the appearance and processing of work
object forms used in your application to create work objects and process
assignments.
Together with section rules, HTML rules, property rules, and others,
harness rules define the structure, appearance, and behavior of the forms
used in applications to create and update work objects and assignments
Process Commander includes more than a dozen standard harness forms

7 of 25

Harness.
Harness

8 of 25

Several Standard Harness Forms

New :

Supports entry of a new work object and the start of a flow

rule execution for that work object.
PerformAllows :

A user has to select a flow action from a drop-down list in the

take Action section, and complete an assignment based on
the selection.
Confirm :

Presents a read-only confirmation display of the work object,

acknowledging user completion of an assignment. Contains
the Get Most Urgent button, which is normally linked to the
standard activity Work-.GetNextWork. Your application can
override that activity.

9 of 25

Several Standard Harness Forms

Review :

Presents the work object and assignment in read-only mode,

not allowing data entry.
Reopen :

Allows a user to reopen a resolved work object.

10 of 25

Section
A section is a portion or area of a standard work object form that

is incorporated on a harness form.

Sections may contain other sections, informally called subsections .
The appearance, behavior, and contents of a section are defined

by a section rule (Rule-HTML-Section rule type). Section rules are

referenced in harness rules .
They are many Standard Section Form provided in PRPC. For e.g.

CoreSummary:
Main work display area when creating a work object.
Confirm:
Displays confirmation for the work object.

11 of 25

Section.
Section

12 of 25

HTML Rules

Are Listed in the Technical rule Category.

Use an HTML rule to describe how the system is to assemble,

through stream processing, portions of HTML displays in your
application.

Are referenced by Harness and Section rules and many standard

HTML Rule

HTML rules are available.

13 of 25

HTML Property
Use HTML Property rules to control
how properties appear on work object
forms, correspondence, and other
HTML forms, for both display and for
accepting user input.
Are Listed in as part of Property rule
category.
Nine standard HTML Property rules
accept input parameters
Date
DateTime
Decimal
Integer
Percentage
PromptSelect
Text
TextArea
Time

HTML Property

14 of 25

HTML Fragment
Use HTML fragment rules to
define universally available HTML
parts, such as style sheets and
scripts, including JavaScript or
JScript files.
This text can be inserted into
other HTML rule instances during
stream processing.
In contrast to text file rules,
HTML fragment rules can contain
JSP tags (or directives) and so can
produce dynamic content that
depends on property values .
Can be called inside HTLM Rule
and HTML Property.

15 of 25

Gadget
A gadget provides a rectangular area on a portal display and each

gadget contains a control that a user can interact with.

We can change the appearance, label, location of gadget on portal

layout.

Gadget

16 of 25

Portal
Define the Portal Layout
Are listed as part of User Interface rule category.
Through Portal we can determine

Bar that appear in Navigation panel and their labels.

Which gadget appear beneath each bar .
Which gadget appear in the workspace sections and their labels.

17 of 25

Skin
A skin rule is an instance of the Rule-Portal Skin rule type. A skin

rule defines four Cascading Style Sheet (CSS) files, stored as text file
rules, that together determine the colors, fonts, images, and layout
of portal, work object, rule forms, and report displays .
Use the Style Viewer tool to identify and preview the appearance of

styles in a CSS file.

We can determine styles for the

Desktop, Work, Reports, Rule forms.

18 of 25

Rules Inspector

19 of 25

Rules Inspector
This tool provides an easy way to locate rules present in the user

interface.

Can be used to display :

Harness being used.

Section being used.
Properties being used.
Declare Expression used.
Refer Lab to navigate Rule Inspector.

20 of 25

Rules Inspector.

Check mark any one of the rule .So that u can view in the User Interface

21 of 25

Added Information
For more information you can refer the below links.
User Interface Concepts and terms
http://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCo

mmander/documents/PRPC/Help_V54/concepts/concepts2/concepts
userinterface.asp

How and why to use the Rules Inspector tool

http://pdn.pega.com/DevNet/PRPCv5/KB/24070.asp
About Harness rules
http://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCo

mmander/documents/PRPC/Help_V53/rule-/rule-html-/rule-htmlharness/main.asp

22 of 25

Added Information
About Section rules
http://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCo

mmander/documents/PRPC/Help_V53/rule-/rule-html-/rule-htmlsection/main.asp

About Skin rules

http://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCo

mmander/documents/PRPC/Help_V53/rule-/ruleportalskin/main.asp

User Interface Category

http://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCo

mmander/documents/PRPC/Help_V53/category/userinterfacecatego
ry.asp\

23 of 25

Summary
This topic familiarized us with :
We Identify the components that make up the User Interface.
About the Rule Inspector

( Complete the Lab Exercise of this topic.)

24 of 25

Thank You

25 of 25