PEGA wants all team members to know what a great user experience is and why it is valuable: to practice empathy and create amazing experiences for the consumers of our products. One must learn to see PEGA UI as a UX specialist does to do this.
Misalignment; spacing issues; data display errors; scrolling errors; and language oversights: are crucial challenges that UX design and front-end practitioners see in rapidly assessing the consistency of user interfaces (UI) implemented.
To get in-Depth knowledge on Pega CSA you can enroll for a live demo on Pega CSA Training.
PEGA UI Implementation module
This module allows you to see and explain and fix problems that are commonly encountered. The aim is to create UIs that help users quickly and efficiently perform their tasks and are frictionless.
A well-implemented PEGA UI should indeed, feel simple and barely noticed. Invisible is a nice UI. There’s a bad PEGA UI distraction.
It’s helpful to understand the difference between PEGA UI and UX to achieve this objective. In software, these words have varying definitions. The PEGA UI(or user interface) refers to the technical elements that a user interacts with on the screen: buttons, connections, fields, etc. UX (or user interface) refers to the full experience, which involves the workflow of users, what information should appear on a screen and when the order and arrangement of that information, and how cohesively different screens fit together.
This module mainly focuses on the fundamentals of the right PEGA UI but also touches on a few UX essentials. Ultimately, observable results decide the overall quality of any design: are users of production applications effective, profitable, and precise?
Take your career to new heights of success with the Pega cssa online course
Fundamentals of PEGA UI
These are overlooked, we all must learn how to see and understand, as a designer or front-end developer, the essential elements of good PEGA UI implementation at a glance.
Let’s begin with a few basics. The “good UI” or “bad UI” fundamentals revolve around four main principles: continuity, meaning, simplification, and accessibility.
Coherence
The amount of work it takes to learn how to use an interface is reduced by consistent application structure, data, navigation, alignment, and spacing. This makes apps more effective and efficient. Applications that behave inconsistently demand users to concentrate continuously on the GUI. Providing our users with reliable ways of communicating with our apps is very critical.
Get hands-on experience on PEGA CSSA with expert knowledge through the Pega cssa certification online training at OnlineITGuru.
Context
Context refers to the collection of variables required by your program to understand how to provide ideal results. This requires a knowledge of who the users are, their positions, their familiarity with the apps, or other applications, and which devices they use. Providing our users with familiar interactions can drive efficiency in our applications and decrease costly training time. The task-specific meaning may also be: which application knowledge or application interactions should be clustered so that they form a conceptual set that is prioritized by probable use. For good application design, understanding the correct context is important.
Simplifies
It is simpler to use simplified software than complex software. There’s a rule in UX called Hick’s Law, which states: With the number and difficulty of choices, the time it takes to make a decision increases.
We still see business applications that disregard this rule and end up with excessively complicated interfaces, although that can sound obvious. It is the same as reducing the options for error and uncertainty, and the same as generating more positive performance, to minimize the number of concepts a consumer interacts with. We need to provide the information and PEGA UI elements required to complete a task for a user, but we should aim to provide only what is needed for the desired result.
PEGA UI enterprise applications
What data is required, for example, for a contact center representative to update the address of a customer and at the same time, provide that customer with the best full engagement? Without offering so much information that the agent is frustrated and as a result, underperforms, how do we have an incentive for improved programs, better solutions, etc.? How do we simplify mouse or keyboard experiences so that when engaging the customer and addressing the customer’s problems, the contact center rep does as little as possible?
Enterprise applications will still have a certain degree of complexity, which can be hard to minimize, but any effort to create the simplest experiences can boost efficiency by simplifying details, text, and interactions.
Accessibility
Accessibility is the last basic principle. The test of whether our apps are accessible by anyone is usability. Accessibility laws, while not discussed in this module, are a legal requirement for most projects. Regardless of legality, building an open PEGA UI is the same as building a quality UI. Indeed it is safer for all to use open UIs, more stable and effective, and easier to update. PEGA UI has resources for usability that you can take advantage of. You will be well on your way to solving several usability problems by observing the other concepts of continuity, meaning, and simplification.
Shape throughout the process of design
In this example, to create this type, the designer used the following PEGA UI elements.
Divisions
- Job details and features are grouped by meaning and purpose into parts.
- In other sections, each section should be used so that the developer can re-use them in a number of contexts.
- When designing flow actions that require additional fields or forms required to complete a task, the designer often uses sections.
Layouts
- Within a section, templates organize properties and controls.
- Assets, marks, buttons, or other parts comprise layout cells.
- How cells are organized is specified by different kinds of layouts.
- The designer used a dynamic layout that automatically changes element alignment based on the screen width.
- It is possible to transform templates into sections automatically so that they can be reused in other harnesses, sections, or flow acts.
The Controls
- In controls like text areas, drop-down lists, checkboxes, or calendars, information about a work item is entered or displayed. Many of these controls are designed so that, without further refinement, they satisfy most process requirements.
- The designer drags and drops it from a drop-down menu onto a layout cell to add a control.
- In the preceding diagram, the red arrow shows how a label was put in a cell. For attaching templates, containers, and parts to the type, the designer uses similar menus.
- Read More Info Here Pega cssa course
The Portals
- Portals are workspaces that assist users and executives in the development, upgrading, routing, and resolution of work objects. Pega 7 provides portals for Case Manager and Designer Studio.
- Usually, the Case Manager portal provides functionality for end-users who use the program.
- For developers with specialized tasks, such as debugging or altering the business process flow or UI, the Designer Studio portal has advanced features and tools.
- In order to reflect the terminology, structure, features, and styles that are suitable for your user base, your team may also create new portals. To present working items and worklists as single or multiple harnesses (or sections) in your portal, you can use auto-generated dynamic containers.
An example of a Case Manager portal is in the following figure.
Example Portal
In order to create a portal, the designer uses the rules and the elements listed above. His overall structure is determined by a panel set in the portal harness. The collection includes panels on the bottom, top, left, right, and middle. Panels are not laws; instead, segment rules are referenced by panels.
Conclusion
I hope you reach to a conclusion about UI design concepts. You can learn more concepts you require to be a CSSA through PEGA CSSA online training.
Architects and developers build the Pega/PRPC instance while administrators and even select business analysts have the option of changing workflow rules during runtime.
So the lesser the code, the closer you are to the goal of a true BPM tool.
Software coding might be reduced drastically.But you still need people with a development background using inputs from Business Analysts to make changes or add functionality.
Pega/PRPC is pretty expensive so they primarily target any corporation that can afford such a luxury.To get in-Depth knowledge on Pega CSA you can enroll for a live demo on pega cssa certification.Most applications require access to data that is provided by another system, or they need to respond to requests from other systems for data or computations.
Process Commander provides integration facilities that support interactions between its applications and external systems, databases, Web sites, e-mail servers, and so on.In Integration situations, a Process Commander application can act as either the client or the server, communicating with both back-end and front-end applications.By using these features, Process Commander can exchange information with many kinds of external systems likeTake your career to new heights of success with pega cssa trainingRelational databasesEnterprise Information Systems (EIS)e-mail serversExcel spreadsheetsText filesProcess Commander interfaces support a wide range of technologies and standards, includingHTMLSimple Object Access Protocol (SOAP)Microsoft .NETSun Microsystems Enterprise JavaBeans (EJB)IBM WebSphere MQ® messagingJava Message Service (JMS)J2EE Connector Architecture (JCA)Business Process Execution Language (BPEL)JSR 94JSR 168These interfaces are called integration servicesTYPES OF INTEGRATIONS IN PEGA-PRPCProcess Commander offers many approaches, technologies, and facilities collectively known as Integration.
They include:• Connector• ServiceInternally, these facilities are in the Pega-IntSvcs RuleSetDATA MAPPING IN PEGA-PRPCWhen you configure a service or a connector you also match or correlate the properties in the process commander application to the corresponding data fields or properties in the external system.
