==========Managing

application development===========

Agile Workbench

Agile Workbench is a tool for project stakeholders and team members

that captures real-time feedback about your application and tracks feature
development.

Agile Workbench supports Direct Capture of Objectives (DCO) and agile

development.

DCO is the process of defining and managing business objectives in your

application.

By managing feedback and development status directly in your

application, you can make application development more efficient.

Agile Workbench supports agile development by providing continuous

access to work item status and new work item creation.

Work items

In Agile Workbench, you create work items:

>user stories,
>bugs, and
>feedback.

1. Stories describe business requirements.

2. Bugs are feature defects.

Developers usually address major bugs in current development, saving
minor bugs for later releases.

3. Feedback items are feature enhancement requests that are often

documented during playback sessions with stakeholders.

Developers use feedback to guide development on current or future

releases.

Work items become the backlog of development work.

Typically, the majority of development work consists of user stories.

You can optionally associate work items with features or subfeatures.

> Features are capabilities that you want your application to

support.
 > Subfeatures are features within a feature.

When you create a new case type in your application, Pega Platform™
automatically creates a feature with the same name.

Every work item has a status of either

> To do,
> Doing, or
> Done.

To change the status of a work item, drag the card to the appropriate
column or use the Status drop-down on the work item itself.

The Application profile displays all the features and work items, as
well as their status, in your application.

The Application profile provides an up-to-date view of application

status.

Agile Workbench integration

Agile Workbench interfaces with Agile Studio,

a separate Pega tool that expands the Agile Workbench functionality

with more robust features around release management,
progress tracking, and team capacity as well as analytics.

Agile Workbench also interfaces with external tools such as Jira or CA

Agile Central.

The integration abilities of Agile Workbench allow customers to

leverage the benefits of DCO while using their existing infrastructure.

===================================================================================
===================================================================================
=

============
Release management with Pega Platform ===========

DevOps

DevOps methodology operates under three pillars:

> people,
> process and
> technology.

DevOps is a set of practices that bridge application development and

operational behavior to
reduce time to market without compromising on quality
and operational effectiveness.
 It allows application developers and business owners to quickly respond
to customer needs,
develop a quicker feedback cycle, and
ultimately achieve business value faster.

DevOps People

DevOps encourages a culture of collaboration between

> development,
> quality, and
> operations teams to reduce or
> eliminate barriers through fundamental practices such as

* continuous integration,-----
Continuously integrating to share a repository every day
* continuous delivery,--------- Always
ready to ship
* continuous deployment.---------
Continuously Deploying/ Shipping

Continuous integration and delivery

A continuous integration and continuous delivery (CI/CD) pipeline is an

automated process to quickly move
applications from development through testing to deployment.

The Pega CI/CD pipeline

Different questions are asked during every stage of the pipeline.

These questions can be grouped into two categories:

1, Developer-centric questions ------- Ready to share,

Integrate changes

Are the changes good enough to share, and do they

work together with other developer changes?

2.Customer-centric questions ---------Ready to accept,

Readyto deploy

Is the application with the new changes functional as

designed and expected by customers and ready to use by customers?

Continuous integration

With continuous integration, application developers frequently check in

changes to the source environment
and use an automated build process to automatically verify these
changes.
 ---------The Ready to Share and Integrate Changes
The Ready to Share and Integrate Changes steps ensure that all the
necessary critical tests
are run before integrating and publishing changes to a
development repository.

Continuous delivery

With continuous delivery, application changes run through rigorous

automated regression testing and are deployed to a staging
environment for further testing to ensure that the application is
ready to deploy on the production system.

---------Ready to Accept step,

In the Ready to Accept step, testing runs to ensure that the acceptance
criteria are met.

-----------------The Ready to Deploy

The Ready to Deploy step verifies all the necessary performance, scale,
and compatibility tests necessary to ensure the application is ready
for deployment.

--------------The Deploy step

The Deploy step validates in a preproduction environment, deploys to
production,
and runs post-deployment tests with the potential to
roll back as needed.

DevOps technology

You can start your DevOps journey by using

> Deployment Manager, and
> you can also integrate third-party tools.

Deployment Manager

Use Deployment Manager to configure and run continuous

integration and delivery (CI/CD) workflows for
your Pega
applications from within Pega Platform™.

With Deployment Manager, you can fully automate your CI/CD

workflows, including branch merging,
application package generation, artifact management, and
package promotion to different stages in the workflow.

Third-party tools

Pega Platform also includes support for open DevOps

integration using popular third-party tools such as
Jenkins and Microsoft Azure DevOps
by providing an open platform,with all the necessary hooks and services.

With open DevOps integration, you can build a deployment

pipeline by using third-party tools to automate branching.

=====================Agile development
best practices============

Agile development best practices include:

> Frequent development iterations that are small in scope

> Continuous application testing to identify issues early
> Branched development that ensures only quality configurations
are introduced

===================================================================================
==================================================================================

==============Sizing a
Pega Platform project==========

Roles on a Pega project

Product Owner
Owns the product backlog and prioritization of backlog items.
Creates acceptance criteria.

Consulting Solutions Executive

Provides thought leadership, oversees project delivery and
direction, establishes best practices and governance.

Specialty Architects
Engage with project development depending on project needs and
skills alignment.

Project Delivery Leader

Provides overall project plan and delivery guidance.

System Administrator and IT resources

Provide expertise as needed. For example, on infrastructure,
security, or integration.

Scrum Master
Promotes and supports Scrum and ensures that all team members
understand Scrum theory and practices. Facilitates Scrum events as needed.
 System Architect (SA, SSA, LSA)
Designs and configures the application.
Lead or principal architects (LSA) design the overall
architecture.
Senior (SSA) and system architects (SA) configure assets such as
user interface forms and automated decisions.
They contribute object-oriented design and technical
implementation skills.

Subject Matter Expert (SME)

Has deep understanding of a particular business topic or domain.
The SME works with the project team to convey business needs and
helps validate information accuracy.

Business Architect (BA)

Works with subject matter experts and stakeholders to understand
business needs.
In a Pega Platform™ application, Business Architects define
business rules, service level agreements, and processes.

Quality Assurance (QA)

Creates and executes functional and performance test scripts,
participates as part of the Scrum team.

Citizen Developers
Collaborate on Pega projects. Citizen developers are non-
technical business users who participate in application development.
These developers bring valuable knowledge about the business
needs.

The Estimator tool

In App Studio, provide information about your planned

application, such as the implementation methodology,
the number and complexity of features that you want to
implement, and how many scrum teams are involved.

The project estimator automatically calculates the predicted

project duration.

To use the Estimator, you first need to define the main elements
of your application:

> Create a case type, and then define the case life
cycle by adding stages, processes, and steps.
> Define personas that represent users of your
application.
> Create data objects that visualize the information
that your cases require to reach the resolution stage.
> Add features that represent usable functionalities
in your application.

Release
Select a specific release (MLP1, MLP2, MLPn, Future, Unplanned,
All, or custom) to view the estimate for that release.

Delivery
Select the implementation method that your development team uses:
Scrum/Agile or Waterfall/Other.

Channels are assigned to a release to estimate the duration for each

release.

Data objects are assigned to a release to estimate the duration for

each release.

===================================================================================
===================================================================================
=

==========Adding
optional actions to a workflow=======

Optional actions

You can define actions that users optionally perform during case
processing. These actions are called optional actions.

Optional actions may depend on the specifics of the case.

Optional actions may also be common case processing actions that

may be invoked at varying times during the case.

Pega Platform™ provides an optional Change Stage action that may

be called at any time during case processing.

Optional actions are accessible at runtime from the Actions menu

in the case.

Use an optional process to configure a series of steps that users

can invoke at any time during a particular stage or at any time during the case.

A series of steps that are not the usual path can be handled with
an optional process.
 Case wide and stage-only actions

You can add optional actions as

>case-wide or
>stage-only actions.

If your action or process is only relevant in the context of a

specific stage, configure the work as a stage-only action.

Pega Platform provides some built-in case wide actions, for

example, Change Stage and Transfer Assignment.

Adding an optional action to the case type allows end users to

choose when they want to modify the address and keep the case on the primary path.

===================================================================================
===================================================================================
=

================Automating workflow decisions=============

Decision points

Automating decisions based on business logic allows application users

to focus on decisions that require human expertise.

a flow is a sequence of events that models a business process.

You create flows to support the different paths that users can take
through a case life cycle.

You can define paths in a flow by using graphical shapes and

connectors.

The shapes and settings that you choose depend on the types of
decisions that users make, and the order in which the events occur.

Decision shapes

You can use a Decision shape to add a conditional path to a flow or

model more complex use cases.

Decision shapes are configured to advance a workflow automatically.

An automated decision evaluates business logic or a set of one or more

conditions.
 Variations of the decision flow include:

1. Cases that move forward but may include another step as

needed.
You can choose when additional processing is needed to
support case processing.

2. Cases that go to another stage.

You can use the Change Stage shape to move a case to a
different stage in the case life cycle.
By skipping a stage, you can support out-of-sequence
processing in a case.

3. Cases that go back to the beginning of the current stage.

You can use the Change Stage shape to return to a
stage in the case life cycle.
By revisiting a stage, you can support repeat
processes in a case as necessary.

===================================================================================
===================================================================================
==

========Automation
shapes in the case life cycle=========

Automation shapes

Pega Platform™ provides automations to perform specific actions

automatically.

Leveraging automations saves development time and enables you to design

business processes more efficiently.

Automations provide flexibility because each automation has unique

parameters that you can configure based on your business requirements.

Additionally, utilizing automations reduces possible human error by

reducing the amount of human interaction.

Automation shapes in a flow represent a task that a user or application

completes as part of a business process.

The Send email automation helps to send automated email correspondence

to all relevant parties.

The Create PDF automation helps to create and attach a screenshot of a

view to the case in the PDF format.

The Run data transform automation helps to run the selected data
transform rule at run time.
Attach content -----Attaches a file, URL, or note to a case

Change to a stage -----Change to a specific stage of a case.

Change to next stage ---------Change to the next stage of a case automatically.

Create case -----------Creates one or more cases from the current case.

Create PDF --------Creates a PDF file from a specified section and attaches it to
the case.

Generate document ------Generates a document from a Word template and attaches it

to the case.

Persist case -------Converts a temporary case to a permanent object in the

database.

Post to pulse --------Creates a message and sends it to the Pulse social stream.

Push notification ----Sends a notification to an iOS or Android mobile device to

indicate that a case requires user action.

Run data transform -----Runs a data transform.

Send email ----Send formatted emails to custom recipients.

Send notification ---Sends a notification to recipients over multiple channels.

Update a case ----Updates the current case or all child cases and descendants.

Search duplicate case ----Automatically searches for duplicate cases using set
conditions.

Wait ------Pauses a case until a specified condition is fulfilled, such as timer or

case status.

Questionnaire ----Asks the user to complete a questionnaire.

===================================================================================
===============================================================================

=============Creating a
child case==========

Case hierarchy

In Pega Platform™, you can model case relationships with a case

hierarchy that contains top-level cases and child cases.

A parent case that creates multiple child cases allows for work to be
processed in parallel.

Different parties with different expertise can handle each child case.

When processing child cases in parallel, the parent case may need to
wait until a child case is complete before the parent case can be resolved.

Child cases are beneficial in situations where you want to:

> Model work that different parties perform

> Model work that follows different reporting options
> Model work that follows different time frames
> Model work that is common to multiple case types

Create Case step

To add a child case to a case type, add a Create Case automation step
to the case life cycle.

When encountering the Create Case step, Pega Platform creates an

instance of the specified case type.

Note: Dev Studio gives you additional configuration options for the
Create Case step.

The created case can either be a top-level case or child case.

Additionally, multiple child cases can be created.

Data propagation

When creating a child case, you can also specify the information to
copy from the parent case to the child case
through a process known as
propagation.

You identify the fields in the parent case to copy from and copy the
values to fields identified in the child case.
This configuration is performed on the Create
Case step.

Note: Data references require advanced configuration in Dev Studio.

=================== =================== =================================

======================== ============================================= ===========
==========

======Identifying
duplicate cases==========

Search duplicate cases step

Pega Platform™ provides the search duplicate cases process to help

users identify and resolve duplicate cases.
 This process is implemented in the case life cycle as a Search
duplicate cases step.

When a case enters the step, the system uses basic conditions and
weighted conditions to compare specific property values with cases already present
in the system.

Does an exixting condition meet the basic condition? -------

NO(Search duplicate cases step ends)

Does the sum meet or exceed the threshold value ---NO(Search duplicate
cases step ends), yes ( potential duplicate cases are displyaed)

If the basic condition evaluates to true, the current case is eligible

as a potential match and is evaluated using weighted conditions.

Resolve current case

The user may decide the current case does match one of the
potential duplicates.

The case will be resolved as a duplicate and processing

terminated.

Display potential duplicate cases

Existing cases which reach the duplicate threshold value are

displayed for the user to review and decide if one of them is a duplicate.

Ignore and continue

After reviewing the potential duplicates, the user may decide the
current case is not a duplicate and continues to the next step in the process.

When a user decides the current case is a duplicate it is resolved

(status Resolved-Duplicate) and processing of the case terminates.

===================================================================================
===================================================================================
===============

=============Skipping a
process or a stage======================

You can define conditions that control whether a process or stage runs
in a case.

A condition consists of a field, comparator, and value.

Processes and stages are either executed or skipped if the case run-
time values match the conditional logic defined.

On a Stage you define a condition with comparators to determine when

the stage is skipped.

On a Process you define a condition with comparators to determine when

the process is executed.

===================================================================================
===================================================================================
===

=========== Pausing and

resuming case processing ==========

Pause and resume case processing

You can enforce dependencies using the Wait step.

The Wait step allows you to pause and resume case processing when
the case meets conditions that you define.

Wait types

The Wait step can be configured to pause case processing based on Wait
type:
>Case Dependency or
>Timer.

Case Dependency

The Case Dependency wait type pauses case processing of a parent case
until the child case dependency resolves.

You can also set the Wait step to To be resolved, where a case is
resolved when the case status is set to a value that starts with the word Resolved.

when a parent case reaches the Wait step, the case pauses until one or
all child cases are resolved.

Note: A hierarchical relationship between cases, such as parent and

child cases,
must exist for the wait shape to consider the dependency
at runtime.

You can also allow users to cancel the wait conditions and continue
processing a case.

Timer
 The Timer wait type pauses a case until the Set date/time interval
expires or until a Reference date/time is reached.

You can enforce all case workflow dependencies by using a ________Wait

Step_____________ to pause and resume case processing.

You can create a wait step configured as a ____Case Dependency___wait

type that waits until all child cases
are resolved before resuming the current parent case.

You can create a wait step configured as a ___Timer____ wait type that
waits until the end of the business day before resuming the current case.

===========================================
============================================
==================================================== =======================

======Validating data
against business logic======

Valid data is required so that the system can process the information
without error.

Some data requirements are outlined in the following table.

Data requirements
Examples

The data must be the right type.

users must enter a number in a Total purchase units field.
The data must be restricted to possible values. users
can only choose a valid loan type by selecting the type from a list of options.
The data must fit the business logic.
a Date of birth field must be in the past.

Tip: Your error message should provide users with the information
needed to identify and resolve the data validation error.

In App Studio, you can validate the value of a field when you submit a
form or when the case enters a stage.

The field type, such as Date and time, validates that data is of the
correct type.

The control, such as a drop-down list, validates that data is

restricted to a set of values.

A validate condition, such as Currency equals USD, validates that data

meets business requirements using business logic.
 Validation on a stage

You can also use business logic validation on a stage.

Use business logic validation on a stage to ensure the application has

generated the correct data and that users have
entered the correct data or performed the
appropriate actions before the case enters a specific stage.

Configure the stage entry data validation on the stage to prevent the
case from entering the stage.

===================================================================================
===================================================================================
=====

=========Exploring
application data with Insights==========

The Explore Data landing page

The Explore Data landing page allows you to explore and analyze data in
your application quickly.

On the Explore Data landing page, you can query your data, and then
sort, filter, and group the results based on your business requirements.

You can save queries you make on the Explore Data landing page as
insights.

Note: Explore Data uses a React-based landing page and is the preferred
data exploration tool for applications that use the Pega Cosmos design system.

Insights

Insights are rules that Pega Platform™ uses to transform data queries
into tables or visualizations that you can then share between users.

You can use insights to retrieve specific data and present the data as
a list or an interactive chart.

The Explore Landing page displays a list of previously-created

insights.

On the Explore Data landing page, you can select a previously-created

insight to view or modify.

On the Explore Data landing page, you can create charts from an insight
to visualize your data.

===================================================================================
==================================================================================

===========Gaining
insight into business efficiency===========

The Report Browser

Report Browser tool to create new reports, organize, run, and share
reports as well as manage report categories.

Pega Platform™ organizes reports by category.

A category defines an organizational framework for reports displayed in

the Report Browser.

Each category consists of a label and an owner type that exposes the
category to a specific audience:
> an individual user,
>a group of users, or
>all users.

The two types of categories are private and public.

Private categories provide shortcuts to reports that you create.

Other users cannot run
or view these reports.

Public categories provide shortcuts to standard Pega out-of-the-

box reports that provide deep insight around
the volume, process, and efficiency for case resolution as
well as reports that users made available to others.

The Report Browser displays reports as visual tiles that provide a

preview of the type of report.

The first row of tiles shows reports recently open by the user. Each
tile includes a time period.

The time period listed on each tile indicates the amount of time
elapsed since the report's creation.

In the following example, the Report Browser shows three reports

recently opened by the user.

Pega Platform populates and sorts standard reports into the following
Public categories.

----- Analyze Performance

1. Reports in the Analyze Performance category analyze and
summarize resolved (completed) work items along quality dimensions.

--------Analyze Quality
2.Reports in the Analyze Quality category identify, by
assignment, which actions were selected, how often, and the timeliness of the
selection.

---Case Metrics category

3. Reports in the Case Metrics category provide information about
open and resolved cases, and historical views of step performance.

Two reports are in the case metrics category —

>Time per stage and
>Case Volume.

The Time per stage report provides a stacked bar chart of

resolved cases by stage with the length of the bar representing
the length of time
spent in each status by work type.

The Case Volume report provides the cases created per day grouped
by case types for the last seven days.

---- Monitor Assignments

Reports in the Monitor Assignments category provide information
about open assignments.

-----Monitor Processes
Reports in the Monitor Processes category list or summarize open
(unresolved) work items in the current application.

Reports in the Open Cases provide the case-level service level

agreement (SLA) status for open cases.

Reports in the Service Level Performance category provide the

assignment SLA statuses.

The User Timeliness report groups the assignment SLA statuses by user.

The open Step Timeliness report groups the assignment SLA statuses by
step.

Reports in the Step Performance category provide the status of process

steps.

The Step Performance category includes the following reports.

> Goals and deadlines by step – Provides the SLA status

grouped by assignment.
> Step duration – Provides a historical view of the time it
took a user to complete a step.
> Time spent in step – Provides a historical view of the
time spent on a particular step.
 Reports in the Predictive Model Monitoring category provide performance
information of your predictive models.

Reports

Application data can be categorized as either

>business metrics or
>process metrics.

Business metrics

Business metrics measure the success or failure of business processes,

and are based on the data you define for an application.

Organizations can use these business metrics to make informed decisions

about improving business performance.

Process metrics

Process metrics measure how work is performed, and are based on

data automatically collected by Pega Platform™.

Process metrics enable business analysts and business managers to

discover issues that impact process efficiency.

The role of reports

Reports present users and managers with business and process

metrics, based on the data collected during case processing as a set of database
records.

Reports can also fetch data to populate user forms with data.

Report structure

The report retrieves the data from a database and returns the results
in a table of columns and rows.

Columns define the content of the report. Defining columns in reports

is critical to designing reports users need.

Each column corresponds to a single data element.

A filter defines a test applied to each record to determine whether the

record contains data your users need.

Filters compare a data value in the record against a defined condition.

===================================================================================
===================================================================================
=

=======Customizing UI
elements=======

Controls and presentation

User interface elements (such as text inputs and layouts) present

information and actionable items on the user interface.

The UI elements of Pega Platform™ include basic controls that you can
use out of the box, including:

Autocomplete controls
Buttons
Charts
Check boxes
Drop-down lists
Links
Sliders
Rich-text editors

The predefined style formats for a button include

* Standard,
* Simple, and
* Strong.

You can style all presentation elements of your interface, including

typography, borders, backgrounds, layouts, and UI placement and alignment.

Presentation and styling are defined for a specific control. Depending

on the control type, you can style different aspects of the control.

Dynamic functionality on UI elements

Dynamic UI design is the practice of designing a user interface to

adapt according to user input.

Dynamic UI content is a key element of an intent-driven UI design.

The benefits of using dynamic UI design include real-time response to

end-user behavior,
>robust functionality available for most user interactions,

>reduced visual clutter on the screen,

>and fewer full-page refreshes,
>which results in improved UI responsiveness.
 To configure dynamic behavior for UI elements, you can manipulate when
elements are visible and disabled.

Visible

Configure the visibility of a field or layout to display the field or

layout when a specific condition is satisfied.

By default, UI elements have a visibility setting of Always, meaning

the UI element always displays on screen.

Always
Condition (expression)
Condition (when rule)
If not blank
If not zero

Disabled

Configure when a field or layout is disabled to limit user access to a

field. A field or layout is disabled when a specific condition is satisfied.

By default, UI elements are never disabled, meaning users always have

access to the UI elements.

Never
Always
Condition (expression)
Condition (when rule)

Required

Configure when a field or layout is required to ensure that a user

specifies a value. A field or layout is required when a specific condition is
satisfied.

By default, UI elements are never required, meaning the user can

proceed with case processing without specifying a value.

Never
Always
Condition (expression)
Condition (when rule)

Event processing with action sets

 Actionable controls are based on an event-action model, which
establishes a cause-and-effect relationship for a control such as a check box or a
button.

The event is a trigger caused by user activity, such as a button click

or field entry.

The action is a response by the application, such as creating a case or

displaying information about a field to guide user input.

The following table lists examples of event-action pairs.

Event
Action

Click a control such as a button, link, or icon

Open a new window
Double-click a row in the grid
Allow editing of the contents of the row
Press the Enter key on the keyboard
Display a menu
Select a value from a list of states or provinces
Update the list of office locations
Enter a value in the Quantity field
Verify that inventory is sufficient to fulfill the order

Action sets

An action set consists of one or more events and one or more actions.

Caution: Both events and actions can be shared between action sets.

As a result, one or more events can trigger an action, and an event can
trigger more than one set of actions.

===================================================================================
============================================================================

============Customizing portal
content==========

Channel interfaces

channel is a messaging service, voice service, web portal, or mobile

portal.

Customers interact with Pega applications through a variety of

channels.

channel is a messaging service, voice service, web portal, or mobile

portal.

Customers interact with Pega applications through a variety of

channels.

Channels also provide ways for users to interact with your application
by using Pega Intelligent Virtual Assistant™ and Pega Email Bot.

Pega Intelligent Virtual Assistant understands intent and

conversational language for dynamic conversations with
your customers regardless of the
channel in which they start or end.

Pega Email Bot automatically detects the intent of an email and picks
up relevant information to automate the processing
with a
personalized response.

You can also use the Pega API to access application functionality using
a REST web service.

The Channels landing page allows you to create, view, and edit all
types of channel interfaces.

Create stage

The Create stage is included in the case life cycle by default when
creating a new case type.

You can also create a channel-specific process in the Create stage.

Portals

A portal is a web channel in use by your application.

End users experience the portal through a browser, regardless of device

type (such as a desktop or mobile device).

Portal authoring is a simple and intuitive way to create an application

web channel.

By default, Pega Platform™ has one portal for application users – the
User Portal.

The User Portal provides a standard user interface for working on

cases.

Landing pages

A portal consists of landing pages that consolidate information for

easy access.
 To build an application that matches the needs of your users, you
create landing pages
with fields, controls, and
resources presented as images and text.

Landing pages allow you to present additional resources to users. You

can create,
configure, and add landing pages to menus
within your application to display specific information.

Landing pages added to a portal menu are also added to the portal.

By managing the list of landing pages, you can customize the main menu
and improve navigation and user experience.

Pega Platform provides out-of-the-box landing pages, called Custom

pages.

Landing pages menu

You can place a finished landing page within one or several application
menus by using the Landing pages menu in App Studio.

You can also add, disable, or manage access to landing pages as well.

> Add landing pages to an existing portal to effectively

organize the content of your channel in a main menu.
> Disable an existing landing page that is no longer needed
to prevent users from adding the landing page to any menu.
> Manage access to landing pages by specifying visibility
by role.

Tip: In App Studio, click Design to toggle Design mode, and then click
Pages to access the Landing pages menu.

===================================================================================
=================================================================================

==========Customizing a
dashboard==========

Dashboards

Dashboards are landing pages that are customizable by end-users.

Dashboards consist of widgets that consolidate summary information and

Key Performance Indicators (KPIs)
from different sources and present it in an
actionable format.

Dashboards contain the information necessary for a particular role to

help increase productivity.
 By default, Pega Platform™ uses role-based interfaces, which includes a
dashboard tailored to a role.

Organization

A template defines the layout of a dashboard and divides the workspace

into slots.

Slots are containers for one or more widgets, which are elements of
the user interface that display information about the
application and KPIs.

Personalization

The default dashboard is assigned based on the user role.

The developer can configure the dashboard for a role by publishing

changes to the default dashboard.

Then, end users can access the published default dashboard assigned to
their role.

End users can also personalize the default dashboard by publishing

changes to their dashboard instance.

Note: Custom landing pages are landing pages that are built as part of
the application;
end users are unable to customize the landing pages.

Custom landing pages are typically built as a landing page to navigate

to listed objects.

Pega Platform provides various templates that allow developers and end
users to organize widgets differently.

The provided templates have different numbers and orientations of

slots.

===================================================================================
==================================================================================

============Designing a
mobile app experience=============

Mobile app channels

Mobile channels have become more powerful and easy to use providing an
additional, convenient access channel to support employees in the field.
 You can use the existing mobile channel to quickly build a consumer-
grade app, or modify an app to meet your needs.

A mobile channel provides developers a way to intuitively configure and

customize various aspects of mobile app behavior.

The mobile channel is organized into settings logically grouped on the

Content, Configuration, Layout, and Manage tabs.

The channel provides a real-time preview of the app design, tailored to

the current tab.

Mobile app security

To make your mobile app more secure, you can use the Security tab to
select an authentication model and configure the locking settings for your app.

Mobile app branding

Pega Platform™, allows you to build custom mobile apps in a low-code

environment.

You can tailor the app's interfaces to reflect your brand identity.

Icon and launch screen design

You can customize the app branding by: uploading an image, selecting
from a list of font icons, or using the default text-based icons.

Theme customization

To ensure a consistent experience throughout the user workflow, define

an application-wide theme for your app.

In the Layout tab, specify colors for various interface elements and
observe the changes in real-time on the mobile app preview.

===================================================================================
===================================================================================
=======

===========Calculating fields using

decision tables============

Decision table logic

 Decision tables are a good approach when you use a set of properties or
expressions to arrive at a decision.

Decision tables in App Studio

You can configure calculated fields using out-of-the-box basic

functions and simple custom expressions in App Studio.

Note: Complex decision tables that are pre-configured in Dev Studio

and marked as
relevant records are available in
App Studio for citizen developers to use.

===================================================================================
=================================================================

====================Inviting users to an
application===========================

Pega Platform™ provides a User Management feature to help you organize the
users of your
application into
personas that share common application security and assignments.

Note: Assigning users to appropriate personas is only one aspect of securing

an application.

Personas

A persona is the business representation of a type of user.

Personas allow the organization to identify unique needs for

application users, which could include different user interfaces to meet those
needs.

Note: Organizations may create multiple personas to reflect different

marketing approaches that may not impact application or case design.

Channel interfaces

In Pega Platform, user interfaces are also called channel interfaces.

Because the needs of different users require access to different

application features, you can configure different personas and channel interfaces.
 When you create an application, Pega Platform provides one default
persona: Users.

Users are case participants that are responsible for creating and
resolving cases.

Associate a persona to the channel interfaces that best satisfy the

needs of the persona.

Multiple personas can share a channel interface if appropriate.

A user is an individual who interacts with an application.

===================================================================================
===================================================================================
========