Based on HTML and XML standards, a wide range of user interaction facilities and approaches is supported. The user interface for an application can take into account the environment, the domain knowledge of your users, their skills, locale, and language.
The appearance, branding, and interaction dynamics of your user interface can match the context and language that is natural to your application's users.
Evolving an application's user interface is best done by designers and developers who have both application domain knowledge and usability skills.
Standard facilities are provided for those workers and managers who use applications throughout the workday. These facilities support:
For access through the standard portal, reusable harnesses are used for work items. The following rule types support the presentation of work items:
The HTML text you enter into HTML rules is known as source HTML. Source HTML contains ordinary HTML code plus JSP tags or directives — server-side instructions that are evaluated at run time to compose the final HTML it sends to the HTTP server (and ultimately to a user's browser session). Known as stream processing, this evaluation accesses the clipboard for text values to insert into the output HTML, incorporates the text of other HTML rules, provides conditional if-then-else testing, and looping through arrays.
Harness forms use the pega:include JSP tag to incorporate multiple sections, which in turn use standard styles and fragments to present properties, labels, and images. For your application, you can copy and tailor parts of these forms as necessary, while inheriting the standard parts.
These tools support your evolution of the user interface of your applications:
When a user submits an HTML form, the values entered into input fields are recorded as property values on the clipboard. The values that users enter may not be in the format required by the property definition, or might not pass validation tests.
See PDN article Top Ten Usability Guardrails.