CSA Flashcards
DCO (Direct Capture of Objectives)
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.
guardrail
Guardrails are guidelines that help developers achieve project success, optimal performance, reuse, and maintainability for applications.
compliance score
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.
case management
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.
Pega Cloud
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.
base class
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
Related Rules
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.
ruleset
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.
situational layer cake
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.
access group
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.
case manager
A case manager is an application user who can view and update delegated business rules, in addition to performing work.
Case Manager portal
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.
case worker (operator)
A case worker is an individual responsible for creating, processing, and/or resolving a case.
Case Worker portal
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.
Cases Type Explorer
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.
operator menu
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.
Pega Certified Business Architect (PCBA)
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.
Pega Certified System Architect
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.
Lead System Architect (LSA)
A Lead System Architect (LSA) is an application developer who provides technical leadership in design and project management tasks to an application development project.
Senior System Architect (SSA)
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.
System Administrator
A system administrator is responsible for system installation and setup, security and access, and other operational functions.
case (work item)
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.
case type
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.
Stage
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.
process
A process is the path, or paths, a case follows as it is completed (resolved.)
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.
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.
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.
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.
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.
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.
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.
Instruction
An instruction initiates an action for a row on an activity form. The instruction keywords are Call, Collect, Branch, Queue, Rule, and Java.
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.
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.
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.
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.
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.
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.
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.
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.
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.
decision (shape)
A decision shape within a flow diagram that calls a decision rule such as a decision tree, decision table or map value.
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.
operator ID
Defines an operator’s username, password, access group organizational setting, calendar and other values.
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.
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.
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.
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.
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.
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.
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.
instruction
An instruction initiates an action for a row on an activity form. The instruction keywords are Call, Collect, Branch, Queue, Rule, and Java.
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.