BA Flashcards
1
Q
Business Architect
A
Work with subject matter experts and stakeholders to understand business needs.
In a Pega application, they define business rules, service level agreements, and processes
2
Q
Product Owner
A
Owns the product backlog and prioritization of backlog items. Creates acceptance criteria
3
Q
Subject Matter Expert
A
The 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
4
Q
What roles are associated with the following responsibilities?
• Configure user interface forms
A
(System Architect)
5
Q
What roles are associated with the following responsibilities?
• Define business rules
A
(Business Architect)
6
Q
What roles are associated with the following responsibilities?
• Create acceptance criteria
A
(Product Owner)
7
Q
What roles are associated with the following responsibilities?
• Define service level agreements
A
(Business Architect)
8
Q
What roles are associated with the following responsibilities?
• Own prioritization of backlog items
A
(Product Owner)
9
Q
case
A
work that delivers a meaningful business outcome
10
Q
case type
A
an abstract model of a business transaction, where a case is
a specific instance of the transaction.
11
Q
case life cycle design
A
allows business users to begin by organizing work into
stages.
12
Q
Stages
A
represent the transfer of a case from one authority to another or a significant
change in the status of the case.
13
Q
A primary stage
A
a high-level phase in the lifecycle of a case that leads to the desired
outcome.
14
Q
A process
A
contains a series of
tasks, or steps, that a user completes as they work the case.
15
Q
A step
A
is either a user action or
automated action performed by the application.
16
Q
alternate stages
A
When a case does not follow the primary path,
17
Q
Change Stage
A
step automates non-sequential case flow, such as to and
from alternate stages.
18
Q
case status
A
the primary indicator of the progress of a case towards
resolution
19
Q
An instruction
A
a step identifies to a user what should be accomplished
in an assignment
20
Q
service level agreement (SLA)
A
establishes a deadline for work
completion.
21
Q
How does the passed deadline interval differ from goal and deadline intervals?
A
can repeat
22
Q
optional process
A
update information in multiple steps.
Users may or may not return to the primary path of the case.
23
Q
Optional user actions
A
update information in a single user screen.
24
Q
parallel processes
A
If processes can be performed in any order
25
assignment routing
to assign work to the most appropriate user
26
work queue
a list of all open assignments, in order of importance, for
| a group of users.
27
A worklist
A worklist is a list of all open assignments, in order of importance, for a
specific user.
28
current user
the employee creating the request enters the expense details.
29
specific user
the manager who approves expense reports.
30
when condition
when you want to route work based on certain conditions.
31
single approval
You can assign single approvals to the worklist of a specific user or a work queue.
32
cascading approval authority matrix
based on an authority matrix is more flexible than reporting structure. It supports routing to other entities outside of the reporting structure.
33
cascading approval reporting structure
Cascading approvals based on reporting structure require approval of an employee's direct manager and higher. You can also configure business logic to set thresholds to determine the number of required approvals.
34
Rules
describe the behavior of individual cases.
35
rule type
is an abstract model of a specific case behavior. Rules are instances of rule types which generate application code.
36
Rulesets
package rules for distribution as part of an application.
37
ruleset version
System architects collect individual rules into a subset of a ruleset
38
ruleset stack
Each application consists of a sequence of rulesets
39
work Classes
Contain the rules that describe how to process a case or cases, such as processes, data elements, and user interfaces
40
integration classes
Contain the rules that describe how the application interacts with other systems, such as a customer database or a third-party
41
data classes
Contain the data objects modeled for the application, such as a customer or collection of order items
42
A parent class
contains another class
43
A child class
is contained by another class
44
Rule check-out
creates a copy of a rule in a ruleset that is only
| visible to you, called a personal ruleset.
45
Pattern inheritance
```
follows the class hierarchy to
support the reuse of rules within an application.
```
46
Directed inheritance
allows your application to reuse
| rules from other applications with different classes.
47
The data elements or
collection of related data
elements in a case type
comprise the
data model.
48
The data model defines
| the
case type data
| structure
49
A collection of related
| elements is called a
a data
| type or data object.
50
Value mode
represents a single piece of information.
51
Page mode
represents a data object that contains related values.
52
A value group
acts as a container for an unordered
| list of single values
53
• A value list
acts as a container for an ordered list of
| single values
54
A page
is a single entity.
55
A page list
is a numerically ordered list.
56
A page group
is an unordered list
57
Simple types
are similar to the property types defined on the
property itself. Use a picklist if you need to display a static list of
options to the user.
58
Fancy types
allow you to provide the capability to upload an
attachment, show a location on a map, or reference a user on
the system.
59
Complex types
define page and page list properties. A field
| group is a page and a field group (list) is a page list
60
Data Access section:
Configure automatic data access and persistence settings
61
Display and validation section
: Define how the property should appear on the screen by specifying a UI control
62
px:
Identifies special properties. Your application can read but not write to these properties
63
py:
You can use these properties in your application.
64
pz:
Supports internal system processing. Your application can read but not write to these
properties.
65
data element
in a Pega application is a pairing of two pieces of
information: the name of the data element, and the value assigned to the data
element.
66
A page
is a structure for
| organizing data elements in an application.
67
The pyWorkPage
is a specific page on the clipboard that stores all the
| data generated while creating and processing a case.
68
An embedded page
is a page within pyWorkPage that stores data
| describing a data type.
69
The pyWorkCover
is a separate page that contains the case data for a
| parent case when the associated child case is processed.
70
User Pages
category contains pages created due to user action, either directly or indirectly.
71
Data Pages
category contains read-only data pages defined by data page
| rules.
72
Linked Property Pages
category contains read-only pages created by linked
properties, which contain information from data objects referenced by a
linked property.
73
System Pages category
contains pages that describe the current user
| session, such as the active user and the active application.
74
• pyDefault data transform
is invoked when a case is created. It is used to
| set default values for cases.
75
pySetFieldDefaults data transform
is used to initialize default field values.
76
Declarative processing
instructs the system to monitor the
application to determine when a trigger event occurs. Declarative rules
define a trigger event and resulting action.
77
Procedural processing
depends on rules to instruct the application
when to look for a trigger event. Rules such as data transforms, activities,
or user interface (UI) rules perform updates based on a predefined trigger.
78
Declare expressions
automatically calculate property values and
| are comprised of an expression and a target property
79
A declarative network
is a set of interdependent declare expressions.
80
Forward chaining
in a declare
expression pushes updates to the
target value
81
Backward chaining
pulls values from
| the source property or properties.
82
Properties
Single value properties have property types such as date, decimal,
integer, text, or true/false. Selecting the appropriate property type
ensures that users enter a valid value.
83
Controls
Controls are another way you restrict users from entering or
| selecting invalid values on a form.
84
Validate rules
to compare a property against a condition when the user
| submits a form.
85
Edit validate rules
to test single value, value list, and value group
| properties for patterns.
86
• Pega system of record
– A Pega system of record can locally source data
types.
• Example: In the New Candidate application, HR can select a conference room in
which to conduct the interview. The Pega system of record locally sources the
Conference Room data type and the Pega system of record would have a list of
the conference rooms.
87
External system of record
– External systems can source data types.
• Example: A Candidate data type stores basic identifying information about
candidates. An external system of record, (external vendor tool that adds and
tracks candidates), sources the Candidate data type.
88
No system of record
– Data types can obtain data entered or
transformed during application processing and not associate with a
system of record.
• Example: During interview scheduling, you capture candidate information about
any dietary restrictions. This helps HR provide an appropriate lunch for the
candidate during the interview break. The Dietary Restrictions data type is used
for case processing but is not pushed to a system of record
89
Data page scope –
captures how widely data is visible in an
application. There are three levels of a scope: thread, requester and
node.
90
Structure of a data page
– uses a single page to load a single record.
| You use a list if you want to load multiple records.
91
Data page source
– any source of data that an application uses, such
| as a connector, report definition, or lookup. Data sources are referenced in data pages.
92
Data page object type
– The object type identifies the information
| the data page will capture.
93
Refresh strategy
– defines when the data is stale and needs to be
reloaded. Data pages are created and updated on demand. The page
is never reloaded until it is referenced.
94
read only
– Used for data pages that should not be modified. The data
| page displays in the Data Page list on the clipboard.
95
editable
– Allows the data page to be modified. The data page is displayed
in the user page list on the clipboard.
96
savable
– Provides the data page by saving through a database source or
an activity. Savable data pages are referenced in save data page locations.
Selecting this mode opens the data save options sections so that you can
select a save plan option
97
In Pega, you build user forms with sections.
Sections group information and
| functionality by context and purpose.
98
Inside a section, you organize UI elements with layouts.
Layouts contain rows
| and columns, defining a set of cells.
99
Dynamic layout
– Organizes a single set of fields in a general purpose layout.
100
Repeating layout
– Organizes lists, tables, and other repeating structures.
| Repeating layouts reference a page list or page group.
101
Label
– Used to identify the purpose of the section. The label is used to generate an
identifier for the record.
102
Class
```
– The class to which the record is applied. The class determines the availability and
re-usability of the section.
```
103
Ruleset and version
– The ruleset and version that contains the record. Pega defaults to
the highest unlocked application ruleset when you create a record.
104
A Responsive UI
enables a layout to automatically adjust to rendering devices. Elements
can move around, resize, or completely disappear based on screen resolution and size.
105
Pega applications have system default responsive breakpoints
that define when changes
| in behavior on different devices skin rules should occur
106
A skin rule
defines presentation formatting instructions for one or more UI forms.
107
Primary
– The unique identifier for the row. Each table must have one primary
column.
108
Secondary
– Important information with a significant effect on usability. Omitting
information in a secondary column impacts the ability of the user to complete a
task.
109
Other
– Information with minimal impact on usability
110
• Event:
A trigger performed by users, such as clicking a button, hovering a
pointer over a field, or entering a value in a field.
111
Action:
A response performed by the system as a result of the user event.
112
Conditions:
A restriction such as when rules can be applied to an event and
action combination.
113
A mixin
defines a set of style attributes that can be reused in user
| interface elements.
114
Report definition
is used to build a report.
115
Report columns
define the report's contents.
116
Functions
in columns make reports more useful.
117
A report filter
compares a data value in the
| record against a defined condition.
118
Business metrics
that represent the data you define for an
| application.
119
The Report Browser
is used to organize, run, and share
| reports.
120
Pega organizes reports by category.
A category defines an
| organization
