CSA Flashcards
(135 cards)
1
Q
DCO (Direct Capture of Objectives)
A
A set of application development tools and best practices designed to capture and tie business and project goals, objectives, processes, specifications and requirements to implementations.
2
Q
guardrail
A
Guardrails are guidelines that help developers achieve project success, optimal performance, reuse, and maintainability for applications.
3
Q
compliance score
A
A compliance score is a weighted score for each application that measures overall compliance with the Pega Platform best practices. This score is available on the Guardrails landing page.
4
Q
case management
A
Case Management is a business practice that helps you deliver outcome driven results. It relies on case types to model customer processes, share information, and ensure that there is visibility into the work that is completed by your application. Case Management automates service-level agreements, escalation, and audit trails so that you can provide a quality, end-to-end customer experience. Use the Case Type Explorer and Case Designer to build a Case Management strategy in your application.
5
Q
Pega Cloud
A
Pega Cloud provides services for customers to augment their IT staff. It supplies the infrastructure, operational support, and life cycle management to support Pega applications as a cloud-delivered solution. Customers contract and are provided specific services from the Pega Cloud service catalog to address their application needs.
6
Q
base class
A
A base class is one of twelve standard abstract classes that are immediately below the top class in the hierarchy. This top class, known as the ultimate base class, is identified by the symbol @baseclass
7
Q
Related Rules
A
Related Rules is a button on the Designer Studio toolbar used to access a list of other rules that are alternatives or otherwise related to this rule.
8
Q
ruleset
A
A ruleset identifies, stores, and manages the set of rules that define an application or a major portion of an application. A ruleset contains rule instances, which are divided into ruleset versions to support version management. A ruleset is identified in the system by the ruleset name, which is an instance of the Rule-RuleSet-Name rule type.
9
Q
situational layer cake
A
A situational layer cake is a metaphor to describe how Pega interacts with customers the right way at the right time. Each layer specializes on a different dynamic variable, such as customer attributes; country or region; product or line of business.
10
Q
access group
A
An access group restricts access to functionality within your application. You can create multiple access groups for the same application to achieve different levels of access control.
11
Q
case manager
A
A case manager is an application user who can view and update delegated business rules, in addition to performing work.
12
Q
Case Manager portal
A
The Case Manager portal supports users who manage cases and their related sub-cases and tasks across multiple channels, lines of business, departments, and systems. Users can create, view, and work on cases and assignments.
13
Q
case worker (operator)
A
A case worker is an individual responsible for creating, processing, and/or resolving a case.
14
Q
Case Worker portal
A
The Case Worker portal provides case workers with a standard interface for creating, viewing, and working on their own cases and assignments. Users cannot monitor and manage work among other operators or workbaskets, or view work statistics.
15
Q
Cases Type Explorer
A
The Case Type Explorer is a tool that lets you view all of the case types that are in your application. Use it to manage the hierarchical structure of your case types, access Case Designer, and browse examples of case management rules that you can leverage in your application. To open the Case Type Explorer, click the Cases icon in the explorer panel of Designer Studio.
16
Q
operator menu
A
An operator menu provides access to your operator profile and a number of features, depending on where you access the menu and your application configuration. You can access the operator menu by clicking your name in Designer Studio, Pega Express, and the Case Manager, CaseWorker, WorkManager, and Manager portals.
17
Q
Pega Certified Business Architect (PCBA)
A
A Pega Certified Business Architect (PCBA) possess the fundamental, essential skills needed for analyzing, designing, and creating business requirements and specifications in the Pega application.
18
Q
Pega Certified System Architect
A
A Pega Certified System Architect (PCSA) is a Pega Platform application developer or technical staff member who has passed an exam that acknowledges the acquisition of foundation-level knowledge of the Pega Platform.
19
Q
Lead System Architect (LSA)
A
A Lead System Architect (LSA) is an application developer who provides technical leadership in design and project management tasks to an application development project.
20
Q
Senior System Architect (SSA)
A
A Senior System Architect (SSA) is someone who has taken additional training, and understands advanced technical concepts such as class structure, inheritance, and rule resolution.
21
Q
System Administrator
A
A system administrator is responsible for system installation and setup, security and access, and other operational functions.
22
Q
case (work item)
A
A case is an instance of a case type and is a primary unit of work in an application. You can manually create, or instantiate, a case in an end user portal or through forms in an application. Your application can automatically create a case when a parent case is created, or email is sent to an account that is associated with the starting process of a parent case. In legacy systems, cases are commonly referred to as work items or work objects.
23
Q
case type
A
A case type represents work in your application that follows a life cycle, or path, to completion. Each case type has a hierarchical structure and can include attachments that provide relevant details about the work that you are processing. Instances of case types are called cases.
24
Q
Stage
A
A stage is the first level of organizing work in your case type. It contains the workflows, or processes, that users follow before they can move a case to the next phase in the case life cycle.
25
process
A process is the path, or paths, a case follows as it is completed (resolved.)
26
step
A step is a unit of processing that is typically executed as part of an ordered sequence. Steps can be represented as numbered rows on a rule form, such as the Activity or Collection form, or tasks within a process.
27
alternate path
An alternate path in a process consists of alternative steps that a case might take from the primary path. You can add alternative steps to the primary path of a starting process or to a subprocess.
28
Case Designer
Case Designer is a tool that helps you visually model stages, steps, and processes for all case types in your application. Its centralized view lets you capture objectives without switching context between individual rule forms and your case type. Use it to design staged-based case types, build user forms, and seamlessly integrate with other rules in your application. To access Case Designer, open the Case Type Explorer and click any case type name.
29
process step
A process step represents a task that helps move a case toward resolution. Steps can be performed by users, your application, or an external application. Use Case Designer to add steps to the processes that are supported by each stage in the life cycle of a case.
30
Assignment
An assignment is a task that must be completed before an open case can continue through an executing flow. You configure assignments in a flow by using Case Designer or Process Modeler. Either a user or external system can act on an assignment.
31
Assignment (shape)
An assignment (shape) identifies a task that must be completed by a user or external system before an open case may continue through an executing flow. An assignment indicates that the case is temporarily paused until a user acts on the case. The user selects the appropriate action to complete the assignment, and provides any information required by the application to support the action the user selects.
32
Case Status
Case status is the primary indicator of the progress of a case towards resolution. Case status is the value of the standard property Work-.pyStatusWork.
33
Instruction
An instruction initiates an action for a row on an activity form. The instruction keywords are Call, Collect, Branch, Queue, Rule, and Java.
34
Case Type (rule)
A case type (rule) establishes how to create a case, including the relationship between the case and any parent or child case.
35
Deadline
A deadline is an interval of time that is defined in a service-level agreement. It is the required resolution time for an item, such as a case or stage.
36
service Level
A service levei is an expectation of performance for completion of a task or case. Service levels establish two time intervals ""a goal and a deadline"" that define when a task or case should be completed, the goal and when the task or case must be completed, the deadline. A service level for a case is defined as part of the case. A service level for an assignment is defined with a service level rule.
37
Urgency
Urgency is a numeric value that brings visibility to unresolved work in your application. The number can range from 0 to 100 and is displayed in worklists and case details. The higher the urgency, the more important it is to address the open work, such as an assignment or case. You can adjust urgency manually or with a service-level agreement.
38
escalation
An escalation is an action that is taken by your application to facilitate faster resolution times, based on a specified service-level agreement. For example, you can send correspondence to interested parties when a case is 5 days overdue. Use the Service-level agreement form to configure escalation behavior in your application.
39
Service Level Agreement (SLA)
A service-level agreement defines intervals of time, such as a goal and deadline, that are used to standardize how you resolve work in your application. You can apply a service-level agreement to cases, stages, steps, flows, and assignments.
40
goal
A goal is an interval of time that is defined in a service-level agreement. It is the suggested resolution time for an item, such as a case or stage.
41
service level (rule)
A service level rule is used to define the time interval required to complete an assignment. It includes one or two time intervals, known as goals and deadlines, which indicate the expected or targeted turnaround time for the assignment or time to resolution for the case. See deadline and goal.
42
decision
In Decision Management, a decision is the result of running a strategy in the interaction context. Several decisions can be involved in a single interaction.
43
decision (shape)
A decision shape within a flow diagram that calls a decision rule such as a decision tree, decision table or map value.
44
assignment
An assignment is a task that must be completed before an open case can continue through an executing flow. You configure assignments in a flow by using Case Designer or Process Modeler. Either a user or external system can act on an assignment.
45
operator ID
Defines an operator’s username, password, access group organizational setting, calendar and other values.
46
router activity
A router activity evaluates assignment criteria, such as required skill sets and user availability, to determine whether an assignment moves to a worklist or work queue for processing. Router activities have the Usage field set to Route on the Activity form, and return a result by assigning a value to the AssignTo output parameter.
47
skill
A skill rule is an instance of the Rule-Admin-Skill rule type. A skill rule gives a name and a range of proficiency value for a specific skill. These skills can be associated with users (in the Operator ID instance) and can be the basis of routing decisions.
48
work queue
A work queue is a list of work in your application that is shared by operators with the same user role. A work queue is sometimes referred to as a workbasket.
49
worklist
A worklist displays open assignments, ordered by urgency, for a specific operator. You can use your worklist to view the ID, status, and relevant instructions for each item.
50
flow shape
A flow shape represents a task that is accomplished as part of a business process. Shapes are differentiated by color, symbol, and name. You add standard, advanced, and smart shapes to a flow by using Process Modeler.
51
Class
A class is a collection of rules or other objects. Each class defines capabilities such as properties, activities, and HTML forms that are available to other, subordinate classes, or to instances of the class. Classes are organized into a hierarchy, where the system searches the class hierarchy from the current class upwards when looking for a rule to apply.
52
case type dependency
A case-type dependency is a condition that must be met before a child case is instantiated or an assignment is automatically completed. Each condition defines a case and a status.
53
instruction
An instruction initiates an action for a row on an activity form. The instruction keywords are Call, Collect, Branch, Queue, Rule, and Java.
54
Process Modeler
Process Modeler is a tool that supports the development of business processes in your application. You use it on the Flow form to add, connect, and configure shapes in a flow.
55
data model
A data model is a collection of entities and attributes that describes the objects modeled in an application, and their relationship to each other.
56
page
Pages are data structures that hold name-value pairs. Pages are stored in the system memory or in the database. Various types of pages are defined in the system, such as data pages that are created when the data is referenced, named and unnamed pages, parameter pages, clipboard pages, and so on.
57
Page List
A property mode that allows an embedded ordered array of pages. See also property mode.
58
property
A property defines the format and visual presentation of data in your application. Each property can be associated with a value and has a mode and type. The property mode, such as Single Value or Page List, defines the structure that is used to store the property value. The property type, such as Text or Date, defines the format and allowable characters in the property value.
59
property type
A property type is a description of the data that can be stored by a value-mode property, such as text, encrypted text, integer, date, or true/false.
60
Value List
A Value List property acts as a container for an ordered list of text values. It can contain an unlimited number of values.
61
single value
A property mode that has built-in data types for lower-level elements such as an integer, decimal or true/false.
62
clipboard
A clipboard is a temporary memory area on the server that is associated with every connected Pega Platform requestor, including browser-based users and unauthenticated guest users. The clipboard has a hierarchical structure, consisting of nodes known as pages, most of which have a name and an associated class.
63
Clipboard tool
The Clipboard tool is a debugging and troubleshooting aid for application developers. The tool lets an application developer examine a snapshot of the structure and contents of his own clipboard and sometimes change these from his workstation browser. The clipboard resides on the server.
64
pyWorkPage
The pyWorkPage is the name of the clipboard page that represents the current case being processed. This name is reserved by Pega, and cannot be reused for another property or embedded page.
65
pyWorkPage
The pyWorkPage is the name of the clipboard page that represents the current case being processed. This name is reserved by Pega, and cannot be reused for another property or embedded page.
66
form
A form displays information or collects input from users as they create, update, and resolve cases in your application. Use Case Designer to define the visual presentation of a form.
67
data transform (model)
A data transform (model) is a rule used to set default values for properties on a clipboard page, copy one clipboard page to another, map properties from one page to another, append properties from one Page List property to another, and iterate over pages in a Page List property to map data on each page. These rules define a sequence of steps, and are executed in order, except when a conditional action, such as a when condition or a transition action, is encountered.
68
backward chaining
Backward chaining allows for a computation to advance even when the value of an input or parameter property is not available. This capability is provided by the Rule-Declare-Expressions rule type and the Property-Seek-Value method working together, and can be seen in standard flow actions including VerifyProperty and VerifyPropertyWithListing.
69
forward chaining
Forward chaining allows for the automatic propagation of changes in one property value to changes in other property values or to indexes. This process only operates when the source properties are not marked as invalid. If a property has an associated message, forward chaining halts.
70
declarative network
The declarative network is an internal data structure that defines the relationship between properties whose value is automatically (declaratively) calculated based on changes to other property values. Complex relationships can be configured and visualized by using the declarative network display, which depicts the target property and all potential input that might affect its final value.
71
declarative rule
A declarative rule that relationships between properties so the system can automatically use one or more input values to determine the value of a property. Pega provides six types of declarative records: Constraints, Declare Expressions, Declare OnChange, Declare Trigger, Declare Index and Data Pages (Declare Pages in PRPC 6.3 and earlier versions). Unlike other types of rules, declarative rules are not called explicitly.
72
data transform (model)
A data transform (model) is a rule used to set default values for properties on a clipboard page, copy one clipboard page to another, map properties from one page to another, append properties from one Page List property to another, and iterate over pages in a Page List property to map data on each page. These rules define a sequence of steps, and are executed in order, except when a conditional action, such as a when condition or a transition action, is encounteredA data transform (model) is a rule used to set default values for properties on a clipboard page, copy one clipboard page to another, map properties from one page to another, append properties from one Page List property to another, and iterate over pages in a Page List property to map data on each page. These rules define a sequence of steps, and are executed in order, except when a conditional action, such as a when condition or a transition action, is encountered
73
expression
An expression is a single line of Pega 7 Platform syntax that allows computation of a value using arithmetic operators, logical operators, Java operators, standard functions, and properties. On many forms, you can start the Expression Builder to provide prompting and guidance while entering an expression.
74
Page (property mode)
Pages are data structures that hold name-value pairs. Pages are stored in the system memory or in the database. Various types of pages are defined in the system, such as data pages that are created when the data is referenced, named and unnamed pages, parameter pages, clipboard pages, and so on.
75
Page List property
A Page List property consists of an ordered list of pages, each identified by an integer index (starting with 1). The Page List property is the most commonly used property mode for holding lists of data.
76
edit validate
An edit validate rule defines a Java routine to test the validity of an input value and/or format data; listed in the Data Model rule category.
77
Perform (harness)
A Perfrom (harness) is a standard Pega user interface rule used to display an assignment for processing by an end user.
78
validate
Validate is a way to check property values against one or more expected values, and return an error message if the property value does not match the expected value.
79
validate (rule)
A validate rule is used to restrict user inputs by comparing the entered properties with a set of conditions.
80
data type
Data types define and hold data for your application. For example, a Customer data type might be used to manage customer contact information. It might include the customer's name, email, phone number, and so on. Data types are managed using the Data Explorer.
81
Data Designer
The Data Designer lets you review and manage data types in your application. When you select a data type in the Data Explorer, the data type opens in the Data Designer.
82
data source
A data source is any source of data that an application uses, such as a connector, report definition, or lookup. Data sources are referenced in data pages.
83
external data source
An external data source is a data source of type connector, a lookup with an externally mapped Applies to class, or a report definition with an externally mapped Applies to class.
84
local data storage
Local data storage is a feature that lets you store data records for a data type without having to manually create or maintain database tables. In the Data Designer, you can access local data storage on the Sources tab for the data type. Use the Local Data Storage wizard to create a local data source.
85
data record
A data record is an instance of a data type stored for your application. For example, Customer records would include data specific to each customer, such as name, email, phone number, and so on. You can manually create data records or import a set of existing data records in Data Designer. Use the Data Type Explorer to view the list of supported data types in your application.
86
connector (rule)
A connector rule is a type of integration rule that allows an application, acting as a client, to interact with an external system or database.
87
data mapping
A data mapping is a table or array that associates data fields received from or sent to an external application with properties or other sources or destinations in Pega Platform. Data mapping is defined in service and connector rule forms.
88
data page (declare page)
A data page is used to cache data on demand to a clipboard page for use by one or more applications. A data page rule defines the source, scope, refresh strategy, editability, and structure of the cached data. Data pages were previously known as declarative pages.
89
report definition
A rule type used to query for and return case or process data. It generates a SQL query and displays the query results in a wide variety of formats. Report definitions can be used to define sets of data used by other Pega components, such as data transforms, data pages, and UI layouts.
90
database table
A database table is a set of related data in a database, organized into rows and columns. Each column contains a different attribute, such as a property value, and each row corresponds to a single record, such as a case.
91
flow
A flow models a business process in your application by using graphical shapes and connectors to define a sequence of events. You can edit a flow in Case Designer or Process Modeler.
92
flow action
A flow action displays a task or a choice, such as Approve or Reject, to users when they run flows. The two types of flow actions are connector flow actions and local flow actions. You can edit flow actions in the Process Modeler or Case Designer.
93
data reference
A data reference is a type of field that you configure on a form. At run time, it displays a list of data-type instances, or data records.
94
user interface (UI)
A user interface (UI )is the portion of an application responsible for the presentation of information and functionality to an end user, to facilitate the effective control of the application by the end user.
95
skin
A skin defines the responsive behavior and formatting, such as colors, fonts, images, and layout, of portals, cases, rule forms, and reports. A skin generates the styling (Cascading Style Sheet) for the application.
96
responsive behavior
Responsive behaviors enable a layout to adjust according to screen size, providing an optimal user experience on a desktop, tablet, and phone.
97
section (rule)
A rule that defines the content and behavior of a user interface, including property references, controls, and layout types, referred to by flow action rules and harness rules.
98
section
A section is an area of a standard user form that is incorporated on a harness form. The appearance, behavior, and contents of a section are defined by a section rule (Rule-HTML-Section rule type). Sections can contain other sections.
99
Dynamic Layout
A dynamic layout is a DIV-based layout that allows for the flexible display of content. Dynamic layouts separate content and presentation. You add content, such as properties, controls, dynamic containers, and other sections, to a dynamic layout within a section. You set the presentation of that content by using dynamic layout formats specified in the skin.
100
application
An application is a business solution that automates work flows in your organization. Multiple, unrelated applications can be hosted in the same system. You create an application by running the New Application wizard.
101
grid controls
Grid controls allow you to display the relationships between large quantities of data and provide a convenient interface for editing or adding to that data. Grid controls appear in Harness and Section forms. For large or complex data displays, use the Grid, Tree, and Tree Grid controls.
102
correspondence
Correspondence is an outgoing email, letter, fax, or text message that is produced by the system and its users. Correspondence is typically associated with one work item, or a cover or folder, and can include text and images. Correspondence that is sent to the originator of a work item is known as an acknowledgment.
103
property reference
A property reference is a notation for a run-time reference to the name or value of a property that you can use in activities, data transforms, HTML, and other places. This notation is also called dot notation.
104
Report Browser
The Report Browser is a tool that provides access to all of the reports that are available to you. From the Report Browser you can complete many tasks, such as browsing and searching for existing reports, running and scheduling reports, creating and modifying reports, and sharing reports with colleagues. The Report Browser is available in the Case Manager portal.
105
unoptimized property
An unoptimized property is an aggregate property, a property within an embedded page, or a Single Value property that is stored in a specially formatted Storage Stream or BLOB column.
106
optimized property
optimized property
An optimized property is a Single Value property that is stored as a column in a database table, in addition to the Storage Stream BLOB, to enhance record selection operations in reporting. Optimized properties are also referred to as exposed properties.
107
Chart Editor
The Chart Editor is a tool that you use to create and edit charts for summarized reports. You can use the Chart Editor to select a chart type and subtype, define the appearance and formatting of titles and information, and specify the report data that populates the chart. You can access the Chart Editor from the Charts tab of a Report Definition rule form or from the Report Editor.
108
interactive chart
An interactive chart provides options, such as a slider control, for increasing and decreasing the level of detail that is displayed. Summary view reports can include interactive charts.
109
branch
A branch is a container for rulesets with rules that are undergoing rapid change and development.
110
unit test
A unit test is a form of testing performed on an individual rule during testing. Unit testing verifies that the rule works as intended, without involving other rules in the testing.
111
Build for Change
Build for Change is Pegasystems' corporate slogan and application development philosophy, that acknowledges the continuous evolution of business processes through methodologies and tools that embrace flexible procedures.
112
delegated rule
A delegated rule is visible to a specific user or group of users with a specific access group. Rule delegation facilitates rule management outside of the development environment. A delegated rule can be a favorite that is accessible from Designer Studio or the Manager and Case Manager portals, or it can be a paragraph, decision table, or data type accessible from the Case Manager portal.
113
Required Field
A required field is an input field on a form that must have a non-blank value to be valid. Many flow action forms mark a required field with an orange asterisk. (This image is only a label to notify users that the field is required, and does not affect input editing or processing.)
114
when (rule)
A when rule is a decision rule that defines a true-false test based on comparing one or more property values with constant values or with other property values. For example, a when rule can test whether an amount is greater than zero or a date is in the future. Also known as when condition rule.
115
action section
The action section is the area in a harness in which the action is performed. It shows users the actions that they can perform. event, action,condition.
116
UI Gallery
The UI Gallery is a collection of examples of effective and dynamic forms and layouts that use many of Pega's design capabilities, represent best practice implementations and comply with Pegasystems guardrails. These examples can be copied into an application and extended as needed.
117
How do you configure an action set on a button to clear user selections and then review the previous actions on the case?
First, configure a click event with a refresh action. Next, add a view history action to the event
118
You are configuring a confirm and pay view that includes a payment type selection list. One of the payment options is paypal. paypal requires users to confirm order details on the paypal website. How do you configure the link to paypal to display only when users select paypal as their payment method?
Configure a visible when condition expression for the paypal link control
119
Which of the following two sets represent action sets (event>action) in pega platform?
Tab key> add new work
| Double click > scan barcode
120
Adding instruction to a step
describes to an end user what should be done in a step
121
when modeling the life cycle of a case, stages represent a blank or a blank
transfer of authority or significant change in the status of a case
122
a collect information step in the case life cycle sets the case status to pending approval. when does the case status automatically update?
at the beginning of the step
123
when modeling the life cycle of a case, alternate stages blank and blank
represent exceptions to the normal course of events and can be sequenced into primary stages
124
what type of step typically requires contextual instruction
collect information
125
Pega System of record
a small company uses a pega application for job applications the available positions data type includes fields for position title, description, and qualifications.
126
External System of Record
An auto repair shop uses pega application to schedule appointments. the vehicle data type includes fields for make,model, and year. the application must be able to accommodate any vehicle
127
No system of record
a standardized test enrollment application contains a special accommodation daya type. special accommodations include needing readers, large print exams, ect
128
A parallel process is defined as
a process that executes over the same time period as other processes
129
automating decisions based on business logic enables
application users to focus on more nuanced decisions that require business expertise
130
conditional paths in a case life cycle are used to define
paths in the case life cycle that are chosen by a user at runt ume or are based on run time values
131
connector
The term connector is used in the following two ways: on a flow diagram, a connector is a line that connects two shapes. Typically, connectors leaving an assignment shape represent flow actions. Other connectors might link to a When condition rule. A connector is also a programmatic component that defines and implements an interface between a Pega Platform application that is acting as a client, and an external system that is acting as a server. A connector is implemented by any of the rule types in the Integration Connectors category.
132
Data page scope
thread requester and node thread: data page is related to a particular case. node: makes a single data page accessible by all users of the application and on other applications. requestor: unique to the users experience
133
You need to fetch exchange rates that are updated on a daily basis from a web service and make them available in your application using a data page. which scope would you select for the data page
node
134
you have a data page with customer data. the data page is configured to relaod if it is older than one hour. which of the following best describes when the data page will reload?
the data page reloads on the next access one hour after it was created
135
which of the following steps provide easy configuration and maintainability of a savable data page for an existing data type?
set the data save options class, set the data page definition edit mode to savable, set the data save options save type to database save
