pega user interface concepts

8/9/2019 Pega User Interface Concepts

1/32

User interface - Concepts and terms

Based on HTML and XML standards, Process Commander can support a wide range of user interaction facilities and

approaches. our application!s user interface can ta"e into account the en#ironment, the domain "nowledge of $our users,

their s"ills, locale, and language.

The appearance, %randing, and interaction d$namics of $our user interface can match the conte&t and language that is

natural to $our application!s users.

'#ol#ing an application!s user interface is %est done %$ designers and de#elopers who ha#e %oth application domain

"nowledge and usa%ilit$ s"ills.

Producing HTML displa$s and forms

Process Commander includes standard facilities for those wor"ers and managers who use Process Commander-%ased

applications throughout the wor"da$. These facilities support(

'ntr$ of new wor" items and co#ers

)$stem-maintainedwor"listsofassignmentssorted %$ decreasing urgenc$

*inding, re#iewing, updating, and performingassignments

)ophisticated and powerful standard forms "nown as harnessesare designed for reuse and customi+ation.

efining user input forms and displa$s

*or access through the standard portal, Process Commander usesharness rulesRule-HTML-Harnessrule t$pe for wor"

items. )i& other rules support the presentation of wor" items(

)ection rulesdefine the contents, appearance, and %eha#ior of portions of harness forms.

*ragmentscontain reusa%le HTML te&t elements not dependent on a class/

Controlrules determine the appearance of a single propert$ on an HTML input form or displa$.

Te&t *ilerules, which can define static aspects of $our user interface such as Cascading )t$le )heets or

0a#a)cripts.

Binar$ *ilerules, which identif$ images such as 0P1 or 12* files.

The HTML te&t $ou enter into HTML rules is "nown as source HTML. 2t contains ordinar$ HTML code plus0)P

tagsordirecti#es3 ser#er-side instructions that Process Commander e#aluates at runtime to compose the final HTML it

sends to the HTTP ser#er and ultimatel$ to a user!s %rowser session. 4nown asstream processing, this e#aluation

accesses the clip%oard for te&t #alues to insert into the output HTML, incorporate the te&t of other HTML rules, pro#ide

conditional if-then-else testing, and looping through arra$s.
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/w/worklist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/w/worklist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/w/worklist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/a/assignment.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/a/assignment.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/a/assignment.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/perform.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/perform.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/h/harnessforms.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-section/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-section/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-section/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/section.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/f/fragment.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/f/fragment.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/propertystream.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/propertystream.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-file-/rule-file-text/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-file-/rule-file-text/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-file-/rule-file-binary/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/jsp/alphalist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/jsp/alphalist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/jsp/alphalist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/d/directive.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/d/directive.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/d/directive.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/streamprocessing.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/streamprocessing.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/a/assignment.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/perform.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/h/harnessforms.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-section/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/section.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/f/fragment.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/propertystream.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-file-/rule-file-text/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-file-/rule-file-binary/main.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/jsp/alphalist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/jsp/alphalist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/d/directive.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/streamprocessing.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/w/worklist.asp


2/32

Harness forms use thepega:include0)P tag to incorporate multiplesections,which in turn use standard st$les and

fragments to present properties, la%els, and images. *or $our application, $ou can cop$ and tailor parts of these forms as

necessar$, while inheriting the standard parts.

ToolsThese tools support $our e#olution of the user interface of $our applications(

Harness rules pre#iew and the 5pplication '&plorer 3 5llow $ou to interacti#el$ re#ise the content and the la$out

of a user form or flow action form

U2 1aller$3 Presents wor"ing e&amples of controls and user interface features

Branding wi+ard3 efines and maintains a famil$ of st$les for the User portal, user forms, and reports

6ules 2nspector tool3 2dentifies the harness, section, HTML rules and properties that together ma"e up a form

2mage Li%rar$ gadget 3 Helps $ou find and identif$ the name of images that are a#aila%le as %inar$ file references

)t$le isco#er$ tooland )t$le 7iewer 3 5llow $ou to learn a%out and e&periment with st$les

Clip%oard tool3 )hows the current propert$ #alues in internal format

Harness form - Completing the La$out ta%

Use the controls at the top of this ta% and drag and drop operations to re#iew or update this harness rule and associated

section rules.

Basics

The ta% presents a real-time pre#iew of the user form, allowing $ou to ad8ust the contents, position, st$le, and other aspects

of the elements in the form 9uic"l$.

5reas of the la$out that correspond to section rules or other elements that $ou cannot update appear with a gra$

%ac"ground. This ma$ mean that the rule needs to %e chec"ed out %$ $ou, or %elongs to a loc"ed 6ule)et #ersion, or

%elongs to a 6ule)et #ersion that $ou are not allowed to update.

ou cannot use this ta% to modif$ section rules referenced in the harness rule with the Auto-generated

HTML?chec"%o& cleared on the HTMLta%. These are mar"ed Manual HTMLon this ta%. )imilarl$, $ou cannot use

this ta% to modif$ section rules are in the legac$ format. These are mar"ed Not Upgradedon this ta%.
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/section.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/section.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/section.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/basics/v6portal/landingpages/userinterface/uigallery.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/applicationskin/aboutapplicationskin.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/rulesinspector/rulesinspectorv5.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/basics/v6portal/landingpages/userinterface/galleries.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/stylediscovery.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/stylediscovery.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/c/clipboardviewertool.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/c/clipboardviewertool.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/section.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/basics/v6portal/landingpages/userinterface/uigallery.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/applicationskin/aboutapplicationskin.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/rulesinspector/rulesinspectorv5.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/basics/v6portal/landingpages/userinterface/galleries.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/s/stylediscovery.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/c/clipboardviewertool.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tab


3/32

:hen $ou sa#e this rule form, Process Commander also sa#es an$ other section rules $ou ha#e open that this rule

references, and #alidates the rules as the$ are sa#ed.

5t runtime, the initial state of each collapsi%le element on a user form 3 collapsed or e&panded 3 is

determined %$ the state on the Harness form when $ou sa#e the form.

5s a %est practice, %uild $our application s"in using the Branding wi+ard %efore $ou de#elop harness rules, especiall$ if

$ou are using )martLa$outs with spacing determined %$ the s"in st$les. The s$stem renders the Layoutta% using the

st$les of the s"in rule identified in the Skinsfield of theRun Process Ingroup of $our Generalpreferences. 2f the Skinsfield

is %lan", these displa$s use the st$les mar"ed Workon the Stylesta% of the s"in identified in $our current portal rule.

)eeesigner )tudio 3 )etting $our preferences.

Using the Harness form to re#iew or update a harness rule creates a clip%oard page and initiali+es properties. This ma$

in turn cause declarati#e processing to e&ecute. Use caution %efore implementing an$ ;nChange declarati#e processing

that produces data%ase updates.

2dentif$ing controls on this ta%

Controls that alter the pre#iew

The pre#iew area of this ta% holds an appro&imate #isual presentation of the runtime appearance of the flow action. These

%uttons do not affect the contents of the rule, onl$ the displa$ on this ta%(

Clic" the %utton to presentthe )mart*rames wireframe pre#iew. Blue wireframe rectangles help $ou

understand the structure of the section, names of rules referenced in this rule, and the si+e and other relationships of

elements in the section.

Clic" the %utton to hidewireframes, pro#iding a less %us$ and more faithful pre#iew.

Controls that alter a la$out ta%le grid

These controls operate on a ta%le structure. )elect one or more cells first, and then clic" the control to appl$ the operation

descri%ed. :hen a control is not a#aila%le gra$ed, it cannot %e applied to the current selection.
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/basics/v6portal/v6preferences.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/basics/v6portal/v6preferences.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/basics/v6portal/v6preferences.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/basics/v6portal/v6preferences.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tab


4/32

Control Description

Delete the contents of a single cell (not a row or column).

Insert a new row before (above) the selected row.

Insert a new row after (below) the selected row.

Delete the selected row.

Insert a new column before (to the left of) the selected column.

Insert a new column after (to the right of) the selected column.

Delete the selected column.

Merge right Combine the selected cell and the cell to the right.

Merge down Combine the selected cell and the cell below it.

Unmerge Undo the previous merge.

ou can also alter the ta%le structure with :indows pointer operations. )elect a row, cell, or column and right-clic" to access

a conte&t menu. )elect menu operations Cut, Copy, Paste, Insert Row,Delete Row, or Delete Column.

Ta%s and


5/32

Clic" the or as desired to control the initial presentation of a section or other element

)tructure of a harness-%ased form

)tructurall$, e#er$ harness consists of one or more containers. The container structure is not re9uired for those harness

rules that are defined through handcrafted HTML code. 5 container can pro#ide a #isual grouping of multiple sections.

Headers %elong to containers. 5 container ma$ ha#e a hori+ontal header, a set of ta%s identif$ing the top-le#el sections it

contains, or no header.

'ach container can contain one or more sections, which in turn can contain la$outs, repeating la$outs, and other sections.

)ections contain cells, arranged in rows and columns.

Protot$ping a harness %efore the wor" item properties are defined

ou can rapidl$ moc" up the la$out, la%els, and controls on this ta% %efore all properties it ultimatel$ will reference are

defined. The de#elopment effort $ou ma"e in designing la$out is not wasted, as the resulting Harness rule is a #alid starting

point for further e#olution after the propert$ rules are created.

:hen $ou first drop a control dragged from the Basic 1roup, the control initiall$ references a standard placeholder propert$,

for e&ample @baseclasspyTemplateInput!o". ou can sa#e and pre#iew the Harness form although these properties are

not part of $our application!s wor" items.

To produce a harness rule with the appropriate la$out, drag and drop the controls, ad8ust the la%els, %ut do not complete the

Cell Properties panel. 6eopen the Harness form and update each Cell Properties panel later, when the real properties are

defined.

*or an e&ample of this approach, see Pega e#eloper ?etwor" article P64B-@A@#se pyTemplate properties and

controls to rapidly prototype user $orms

:or"ing with the Cell Properties panel

'ach control is defined %$ $our inputs in floating panel, which $ou can pin for faster input. To open the panel, select the

control after dropping it and clic" the magnif$ing glass icon that appears. Use these controls on the header of floating

panel(

3 Pin the panel to a location. The ;4%utton disappears, and each input $ou enter is immediatel$ applied tothe open rule form.

3 6elease the pin. The ;4%utton appears. our inputs do not affect the open form until $ou clic" ;4.
https://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/devnet/prpcv5/kb/25216.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/devnet/prpcv5/kb/25216.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tab


6/32

3 Collapse hide the panel %od$.

3 '&pand a collapsed panel %od$.

3 Close the panel. 2f $ou ha#e entered changes that are not $et applied, a warning dialog ma$ appear,

depending on the Warn on modiiedchec"%o& in the Smart!rames "ditarea of the "ditpreferences group.)eeesigner )tudio 3 )etting $our preferences.

La$out 1roup( 5dding a container, section, la$out, ta%, or repeating la$out

Clic" the down arrow in the Container control group and select a control(

Contr

ol

Description

Add a panel setto this harness, to support a composite portal. See Adding a panel

set.

Add a containerto the harness form. Every harness must contain at least one

container. The sections within a container may be presented vertically or with tabs.

See Adding a container.

Add a tabto a harness. SeeAdding a tab.

Add an accordionto the harness. See Adding an accordion.

Add a sectionrule into this harness. See Adding a section.

Add a layoutto the harness a


7/32

and one or more columns. "ou can then change the number and si#e of rows and

columns, and set up the contents of each cell $a


8/32

lace a button into a cell at the bottom of the form. 'hen cliced at

runtime& the button starts an action. Corresponds to a p"!uttoncontrol

rule. Adding a button.

Add a checbo% representing a TrueFalsevalue. Corresponds toap"C&ec'bo" control rule. Adding a Checbo%.

Add a radio button group representing a propert value. Adding a radio

button group.

lace a te%t lin in a cell. 'hen cliced at runtime& the lin starts an

action. Corresponds to a p"Lin'control rule. Adding a *in control.

Add a te*t bo* containing a Dateor DateTimevalue. +orresponds to

ap"DateTime control rule. Adding a +alendar control.

Add a Select control that presents a fi*ed list of values. Adding a Select control.

nclude an image in the form. Adding an mage.

5d#anced 1roup

Clic" the down arrow in the 5d#anced control group and select a control(

Control

Description

!eference& in a cell& a paragraph rule that presents onl read$onl te%t

and images using rich te%t. +ptionall& ou can lin a ,martInfo pop$up

section with the paragraph. Adding a paragraph.
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlaybutton.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutpxcheckboxV62.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutradiogroup.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutradiogroup.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutpxlinkV62.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutpxdatetimeV62.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutselect.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutimage.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutparagraph.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlaybutton.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutpxcheckboxV62.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutradiogroup.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutradiogroup.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutpxlinkV62.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutpxdatetimeV62.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutselect.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutimage.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutparagraph.asp


9/32

Use an AutoComplete te%t bo% to present a drop$down list of dnamic

choices computed b an activit. Adding an AutoComplete -eld.

Add a red label that opens a pop$up ,martInfo section when the user

hovers the mouse pointer over the label. Adding a ,mart *abel.

Add a dnamic drop$down list. Adding a Dnamic ,elect control.

Adding a control that allows multiple selections from a possibl long

list. Adding a list$to$list control.

resenting rows of a report& optionall allowing selection. Adding a *ist

iew displa.

A cell can contain an interactive chart& de-ned b a summar view rule

with a completed Charttab. Adding a chart.

/or harnesses that are part of a composite application built with Internet

Application Composer onl. Add a hidden -eld to e%pose a propert

value& maing it available to the e%ternal page that displas the

composite application. ,ee Adding a Data /ield control.

Add a menu to a composite portal. ,ee Adding a Menu 0ar.

Adding a 'or Area to a composite portal. Adding a 'or Area.

12A In addition to these Advanced controls& ou can add interactive data

displas to support 3uic review or editing for a Page Listor Value

List. Adding a "ree&Adding a #rid& Adding a "ree #rid.

ragging a propert$ from the 5pplication '&plorer

ou can complete two cells of a la$out in one step if the left cell is to contain a te&t la%el and the right cell is to contain a field

corresponding to a propert$ on the 5pplication '&plorer.
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutautocomplete.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutsmartlabel.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutdynamicselect.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutlistotlist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutlistview.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutlistview.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutachart.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutdatafield.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutmenu.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutdocumentview.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayouttree.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutgridv6.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayouttreegrid.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tabhttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutautocomplete.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutsmartlabel.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutdynamicselect.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutlistotlist.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutlistview.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutlistview.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutachart.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutdatafield.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutmenu.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutdocumentview.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayouttree.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutgridv6.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayouttreegrid.asphttps://pdn.pega.com/help-system/prpc/62-sp1/harness-form-completing-the-layout-tab


10/32

. Locate and e&pand the wor" t$pe that contains the propert$ on the 5pplication '&plorer.

@. '&pand the ata Model categor$ and the Propert$ rule t$pe to list propert$ names.

D. )elect the %lue dot for the Single Valuepropert$ to %e placed in the field. rag and drop the dot into the

desired cell.

E. The s$stem places the Short #escriptionte&t of the propert$ as a la%el in the left cell. 2t places the propert$ as aread-write field in the right cell. ou can ad8ust the settings for these cells.

A.)tandard Harness rules

. )e#eral standard rules are a#aila%le for $our use in the @baseclass( )or'-class, or othr classes. ;ther standard

harness rules not listed are used in the 5pplication 5ccelerator and other wi+ards. our custom harness rules

t$picall$ o#erride these %$ using the same Purpose"e$ part.

F. 5 to 1

4arness Description More

@baseclass

%cti*ity+tatus+ucces

s

resents a form when a top$level activit

completes with presenting an 4"M*displa. (5"he operation completed

successfull& but returned no content.5

with green checmar.)

4ow to

customi6e theactivit success

and e%ception

windows

@baseclass

%cti*ity+tatus

,"ceptionHandler

resents a form when an activit fails or

an uncaught 7ava e%ception occurs.

(5lease contact our ,stem

Administrator .5 with red 8.)

4ow to

customi6e the

activit success

and e%ception

windows

%utoClose Closes the wor ob9ect form automaticall:

an alternative to Con$irmwhen there is no

new information to displa.
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/howto/howto2/exceptionwindow.asp


11/32

Con$irm resents a read$onl con-rmation displa

of the wor item& acnowledging user

completion of an assignment. Contains

the 1et Most Urgent button. "his button is

b default lined to the standard

activit)or'-et.e"t)or'. ;our application

can override that activit.

Ma%imi6ing

User

roductivit

with

#et1e%t'or

DisplayInput ,pecial purpose& not for use in 0M

applications that use


12/32

.ewCo*ered Allows a user to create both a cover wor

item and in the same form create one or

more covered wor items.

cover

.ew+ample /or wor item creation& used b the (basic)Application Accelerator. Incorporates stles

from the standard #sersim rule& introduced

in ersion =.>.

About theApplication

Accelerator

)or'-Per$orm Allows a user to select a


13/32

portlet$compliant 4"M*.

Print/ptions Allows a user to select which top$level

sections are to be printed.

Print2iew rovides a presentation of a wor ob9ect

suitable for printing.

pyCMCon$irm !eserved. Do not use.

pyCMPer$orm !eserved. Do not use.

pyCMRe*iew !eserved. Do not use.

. 6 to I

urpose Description More

Reopen Allows a user to reopen a resolved wor item. reopen

Re*iew resents the wor item and assignment in read$

onl mode& not allowing data entr.

Re*iew+ample resents the wor item and assignment in read$

onl mode& not allowing data entr. Copied into

applications created b the basic Application

Accelerator& with the name !eview.

About the

Application

Accelerator

Rule1orm ,econd e part of multiple standard harnessrules that de-ne the structure of rule forms.

!eserved.

+impleCon$irm ,imilar to the Con$irmharness rule& but with

portlet$compliant 4"M*. Use this version when

portlet
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/r/reopen.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/portlet.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/r/reopen.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/portlet.asp


14/32

our


15/32

Advanced

:here referenced

6ules of the following t$pes can reference a section rule(

Harness rules

;ther section rules

List #iew and summar$ #iew rules, as the contents of a pop-up )mart2nfo window.

Paragraph rules, as the contents of a pop-up )mart2nfo window.

5ccess

Use 5pplication '&plorer to access section rules that appl$ to the wor" t$pes in $our application. Use the 6ules %$ T$pe

'&plorer to list all the section rules a#aila%le to $ou.

e#elopment

*or section rules that use the )mart*rames format, $ou can maintain the section rule directl$ from the Harness rule form as

well as from the )ection rule form.

Categor$

)ection rules are instances of the Rule-HTML-+ectionclass. The$ are part of the User 2nterface categor$.

)tandard )ection rules
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/common/commonlayoutselect.asp


16/32

our s$stem contains hundreds of standard section rules. Most useful in $our application are those that appl$ to

the )or'-or )or'-Co*er-class. ;thers 3 t$picall$ that appl$ to @baseclass3 support a composite portals. 5dditional

standard sections support de$eloper-oriented flow processing, such as that pro#ided %$ the 5pplication 5ccelerator and

Connector wi+ard.

To understand the structure of a harness-%ased form, use the 6ules 2nspector tool to identif$ the underl$ing harness,

section, and propert$ rules.

To see a complete list of the standard and custom section rules a#aila%le to $ou %ased on $our 6ule)ets and securit$, use

the 6ules %$ T$pe '&plorer.

These standard section rules are nota%le(

)ections for User forms 5 to H

1ame urpose

)or'-%ction

6or /0 only. 7resents, as a drop8down list, the available flow

actions available to a user who is performing an assignment.

4eferenced in the standard harness rule )or'-Per$orm.

6or new /2 applications, use or copy the standard action

section)or'-py%ction%rea. See7resenting flow actions.

)or'-py%ction%rea

4ecommended action sectionfor new applications. See 7resenting

flow actions.

)or'-%ction0!uttons

6or /0. 7resents an array of buttons identifying the flow actions

available to a user who is performing an assignment. 4eferenced in

the standard harness rule )or'-Per$orm0!uttons.
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-harness/presentingflowactions.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-harness/presentingflowactions.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/a/actionsection.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-harness/presentingflowactions.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-harness/presentingflowactions.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-harness/presentingflowactions.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/a/actionsection.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-harness/presentingflowactions.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/rule-/rule-html-/rule-html-harness/presentingflowactions.asp


17/32

6or new /2 applications, use or copy the standard action

section)or'-py%ction%rea. See7resenting flow actions.

)or'-%ction,"ternal ,upports e%ternal assignments.

)or'-%ction0+tep

6or /0. 7resents the preselected flow action as a default choice,

with others available through buttons. 4eferenced in the standard

harness rule )or'-Per$orm0+tep.

/or new ? applications& use or cop the standard action

section)or'-py%ction%rea. ,ee resenting


18/32

)or'-1lows ,upports the )tart ?ew Process button& that allows users to

select and start a second (or additional) .

)or'-/wners&ip Displas thepy/rig#serID&pyContactC&ange&

andp"CreateDateTimeproperties.

)or'-Party+imple Captures information about the wor partiesinvolved in

the wor item: allows the user to add a part (sub9ect

the relevant wor part rule). Copied into applications

created b the (basic) Application Accelerator.

Introduced in !elease =.>.

)or'-Portlet+ection "emplate rule& cop for sections that are to support

access through 7,!$?B portlets.

)or'-Process+teps ,upports hori6ontal presentation of the breadcrumbs

control.

)or'-Process+teps2ertic ,upports vertical stac presentation of the breadcrumbs

control.
https://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/w/workparty.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/portlet.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/b/breadcrumbscontrol.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/b/breadcrumbscontrol.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/b/breadcrumbscontrol.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/b/breadcrumbscontrol.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/tools/basicappaccelerator/basicappaccelerator.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/w/workparty.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/p/portlet.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/b/breadcrumbscontrol.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/b/breadcrumbscontrol.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/b/breadcrumbscontrol.asphttps://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V62SP1/definitions/b/breadcrumbscontrol.asp


19/32


20/32

1ame urpose

@baseclassDas&board resents four interactive charts summari6ing wor

processing& as in the Manager portal.

@baseclass1ind)or' ,upports searching for wor items.

@baseclassLog/$$ rovides a Log ;ffbutton or lin.

@baseclass.ew)or' Allows users to enter a new wor item. arious formats.

@baseclassPro$ile Displas selected facts about the operator pro-le& andincludes a button that provides a full pro-le displa.

@baseclassp"Calendar Displas a month grid with individual events on each da.

,ee Using and con-guring the p%Calendar section.

@baseclassRecent)or

'

Displas recentl opened wor items.

@baseclassRecent)or'

Displas a worlist.

;ther sections

1ame urpose

@baseclasspyridModalTemplate

"emplate section rule to cop for modaldialogsaccessed from the #rid laout.

@baseclasspyModalTemplate "emplate section rule to cop for modal

dialogsfor local


21/32

)uggested 5pproach

*ollow these steps to add a )martLa%el control to a harness, section, or flow action form.

. 2dentif$ or create the section rule. 2n most cases, set the 5pplies To "e$ part of the section rule to match the 5pplies To

"e$ part of the rule that is to contain the )martLa%el.

@. ;pen the harness, section, or flow action rule. )elect SmartLa%elfrom the

5d#anced group of controls.

D. rag the control from the menu and drop the control in a cell. Clic" the magnif$ing

glass icon to the right of the cell to open the Cell Properties panel.

E. Complete the Cell Properties panels. ;n the Fieldta%, accept the default placeholder propert$pyTemplate+martLabel.

;n the Presentationta%, clic" the magnif$ing glass icon at the right of the *ormat field.


22/32

A. Complete the pop-up Params window to suppl$ three parameters for the )martLa%el( the te&t of the la%el, the second "e$

part of the section, and header te&t for the pop-up window.

. Clic" )a#eto close the

Params window.

F. ;ptionall$, complete additional fields on the Presentationand Conditionsta%s of the Cell properties panel to

control additional aspects of the la%el.

G. Clic"5ppl$to appl$ changes to the Cell Properties panel. Clic" ;4to close the Cell Properties panel.


23/32

. )a#e the rule form. Test with the Pre#iew tool%ar %utton, the 6un tool%ar %utton, or in conte&t of the application.

How to use regular e&pressions to #alidate user

input

)ummar$

6egular e&pressions pro#ide a popular means to search te&t for a pattern. ou can use regular e&pressions in edit #alidate

rules Rule-,dit-2alidaterule t$pe in $our application to chec" the format of a user input.

Because regular e&pressions can descri%e a wide #ariet$ of te&t patterns, this approach can pro#ide impro#ed data

#alidation without re9uiring $our de#elopment team to write and test long 0a#a routines.

)uggested 5pproach

5n edit #alidate rule Rule-,dit-2alidaterule t$pe chec"s the format of a te&t #alue, such as a #alue t$ped into a form %$ an

application user. The result outcome is either true 3 the #alue does meet the criteria defined in the rule, or false 3 the input

#alue is re8ected with a message.

2n general, Process Commander de#elopers need 0a#a s"ills to create new edit #alidate rules. Howe#er, 0a#a includes the

well-"nown pattern matching facilit$ "nown as regular e&pressions. This facilit$, li"e the U?2X grepcommand, tests an

input string against a pattern, finding the first match if an$, or all matches. Using a short 0a#a snippet, an edit #alidate rule

can test an input string against a regular e&pression.

Man$ %oo"s, :e% sites, and software products e&plain regular e&pressions, which are not e&plained here. *or the

complete, official specification see http(//8a#a.sun.com/8@se/.E.@/docs/api/8a#a/util/rege&/Pattern.html. The simple

e&ample %elow illustrates a Canadian postal code chec", %ut other more comple& regular e&pressions can %e tested with

similar code.

'&ample( Canadian Postal Codes

'#er$ postal code for Canada consists of se#en characters including a single space in the format 5?5 ?5?, where 5 is a

letter and ? is a digit from K-. The first character is one of G specific letters> others are not so constrained. *or e&ample,

the Pegas$stems office in Toronto is located in Postal Code MAX 'D.
http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.htmlhttp://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html


24/32

3 De*elop and test t&e regular e"pression

The regular e&pression !A"#EGH%LMNP&STV'()!*-+)!A-,) !*-+)!A-,)!*-+)captures the

Canadian Postal Code format. To confirm this(

. ;pen the %uilt-in regular e&pression tester acti#it$ Code-Pega-ParseReg,"pTester. This supports the same )unMicros$stems implementation that the edit #alidate rule e&ecutes.

@. Clic" the 6un tool%ar %utton .

D. Clic" 6un 6uleand then clic" Execute. Lea#e the parameters %lan"

E. Complete the 6egular '&pression field. 'nter a test string in the )ource field.

A. Clic" Test "&pression.

This test case confirms that the source =MA6 @'G= matches the regular e&pression pattern.

5 second test case confirms that A6 @'G does notmatch. is not one of the allowed first letters.


25/32

?ote that the tester ma$ find a match as a su%string of a longer string(

4 Create t&e ,dit 2alidate rule

)a#e the pattern $ou tested. in a scratch te&t file. Create an edit #alidate rule that uses

thea.a/util/rege0/Patternclass to appl$ the pattern to the predefined input #aria%le t1eValue(


26/32

Paste the pattern $ou tested into the compile method. 2n this e&ample, the entire 0a#a )ource field contains onl$ a few

lines of code(

2oolean ret.al 3 alse4

i 5t1eValue/lengt156 33 7 6 8

a.a/util/rege0/Pattern p 3

a.a/util/rege0/Pattern/9ompile5:!A"#EGH%LMNP&STV'()!*-+)!A-,) !*-+)!A-,)

!*-+):64

a.a/util/rege0/Mat91er m3 p/mat91er5t1eValue64

ret.al 3 m/mat91es564

;

return ret.al4

5 Re$erence t&e edit *alidate rule in an acti*ity or *alidate rule

'dit #alidate rules e&ecute through acti#ities or through #alidate rules Rule-/b6-2alidate. To illustrate one use of the

Canadian Postal Code, $ou can o#erride the standard #alidate rule Data-Party)or'%ddress, which %$ default re9uires onl$

that the propert$py)or'PostalCodenot %e %lan".

'nter =Canadian Postal Code= in the 7alidate field and an error message or Rule-Message"e$ in the'rror Message field.


27/32

*or testing purposes, delete the row for thepy+tateCodepropert$.

7 Test

To e&ercise the #alidation rule and edit #alidation rule(

. )elect the 1ile 8 /pen 8 )or' Pool 8 +ample )or'menu item to access the Pega)ample sample application.

@. )elect the Run 8 Process 8 eneral Tas'menu item to enter a 1eneral Tas"

D. 2n the Parties section of the ?ew form, select 5dd Part$... Customer.

E. )et the Contact Preferences to :or" 5ddress. 'nter customer details, including an in#alid or #alid Canadian PostalCode in the I2P field.

A. Clic" 'reate.

2n this e&ample, the in#alid code G4 J was re8ected.


28/32

Limitations and notes

'dit #alidate rules pro#ide onl$ $ormatchec"ing. Man$ #alues that ha#e the correct format and so are accepted as

input do not correspond to real Canadian Postal Codes. Howe#er, format chec"ing can detect man$ input errors, and isalwa$s %etter than accepting input without an$ chec"ing.

The )u%mit operation for HTML forms strips off leading and trailing spaces. There is no need to test for them or to

match them.

our Rule-,dit-2alidate0a#a code should not accept a su%string as a #alid match.

::: and other pu%lic sources pro#ide regular e&pressions for %oo" identifiers 2)B? num%ers, telephone

num%ers, email addresses, 2P addresses, and man$ other patterns. ;f course, $ou should test an$ e&pression $ou plan toadopt to confirm that it matches $our application re9uirements.

Consult the Help )$stem topic =5%out the 6egular '&pression tool= for more information on the %uilt in testing tool.

Li"e 0a#a, the 0a#a)cript language also supports regular e&pressions, so after $ou ha#e implemented and tested

an edit #alidate rule, $ou optionall$ can e&tend #alidation to the wor"station using the client-side format #alidation featureand the standard Client2alidationHTML Propert$ rule.

How to add a list-to-list control to a flow action form

)ummar$

5 List to List control on a wor" o%8ect form allows a user to ma"e multiple selections from one list of candidates. 2n this

e&ample flow action from an auto insurance application,, a user selects safet$ e9uipment from the left list, each identified %$

name, and clic"s an arrow to add the selection to the right list. The right list identifies chosen safet$ e9uipment options> the

left list contains all of the a#aila%le options.


29/32

5dditional controls unless disa%led when the rule is configured allow the user to sort either list, to remo#e pre#ious

selections, to cop$ all or remo#e all selections. The user can ma"e further changes until the user su%mits the flow action

form.

The List to List control is supported %$ two Page Listproperties, one pro#iding the list of source #alues and one

pro#iding the list of destination #alues. 5s a result, the output of a List to List operation is not an arra$ of te&t #alues such as

can %e stored in a Value Listpropert$, %ut an arra$ of em%edded pages, identified %$ one #isi%le te&t propert$ such

as a name.

This article presents a step-%$-step procedure for adding a List to List control to a harness, section, or flow action form. *or

full details on all options, consult the Help s$stem topic.

)uggested 5pproach

Preparations

2dentif$ or create these parts of the List-to-List control(

The source propert$, a Page Listpropert$ of class Code-Pega-List.

5n acti#it$ or other processing to populate the source propert$.

5 Single Valuepropert$ within each em%edded page that identifies the page, for displa$

The target propert$, also a Page Listpropert$, t$picall$ part of the wor" o%8ect. The em%edded pages of the

target propert$ are often of the same class as the em%edded pages of the source propert$, %ut this is not a re9uirement.

Properties that are needed in the target em%edded pages.


30/32

The source propert$ structure matches those produced %$ the ;%8-Browse, ;%8-List-7iew, and 6B-List methods, %ut $our

application can create the source propert$ %$ an$ means.

Unli"e the $namic )elect control and 5utoComplete control, the List to List control re9uires the source propert$ to %e

populated be$orethe user sees the form containing the control.

5dding the control

To add a List to List control to a flow action, harness, or section rule(

. ;pen the rule form. )elect List to Listfrom the 5d#anced control group.

@. rag the List to List icon to a cell on the form, and drop it. The cell ma$ change si+e

to accommodate the large control> $ou can ad8ust the si+e later.

D. Clic" the magnif$ing glass icon at the upper right of the cell to open the Cell Properties panel.

E. ?o changes are needed on the Fieldta% of the Cell Properties panel. ;n the Presentationta%, confirm that

the *ormat isListToList.

A. Clic" the magnif$ing glass to the right of the !ormatfield to open the

Params pop-up window.

. Complete the Params window. 2dentif$ the source propert$, the target

propert$, and the te&t propert$ to appear in the source lists. 2nclude dou%le-

9uotes around propert$ references if the$ contain a period character.

;ptionall$, enter two captions, to appear a%o#e the two lists.

)elect 'op( all propertiesif, when a user selects an item, the s$stem is to

cop$ all properties on the em%edded source page, creating a page with identical properties on a new em%edded page with

the target propert$. 5lternati#el$, $ou can define a from-to mapping and control which properties are copied.


31/32

B$ default, the left list displa$s at most @KK #alues, e#en if the source propert$ contains more than @KK em%edded pages. B$

default, there is no limit on the num%er of pages that a user can add to the target propert$. ou can change either limit

through parameter settings.

F. Clic" )a#eto close the Params window.

G. ;ptionall$, complete other #alues on the Presentationta% and Conditionsta% of the Cell Properties

panel.

. Clic"5ppl$to appl$ the changes $ou made to the Cell Properties panel and Parameters window. Clic" ;4to close the

Cell Properties panel.

K. )a#e the rule form.

. Test. 'nsure that $our application populates the source propert$ %efore the wor" o%8ect form or flow action form

appears.


32/32

5 sample acti#it$

This one-step acti#it$ creates a page )afet$'9uipment of class Code-Pega-List. 2dentif$ this page on the Pages

Classesta% of the 5cti#it$ form.

:he

n e&ecuted, the clip%oard contains a page for each piece of safet$ e9uipment.

5fte

r a user su%mits the flow action form, Process Commander copies pages from the source propert$ to the target page. )i&

selections appear as em%edded pages to propert$ p$:or"Page.'ntrants.

pega user interface concepts

Documents