Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Pega
Pega Foundations CSA Certification
| Term | Definition |
|---|---|
| Business Process Management | The discipline of managing processes rather than tasks to improve business performance, outcomes and operational agility. |
| Case Management | Asychronously manage a collection of tasks, action, processes even ad-hoc content to support a specific business objective |
| Case | Projects, transactions, services or responses Opened and closed to resolve a problem, claim, request or complex activity. Cases involve multiple persons inside, outside of the organization. Cases involve multiple processes that include documents |
| Operator ID | a user account |
| Access Group | collection users associated with applications/ portals/roles |
| Application | collection of riles and data developed to support business functions |
| Portal | workspace to support interaction with the system, designed to meet the needs of a specific user group |
| Role | concise description of a party and their part in a process |
| Standard portals | Case Manager, Designer Studio |
| Business Objectives | |
| What is DCO? | Directly Capture Objectives - enables a project team to directly enter business requirements for an application into Pega. |
| What are two possible consequences of not following best practices and guardrails when designing and building an application on the Pega 7 platform? | you are more likely to spend more time re-creating existing functionality, or spend more time debugging a component that is not well designed. There is also the risk that you will implement a feature that does not work correctly |
| case | work that delivers a business outcome |
| What is the outcome of a case | meaningful deliverable provided to a customer, partner, or internal stakeholder |
| Case life cycle design | modeling technique Pega uses to describe, in business terms, how a business application should work |
| Cases are organized into high-level milestones, known as | stages |
| Stages are further organized into ? which define one or more paths the case must follow. These contain a series of actions, or steps that must be completed to resolve the case. | processes |
| In a case life cycle, stages that lead to the expected outcome are called ? stages. The sequence of these stages is often referred to as the ?. | primary , happy path |
| A process contains a series of ?. This can be an action that a user performs, an automatic action performed by the application, or other processes that contain a separate set of actions. | tasks, or steps |
| naming processes and steps, use a ? naming convention | “verb + noun” |
| You configure routing for an assignment for the ? | step |
| The goal milestone in a service level defines: | The amount of time in which the case or step should be completed |
| The primary purpose of a service level is to __________. | Help ensure timely completion of assignments |
| View Configuration tool contains an array of rows — one for each UI field. Each row has three fields. The fields define ? | the data element, format, and enable edit setting (required or optional). |
| UI Design should be ? | intent-driven, model-driven and simple |
| What three questions can you ask to help you plan user views? | How will users enter values in those fields? Can users modify the values or only read the values? What fields do users need to see? |
| Requirements management | is the process of collecting, analyzing, refining, and prioritizing product requirements, and then planning for their delivery |
| Goals of Requirements management | -ensure the business application you build validates and meets the needs of all customers and stakeholders. (continuous process throughout a project) -helps keep the project team organized and provides visibility into every aspect of the project |
| Business objectives | statements that describe the business value the application must provide, or the business needs the application must address |
| ? review the current state of a business process to identify inefficiencies. | Business architects |
| ? create business objectives to fix the inefficiencies. | Business architects |
| Define requirement | agreement between stakeholders on what a business application will do. requirement uses business language to describe what the application must do to meet your business needs. Requirements can also provide benchmarks to test your application against |
| inventory of events, conditions, or functions that must be implemented and tracked in a development project | requirement |
| 5 requirement types | -Business rule - usually associated with a specific use case or step in a process -Change Control -Enterprise Standard -Functional - a function, such as calculations or data manipulation -Non-functional - performance metrics |
| What do specifications do? | Specifications define how you implement your application. Use business language to describe the steps needed to meet a requirement |
| When are business objectives identified | Inception of project |
| benefits of using a model-driven application design and development approach. | use visual, form-based definitions of an application component at a level higher, less technical, and closer to business semantics than programming code. |
| What does Unified mean in relation to Pega | functionality needed for business applications is configured using a consistent set of artifacts that are defined and stored together in a single database repository |
| Case participants | business users of the application. -process and close cases -usually organized by roles |
| two types of Case Participants | Case workers - creating, viewing, and working on their own cases and assignments. Case managers- responsible for working on cases and monitoring work group status, goals, and deadlines. responsible for generating work manager reports |
| Case designers | part of the delivery team responsible for designing and building business applications. |
| two types of case designers | Business architects - with case participants and other stakeholders to define business objectives and application requirements. -plan application behavior to address the business objectives and requirements with specifications. |
| Specifications | describe how application manages and automates work. System architects often prototype application features to help refine the specifications. These prototypes help align the application with the business needs. |
| which Design time portal should you use to quickly capture application intent and build out the high-level case structure and process steps. | Pega Express |
| Use ? to refine the case life cycle design. | Designer Studio |
| 2 design time portals and 2 run time portals and what they are used for | Pega Express - Develop Prototype for business users Designer Studio - Add Alternate stages Case Worker Portal - Manage assigned cases Case Manager Portal - manage their assigned cases and view the status of the cases assigned to direct reports. |
| What can you do in Pega Express? | create cases create user views and fields add or remove existing users from your application define settings for theme, mobile apps, and other tools |
| The Designer Studio consists of four components: | 1. Work area 2. Header 3. Explorer area 4. Developer toolbar |
| Designer Studio ? provides tools to create and manage application assets | header |
| Developer toolbar helps users ?, ? & ? | debug applications, tune performance and quickly analyze the composition of UI components |
| Tracer tool ? Clipboard tool ? Live UI tool ? Performance tool ? Alerts tool ? | to debug rule execution. view data in memory. identify user interface elements to analyze application performance. to view system alerts generated by Pega. |
| situational layer cake | allows you to organize your application using the same dimensions as your business |
| Best practices | well-defined methods or techniques that lead to desired results. |
| Pega Best Practices | Leverage DCO to improve product quality Use standard Pega capabilities Iterate and test as you build Communicate project progress at all levels Ensure project team members are certified Follow Pega guardrails |
| A business view of work | Business applications should function in the same way business users naturally think about and describe their work. |
| work that delivers a business outcome | case |
| Cases are organized into high-level milestones, known as ? | stages |
| Stages are further organized into ? | processes |
| case type | is an artifact in Pega used to define the tasks and decisions needed to resolve a case. |
| primary stages. | stages that lead to the expected outcome |
| Consider limiting the number of steps in each process to ? | five, plus or minus two |
| You configure routing as part of the ? configuration. | step |
| Record the values end-users enters in a ? during form design. | specification |
| Before you create a form, ask the following questions: | What fields do end-users need to see? l How will end-users enter values in those fields? l Can end-users modify the field values or only read the values |
| Requirements management | is the process of collecting, analyzing, refining, and prioritizing product requirements, and then planning for their delivery |
| What phase do you do requirements management | continuous process throughout a project |
| ? define how you implement your application | Specifications |
| are the center of traceability | specifications |
| ? allows you to link specifications to requirements, business objectives, and the artifacts that implement the specification | Application Profile |
| ? provide a way to model out-of-sequence events in the life cycle of a case. | Alternate stages |
| ? allow you to further refine the run-time order of stages. | Stage transitions |
| To allow transitions to other stages before the completion of the current stage, you can add a ? to a stage | controlled transition |
| You can configure a step to allow a user to select the stage to which the case transitions | |
| ? process step to automatically transition the case flow to a specified stage. | Change Stage. This type of configuration is most useful for automating transitions to and from alternate stages. |
| Controlled transitions can be added as a process step using the ? smart shape, or ? | Change Stage; as an optional user action in a process step |
| As a user works on a case, situations arise that may require the user to stray from the primary path to perform a task. These tasks are called ? | user actions |
| ? supplement the tasks users can do as they work on a case. | User actions |
| User actions allow users to ? | leave the primary path of a case to complete another process. |
| What determines execution of user action? | User |
| Where are User Actions available | User actions can be made available for a stage or an entire case |
| two types of user actions: . | optional processes and local actions |
| optional process | when multiple steps are needed to update information. |
| After completion of the optional process, return to a user ? return to the primary path. | may or may not |
| local action | when the case information can be updated in a single screen. |
| What happens after completion of the local action, | the user returns to the primary path of the case. |
| Answer three simple questions to achieve effective communication: | Who should receive the communication? How do I communicate with them? When do I send the communication? |
| Pega provides four correspondence types to communicate with users: | email, text message, fax and regular mail. |
| Adding ? & ? keeps the user informed about a case. | work statuses and instructions |
| ? is the primary indicator of the progress of a case towards resolution. | work status |
| ? create instructions based on the ? defined by the business | System architects ; requirements |
Created by:
bvennen
Popular Engineering sets