H A R N E S S (Rule-HTML-Harness/UI)

.Harness is an application related screen (also called work object form) of type Rule-HTML-Harness
.Mostly used standard Harness types are 4 which are available at Work- or @baseclass as explained below:
New: (For creating new work objects from UI)
.It is a brand new screen/form to capture the information (that drives the business process) from the user at
first time when the Work type/Flow is triggered
.Work object flow starts here in UI
Confirm: [Confirming work object resolution_(read only)]
.It presents the read-only confirmation display (like acknowledgement) of the Work object.
Perform: (Performing assignments on existing work objects)
.It allows a user to select a Flow action and to perform/complete an assignment
.It appears when an assignee (like Manager) opens the Work object to perform on it
Review: [Reviewing the closed objects_(read only)]
.It appears when try to open the pending work object status.
.It presents the work object and assignment in read-only mode, not allowing the data entry except by clicking
top right corner icons
.The Work user opens by find with Work object ID to know his work object status.
Harness Structure: (Harness-->Container-->Section-->Layout-->Cells)
S E C T I O N(Rule-HTML-Section/UI)
.Section (also called HarnessSection rule) is a reusable horizontal component/portion on the Harness
.Tasks to be performed in Section:
1. Operating Rows/Columns
2. Cells filling/adding/deleting/merging/...
3. Dragging a Section/Layout/Repeating Layout
.Layout:
.contains rows and columns made up of cells which in turn contain labels, buttons, URLs, icons, fields and nested
sections.
.It has 3 typesof Layouts:
1. Template (default): also called Smart Layout [fixed cells]
2. Repeating Layout: (applicable only for Page List/Group)
In turn it has some other layouts i.e. Row / Column / Tabbed / Grid /Tree Grid / Tree
3. Free Form: also called just Layout [control over cells]
Standard Sections:
1. Core Summary: : (where application's critical data resides)
This is the major main work area where the user gives the core information when creating the Work object
2. Confirm: It displays confirmation information for the work object
FLOW ACTION (Rule-Obj-FlowAction/UI)
.It allows a user to act on a Work Object/Item assigned (called Assignment)
.The arrows coming out of the (emanating from) Assignment shape are nothing but Connector Flow Actions or
simply
called as Flow Action.
.It is of 2 types:
.Connector Flow Action (Flow Action):
.It allows a user to act on a Work Object and causes that work flow/object (Assignment) to move/proceed
(from that
assignment) further (to another shape). [It causes the work object to progress along the connector to the next
task]
.Important options:
.Likelihood field:
.It determines the order in which the flow actions appear in the UI (order in the drop down list/button

sequence)
.% is just for representing purpose, not for calculating.
.Local Flow Action (Local Action):
.It allows a user to update the work object/object (Assignment)but doesnt allow this to
move/proceed(from the assignment)
Further (to another shape)
.Some of standard Flow Actions: (under WORK- class)
Standard Connector Flow Actions Actions:
Approve/Reject/Resolve/Assign/CancelAssignment/TransferToWorkBasket/Withdraw/RemoveSLA/Verify...
Standard Local Flow Actions:
AddAttachments/AddMultipleAttachments/AddParty/AttachANote/AttachAUrl/AttachAScreenShot/
AttachFromScanner/
ChangeAssignmentSLA/ChangeWorkSLA/TransferToManager/TransferToWorkBasket/UrgencyUpdate
Note:

Standard Attachment types are: AttcachAFile, AttcachANote, AttcachAScreenShot

Important UI Components:
1.
2.
3.
4.

Harness rule
Section rule
Flow Action rule
HTML Rule rule: (Customizing Screens)
.Used to customize the screens completely with hand coding of HTML or JSP.
.There are 2 ways to write the code:
a. under HTML tab of HTML Rule
Note: After create this HTML Rule; refer this in Harness/Section... rules with a single
line code
b. under HTML tab of 'Screen related Rules' (like Section/Harness) by unchecking 'Auto
generated HTML'
5. HTML Fragment rule: (reusable piece of code)
.This is just like 'HTML Rule' but it is reusable pieces of code (of HTML text, Java Script,
CSS, JSP) across organization.
.It is not tied to any specific class.
.It can be included in another HTML Fragment/HTML Rule/HTML Property rules whenever
the developers feel to
reuse this piece of code at their interest.
6. Portal rule (Rule-Portal/UI):
Portal is visualized into 2 parts i.e. Navigation Panel and Work Space
Navigation Panel:
The left panel of the portal is known as the Navigation Panel.
Workspace:
The right panel of the portal is known as the workspace. This area may contain lists, rule
and data forms, graphs, work object forms, or other controls, depending on your access
role and current task.
The appearance and contents of workspaces is determined by a portal rule.
7. Skin rule: (look & feel of Desktop/Work Object form/Reports/Rule Forms is customized
here)

.like Theme in your mobile where you can reference directly the HTML programs called
Style sheets.
.It defines the CSS used to display the Portal layout
.used to control the look & feel of Desktop/Work Object/Reports/Rule Forms
.for similar look and feel like same colors, boarders for all the screens in your project
8. Gadget, not a rule: (portion in Portal, not a rule)
.Every portion (rectangular area) in the Portal is known as Gadget where as the portion in
the Harness is known
as Section rule.
.Gadget has a purpose and control few things.
.There is a HTML Rule behind the Gadget and the class 'Data-Gadget' is there behind the
activities of Gadgets.
Ex: Work list area, My Work in Progress, New, Find.....
.We can customize the Gadgets under Data-Gadget class
.We can control the Gadgets in Portal rule.
.Portals look & feel depends on the Gadgets
.Client Event: controls dynamic form actions based on user updates or values for this field
Ex: We will write the code in Activities to perform the actins when the Control actions (like
button click...) happened.
.There 3 Client Events in PRPC 6.1:
.OnClick:
.OnChange:
.OnBlur: when focus releases/control comes out