PEGA SSA

PAL (location)

(Dev Studio > System > Performance)

how the Application packaging wizard displays steps

1. Application 2. Application stack 3. Application dependencies 4. Organizational elements 5. Access groups. 6. Operators 7. Work queues 8. Work groups 9. Data tables 10. Code archives 11. Database storage 12. integration resources

Steps to configure connector simulations

1. Navigate to the connector you want to simulate. 2. Specify the simulation activity. 3. Select the scope: Global or User session. 4. Apply the changes to activate the simulation.

<APPEND>

Adds an element to the end of a value list or page list property

Branches in teams applications

After you create the team application, you define branches in the application and add them to the application record for the team application. Specify a unique name for the branch that identifies the feature being configured. Pega limits the name of each branch to 16 characters. Branch names are visible across all the applications on a system. When creating a branch, use a name that identifies the appropriate application, such as Expense[Feature]. This avoids confusion when development teams attempt to add branches to their applications. Ensure that if you have multiple branches order is the same as resolution

Pega Platform gathers the following data for PDC

Alerts Parameter page Database alerts Exceptions Performance statistics Database indexes Guardrail violation counts

Authenticate API

Allows you to verify user credentials

to change the logo image in a user portal

App Studio, from the Explorer panel, select Settings > Theme to open the application theme. Under Logo, click Upload logo to open the File Explorer. Select your image file and click Open. The image to the left of the Upload logo button updates with the image you selected. In the header, click Save to complete your configuration.

Access control for work queues

By default, any user who can access a work queue can perform an assignment in the work queue. To control whether users can perform assignments in a specific work queue, you apply one or more roles to it. When you apply a role to a work queue, only users assigned to a listed role may retrieve an assignment from the work queue.

Grant access to the team application

Create an access group that references the team application. To name the access group, include the application name plus the standard user type, such as HRAppsPOAdmn. When you create the access group: Verify that the access roles are sufficient to develop and test the application. Reference the work pool for the main application. Specify the correct portal, such as the Developer portal for application developers. Probably want to start by copying access groups from original app

Pega skimming wizard

For each rule instance in a specified ruleset, the wizard identifies the highest-numbered version and creates a copy with the number you specify.

Pega Mobile application package file

Lets you use third party development tool to contain Pega app on appropriate platform

Join conditions (parallel processing)

On Split For Each and Split Join shapes property forms, you specify a join condition. The join condition setting controls when the main flow resumes. 1. Select Any if you want the main flow to resume after any one of the subprocesses completes. At that time, processing of the other subprocesses that have not completed is stopped. Open assignments for these subprocesses are cancelled. 2. Select All if you want the main flow to resume after all of the subprocesses complete. 3. Select Some if you want to use a when rule or a count to determine when the main process can resume. The Split for Each shape also contains an Iterate join condition. This starts flows for items on the Page Group or Page List property one by one, testing an optional when condition to determine whether to start the flow for a given iteration. A Spinoff does not have a join condition because the subprocess never rejoins the main process.

Accessing ruleset list

Operator > Profile. (has multiple answers)

Connectors supported

Pega provides connectors for a wide range of industry-standard protocols and standards. Standard connectors include SOAP, REST, SAP, EJB, JMS, MQ, File, and CMIS.

Service Activity

Provides the processing for a service rule

<LAST>

Sets or retrieves an element value from the end of a value list or page list property

Embedded classes (parallel processing)

Split joins allow you to call a flow on a embedded page such as a data class

Unit test a decision table or decision tree

Testing a decision table or decision tree on its own before testing it in the context of the entire application has a specific name and is what this feature is. Since decisions are evaluated automatically, they can have a significant impact on case processing. Ensuring that the decision logic is correct helps avoid troubleshooting the process if you get unexpected results. Several different ways you can employ this for testing decision rules by testing the logic, checking for conflicts in the logic, and checking for completeness.

Temporary cases

These are only stored in memory on the clipboard and not in the Pega Platform™ database. They do not have case IDs. They are processed by single operator and can't be routed

Log files

This is where Pega writes errors, warnings, and other debug information. This is where Pega tracks excpetions. Each is managed by an appender.

Split for each (parallel processing)

This shape allows you to run one subprocess multiple times by iterating through a set of records stored in a page list or page group. When the items on the list have been processed, the main flow continues.

Select Include all rows in <prefix> (class join setting)

To include all qualifying instances of the joined (prefix) class, even if there is no match found in the Applies To class (referred to in database terms as an outer join)

Access control for attachments

You apply a privilege or when condition to an attachment category to allow or deny attachment actions to users. You enable attachment level security to restrict access to the attachment itself.

Creating a SOAP service using the Service Wizard

You run the Service Wizard to create all the records needed to expose your application as a service. The Service Wizard walks you through entering the settings required to create the service. The Service Wizard does not create XML mappings for inherited properties, so you must add those properties as needed.

Customizing a user portal

can be achieved via portal rules checking who is using the portal, aka users or devs, changing the layout via harness rules, changing the branding using skins, can copy records into the application ruleset. Use Live UI to help find them.

Availability = Final

can be used during rule resolution (but not edited or copied into another ruleset)

Availability = Available

can be used during rule resolution (multiple anwsers)

Authorized managers (work groups)

can transfer assignments

Rollback method (cancel/rollback operations)

cancels or withdraws any previous uncommitted changes to the PegaRULES database (and to external databases accessed from an external class) from the current thread.

The ruleset list (location)

(Dev Studio > Configure > Application > Structure > RuleSet Stack).

Performance profiler (location)

(Dev Studio > System > Performance > Performance Profiler)

Rules Cache flows as follows

1. Choose rules with correct purpose 2. Discard rules that not available 3. Filter rulesets and versions user has access to 4. Discard rules not in inheritance path (To be considered in this step, a rule type must have the Use class-based inheritance to arrive at the correct rule to execute? check box selected in the class definition.) 5. Rank remaining rules. (has multiple aspects ranking differently based on Class, Ruleset, Circumstance, Circumstance Date, Date/Time Range, then Version. and removing withdrawn rules) 6. Set rules cache

Multivariate circumstancing flows in which steps

1. Circumstance template 2. circumstance definition 3. circumstance record

Join filters (subreports)

1. Create a subreport for purchase requests that retrieves the most recent update date by update operator. On the main report in the Query tab, add columns for the requested data for each case and specify the subreport you want to reference. 2. On the main report's Data Access tab, add the subreport. 3. Create a join filter condition for the subreport. The filter defines how you want to join the subreport data to the main report. 5. On the Query tab, add a filter condition so that the update date value is equal to the update date value in the subreport.

Aggregation (subreports)

1. Create a subreports that shows the managers who have direct reports, and how many they have. You use filter conditions to limit the data to managers who are part of the Engineering division and report directly to someone. 2. On the main report's Data Access tab, add the subreports. 3. Create a join filter condition to join data from the subreports to the main report where the value in the subreports operator column matches the value in the operator column in the main report. 4. Create a filter condition to use only data from the subreport where the number of reports-to instances is greater than ten.

To develop rules in parallel using branched rulesets, each team follows these steps:

1. Creates a team application built on the main application 2. Creates one or more development branches in the team application 3. Grants access to the team application 4. Creates or configures rules using the branch 5. Merges each branch into the application rulesets when development in branches is complete and stable

Rule resolution (how process works)

1. Find rules in rules cache a. find the best match ( if dupe then Pega sends message stops populating b. populate the rules cache 2. rule blocked? a. error if it is (message added to log file) b. no 3. User has access? a. error if they don't (message sent not authorized) b. run rule if they do

Running the Service Wizard

1. In Dev Studio, select Configure > Integration > Services > Service Wizard to start the Service Wizard. 2. Complete the Select Service Purpose section: a. Set the Service Purpose to Create and manage work. b. Set the Service Type to SOAP. c. Click Next. Quick Note create and manage work is the most common reason to create a service. You invoke an existing service activity if you have created the activity previously. The Process input or output data provides an empty activity that you configure to get or process the desired data. The options in the Wizard differ based on the Service Purpose selected. 3. Complete the Provide Service Details — Select Work Properties section: a. Set Work Type to TGB-HRApps-Work-Onboarding. b. Set Flow Type to pyStartCase. c. Select Create Work and set the Organization to TGB. d. Click Next. 4. Click Next. Note The pyStartCase flow does not have any flow actions that you want to consider a service to execute. 5. Select Use XML for data mapping to allow for list structures in the request. Note Only properties defined directly in the TGB-HRApps-Work-Candidate case type are displayed. Inherited properties are not displayed and need to be added manually after the Wizard has been completed. 6. Select the following input properties: (Some examples given) 7. Click Next to confirm the proprieties to use. 8. Set the Ruleset Name to HRApps, and set the Ruleset Version to the version in which you are working. 9. From the Service Package Options drop-down list, select Configure a new service package, then click Next. 10. Keep the default settings in the Configuration Data Records screen. Click Next. Note Requires authentication is selected by default. This means that you need to provide an operator and password when you call your service. 11. The Review and Save screen displays the records that will be created by the Wizard. Click Finish to create the records. The final page displays the records created by the Wizard.

Configuring a decision table (steps in order)

1. Open the Application Explorer. 2. Select the class in which you want to create the decision table. 3. Right-click and select Create > Decision > Decision Table. The New Record form opens. 4. In the Label field, enter a name that describes the purpose of the table. 5. Click Create and open. The decision table rule form opens. 6. On the table under Conditions, click the empty header cell. The Decision Table property chooser dialog opens. 7. In the Property field, enter or select a property. You can alternately click the gear icon to build an expression. 8. In the Label field, enter the name of the property that you entered in the column header. 9. In the Use Operator drop-down, select a comparison operator. 10. Click Save. The Decision Table property chooser dialog closes, returning you to the decision table rule form. 11. If you want to add another condition property, add a column to the right of the first column by selecting the add column icon on the control header. 12. Add a second property to the new column. 13. In the if row, click the empty cell under the first property and enter a value. 14. In the Return column, enter a return result. The following image shows the first condition set. 15. If you want to add conditions, select the add row icon on the control. 16. Enter values in the first and second columns and a return value. In this example, values for Credit Score and Outstanding Balance are entered. 17. Enter another row and return action. Repeat this process until you add all the rows required to create the decision table. 18. Add a return value to the otherwise row. 19. click save

Adding inherited properties (SOAP Wizard)

1. Open the CreateNewWorkResponse XML parse rule generated by the Wizard. 2. Click Add Element to add the required input parameter that was not available for selection in the Wizard. 3. Double-click the new property to configure it. 4. Enter a Node Name and specify the Property to map the value. 5. Click OK to update your changes.

Inputs to the rule resolution algorithm include:

1. Predefined rule keys that are used as a unique identifier, such as the Apply to: class, rule name, and rule type 2. User's ruleset list 3. Class hierarchy of the rule in question 4. Circumstances such as the value of a property, or time and date restrictions 5. Availability of the rule 6. User's access roles and privileges

Services, the order of steps

1. Receive Request Message The service listener instantiates the protocol-specific service to provide communication with Pega and establish a requestor. The service listener optionally performs authentication. 2. Instantiate Services The service parses the incoming request and maps the request onto the clipboard. The service then invokes the service activity. The service activity provides the logic for the service. a. Map Inbound Data b. Invoke Service Activity c. Map Outbound Data 3. Send Response Message When your service activity is complete, control is returned to the service. The service builds the response using data on the clipboard, and the service listener sends the response to the external system.

Configuring background processing

1. Specify an Activity to perform 2. Identify the class of the object do you want your Queue Processor or Job Scheduler to resolve it 3. Identify the nodes in the cluster BackgroundProcessing nodes (note can configure to run on another type of node) Universal nodes support queue processor and job schedulers (common to take care of tasks that were placed on any node) 4. Add access groups to AsyncProcessor is a requestor type to identify active queue processors and job schedulers. Connected to operators access group to provide context to resolve rules. You must add an access group with access to your application to the AsyncProcessor requestor type so that Pega Platform can initialize the queue processor or job scheduler.

Data access patterns

1. The system of record pattern provides access to data stored in another system or application. The application always references the system of record, so the data is always current. 2.. The snapshot pattern copies data into the case. The application always references the copied data, so the data is only current as of the time the application copied the data. 3. The reference pattern allows an application to use data without adding that data to the data model for the application. The reference data pattern is used often to populate UI controls, such as drop-down lists. The value selected by the user is copied to the case.

Data Page/ Activity (connectors)

1. Use Data Transform to Set Request Data The data page or activity executes a data transform to map the data from your application to the integration clipboard pages. 2. Invoke Connector The data page or activity invokes the connector a. Initialize Connector The connector is initialized based on its type. The type is the protocol the connector supports. b. Map Outbound Data The connector maps the request data to the protocol-specific format using the mapping rules specified for the connector. Do not confuse this mapping with data transforms. This mapping is between the clipboard and the format required by the protocol. c. Invoke Service The application sends the request to the external system. d. Map Inbound Data The application receives the protocol-specific response. The response data is parsed using the mapping rules specified in the connector rule and placed on the integration clipboard pages. e. Finalize Connector The connector is finalized and returns control to the data page or activity. 3. Use Data Transform to Map Response Data Finally, a data transform maps the response data from the integration clipboard data structure to your application.

Exchanging data through a Pega Web Mashup

1. Use the data-pega-event-onpagedata attribute to specify the default value for the gadget. 2. Use the Javascript function doAction() to set or read data values from the web page hosting the gadget, such as by clicking a button. Call the doAction() function using the syntax: pega.web.api.doAction([gadgetname],[action],[parameters]). 3. Use an action object to perform additional actions on a web mashup gadget or configure the gadget to interact with another gadget. Configure the action object as a script within the gadget DIV tag and specify the attributes and parameters as required to perform the action.

Localizing an application steps

1. define field values 2. define paragraphs 3. define correspondence rules 4. Install language pack a. If a language pack is not available for one of your target languages, you can use the Localization wizard to export the Pega rulesets and translate them along with the content on your UI forms. You are creating your own custom translation pack. b. While most records in Pega Platform are set by default to be translatable, records from previous versions of Pega may not have the Localize option preselected. You manually set those records to Localize before running the Localization wizard. 5. verify language pack a. Set the Locale setting to a target language (for example, Spanish) and run your application to verify that all of the labels, notes, instructions, messages, and emails are successfully localized. If any are missing, check the appropriate translation pack, add the missing translations, rerun the Localization wizard, and verify again. Also verify that the Italian terms are displayed correctly when an Italian locale is selected. The locale setting is available on the last screen of the Localization wizard. In Dev Studio, under the Configure > User Interface >Application readiness > Localization menu. 6. run localization wizard 7. verify translation

Import gadget steps

1. go to Configuration > Application > Distribution > Import. 2. select the archive to upload. Local or upload no more then 1 GB If you choose to import a file from a repository, you must specify the Repository name, Artifact type, and artifact Name. 3. Optionally click show content details 4. Optionally click enable advance mode to provide more granular control over the import process 5. Optional select the do not set restore points or svave metadata during the import 6. click next 7. click next If you import rules in a ruleset that users can already access, the rules may begin executing immediately. These rules may execute before all the rules in the same archive have been imported. Similarly, declarative rules begin executing immediately. This means that the declarative processes might fail if the elements or properties they reference have not yet been uploaded. This needs to be planned for when an archive is imported on a system with active users.

Steps to circumstance a rule

1. in Dev Studio open the base rule 2. on the base rule, in the header tab, select Save as > Specialize by circumstance. The New Record form opens with two circumstancing options: Template and Property and Date. 3. On the New Record form, identify the type of circumstance. To circumstance on one variable, select Property and Date. To circumstance on more than one variable, select Template. 4. Configure and save the circumstance conditions.

Configuring keyed data pages

1.Define the data page Structure as a List. 2. Select Access pages with user defined keys. 3. If you want the data page to return more than one instance, select Allow multiple pages per key to filter a large list to create a smaller list. 4. Specify the Page list keys used to access the list entry or list entries. 5. Once the keyed data page is configured, reference the keyed data page in the page property using the selected keys.

Testing the service (SOAP Wizard)

1.Open the service rule. TIP: You can access the service rule from the final screen of the Service Wizard. If you have closed this screen, you can open the Records Explorer and navigate to Integration-Services > Service SOAP to access it. 2. Click Actions > Run to test the service rule. 3. Select Supply SOAP request envelope to enter values for the test. 4. Update the request and enter values for each option. In the following screenshot, you see values have been entered for Employee, SSN, and FirstName. 5. Click Execute to test the service. 6. Your response will vary based on what you are attempting to do. If there is an error, you see a SOAPFault exception produced.

Symbolic Indexes (database updates)

<APPEND> Adds an element to the end of a value list or page list property <PREPEND> Inserts a new element into a value list or page list property as the first element. All existing elements are "pushed down" by one. <INSERT> Inserts a new element into a value list or page list property at a numeric index position. Any elements with the same or higher index value are "pushed down" by one. <LAST> Sets or retrieves an element value from the end of a value list or page list property <Current> Use differs depending on where it is used.

Organization records

A Pega application uses an organizational structure to direct assignments to the right operator or work queues, determine the access rights of operators, and report on activity in various company departments. The Pega organizational structure is a three-level hierarchy. The top level is known as the organization, the middle level contains divisions, and the lowest level contains organization units. Note divisions can't have subdivisions

Default rule (rules cache)

A default rule candidate is the first rule candidate (highest ranked) that has no qualifiers. This default rule candidate is the last possible rule to be executed as it always matches any additional requests for this rule. Additional rule candidates ranked below the default rule candidate are discarded.

Deferred save

A deferred save adds a deferred operation to an internal list of operations to be performed on the next commit. The internal list is also known as a deferred operations list or deferred list.

Service Error (exception processing)

A valid instance of the service activity cannot be found.

whitelist and blacklist

A whitelist is a set of rules requiring synchronization between a mobile app and the server. A blacklist is a set of rules that are not synchronized between a mobile app and a Pega application. You update the whitelists and blacklists for an application on the Offline rules tab of the Mobile: Offline Configuration page. To access the Mobile: Offline Configuration page, in Dev Studio, from the Configure menu, select Mobile > Offline. Pega provides a set of five customizable whitelists for your applications. Each whitelist manages instances of a specific rule type: data page rules, field value rules, data transform rules, validate rules, and when rules.

Application Security

Access control is key to limit who can look at what

ABAC rules

Access control policies (Rule-Access-Policy Access control policy conditions (Rule-Access-PolicyCondition)

Calling other activities

Activities can call other activities. Two methods Call and Branch

Persisting temporary cases

Add a Persist Case automation step to the case life cycle. When Pega encounters the Persist Case step, Pega creates a case ID and commits the case data to the database.

Adding relevant records to classes

Add records to the specified class by clicking Add records. In the Add relevant records modal dialog box, select the record type and specify the record name.

Referencing an association rule

After you create a report definition in the class you want to report on, reference an association rule to join another class. 1. Open your report definition. 2. In the Edit columns section, in the Column source and Column name fields, enter the name of the association rule you want to reference. The system uses the prefix for the properties you want to include. 3.Click Save to save your reference to the association rule. When you add a column that uses an association, the system automatically references the association. The Associations field on the Data Access tab displays the association.

Configuring a class join

After you have created a report definition in the class you want to report on, create a class join to establish a relationship to instances of another class. 1. Open your report definition. 2. On the report definition form, open the Data Access tab. 3. In the Class joins section, click Add class join to add a row. 4. In the Prefix field, enter a prefix for the class to join to the report definition. Use this prefix to reference properties in the class. 5. In the Class name field, enter the class to join to the report class. 6. At the end of the row, click Edit conditions. The system displays the Enter filter conditions dialog. 7. In the Column field, select a property within the joined class. 8. In the Value field, enter a property in the report definition's Applies To class. 9. Click Submit to save your filter condition and close the Enter filter conditions dialog. 10. Open the Query tab. 11. In the Edit columns section, enter Column source and Column name values. 12. Click Save to save the join configuration in your report definition Note: Use the class prefix to find properties in the joined class you want to include in the report.

Data Pages (error detection)

All data source errors must be handled as part of the data page load mechanism. The type of data source being leveraged to load the data page affects how errors are detected and handled. Connectors, report definitions, and lookups use the response data transform to detect errors. Activities use a transition condition in the activity step to detect errors. The response data transform is invoked after the connector call is complete. If there is an issue, messages are added. In your response data transform, use a when condition to check for any error messages on the page. If an error has occurred, apply the reusable error handling data transform.

Parameters (activities)

Allow you to make activities more reusable by passing arguments when the activity is called, rather than upfront during development. Found on the tab with its name Use the notation Param.<ParamName> to reference held on a special clipboard page, known as parameter page. Not visible with the clipboard tool

The Java Method

Allows you to add custom Java code to an activity. Use with extreme caution. Violation of Pega best practices.

Application Packaging wizard

Allows you to create a product archive that contains all of the classes, rules and data that make up an application. The result of the wizard can be exported to a ZIP file and then imported or migrated to another Pega system.

Import gadget

Allows you to import contents of an archive on a destination system. Requires the @baseclass.zipMoveImport privilege.

Disability preview

Allows you to see what it would look like if you had issues None Achromatopsia (Absence of color) Deuteranopia (Red Green confusion) Protanopia (Red Green confusion) Tritanopia (Yellow Blue confusion)

Dependent role

An Access Role Name record can be configured with one or more dependent roles to simplify the configuration and management of permissions. The access role inherits the permissions set for each dependent role. If permissions for a class vary between the dependent roles, the access role name inherits the most permissive permission settings. To view the dependent roles applied to an access role, click Manage dependent roles on the Access Role Name record. Pega Platform provides two options to customize an access role based on one or more dependent roles. If you need to customize a small number of classes for an access role, manually add the impacted classes to the Access Role Name record and specify the necessary permissions. If you need to configure changes over many classes, clone the appropriate dependent role to override all the inherited permissions, and update each class as needed.

Availability = Withdrawn

An availability set to this indicates all rules that are in the current version ruleset and previous version ruleset and have the same purpose (or rule type) and Apply to: class are hidden and no longer considered after Availability is checked during the rule resolution process. When a rule marked as this is found during rule resolution, the system looks for an instance of the rule in the parent class or next highest ruleset in the application ruleset stack.

Availability = Blocked

An availability set to this indicates the rule may be used during the rule resolution process. Rules marked as this can be viewed, copied, or edited in Dev Studio, but do not execute. If a rule set to this is selected during rule resolution, execution is halted, and an error message is added to the log file.

Mapping Error (exception processing)

An error occurs while mapping incoming data from the request message to the clipboard.

Class mappings and database tables

Any Pega class that has instances, such as case types, can be mapped to a database table. For example, when users create cases, the system assigns the case an ID and saves the value as an individual row in a database table. When you generate reports, you are retrieving data from rows in database tables. Reports use class mappings to locate the data from one or more database tables. When designing reports, you need to know which table has the data and how the data is mapped. For example, you may need to create a report that contains information about Candidate cases. These records are instances in the case work class. In the same report, you may also want to include workbasket information about each candidate case. Workbasket records are instances in a workbasket class. The information for each type of information is stored in separate tables. When you combine the information in a report, you use class names to identify in which tables the information is stored. Note Pega now uses work queue in place of workbasket, class structure still uses workbasket

SOAP service steps

Application 1. Request A client application sends a request to your application. Service Listener 2. Receive Request Message The service listener listens for incoming requests. This functionality is provided by either the Web Server, Application Server, or Pega Listener. Service 3. Instantiate Service The service listener receives the request and instantiates the Service API to provide communication with Pega. Then, the Service API hands control over to Pega. 4. Look Up Service Package and Rule Pega looks up the service package and related service rule, using the access group specified in the service package. 5. (Optional) Authenticate Pega then establishes the service requestor and optionally performs authentication based on security credentials that are passed in the request. Once authenticated, service processing continues using the authenticated user's access group, not the access group that is contained in the service package. 6. Map Inbound Data The request is mapped, using the instance of an XML Parser rule, onto the clipboard according to the specifications contained in the service rule. 7. Invoke Service Activity Control is passed to the service activity, which provides the logic for the service. 8. Map Outbound Data The service rule maps the clipboard data to form the response data, using the XML Stream rule. Service Listener (again) 9. Process Request The service listener receives the response from the Service API. 10. Send Response Message The service listener sends the response back to the application that made the request. Application (again) 11. Response The client application receives the request.

Standard activities

Apply to the @baseclass, Work-, Assign, and History- classes. Are key to use as opposed to writing custom

XML Stream

Assembles and sends an XML document in an email message, a SOAP message, a file, or other types of messages

Steps to verify archive file is correct

Associate your data records with rulesets; this ensures that all the data records required by your application are included in the archive file. Make sure that all rules are checked in so that the rulesets are complete and current. In most cases, lock the application rulesets included in the package to help ensure that the migrated application and its rulesets are synchronized among the source and destination systems. Merge branched rulesets and remove the branches from the application if you are exporting the application to a production system.

Property reference as the value of a gadget attribute or parameter

Attribute/parameter = [propertyReference] [gadget/gadgetName/propertyReference] To perform an action on a gadget using data from the gadget, create an action object for the gadget. If the property you need to use is in the same gadget as the reference, use the syntax Attribute/parameter = [propertyReference]. For example, when configuring an action object to display a confirmation page that uses operator information as parameter values, set the value of the pageURL attribute using the syntax pageURL: "/statusPage" + "CreateOper=[.pxCreateOpName], where CreateOper is the name of the parameter and pxCreateOpName is the reference to the property in the Pega application. If the property you need to use is in a different mashup gadget, use the syntax [gadget/gadgetName/propertyReference] to identify the gadget containing the property. This is the same syntax that you use in a property reference from the page JavaScript.

Secuirty Error (exception processing)

Authentication fails.

Adding work groups and que

Because of mutual dependencies, a work queue or a work group must already exist before either instance can be created. You cannot create both the work queue and the work group at the same time. For example, when you create a new work group, you must use an existing work queue — this is required value. After you create a new work queue, go back to the work group, and update the work queue. From the Records Explorer, create a work group record. By convention, end the work group name with an at sign (@) and an organization name, such as Benefits@TGB. In the Manager field, enter a work group manager for reporting and routing purposes. In the Default work queue field, select a work queue. The standard router activity ToDefaultwork queue uses this value to locate a work queue, based on the work group associated with the current operator. For example, you can enter the default organization work queue such as default@TGB. After you create a new work queue for the work group, you update this default work queue with the new one. Save the work group record, but leave it open. Next, enter the name of the new work queue in the Default work queue field. To help users and developers easily distinguish work queue and operator identifiers, choose a naming convention specifically for work queues. For example, include WQ as a part of the name as shown in the following example. Then, click the crosshairs icon to open a Create Work queue form.

The Tracer (refining event logs)

Before you begin capturing, refine what you need to capture by indicating the types of events and break conditions to log by using the Settings, Breakpoints, Watch, and Remote Tracer buttons on the Tracer toolbar.

Enabling accessibility features for application users

Before you begin, identify the access group requiring accessibility support. The roles provided in PegaWAI require no additional configuration. To implement the PegaWAI ruleset, you first add and save the ruleset to the list of production rulesets in the Advanced section of the application Definition page. Next, you add and save the ruleset to the Production rulesets list under Run Time Configuration on the Advanced tab of the Access group. Your last step is to select the Enable accessibility add-on check box.

Case locking and child cases

By default, if Allow one user is selected for the parent case, Pega Platform locks the parent case whenever a user opens a child case. To override this behavior and allow a second user to update the parent case while the child case is open, select the Allow other users to access parent case when the child case is opened check box. If Allow many users is selected for the parent case, Pega Platform prohibits case locking configuration on any child case. Note advanced tab if you want to configure locking of a standalone child case

The Tracer

Capture and view events during case processing but very performance heavy. You use this often when you see something unexpected or see that a log shows an error

Assignment reports

Cases requiring user interaction are assigned to a user during processing. Each time a case is assigned, Pega creates an assignment object. When the case is completed and advances to the next assignment, Pega creates another object. If the assignment is routed to an operator, Pega saves the object to the database table named pc_assign_worklist. If the assignment is routed to a workbasket, Pega saves the object in a database table named pc_assign_workbasket. Some commonly used properties that are specific to assignments include the operator who has the assignment (pxAssignedOperatorID) or the name of the flow rule for the assignment (pxFlowName). When creating assignment reports, you often use pxRefObjectKey — this is mapped to pzInsKey. The pxRefObjectKey property allows you to relate the assignment to the case.

Access roles

Categorizes users according to their job function. each identifies one or more. Each represents how a set of users interacts with an application to create and process cases

ABAC control policies characteristics

Class limitations access control policies can be defined only for Assign-, Data-, and Work- classes ABAC Inheritance functionality. ABAC use Pega's inheritance. ACAB policy rules can be inherited form multiple classes. Combined and access only allowed when all policy conditions are met And conditions if multiple access policies apply, access is allowed when all are policy conditions are met. Even if a ABAC grants access RBAC must also if it applies Control enforcement Access control policies are enforced everywhere in Pega. Not just in UI. Such as reporting rules, search, custom SQL

Adding work queue

Complete the New Work queue form and create the record. In the Organization section on the work queue form, select the organization in the Name field, and then complete the Division and Unit fields. In the Work group field, enter the name of a work group that uses this work queue. This field determines which work queues appear in a Team Work Queue list on the Manager portal. Save the record to associate the work queue with the work group.

Individual instances to include (components of a product rule)

Complete this optional array by listing the specific class instances that you want to include in the archive file. For example, you may want to include only specific operators or access groups in the product rule, rather than all instances. If you select Include associated data in the Applications to include section or RuleSets to include section, your selections are ignored if the instances are associated with application rulesets. Instances are processed in the order listed on the product rule. This is important if your application includes views that reference each other. Listing the instances in the wrong order can create dependency tree errors. Drag the instances onto a different row on the list to change the order. As a best practice, when selecting large numbers of instances, use a filter in the Class instance to include section.

Relevant records (location)

Configure > Application > Inventory > Relevant Records. Relevant records can be accessed from the Data Designer or the Case Designer. Its reusable fields in Data Designer. Several locations in Case Designer such as Data model tab, Workflow tab, Views tab

Accessing lock and roll

Configure > Application > Structure > RuleSet Stack page

Adding a level to the organization hierarchy

Configure > Org & Security > Organization > Organizational Chart right click on stuff once there

Logs (location)

Configure > System > Operations

Accessing skimming

Configure > System >Refactor > RuleSets page

Prerequisites to configuring a cascading approval with an authority matrix

Configure a page list property to hold the list of approvers. Configure a single-value property as an element of the page list to identify each approver in the list. Optionally, configure a decision table to determine the conditions for populating the page list. When using a decision table with an authority matrix, set the decision table to Evaluate all rows to return a list of results. Otherwise, the decision table returns only one result.

Authentication

Confirms the identity of a user and verifies that the user is allowed access to an application. In Pega the records for the operator ID, access group, and application allow authentication of a user

Simulating connector data

Connector simulators can be set up for most connector types. First, create the simulation activity for the connector. Then, configure the activity for the connector. Requires an activity (this section is repeated slightly differently) 1. Create a data transform in the same class as the connector. 2. Use the values on the request page to create responses based on incoming values. 3. Set the values on the response page to simulate the response returned by the external service. 4. Create the simulation activity in the same class as the connector it simulates. 5. Apply the data transform in the simulation activity. Open the simulations settings for the connector. You have two options: At the bottom of the connector record, click Simulations. On the Connectors landing page (Configure > Integration > Connectors > Connector Definitions & Simulations), click the Simulations link for the connector. Specify the simulation activity. Select the simulation scope. Click Submit.

Error handling in connectors

Connectors are used to read data from or write data to an external system. Two types of errors can occur when integrating with an external system: 1. Transient errors 2. Permanent errors best practice include error handling for all connectors like note try again later or write details to a log for investigation

Combining data from different classes using a subreport

Consider subreports as a way of combining data using IN, HAVING, and WITH clauses. Subreports can be defined in classes different from the main report. You can access data in different classes similar to the way you would use a class join or an association. You commonly use subreports to satisfy complex reporting requirements. For instance, you can use subreports to filter results. This approach allows you to include or exclude data. You can also use subreports to display aggregate calculations on specific rows in a main report. You use two different methods to create a subreport: join filters or aggregation.

Creating a product rule without the wizard

Create the rule instance manually and add the information to the fields on the rule form. The rule form provides greater flexibility than the wizard. For example, you can set minimum or maximum ruleset versions to include in the archive rule. You can also include rulesets that are not in the application. However, manually entering information — such as selecting specific data instances — can be time-consuming and error-prone. You can use buttons on the product rule form to create the archive file

How connectors exchange data

Data page or activity - Specifies the connector to use and data transforms for request and response mapping Data transforms - Maps the data structure of your application to the integration clipboard pages, which correspond to the format expected by the service Connector rule - Uses the integration clipboard pages to build the request according to the protocol and service definition, invokes the service, and parses and places the response on the integration clipboard pages Mapping rules - For most connectors, mapping rules are used to build outgoing and parsing incoming messages External system - Exposes the service called

Included in synchronization

Data transforms, data pages, field values, and validate rules used in the UI When rule used to skip a process Validate rules called by a flow action or from a step in the case life cycle

Records used for mapping classes to tables

Database and Database Table.

Condition branches (decision trees)

Decision trees contain condition branches — a comparison value, a comparison operator, and an action. The action can be to return a result, to continue the evaluation, or stop the evaluation. The branches are organized in a hierarchical tree structure. Typically, you specify common conditions and results at the trunk of the tree. You then extend the tree outward to more-specific conditions and their actions. When the decision tree is invoked, the system evaluates the top row and continues until it reaches a result that evaluates to true. The result is returned to the system. If the system processes through all the branches but does not reach a returned result, the system returns the final otherwise value.

Page-Remove (method)

Deletes a specified clipboard page that is no longer needed

Method (activities)

Describes the action the system takes. Description will auto pop

Design considerations mobile apps

Design for offline use, design for the device itself. Min custom apps

Configuring a GRS for a connector endpoint steps

Designate a class for the references As a best practice, create the class in the base class of the integration. Create the environment properties Create a page property for each environment reference. For SOAP connectors, use the class Embed-Env-SOAP. Create a data transform to assign values to the environment properties Pega provides several ways of specifying environmental variables without requiring unlocking rulesets. The following table provides the options with relevant utility functions used to obtain the value. Dynamic System Settings, Java System Property, Java Properties File, and JNDI Entry. Note avoid unlocking locked rulesets using these and hard cording and avoid environmental variables being packages as part of the application since that would overwrite the settings on the target system when an application is migrated. Consider a naming convention to categorize the Dynamic System Settings entries and assure their uniqueness. For example, the first entry could be GRS, a namespace for these types of entries. The second is the name of the interface, and the third is the name of the property. Create a data page As a best practice, choose a name that includes the name of the integration to help avoid later confusion when users access multiple integrations (and each integration has its own data page). For object type, enter the class created in the first step and select the node scope. Use the data transform created to populate the data page. Use the Global Resource Settings syntax for references to external systems After you have set up the data page for GRS, use the following syntax to refer to the values: =DataPageName.IntegrationPropertyName .FieldProperyName Where: PageName is the name of the data page, and PropertyName is one of the properties Execution-time sequence 1. The SOAP Connector is invoked. 2. A data page property is referenced. 3. The data transform for the data page is executed if the page is not already available on the clipboard. 4. The data transform invokes a utility function to obtain the value of, for example, a dynamic system setting. 5. The value is used by the SOAP connector to invoke the service.

Authorization

Determines what data the user can view and what actions the user can perform

Validation tool

Dev Studio > Configure > Application >Tools > Validation allows for quick identification of invalid rules

Event viewer

Displays a list of problematic issues in the system that occur during a selected time interval. Recommended for advanced users.

Configuring parallel processing

Done via adding the smart shape into the flow diagram. Note split for each needs to be configured like its a flow for each. Ensure that the flow and page list used for the shape are in the same class. Spinoff flows configured the shape in the flow rule (has a checkbox)

Varying access

During development, you may want to configure more permissive access control to users to support debugging. However, you want to configure more restrictive access control on a production system. You can update individual Access of Role to Object and Access Deny records to automatically revoke access to actions and tools as the application advances towards production. An Access of Role to Object record grants access for action on a scale of 0 to 5. A zero means the action is denied. The remaining ratings are compared to the production level value of your system. If the privilege level is equal to or greater than the production level value of the system, Pega allows the action. If not, Pega denies the action. 5Production system 4Preproduction system 3Testing system 2Development system 1Experimental system

Weighted Conditions (duplicate cases)

Each condition has a weight (between 1 and 100) to determine the relative importance of a condition when making the comparisons. The system adds up the weights of all the conditions that evaluate to true. If the sum exceeds a specified threshold value, the system flags the current case as a potential duplicate.

Offline support

Enabled on access group advanced record to allow offline support. Use caching to improve performance. Best practice customize the pyCaseWorker portal case types tab has a select for enable offline. Ensure it uses the pyStartCase, otherwise need java script. Try to use optimistic locking

Applications to include (components of a product rule)

Ensure RV has prerequisites included. AV should be in the context of an application Settings Include associated data Custom/production rulesets Include rule history Include data types Delta Mode

Action Activities

Execute steps in a numbered order. Loop, When, and Jump indicate when you want to repeat steps, alter the sequence in which steps execute.

translation wizard steps

Export 1. select languages 2. select rulesets 3. enable records 4. export translations Import 1.. select import rulesets 2. upload translation pack 3. view import rulesets

Data API

Facilitates the process of obtaining the contents of a data page and obtaining the metadata for a specific data page

Create a team application

First, Team A and Team B each create a development team application built on the main application. Team application names typically reflect the base application, team name, or the focus of the team. Open the main application rule and perform a Save As to create the team application. Under the list of Built on applications, configure the team application to reference the main application.

Attributes

For example, if you use an external directory, you can assign the attributes to users in the directory. You then map those attributes to the Pega application into the user's operator record or a requestor level data page. Defining an attribute for an object is easier — you add the attribute value into a property field of the object's class. You can use three data types to represent an attribute: a single string value, a list of string values, and a numerical value. Also, hierarchical attributes represent a specified order of values. You can use either string type properties or numerical data types to define hierarchical attributes.

Access groups

Grants access to a specific functionality within your application. You can create multiple access groups for the same application to achieve different levels of access control A user can belong to multiple, but only one is active at a single time When a user signs in Pega identifies the default and opens the corresponding application in the specified portal Note moving between apps resets session and discards any unsaved work

Tracer color code

Gray - Activity processing Orange - Events from flow, decision, or declarative rules Light blue - PegaRULES database and cache operations

Service Package

Groups one or more service rules that are designed to be developed, tested, and deployed together

Lock and roll

Ideal for small patches or changes to rulesets. Creates a new empty ruleset. Minor and major versions require application record and access group updates. Patches usually do not need the updates. May want to reserve space when updating. Labor intensive for major updates.

Product rule

Identifies the application components you want to move to a destination Pega system. Lists the rulesets, data, and other objects that make up an application. Usually does not include standard rulesets and data because those components are built into all Pega systems. Is an instance of the Rule-Admin-Product class, also referred to as a RAP. You can find it in the SysAdmin category in the Records Explorer. Put into a zip archive file (sometimes called RAP file) could be created directly in the rule form or Pega provides a Appalchian Packaging wizard

creating new access groups

Identify the application and application version for the access group. Identify allowed portals for user interaction. Identify allowed access roles for group members. Identify the cases that users can create. if you are just migrating then just update the definition tab. Also can be used to see available portals, roles. Advanced tab shows the cases that can be created

Breakpoints

Identify when to stop execution once the application reaches an activity or a specific step in an activity. will stop the tracer until you click play or a hour passes

Branch (activities)

If A branches to B, the control returns to the rule that called A when B finishes

Call (activities)

If A calls B, then control returns to A when B finishes

Retry a connector invoked from a data page

If the returned error is temporary, you may give the user the option to retry the connector. To retry the connector, configure the data page refresh strategy: 1. Create a when condition that returns true when there are no error messages. 2. Set the Do not reload when setting so the data page does not reload if there are no error messages.

Queue When (exception processing)

If the specified when rule returns true, the request is queued and a Pega-specific SOAP fault that includes the queue ID of the request is returned. Useful when processing errors are due to temporary issues, such as item locking.

Error handling data transform

If there is an immediate need for the response to be returned by the invoked service, you should: 1. Display an error message 2. Write the error to the log file Writing a message to the log file helps troubleshoot errors. For example, a log file can be analyzed to identify patterns related to a specific error. In the log message, include details about the connector request to help identify the cause of the error. Note there is a function to write to logs in data transforms Another option is to generate an email that includes error details. The template error handling data transform includes examples of standard utility functions to: 1. Get available messages 2. Clear messages 3. Add a message to the data page 4. Write a message in a log file 5. Send an email

Application validation mode

If this mode is used, rules in the ruleset can reference all rules in the rulesets defined in the: Same application Rulesets belonging to any built-on application Rules in the ruleset cannot reference rules outside the current application stack or above the defining application.

Decision table

If you are asking a yes/no question when using an automated decision process, then a when rule serves the purpose. For example, a decision such as "Does this purchase order require additional approval?" works well with a when condition. However, if you need to test the values of multiple properties to answer questions such as "What promotional offer should the company offer?", you can use this feature.

Simulate an integrator activity

If you invoke the connector from an integrator activity, you can apply a simulation data transform to populate the case with response data. Use a data transform to define simulation data if your connector is invoked from an integrator activity. Set the simulation data directly in the case in the same way you map the response data returned from the connector.

Accessing logs

In Dev Studio, logs are available from the Configure > System > Operations landing page. In an activity, use the Log-Message method to add a message to the PEGA log.

Configuring error detection for a data page

In Dev Studio, search for the standard data transform called pxErrorHandlingTemplate. Save pxErrorHandlingTemplate with a new name to create a new data transform in your application. Next, in your response data transform, apply the error handling data transform you just created. Open the response data transform. Create a new response data transform if one does not exist. Use the standard when condition pxDataPageHasErrors to detect errors in the data page. Note take care to ensure that the standard error template is updated

Use Integration Designer in App Studio

In addition, you can view a list of simulated data pages, also called data views, from the Integration Designer. In App Studio, select the Data Explorer to open the Integration Designer. Select the Simulated icon in the system of record row to filter by the simulated data types and find all the simulated data pages quickly.

Configure the columns (decision trees)

In the comparison column, select the property to evaluate. Use the drop-down to select the comparison operator. In the action column, specify the literal value or property to compare against. In the next value column, use the drop-down to select the outcome of the comparison. The options are: return - If the condition evaluates to true, the system returns a result value that you define in the field to the right of the drop-down. continue - Causes the next branch of the decision tree to nest within this branch. The system indents the next branch on the form. otherwise - Select only as the last result for a branch. The value in the right column of this row becomes the result of this decision tree branch if no preceding condition in the branch returns a result. Typically, you use this option when configuring indented branches. Note there is a show conflict button

Simulate a data page

In the data page, select the Simulate data source option to simulate the data source in the data page. You can simulate a data page by using a data transform, report definition, or activity. Selecting simulation disables any data source configured. From Dev Studio, select Configure > Data Model > View external data entities to open the External Data Entities landing page and get an overview of simulated data pages in your application. Source systems marked with a green dot are production-ready. Source systems marked with an orange triangle are simulated.

<PREPEND>

Inserts a new element into a value list or page list property as the first element. All existing elements are "pushed down" by one.

<INSERT>

Inserts a new element into a value list or page list property at a numeric index position. Any elements with the same or higher index value are "pushed down" by one.

Work queue

Is a list of work in your application that is shared by operators with the same user role. Is sometimes referred to as a workbasket.

Global resource setting

Is a property value on a data page that is referenced through specific syntax on a connector rule, or by a data instance that supports a connector. Can reference any property of the appropriate type on a data page. Allows greater flexibility for changing values such as port numbers, addresses, and URLs, then fixed text values in rule forms.

Rule resolution

Is a search algorithm used to find the most appropriate instance of a rule to execute in any situation. Happens every time you need a rule to resolve. Applies to most rules that are instances of classes derived from the abstract Rule- base class

search duplicate cases process

Is provided by Pega helps identify and resolve duplicate cases. Uses basic and weighted conditions

User portals

Is the application user's view into the application. Pega provides several defaults. Each portal is customized to the needs of a specific type of user. While these portals can be used in an application as is, some situations require that you customize the layout of the portal or the tools presented to the user.

circumstancing

Is the practice of creating additional variants of a rule based on specific circumstances, such as property values. When the circumstancing criteria are met, Pega automatically executes whichever version of the rule either the base rule or the qualified circumstanced version of the base rule.

Skimming

Is the process of saving the highest version of a rule into a new, higher ruleset version. Applies mainly to resolved rules. Is useful when rule changes follow a logical sequence. The two types of are minor and major. The types correspond with the update types (major or minor/patch). for minor rules withdrawn are carried forward You must update application rules, the Requires RuleSets and Versions prerequisites array in RuleSet version rules, and access groups to reference the new major version after the skim completes. Log out and log in to access the new version.

Logging Level Settings tool

Is used to control which logging events appear in the PEGA log. The prlog4j2.xml configuration file defines the levels of logging events. In a multinode Pega system, you can create separate prlog4j2.xml files for each node Can create overlap if you have multiple rules or activities with the same name

Integration simulation

Is useful in situations when the external service is not available or when you want to dictate the response returned. You can simulate any external service as long as you know what data the external service is expecting and returning. The exact interface definition does not need to be in place.

Overview (admin studio)

Key things to know its where you manage users, nodes and jobs. Likewise requestor pools and queue processors

Setting large data pages

Large data pages are created using the standard data page record type. After the data page is created, you declare it as a large data page by adding it to the pyDataPageWhiteListForOffline rule. Large data pages can be automatically sourced from report definitions. You can also source large data pages from a connector, an activity, or a data transform, but a custom JavaScript populator function is required. Caution: Before you configure the data page, confirm the value of the datapages/addReportDefinitionToDatapage Dynamic System Setting on the system. To source the data page from a report definition, set the value to true. If the setting is not present on the system, Pega assumes the value is true. If the setting is false, create a custom JavaScript function to source the data page.

The service listener

Listens for incoming requests. Service listeners provide the Pega Platform with information the platform needs to route incoming messages to a specific service. The service listener establishes a requestor. A requestor is the processing and data associated with the incoming request initiated by the external system. The underlying Web or Application Server sometimes provide this functionality, and sometimes a Pega listener provides this functionality.

Exception processing configuration

Many service types, including SOAP, have an exceptions or faults tab where you can define what the application does when a service error or exception is encountered. When the service encounters a processing error, and a condition evaluates to true, the application returns a defined error message to the calling application. The following conditions are available for defining an error response message. When Queue When Mapping Error Security Error Service Error

Using object literal notation

Many system properties and parameters have names with mixed cases. When displaying a non-XHTML page, the Firefox browser converts attribute names to all lowercase letters. To prevent this, specify parameter name/value pairs using object literal notation. The following two examples demonstrate the use of object literal notation: To set the value of the data-pega-parameters attribute on the mashup definition using object literal notation: data-pega-parameters="{Customer:'[page/id/Account]', Level:'gold'}" To set the parameter object for a gadget action object using object literal notation: params: { Status:"[pyWorkPage.pyStatusWork]"}

XML Parser

Maps data from an XML message into clipboard property values

Mashup code structure

Mashup code consists of an HTML SCRIPT tag to access Pega Platform and an HTML code block that identifies the action performed by the mashup. This code block consists of either an IFRAME or DIV tag that represents the Pega Gadget. Gadget refers to the application view provided by the Pega Web Mashup. (only create one per element) The IFRAME and DIV tags support a set of attributes for customizing the behavior of the gadget on the web page. Single quotation marks encapsulate the value for each attribute, and the attribute named PegaGadget specifies the name of the gadget.

Channels and Interfaces tab in App Studio

Mobile app type Security Accessing other Pega apps Apps branding Containing app layout settings

Watch (the tracer)

Monitor a property value or page to detect when the value changes. Useful for seeing property value, calculation consistency, and patterns in a trace

Merge branches when development is stable

Move the new and updated records from the branch to the base rulesets when development activity in the branch has reached a stable point. This makes the newest updates available to the wider development team. When you merge a branch into the application, you can either delete the branch if development is complete or maintain the branch to support additional development of the feature. Before you begin the merge process, view the contents of the branch on the Content tab of the Branch landing page. Content information includes the changed rules, ruleset and the user ID of the individual who updated the rule. Make sure what needs to be checked in is checked in.

Obj-methods (save to a database)

Obj-Save saves the contents of a clipboard page to the database Note that this immediately writes the object to the database only if the Writenow parameter is selected. if its not then Obj-Save becomes a deferred save A valid read to perform a WriteNow is the need to immediately reread the instance before issuing a commit

Obj-methods (cancel/rollback operations)

Obj-Save-Cancel cancels the most recent uncommitted Obj-Save method so that the instance is not written as part of a later Commit operation Rollback method cancels or withdraws any previous uncommitted changes to the PegaRULES database (and to external databases accessed from an external class) from the current thread.

Obj-methods (read from a database)

Obj-open opens the object you read Obj-Open or Obj-Open-By_Handle loads an instance of a class stored in either the PegaRules database or an external database. Both methods create a clipboard page for the open instance. Obj-Browse searches the database, retrieves multiple records, and copies them to the clipboard as an array of embedded pages Obj-Refresh-and-Lock tests whether a clipboard page is current and if a lock is held if the object is not locked, the activity acquires a lock and refreshes the page if it is stale

Class join settings

On the Data Access tab on a report definition form, in the Class name field you specify the class you are joining. For each class, in the Prefix field you enter a text prefix. The prefix combined with the class name serves as an alias for the joined class and its properties. Only include matching rows Select Include all rows in <class> Select Include all rows in <prefix>

Configuring ability to check out rules

On the Security tab on the ruleset, select Use check-out? to enable checkout. On the Operator record Security tab, operators need to have the Allow Rule Check out selected in order to update rules in rulesets that require checkout. If a rule is not available for checkout, it is already checked out by someone else, or it is in a locked ruleset version.

Ruleset best practices

Only use RV for rulesets that are designed to be used across multiple applications Create applications for common rulesets; use the built-on functionality to include common rulesets in the application. Include unlocked AV rulesets in one application only. Run the Validation tool after implementation of critical changes or milestones.

Updating the operator record

Open an operator record that you want to associate with the new level. On the Work tab, update the Organization unit values. Then, in the Work group field, select the work group you want to associate with the operator. Finally, add the work group to the Work queue field.

Marking relevant records

Open the Actions menu, and click Mark as relevant record. The Mark as relevant record option is available from the Actions menu only if the selected rule type is available for designation as a relevant record. If the Mark as relevant record option is grayed out in the Actions menu, the selected record has already been marked as relevant.

Create the decision tree

Open the Application Explorer. Select the class in which you want to create the decision tree. Right-click and select Create > Decision > Decision Tree. The New Record form opens. In the Label field, enter a name that describes the purpose of the tree. Click Create and open. The decision tree rule form opens. Note continue creates the nested branch

Trusting domains (Pega Web Mashup)

Opening a channel between the host site and the Pega Platform application requires you to configure the application permissions by specifying a list of trusted domains in the Pega Application rule. Add the web domains to the application rule as a trusted origin. The list contains the URLs on which you are deploying the mashup and informs Pega that mashup requests originating from the web page are legitimate. Trusted origins are listed on the Integration and Security tab of the application rule in the Mashup security section.

PDC case types

Operations - High-urgency issues that you should resolve immediately Database - Issues that occur in your database configuration Pega Platform Tuning - Issues related to your Pega Platform configuration Connectors - Issues related to system connectors Decisioning - Issues related to Decision Strategy Manager (DSM) Exceptions - Issues related to run-time errors during Pega execution Application Logic - Issues related to the way the application is built Other - Issues related to any other type of problematic event

Access manager (configuration)

Org & Security > Access Manager Use the Work & Process tab to configure access control for instances of a specific case type. Use the Tools tab to configure access to Pega tools such as the Clipboard and Live UI for end users. Use the Privileges tab to manage access to specific records, such as flow actions and correspondence records. To configure the access control for a setting, expand the Case Type and click the icon in the column for the appropriate role. Select the level of access to grant — Full Access, Conditional Access, or No Access — from the pop-up window. The Access Manager manages the Access of Role to Object and Access Deny records for case types for a selected access role. When you update a setting, the Access Manager updates the appropriate record. Note You must create an Access Deny record manually. The Access Manager creates only Access of Role to Object records.

The Tracer (settings)

Pause- Suspends event logging in the Tracer. While the Tracer is paused, in the lower right of the tracer window, Tracing stopped or Waiting are displayed and Pause is replaced with Play. Play resumes the event logging. When the tracer is active, in the lower right of the tracer window, Tracing is diplayed. Clear- Removes all logged events from the screen. Save- Generates an XML file listing the events on screen. Save the output from the Tracer as an XML file for your records or forward to others for troubleshooting. Pega Client Support may request the Tracer output to help find the source of an issue.

Mobile channel configuration comprised of three main groups of tasks

Pega Mobile Client general options Such as security offline access OS-specific build options such as IOS Android options like debuggins App branding how it looks and feels

JAR files to include (components of a product rule)

Pega Platform™ allows you to extend the Java code built into the Pega Platform with your own code. The code can be used with activities (Rule-Obj-Activity rule type), user interfaces, or system interfaces. If your application uses JAR files, complete the array in the Jar files to include section to include JAR files in the product archive. To locate available JAR files, enter a class name in the Search jar files field and click Query jars.

Performance Analzyer (PAL)

Pega Platform™ always gathers cumulative resource statistics. Use this to understand the system resources consumed by processing a single requestor session. PAL works on existing data; it does not degrade processing.

Pega Web Mashup Authentication

Pega Web Mashup enables you to embed a Pega application in another web application. The system must authenticate the user before displaying the application mashup on the external web page. Similar to an SSO configuration, a third-party authentication module manages the authentication of Pega Web Mashup users. There is a standard service of Internet Application Composer (IAC). While this is quick, you will want to update the authentication activities to ensure security in a production environment. When users log in to the mashup application, the IACAuthentication activity uses information in the HTTP request header to identify a corresponding Pega Platform™ operator ID record. Pega can create one if it doesn't exist

Pega Web Machup

Pega Web Mashup enables you to embed a Pega application within a web page or other web applications on your intranet or internet site. You create a Pega Web Mashup directly in App Studio or Dev Studio and deploy it to leverage the security and user interface features of the Pega Platform™. some common actions include Opening a new case Displaying a user's worklist Selecting and performing an assignment to create one use the Channels and Interfaces landing page in either App Studio or Dev Studio, customize the code as necessary, embed that code to a web page, and configure a list of approved sites for the site origin.

Interaction of multiple access groups and roles

Pega allows for multiple access groups and roles to overlap allowing for the creation of a modular setups to meet complex security needs. If there is a conflict most permissive applies

access groups (accessibility)

Pega provides accessibility features to individual access groups. The accessibility features are available to access groups with the accessibility ruleset provisioned. An application can display as expected to access groups without accessibility.

Supported Services

Pega provides services for a wide range of industry-standard protocols and standards, including SOAP, REST, EJB, JMS, MQ, and File.

Database updates (three major databases)

Pega rules contains all of the rules and system information. Easy to update the database structure since detailed knowledge about the database is unnecessary for most application tasks Pega data contains cases, assignments, case history. automatically created deleted updated and saved. Uses user inputs, decisions, and results of calculations. This is separate then rules and support high availability and in place upgrades external databases Pega applications almost always require access to data stored outside of the application. You can Create an external class in your app to directly manage data read and written to an external database

Data storage in Pega

Pega saves data across multiple database tables when a case is processed. The system uses Pega classes to organize and store the data in the appropriate table. When you create reports, the Pega reporting tool uses the Pega class organization to find and retrieve information from these tables. Efficient data organization and access enables the organization to generate reports that support key strategic decisions.

Application accessibility

Pega supports the Web Accessibility Initiative-Accessible Rich Internet Applications (WAI-ARIA) he WAI-ARIA standard conforms to the Web Content Accessibility Guidelines (WCAG). standard. WAI-ARIA is a technical specification that defines ways to make Web content and Web applications more accessible to people with disabilities using accessibility roles.

Simulating an integration

Pega uses connectors to integrate with external systems. A connector can be invoked from either a data page or an integrator activity. If the interface definition is available, a connector can be generated using one of the connector wizards. How an integration is simulated depends on whether or not a connector is available. If you need to simulate an external service which has not yet been defined, but you know what data the service is going to return, then simulate the data page source or integrator activity. Simulate the connector if it already exists.

What can be marked as relevant records

Properties Sections Harnesses Paragraphs Correspondences Service Level Agreements Flows Flow actions Ensure guardrail compliance prior to marking

System Summary

Provides a summary of all performance metrics

Docs API

Provides access to the complete documentation for the Pega API

Improvement plan

Provides an overview of the issues affecting your system

Assignment API

Provides the ability to obtain a list of assignments for a user, obtain the details of any specific assignment, and perform an assignment action

Casetypes API

Provides the ability to obtain a list of case types for the authenticated user

Cases API

Provides the ability to obtain a list of cases for a user, create a new case, obtain case details, and update a specific case

Background process management

Queue processors and job schedulers can fail to process items correctly for a number of reasons. For example, the processes are unable to obtain a lock on an entry because they lack security access or an activity or related class is named incorrectly.

Access control policy rule form

Read Update Discover Delete PropertyRead PropertyEncrypt

Rules purpose (choosing rule with correct purpose)

Remember, the purpose of a rule is defined by a combination of all the key properties of a rule, except the Apply to: class on which the rule is defined.

Job Scheduler

Replaces agent rules with advanced configuration. Handles reoccurring tasks. Runs at specified interval. Identifies the tasks to process at that time. Doesn't manage the read/write operations on database objects 1. select nodes 2. select when it reoccurs 3. get specific with the time if you want 4. identify a context for the task. Determines privileges and permissions 5. You can further select the context determined by the AsyncProcessor requestor, or specify an access group

Queue processors (failure)

Reverts the changes if the process fails and the system cannot commit a queue entry, the system puts the entry into failure status and indicates the process is broken. The system also reverses any changes the process initiated. Admin studio manages and troubleshoots In Admin Studio, you use the Queue processor landing page to trace and monitor Queue Processor rules in your application. If there is an error, users with the SysAdmin4 role can troubleshoot issues with the queue processor by tracing the running processes and examining the items in the Broken queue.

RBAC rules

Roles (Rules-Access-Rolename) Access of roles to objects (Rule-Access-Role-Obj) Deny rules (Rule-Access-Deny-Obj) Access groups determine the list of roles a user has access to which determines the applicable access of roles to objects and deny rules

Whitelist entry required

Rules called by scripts as part of an action set on a UI control Rules called from a script using a Run Script action or from a custom JavaScript function

Localization wizard output

Rules such as correspondence, paragraph, and work party rules contain text that is translated manually and stored in the corresponding translation ruleset with the aid of the Localization wizard. Text that is used in paragraphs, correspondence, and correspondence fragment rules is packaged and output in a pair of HTML files called Base.html and Translation.html. Both files initially contain the same text. The translator puts the translated text into the Translation.html file. Note that the localization wizard can export the strings to be translated such as field value or message rules. Short and under 64 characters Any text editor can be used to edit the HTML translation

Access manager limitations

Security for two application elements cannot be configured in the Access Manager: work queues and attachment categories.

A SOAP service uses a combination of rules to process a request.

Service Activity XML Parser XML Stream Service Package

Standard ruleset accessibility options

Set tooltips on controls, buttons, links, icons, and input fields. Announces control functions to users with a screen reader Configure a high-contrast color scheme. Ensures the contrast is sufficient for users with vision limitations Set the enter event on a control when you set a click event on the control (for example, configuring the up and down keys to support navigating through a list and set focus on an item). Enables keyboard controls for tabbing through the interface Include links with icons. Provides a visible description of the icon that an assistive device can read to a user Use a button or a link to dismiss an overlay. Provides a navigation element that an assistive device can describe to a user Mark a dynamic container as the main content area by default. Provides the ability for users tabbing through a page to skip to the main content link by pressing the Enter key Use a drop-down list of options instead of text entry for fields with predictable answers (for example, a series of numbers or colors). Provides a visible list of options that an assistive device can read to a user

Property-Set (method)

Sets the value of a specified property

Pega Predictive Diagnostic Cloud™ (PDC)

Software as service runs on Pega Cloud. It actively gathers, monitors, and analyzes real-time performance and health indicators from all active Pega Platform™ applications. This gathers, aggregates, and analyzes alerts, system health pulses, and guardrail violations generated from Pega applications to produce trending dashboards. This tool empowers business stakeholders and IT administrators to take preventative action by predicting potential system performance and business logic issues and providing remediation suggestions.

Rulesets to include (components of a product rule)

Specify rulesets that are not part of an application. The rulesets can be entered in any order. During import, the system determines a valid order to load the rules. Make sure that the prerequisites are included in the list or already exist on the target system. For example, when you include rulesets from other applications, you must verify that all the prerequisites are listed in the product rule or are already present on the target system. If the prerequisites are not present on the target system, some rules may be unavailable. has the following settings Min/max fields exclude non-versioned rules Include assocaited ata

Pega Mobile client

Standalone app that lets you wrap device specific container around Pega. Makes hybrid applications

Subreports

Subreports can be defined in classes different from the main report. You can access data in different classes similar to the way you would use a class join or an association. You commonly use subreports to satisfy complex reporting requirements. For instance, you can use subreports to filter results. This approach allows you to include or exclude data. You can also use subreports to display aggregate calculations on specific rows in a main report. You use two different methods to create a subreport: join filters or aggregation.

Delta Sync

Synchronizes only objects changed since the last Sync

Exporting via the wizard steps 1-16

The Application Packaging wizard simplifies the process of exporting an application by guiding you through the steps to create a product rule. In each step, you add the application components that you want to include. After you complete the steps, the wizard creates the product rule. You can then review the product rule contents and generate the archive file. 1.navigate to the wizard 2. select the select the application 3. select the ruleset and unlocked version 4. optionally click check to display only application rulesets 5. identify the chain of built on apps sometimes you don't need them all 6. identify the products which Pega supplied apps dependent 7. identify the organization 8. identify the access groups 9. identify the operators 10. identify the work queues 11. identify the work groups 12. identify the data tables Aka local data storage data types 13. identify the Java code used 14. identify the databases and database tables available 15. identify the integration resources available 16. finish the sucker and then can perform the following Preview, Modify, Migrate, Export, OK, download the file Note After you have created your product rule, you can also create the archive file using the Export gadget. The gadget is available from the Configure menu in Dev Studio by selecting Application > Distribution > Export. In the gadget, provide the product information and click Export. You can also use the Export gadget to quickly package specific rulesets and data objects without having to create a product rule.

PAL (analyze)

The INIT row displays the totals from the first time the Performance tool made a reading. Each subsequent reading is labeled as a DELTA — this indicates the change from a previous reading. The FULL reading is the total sum of all the statistics from the last time the data was reset.

Leveraging the Pega API

The Pega API provides a standard set of services that includes new case creation, assignment processing, and access to data pages. These built-in REST/JSON services enable the rapid implementation of Pega-powered mobile and client applications. You can call any of the Pega API services by using standard HTTP methods (for example, GET, POST, or PUT). Refer to the Pega API resources page in Dev Studio or App Studio (in Dev Studio click the Resources menu and select Pega API; in App Studio click Interfaces and select Pega API) to see details of the request and response data requirements.

PAL (usage)

The first step to measuring your application performance is to take measurements. You start by clicking Reset Data to clear any data in the tool. Since the system is continuously monitoring performance, you are eliminating any previously recorded entries from your results by resetting data. You have two options for adding a reading: Add Reading and Add Reading with Clipboard Size. The only difference between the two readings is the addition of the clipboard size, which takes extra time to calculate. When adding a reading, the best practice is to define points that identify what occurred during that reading. For example, use one reading per flow action or screen render, depending on what process you are measuring. Click Save Data to download the results to an Excel file.

Modifying the product rule after you use the wizard

The product rule created by the wizard uses default settings that you may have to override, depending on your requirements or selections you made in the wizard. Click Modify to open the rule and make your updates. what you want to export is the top, below is where to make the update You export delegates rulesets: In the File details section, select the Allow unlocked ruleset versions? check box. These rulesets must be unlocked so that users can access them on the destination system. In the Applications to include section, select the Custom/Production rulesets check box. You exclude specific associated data instances in the wizard: In the Applications to include section, clear the Include associated data items check box. Otherwise, all associated data items are included in the archive file. You exclude specific data tables in the wizard: In the Applications to include section, clear the Include data types check box. Otherwise, all data types are included in the archive file. You want to exclude rule history instances: In the Applications to include section, clear the Include rule history check box.

Date Property (circumstancing)

The rule variant is effective whenever the value of a date property satisfies the circumstancing condition. This condition can be either a single date or a range of dates. If the value of the property is later than the specified date or falls within the range of dates, the application uses the circumstanced variant of the rule, rather than the base rule.

Single value (circumstancing)

The rule variant is effective whenever the value of a single property satisfies the circumstancing condition. You specify the property to evaluate a comparison value when circumstancing a rule. If the value of the property matches the specified value for a case, the application applies the circumstanced variant of the rule, rather than the base rule.

Branch rulesets

The rulesets associated with a branch. Is based on (branched from) another ruleset Contains rules that are in active development in the associated branch

When (exception processing)

The specified when rule returns true.

Decision Table property chooser tool

The tool allows you to: Select a property or create an expression used for the evaluation. Enter a label that appears on the table. Select the comparison operator. The default is the equals sign (=). If you select a numeric property, you can use greater than/less than operators. You can also use these operators to define a range.

Exposing an application as a service

The two most common ways to expose your application as a service are either to create a web service or to leverage the Pega API. Conceptually, these two options work the same way: a request is made to a URL, and a response is returned. The difference is how you communicate with the service.

Error detection configuration

The way errors are detected depends on how the connector is invoked. Connectors can be invoked by data pages or activities. When data pages and activities invoke a connector, the best practices are to: Add error detection to all data pages and activities Invoke a reusable data transform to handle errors Pega provides a template data transform called pxErrorHandlingTemplate. In addition, each connector has an error handling flow. Pega automatically invokes the error handler flow if the error is not detected by another mechanism.

Background Processing

Think of it like moving tasks to dedicated node or off peak hours. Can be done in clusters so each node handles a task

Services

This allows you to expose the data and functionality of your application to external systems. This implement the interface of a specific protocol and provide data mapping for outbound and inbound content. You can parse, convert, and map data in either direction to or from the clipboard. Data can be in XML, fixed record structure, or separated by a delimiter character format.

pxErrorHandlingTemplate

This can be used to create a reusable error handling data transform. The error handler data transform can be used with both data pages and activities. Is in the base class and is shipped as part of the product.

Circumstance definition

This defines the combination of conditions in which a property uses a variant of a rule

Circumstance template

This defines the properties on which to circumstance a rule

Filter conditions

This defines the relationship between the classes. The filter uses one or more properties to establish the relationship. You cannot join to a class in a different database than the Applies To class of the report. The Column property must be an exposed column. You can use the Optimization tool to expose columns.

appender (log files)

This determines the type of events written to the log file. Pega manages logs based on the configuration in the prlog4j2.xml file for the node

Rule checkout and check-in

This feature ensures that different team members are not editing one rule at the same time. The system enforces the use of both sides of these operations when a ruleset has this enable. Before you can change that rule, you must perform either the standard version of this or the private version

Work groups

This identifies a cross-functional team that contains a manager, a set of operators, and a work queue. You create this so that resources can be shared among units, divisions, or the entire organization. Even though operators and work queues belong to a unit, associating this with an operator allows the operator to share work with operators in other units. Note an operator must be associated with at least one of these and can belong to more than one of these (called teams in case manager portal) (technically outside of the org structure)

Access manager

This is a toll that provides a easy to use interface for managing application security. You can view and edit the current access settings for a given role in one place instead of editing dozens of ARO rules

zipMoveSkim privilege

This is required to run a skim Pega provides a default role for system architects which includes this privilege. SysAdm4 is the default system role for system architects and includes this privilege. When an application is in production, the SysAdm4 role becomes the Administrator role.

Circumstance record

This is what record you would circumstance according to what exactly you were circumstancing. So like a correspondence record if you were referencing a template and a definition for an email

Duplicate cases

This is what's on the tin, its a case that's duped. In many situations, a user may enter a case that has many of the same data values as another case already in the system.

Queue processors (admin studio)

This is where you can run a processor trace with the following steps 1. In the sidebar menu of Admin Studio, click Resources > Queue processors to open the Queue processors page. 2. On the row with the queue processor you want to trace, click the Actions menu icon to open the actions menu. 3. On the Actions menu, click Trace to begin the trace. Tracing the pzStandardProcessor queue processor requires an additional step. You must specify the activity to run after clicking Trace from the Actions menu and then click Open tracer to begin the trace.

Division layer

This layer is the middle level of the three-level organization hierarchy and is available for use in every application.

Paragraph rules (localization)

This make content reusable. Instructions on a UI form, copyright declarations, and privacy notifications are all examples of reusable paragraph rules. Paragraphs longer than 64 characters can be kept intact as boilerplate content and easily applied multiple times in an application.

Cascading approval

This model has two basic setups which are reporting structure and authority matrix. You use the reporting structure model when approvals always move up the reporting structure of the submitter or another defined list. You use the authority matrix model when a set of rules directs the approval chain to individuals both inside and outside the organization of the submitter.

basic condition (duplicate cases)

This must be met before considering potential duplicate cases. Once all of these are met, the system continues to evaluate the weighted conditions to receive a weight value.

Multiple pages per key and multiple keys

This option allows you to return multiple matching instances. If not selected key will only return first matching instance. Note you can add multiple keys to a single data page as well

Spinoff (parallel processing)

This option in the Subprocess shape allows you to run the subprocess in parallel with the main flow. The main process does not wait for the subprocess to complete before proceeding. The spinoff option is an advanced feature in the Subprocess shape and is accessed in the flow diagram.

Privilege

This record allows or denies access to certain records, such as flow actions and correspondence. can't be configured for an access group. Like a token you grant to a user role. Good for allowing access to particular rules. Note you need to update the record make it then update the rule you want to restrict as well. Can combo with access when to grant or deny. Also could even grant or deny depending on production level. For access manager you have to specify it to show inherited if you extend it out to all case types in your app for example.

Database table

This record identifies a specific table in a specific database, and specifies the corresponding Pega class. Pega uses this record to identify which table to write case data when a user creates or updates a case.

Database record

This record identifies how Pega connects to a specific database for the named database. The record contains connection information so Pega can access the database. The record establishes an alias that can be referenced elsewhere, such as a database table record. Database records can be configured to use either JNDI or JDBC url for the database connection. By default, Pega uses the following standard databases in a database record: PegaRULES maps to a database where all Pega rules and system data are stored. PegaDATA maps to a database where data and work instances are saved.

Rule Availability: Blocked

This rule is carried forward (multiple answers)

Rule Availability: Final

This rule is carried forward (multiple answers)

Rule Availability: Yes

This rule is carried forward (multiple answers)

Rule Availability: No

This rule is not carried forward

Rule Availability: Withdrawn

This rule is not carried forward but is if its a minor skim

Test for conflicts (decision tables/trees)

This test shows you if your decision rule prevents one or more of its rows or branches from ever being used. For example, assume your decision table contains a row that tests for purchase requests that exceed USD300. The next row tests for purchase requests that exceed USD500. The second row may never be evaluated, because the upper row includes that condition. To test for conflicts, on the decision form, click Show Conflicts. If a conflict exists, a warning is displayed on the row causing the conflict.

Database Trace

This tool is useful to tune the application in case of any database performance issues. Run this tool if PAL readings indicate performance issues in the database operations. this tool can trace all the SQL operations like queries or commits that are performed.

KPI value

This value is measured value recorded by an alert. If the recorded value is higher than the threshold configured in Pega Platform, the alert is triggered. Each alert maps to an action item type in PDC. When you elevate this value on an action item, all alerts with a lower value are ignored. Alerts with an equal or higher value are processed and assigned to an action item type. You can elevate the value on an action item in PDC.

dashboard template.

To customize the dashboard, determine the template to use to organize the dashboard, then add widgets to each slot.

Obj-Delete (delete a database record)

To delete a database row identifed by a page on the clipboard.

Obj-Delete-By-Handle (delete a database record)

To delete an instance using its unique ID without require a page on the clipboard

Test for completeness (decision tables/trees)

To employ this test on the decision form, click Show completeness. The system adds rows to indicate values that will not be evaluated. The results are suggestions. You can add return results to additional rows if you think the decision rule needs a more detailed evaluation of the values.

Select Include all rows in <class> (class join setting)

To include all qualifying instances of the Applies To class of the rule, even if there is no match found in the joined (prefix) class (referred to in database terms as an outer join)

Only include matching rows (class join setting)

To only include instances in each class that have a matching instance in the other class (referred to in database terms as an inner join)

Configuring an access group to reference the portal

To provide users with access to a user portal, add the portal to one or more access groups. To add a portal to an access group, list the portal in the Available portals section of the Definition tab of the access group record. For each access group, you select one portal for Pega to use as the default portal. Pega presents the default portal to a user when the user first logs in to Pega. The remaining portals are available to users from either the Operator menu or the Launch menu, depending on the portal.

Branch quality tab

To view the possible rule conflicts, guardrail warnings, and unit test coverage, on the branch rule

Remote Tracer

Trace events that are generated by a service requestor or another user. The user must be logged into the application to trace events.

Return multiple results (decision table)

Under the Results tab, if you enable the Evaluate all rows option, the decision table evaluates all rows defined in the decision table. If the condition is true, the decision table performs the actions and returns an array of results that can be parsed.

Pega mobile app prereqs

Upload certificate set Configure access to Pega Mobile Build Server Confirm with the system administrator that Pega is configured to support access through HTTPS

Obj-methods (delete a database record)

Use Obj-Delete or Obj-Delete-By-Handle to remove an instance from the database. Use Obj-Delete to delete a database row identifed by a page on the clipboard. Use Obj-Delete-By-Handle to delete an instance using its unique ID without require a page on the clipboard

<Current>

Use differs depending on where it is used.

Creating product rules with the wizard

Use the Application Packaging wizard — it guides you through a series of steps that populate and create a product rule. The wizard includes the rulesets in your application. Because the wizard presents an inventory of components that are in your application, selecting the components you want to include is easier and more accurate than manually entering them in the product rule. When the wizard creates the product rule, it enters your selections automatically on the form. For finer control, you can modify the product rule after you have created it in the wizard. Landing page that includes the wizard can make the archive file

Min/max fields (settings rulesets to include product rule)

Use the Minimum version and Maximum version fields to define a range within a major version that you want to include in the product. Leave both fields blank to include all versions.

Reference pattern

Use this pattern to populate UI controls with dynamic data. When you use the reference pattern, only the selected value is copied to the data model of the case. For example, you can use the reference pattern to populate countries and states in drop-down lists. Usage To implement this pattern, reference a data page from a record other than a property. The following example demonstrates populating a drop-down control with values from a data page. The application creates the data page the first time the property is referenced. If the data page contains information that applies to multiple cases, you can set the page scope to node to save memory by sharing the contents of the data page between requestors. Reloading data with this pattern With this pattern, the data reloads according to the refresh strategy specified on the data page. The control always points to the current version of the data page.

System of record pattern

Use this pattern when you always need to reference the most current data from an external system or application. The case does not contain a copy of the data. Instead, the application references the data from the source when needed. Usage To implement this pattern on a property, in the Data Access section of the property record, select the Refer to a data page option. The type of property (page or page list) must correspond to the structure of the data page (page or list). A new data page is created on the first reference to the property. Reloading data with this pattern With this pattern, the data reloads according to the refresh strategy specified on the data page. The property always points to the current version of the data page. Whenever a data page parameter is updated, a new data page is created. The property then points to the new page.

Snapshot pattern

Use this pattern when you need to copy data to a case at a specific point in time. Once you copy the data to the case, the data is not retrieved from the source again unless the request parameters change. Usage To implement this pattern on a property, in the Data Access section of the property record, select the Copy data from a data page option. The type of property (page or page list) must correspond to the structure of the data page (page or list). The first time the property is referenced, the data page is created, and the data is copied to the property. You may also choose to specify a data transform for data mapping in Optional data mapping. Reloading data with this pattern When you copy data from a data page, the data is stored in the property. The data page is not accessed again unless it has a parameter that changes. When the parameter changes, a new data page is created. The impacted data is copied to the property and overwrites the existing data.

File details (components of a product rule)

Use this section to prepare the product rule for packaging in a ZIP archive file. The date in the Creation Date field is displayed in the destination system before the archive file is imported. The date value entered persists even when the file is copied or renamed. Enter a text description of the contents of this file in the Short Description field. This value appears on the destination system before the archive file is imported. As a best practice, lock the ruleset versions you want to include in the archive file. Doing so helps prevent updates to the rulesets after they have been packaged in the archive file. Select Allow unlocked ruleset versions? if you want to include unlocked ruleset versions. For example, select the check box if you include a delegated ruleset. If you want to include post-import instructions such as a Read-Me text, identify an HTML rule on the Installation tab. The file is displayed at the end of the import operation for this product rule. The Preview Product File button lets you review the items that will be included in the archive file. It is a best practice to review contents before you create the archive file to ensure that the contents are correct. The Create Product File button creates an archive file on your local computer.

Performance Profiler

Use this tool to obtain a detailed trace of performance information about the execution of activities, when condition rules, and data transforms executed by your requestor session. This tool traces every execution (in all Threads) of rules of these three types in all rulesets. It should be run in conjunction with Performance Analyzer The Performance Profiler is useful when determining which part of the process might be having performance issues, or identifying the particular step of a data transform or activity that might have a performance issue.

data pages (database updates)

Useful as a best practice to have a savable data page read and write updated info without an activity

Creating new roles

What is the role of the user in processing a case? What actions do these users need to perform How doe these actions differ from the actions allowed for other users In Pega, you define an access role with an Access Role Name record, a label that describes a specific set of application users with a unique job function. You apply the role to Access of Role to Object (ARO) and Access Deny records to identify the actions allowed or denied to users assigned the role. An Access Role Name record can be configured with one or more dependent roles to simplify the configuration and management of permissions. The access role inherits the permissions set for each dependent role. If permissions for a class vary between the dependent roles, the access role name inherits the most permissive permission settings. To view the dependent roles applied to an access role, click Manage dependent roles on the Access Role Name record. Note dependent is overwritten by permissions in the Access Role Name record

History reports

When a case is being processed, the system automatically captures audit trail data in the history classes. The classes are mapped to the History database tables where the data is saved. For example, the history class History-TGB-HRApps-Work is mapped to pc_History-TGB-HRApps-Work. These reports use properties in the History- and History-Work- classes. These properties include pyHistory type (identifies the event that caused the history event), or pyPerformer (identifies the operator who completed the event recorded in the history instance). Properties in history classes can be used to design performance-based reports. For example, you can use pxTaskElapsedTime to report the total time spent on an assignment. If an assignment is routed to multiple users, you can use pyPerformTaskTime to report on the total time spent by all users. If pyPerformTaskTime is significantly lower than pxTaskElapsedTime, then the assignment has been idle for a long time.

Work reports

When a case is created, Pega uses standard properties in the Work- base class to define each case. This Work- base class includes properties that describe the following: A case identifier (pyID), the work parties participating in a case (pyWorkParty) The customer identifier such as an account number (pyCustomer) The work status of the case (pyStatusWork)

Check in a rule

When a rule is checked in, the checked-in rule replaces the original base rule. Add a comment describing the changes to the rule. You can view the check-in comments on the rule History tab. Use the bulk action feature to check in, open, or delete several checked out rules at the same time. The bulk action feature is located in the Private Explorer menu or under the check mark icon in the header.

FlowProblems.

When an error occurs, the original flow execution is paused. Control is handed over to the error handler flow. If the resource is unavailable, a transient error may be preventing processing. If there is no transient error, the connector is retried, and processing continues in a flow (called the name of the definition) lets operators 1. Retry the connector 2. Resume the flow without retrying the connector 3. Restart the initial flow 4. Cancel the error handling flow

Field values

When building an application, you often need to use a list of allowed values for a specific property. If the list of allowed values is short, mostly static, and common, for all case types in the application, the list of allowed values may be defined in a local list on the property record. If the list of allowed values is large, expected to change frequently, or may be specific for each case type, you can use a this (aka the definition of this term). provide an alternate method for defining allowed values for properties. This enables you to manage the list of allowed values separately from the property. Managing the allowed values separately from the property enables you to reuse a single property, and customize the allowed values based on the context of the property.

Authority matrix model

When configuring a process that requires multiple approvals, where a set of rules directs the approval chain, you use a cascading approval step with this model

Parallel development

When multiple teams are working in the same application rulesets, coordinating changes across teams is a challenge. When development teams configure an application in parallel, rule changes might result in conflicts. Resolving conflicts disrupts the overall project and may delay time to delivery.

Connectors

When the application requests data from another system. Pega uses Connectors to facilitate this type of integration. Connectors are protocol specific, and they establish the link to the external system. Connectors implement the interface of the service running on the external system. Connectors also map the data structure of the application to the data structure used by the service called. You can parse, convert, and map data in either direction to or from the clipboard. For example, you can map data to and from XML, fixed record structure, or a record structure separated by a delimiter character. Can be invoked from data pages and activities. You need an activity to call a connector from a flow

Activities (error detection)

When the connector is invoked from an activity, use a transition condition to check for the presence of an error in the activity step invoking the connector. If an error is detected, apply the reusable error handling data transform.

Configure connector simulation

When the interface of the service to which you are integrating is defined and has an existing connector, but the service may still be under development or has not yet deployed. The Connectors landing page (Configure > Integration > Connectors > Connector Definitions & Simulations) provides you with an overview of available connectors and their simulations. Connector simulations are not available out-of-the-box. Simulation is not available for SQL connectors. Connectors are simulated using a simulation activity. The simulation activity sets the properties to be returned by the external service on the integration page used by the connector. A connector can be simulated either for all users in the application using the Global option, or for the current user only using the User session option.

Keyed data page

When this type of data page is referenced, a value is provided for the key, the first time the data page is referenced, all the data is loaded according to the data source configuration and stored on the page despite providing a key. The key is then used to locate the specific instance on the data page and returns only the matched result to the caller. When another request to the data page with a different key value is made, the products are already on the data page. The system only needs to locate the correct instance on the page no trip is necessary. So changes infrequent accessed often. List structure is necessary for it to be selected. If there was a single page no need for a key Only properties can reference this type of data pages. a property that references a data page is configured in the same context as the data page it is referencing. Context refers to class structure. property referencing a data page has the same configuration context as the data page it is referencing. so think data page with the list structure would be a configuration point Parameters may be used simultaneously with keys to access specified instances of data

Attachment-level access control

When users add an attachment to the category, they identify one or more work groups to which access to the attachment is allowed. To enable attachment-level access control, select the Enable attachment-level security check box on the Security tab of the Attachment category record.

Configuring case locking (child cases considered)

When working with a case type hierarchy, you set locking on the top parent case. The settings cascade down to each child case when it is instantiated. If the child cases are instantiated as part of the parent case, they have the same locking settings as the parent. In the Case Type Explorer, select the parent case type to set locking. Then, in the Case Designer, on the Settings tab, select the Locking option. If you select Allow one user, you can modify the default locking timeout of 30 minutes. Consider the business context when setting the timeout duration. For instance, if a case will likely be opened frequently, you may want to shorten the timeout so that users can more quickly access the case.

Class joins

When you build a class relationship in a report definition, you configure this Determine the class to which you are joining. Create a prefix that in combination with the class name serves as an alias for the joined class. Decide whether you want to include or exclude instances that do not match. Create a filter that describes how you relate the classes. In the report definition form, you specify the class as the primary join. If this work type is derived from Work-, determine whether the join is to an implementation class or to a framework class. This ensures that you are joining to the correct data set. Care as you cannot join to a class in a different database than the applies to class of the report. The column property must be an exposed column.

Pre- and post-processing in flow actions

When you configure a flow action with a pre-processing action, Pega performs the action whenever a user selects the flow action as well as each time the user is presented with the assignment. When you configure a flow action with a post-processing action, Pega performs the action each time you perform the action.

Configuring a GRS for a connector endpoint

When you configure a global resource setting (GRS) for an integration, you first create a class for the references to external systems. You place all GRS rules in the same ruleset as the integration rules. Next, you determine which environment references to external systems will use the feature. Then, you create a page property for each environment reference. Continue the process by creating a data transform to assign values to the environment properties using utility functions. Finally, you create a data page to tie these artifacts together.

Creating a SOAP service

When you have a requirement to implement a SOAP web service to expose your application to other applications, you do this by creating a service. SOAP web services communicate using the SOAP protocol and pass XML messages from one application to another. Your application needs to convert that XML message to Pega objects to process them and then convert those Pega objects back to XML after the processing is complete.

Rules Cache

When your application references a rule, Pega checks the rules cache for the referenced rule. If the referenced rule is not available in the rules cache, Pega uses a multiple-step process to populate the rules cache.

Pessimistic locking

With this locking strategy, an application applies an exclusive lock when opening an item, such as a case. A user or the system that opens the object gains exclusive access to the object until the application releases the lock. While the item remains locked, other users cannot edit the item.

Optimistic locking

With this locking strategy, an application does not apply an exclusive lock when opening an item. Instead, any user — or the system itself — can open and edit the item at any time. When the item changes, the application checks whether the item has changed before committing any changes.

Three common reports

Work reports Assignment reports History reports

Parallel processing

You can configure a stage to run multiple processes in parallel. This configuration allows users to perform tasks independently in order to complete the work in a stage.

Key uses for organizational records

You can define access groups available to operators at the organization or division levels. These access groups only apply if operators do not have an access group defined in their operator ID record. You can configure routers that send assignments to operators or work queues defined within the organizational structure. You can use manager data associated with the organization records in routing configurations, approval processes, and SLAs. For example, an operator ID lists a manager the operator reports to, and a unit record specifies a unit manager. The operator's manager can report to the unit manager. For example, you can route a purchase request to a manager if the amount is up to USD10,000. If the amount exceeds USD10,000, you can route the request to a unit manager. You can configure SLA configurations. Since each assignment contains the organizational data of the assigned operator, you can use the data to determine escalation actions to specific managers. For instance, if a purchase request is past goal, the case is escalated to the manager of the operator. If the case is past deadline, the case is escalated to the unit manager.

Class instances to include (components of a product rule)

You can include all instances from any class by entering a class name. In addition to concrete classes, you can enter an abstract class that has concrete subclasses. This section is useful for specifying data classes (derived from the Data- base class) that are required for an application to run correctly on the destination system. Remember that if you have selected the Include associated data check box in the Applications to include section or RuleSets to include section, all data instances associated with the rulesets are exported by default. Be careful to note any dependencies among data instances or between data instances and your rules. During import to the destination system, data instances already present are by default not overwritten. These data instances may require adjustment after import. You can use a when rule in the When filter field to filter the class instances that you want to include in the ZIP file. The ListView filter column is included for backward compatibility. If you select Include descendants?, all the subclass instances are included and the ListView filter and When filter values are ignored. Use the Exclude classes field to enter the names of descendant classes you do not want to include. You can enter more than one class using a comma (,) to delimit the names.

Nested branches (decision trees)

You can organize decision tree branches in a nested structure. Think multiple routes to get to a result

Class combination using joins and associations

You can relate properties in multiple database tables or classes to combine data in a single report. Use case and subcase relationships to show subcase data along with the parent case data. Use case and assignment relationships to show how the system processes assignments for a specific case or a subcase. Use case and history relationships to monitor performance. You create class or database table relationships in a report definition. You do not specify database tables to define joins. You can either configure class joins or you can reference association rules.

Creating associations and joins in reports

You can report on records in multiple classes mapped to one or more data tables. To create these reports, in a report definition you can reference an association rule or configure a class join.

Security (activities)

You can restrict how activities are called. Restrict access restricts the user at runtime and Activity type limits how developers can use the activity

Test for logic (decision tables/trees)

You can test the logic of a decision rule by entering test values and running the rule to observe the results. If you do not see the expected results, make sure that the properties and comparison operators are correct. To test for logic, on a decision rule form, select Actions > Run. The system displays a test page for entering test values. On the form, click Run Again after you enter each value as shown in the following example.

Replacing the Pega logo

You can update the icon displayed in the upper left corner of the portal. Standard Pega portals display the Pega icon. You can update the portal configuration to display a different icon, such as a company logo. To add an image or another non-text file to a Pega application, Pega creates a binary file record. A binary file record acts as a wrapper for the file, providing the security, inheritance, versioning, and deployment benefits of rule resolution. To update the icon displayed in a portal use App Studio, go to Settings > Theme, and upload a new logo. This instructs Pega to create a binary file to store your image. Binary files are organized in the Technical category in the Records Explorer and the Create menu.

activity (database updates)

You can use Obj-methods to read and write. This is subset of activity methods used to operate on one or more objects, rows, in a database table

Ruleset locking

You can use this feature to prevent changes using the Lock and Save button. Typically, you typically do this when development has reached a specific state, and the application is ready to be promoted to testing. You cannot add or update rules in a ruleset that has this feature enabled

Decision tree logic

You can use this to handle logic that returns a result from a set of test conditions. This can evaluate against different test conditions and properties. A true comparison can lead to additional comparisons.

Integration Designer in App Studio

You can view a list of simulated data pages, also called data views, from the Integration Designer. In App Studio, select the Data Explorer to open the Integration Designer. Select the Simulated icon in the system of record row to filter by the simulated data types and find all the simulated data pages quickly.

Examine Processors (admin studio)

You can view advanced statistics on each queue processor by viewing the data flow. Follow these steps to view the data flow for a queue processor. 1. On the Queue processors page, click the Actions menu icon to open the actions menu for the processors. 2. Select View Data Flow to open the Data Flow Work Item for that processor in Dev Studio.

Configuring case locking

You configure this from the Settings tab of the Case Designer in either App Studio or Dev Studio. Pega Platform provides two locking options for case locking. Allow one user is pessimistic Allow multiple is optimistic

Field Values (localization)

You define Field Value rules for those rule types that use labels or other text strings under 64 characters.

Configure a decision table

You first specify a property or expression in the Conditions column header. Then, on the first row, you enter a value in the column that defines the condition. Under the Return column, enter the result that the table returns when the condition evaluates to true. Finally, in the otherwise row, enter a value that the table returns if none of the conditions evaluate to true.

Mashup sizing

You may need to control the display size of your mashup to fit inside a defined area. To control the size of a mashup using the DIV tag, set the data-pega-resizetype attribute to customize the mashup width. By using the mashup attribute data-pega-resizetype, the mashup can fit inside a fixed space (data-pega-resizetype = 'fixed') or it can expand to fill the available space on the page (data-pega-resizetype = 'stretch'). By default, the value of the attribute is stretch. best practice it to make sure style='overflow:auto' to help scroll bars appear if DIV needs to stretch. If its set to that don't set other sizing attributes

Temporary changes to logging level setting

You may temporarily override the severity settings in the prlog4j2.xml file for the current node. When you make this temporary change, the prlog4j2.xml file is not altered. Logging on nodes other than your current node is unaffected. Your changes take effect immediately and remain in force until the server on the node is stopped, or until you or another developer uses the Logging Level Settings tool again to reset the logging level.

ABAC (Attribute Based Access Control)

You restrict access to specific instances of classes or to specific properties within instances independent of an access group role. This is enforced through access control policies. You define a set of policy conditions that compare user properties or other information on the clipboard to properties in the restricted class

Identifying the components of a product rule

You specify the components you want to export on the Contents tab of a product rule. The tab includes the following sections: Applications to include Rulesets to include Class instances to include Individual instances to include JAR files to include File details

Association rules

You use these rules to join multiple classes. Unlike a class join (unique to each report) associations can be reused in any report. Managers can also use associations when they create reports in the Case Manager portal Pega provides a set of standard that can be used for many class joins.

Split Join (parallel processing)

You use this shape to call multiple independent processes that operate in parallel and then later rejoin. Has multiple join conditions

Update my application (lock and roll)

You use this to include the new Ruleset Versions when you are rolling out an application and updating the minor version or when the application rule lists the ruleset patch version number. You may enter a new application description. The default application description is current. If the current application is locked, enter the application password.

Do not update my application (lock and roll)

You use this when you update the patch version number of a ruleset without updating the application ruleset list. By default, the application rule only lists the major and minor version numbers for a ruleset, so incrementing the patch version number does not require a change to the application rule.

RBAC (Role Based Access Control)

You use this when you want to restrict users roles to access only certain UI elements, to perform only certain actions in the UI, or to have any access to a class. Configured by defining roles with the desired authorization and privileges. one or more roles are then associated with an access group

Create a new version of my application (lock and roll)

You use this when: You want to lock and roll the version and create a new application rule. You may enter a new application version, if different than the default one increment higher. You may enter a new application description. The default application description is current. If the current application is locked, enter the application password. You want to allow people access to more than one version of the application (for example, during a phased roll-out or a test period).

Property reference in the page JavaScript

[gadget/gadgetName/property] Use the getGadgetData and setGadgetData actions to read and set property values in a mashup gadget. The getGadgetData action uses the syntax [gadget/gadgetName/property] to reference the property reference where gadgetName is the name of the mashup, and property is the name of a property used in a Pega application such as .pyID, pyWorkPage.pyID, or.pyWorkParty(operator).pyUserName. gadget is a keyword required by the getGadgetData action.

Value returned by a function in the page JavaScript

[page/function/token] To use the value returned by a function on the page JavaScript as the value of a mashup attribute or action parameter, use the syntax [page/function/token], where token is a string that has meaning to the function. Specify the function used to retrieve the value using the data-pega-event-onpagedata attribute.

Value of a DOM element

[page/id/elementID] To use the value of an element from the page JavaScript as the value of a gadget attribute or action parameter, use [page/id/elementID], where elementID is the name of the DOM element.

Reporting structure

a form a cascading approval that goes on a predefined list (need to verify what this custom levels thing is)

The requestor pool

a set of requestors reserved for use by the services in the Service Package. Requestor pooling often improves the performance of a service. Requestor pooling enables requestor reuse, shares allocated resources, and eliminates server wait time for requestor creation. Requestors associated with a pool belong in one of two categories: Idle requestors are currently in the pool, waiting for a service request. Active requestors are currently out of the pool, managing service requests.

Accessibility Inspector

allows you to identify and rectify accessibility issues with your application. The inspector has two main features that aid accessibility design. has disability preview. also allows you to audit your current application UI to identify configurations that may negatively impact application accessibility. The issue categories are: Content - For example, an icon is missing helper text or a label. Structural - For example, the heading level hierarchy is out of order, which can potentially confuse screen readers. Interactivity - For example, the skip to content navigation is missing on the harness, which prevents users from using the Enter key to navigate to the main content easily. Compatibility - For example, a tab group layout, which is deprecated, is used instead of a layout group.

Relevant records

are rules that have been marked for reuse automatically by Pega or manually by application developers in Dev Studio. More technically advanced developers might configure advanced behavior on a rule in Dev Studio, then mark the rule as relevant so that the rule is accessible by other developers from prompts in App Studio. Automatically tagged when created in Data designer or case designer Fields and Views lists are populated with relevant records

Accessibility roles

are specific attributes applied to user interface elements. They enable communication between assistive devices and Pega applications about UI elements.

Circumstance rules

are the particular rules set up to deal with particular circumstances has several different possible circumstance conditions 1. Single value 2. Multiple value (based on template and definition 3. Date property 4. as of date

Activity rules

automate processing. Created in Dev Studio. Sequence of steps. control returns back to the rule that called it after its done. Some best practices Keep it short, less then 25 steps Use alternatives whenever possible, such as data transforms Limit hand coded Java. Standard and custom rule types, library functions, or activity methods are available. Note that the step page could be like UpsellCandidates.pxResults That .pxResults is what is put after like a Obj-Browse method

Localization wizard

automates many of the steps necessary to create language-specific versions of your application. The Localization wizard identifies field values and text strings that are used in user interface rules. Text strings include labels, captions, Tool Tips, and instructions that appear in user-facing rules such as harness, section, list view, summary view, message, and portal rules.

the three ways of designating relevant records

by creating the record in App Studio, by marking as relevant from the record itself, or by adding records from the Relevant Records tab of the Application: Inventory landing page.

Obj-Save-Cancel (cancel/rollback operations)

cancels the most recent uncommitted Obj-Save method so that the instance is not written as part of a later Commit operation

external class

cannot belong to a class group. Instead it corresponds to a database table not administered by Pega. Each external class should be mapped to a unique database. Does not contain either the pzInsKey or pxObjClass properties. Those can be found in Pega rules and Pega data. What is used is the key column specified by the database table to identify unique rows instead Maps Pega properties to database columns. that correspond to the properties used in the application. Note it is possible to create declare expressions as this is in clipboard

Dashboard Widgets

changes the content displayed on the dashboard such as a case manager portal

Include associated data (settings rulesets to include product rule)

check box to include data instances associated with the selected rulesets.

Enterprise Class Structure

class hierarchy structure

Access when

configured at a specific class and instance level. consider the case of when you update goal setting only being allowed at specific times

Skins

contain instructions for formatting elements of the user interface, such as text size, font style, and background color. To customize the appearance of a portal, you choose between applying the application skin to the portal and configuring a skin for the portal. To apply this to the portal, rather than reusing the application skin, select the Other skin option on the Details tab of the portal record, then enter or select the skin to apply.

ALERTSECURITY log

contains alerts (identified by the prefix SECU) that suggest improper configuration of Internet Application Composer facilities, or overt attempts to bypass system security features through URL tampering.

Framework Layer

contains assets that can be extended in specific implementations. It may be comprised of one or more generalized applications, such as a standard Pega application for a specific industry, or an extendable custom application.

CLUSTER log

contains information about the setup and run-time behavior of the cluster.

ALERT log

contains performance-related alerts. Use the PLA tool to parse and summarize this file into a Microsoft Excel spreadsheet.

Organization layer

contains the assets used on an enterprise-wide basis. Such assets are rules for enterprise-wide business logic such as standard properties, decision tables, and service level rules.

Pega Platform Layer

contains the built-in assets necessary for processing cases and other work in Pega applications. This layer also contains the assets Pega Platform uses.

PEGA log

contains warnings, errors, and information messages about internal operations. This file, also referred to as the Console log or System log, is used for debugging the application. By default, it is filtered to entries that match the current operator ID.

Multiple-class mapping to a single table

create a database table for each case type, you can designate a class as a class group (also referred to as a work pool). Class groups cause the system to store instances of similar or related case types together in a single database table. If you create a report in a specific case type such as Candidate, your report returns only records in the case type. If you create a report in the class group, the report returns all instances in the classes that belong to the class group.

Styling a Pega Web Mashup

create a portal and assign the portal to the access group for web mashup users. Sometimes you may have it be intended for non Pega users. In this case configure the access group created for the mashup user to reference the portal. Create a portal skin to configure the application styling for web mashup users. Pega will use the skin rule associated with the portal rule. Can inherit from app skin. Can use other skin option if you want to change it. If you do edit the Harness class and name to match those associated with your mashup app and save your changes.

Configuring field values

create field value record for each allowed value consider localizations

Implementation layer

defines an application customized for a specific division or line of business. It may extend one or more framework layer applications

Navigation record

defines the entries in a menu and the action performed when a user selects the menu item. These are used to organize the menus displayed in standard portals such as the Case Manager and Case Worker portals.

Error handling flow

detects errors that are not detected in a data page or an activity. This feature is always enabled. The error handler flow allows you to implement a process for handling the error. It is typically used when the connector response is not required immediately — for example, when updating a legacy system.

Ruleset validation mode

each ruleset version defines one or more ruleset versions on which the ruleset version depends. If your ruleset version does not have any prerequisite ruleset versions, you need to specify the base product ruleset Pega-ProcessCommander as a prerequisite.

Situational processing

exceptions to typical case behavior

Delta Sync blacklist

excepts certain data pages from sync. Can skip backward chaining to improve speed

Configuring ABAC

first determine the attributes used for access control purposes. Then, define the access control policy condition that compares the object's attribute values to the user's. Finally, define the access control policy to specify the action that is controlled by the evaluation of the condition logic.

Dynamic System Settings

getDataSystemSetting This function reads the specified Dynamic System Settings from the database and returns it as a string.

JNDI Entry

getJNDIEntry This function does a lookup for the specified JNDI entry and returns the entry as a string. If the function is unable to perform the lookup, the function returns an empty string and writes an error to the log.

Java Properties File

getJavaPropertyFromFile This function loads the specified Java properties file and returns the value of the property specified in the function's Key parameter as a String. If the property cannot be found, the function returns an empty string.

Java System Property

getJavaSystemProperty This function returns the specified Java system property as a String.

Decision table logic

gives results when a all the conditions in a row are cleared and has a otherwise result if nothing is

ruleset list, sometimes referred to as the ruleset stack

governs rule execution at run time

Case locking

has a overwrite risk. two major types of locking pessimistic locking and optimistic locking

Production rulesets

have at least one unlocked ruleset version in the production environment. Commonly delegated rules. Configured on the application and access group

portal rule (record)

identifies the type of user expected to use the portal, the harness used to organize the portal contents and the skin that defines the branding applied to the portal. They are listed in the User Interface category in both the Records Explorer and the Create menu. technically classless

personal ruleset

if you are allowed to check out rules you get one of these Has the name of the operator ID and contains the rules checked out by the operator.

Configuring mashups

in Channels and Interfaces, enter a descriptive name, mashup description, and the URL of the system hosting the Pega Platform application under Basic options. All actions require you to specify the following the thread in which the action is performed A fixed or automatically-sized IFRAME The action prompt Optionally, Specify the skin used to format the mashup contents Encrypt traffic bewteen the web page and Pega Platform Defer loading of the mashup Select the skeleton used to organize the contents of the mashup

Property Inspector tool (the tracer)

indicates how the values changed.

Branch

is a container for rulesets with records that are undergoing rapid change and development. In Pega, you create one of these for each team. This allows each team to create and update rules without impacting other teams.

Dynamic System Setting

is a data record used to store environmental variables and are not part of a ruleset. Data records are editable even when rulesets are locked in production

Cache manifest

is a simple text file defined using an HTML rule form named pyCustomAppCache. Save that to your application ruleset, must be applied Data-Portal. If the name of the requested resource file uses a series of numbers in the src attribute such as webwb/filename_1234567890.xxx!!.xxx, use the <pega:binaryfile> element with the name and app attributes.

PegaRULES Log Analyzer

is a standalone web application that developers and system administrators can use to view summaries of console logs. Consolidates ALERT, PEGA, GC logs Performance, stability, memory use Often used for UAT user acceptance testing, stress testing, and immediately after deployment Note that each node on a Pega system produces the two log files of ALERT and PEGA

Persist Case step

is a type of automation that persists a case could be called a smartshape

BIX Log

is created by the Business Intelligence Exchange during extract operations. It is an optional add-on product that provides the extract functions of an ETL (extract, transform, and load) utility.

Step Page

is the page in memory on which the method is processed. Default is context which it was called. Can be set to another context but needs a reference to the page in the Pages and Classes tab of the activity form

Merge Branch Rulesets wizard

is used to move branch contents into the base rulesets. helps identify conflicts

Obj-Open or Obj-Open-By_Handle (read from a database)

loads an instance of a class stored in either the PegaRules database or an external database. Both methods create a clipboard page for the open instance.

SERVICES-PAL log

log contains performance data saved from services.

Marking relevant records inactive

on the Relevant Records tab, select the record of interest, click the Actions menu, and select Mark as inactive.

Obj-open (read from a database)

opens the object you read

The Generate Mashup code option

option opens a window that provides the necessary HTML for you to copy, paste, and view within the web page. You can modify the code to meet the specific needs of the web page or to customize the appearance of the mashup, for example, setting the width of the mashup. is HTML5-compliant Clicking Generate mashup code creates the mashup code, which you can copy into the web page using any text editing. After saving your work in the web page, refreshing the page displays the resulting mashup.

screen layout

organizes the elements of the browser window into a main content pane and smaller surrounding panes.

Harnesses

organizes the structure of a portion of the user display. In Pega, you use it to organize either a work form or a portal. 4 common standard ones are New: Supports the creation of new cases. Perform: Enables users to select a flow action to perform to complete an assignment. Review: Presents an assignment in read-only mode, preventing data entry. Confirm: Presents a read-only confirmation of completion of an assignment if the next assignment is not performed by the user.

Analyzing applications with the Database Trace

produces a text file containing the SQL statements, rule cache hit statistics, timings, and other data that reflect the interactions of your requestor session with the Pega Platform™ database or other relational databases. Familiarity with SQL is not required to interpret the output.

Keywords and notations (database updates)

provide two way mapping between Pega features --such as clipboard, Database Name instances, and Database Table instances -- and the tables, rows, and columns of the external database. Employ the syntax in Connect SQL form Data Mapping (see online sources for further) A dynamically created WHERE clause can add flexibility to SQL connections. (see online sources for further)

Pega mobile preview

provides an approx of the user experience on mobile devices

Multivariate circumstancing (template)

refers to records that you circumstance by more than one property. Seems just like multiple properties

Queue Processor

replaces agent rules with standard configuration. Tasks can queued using either a Run in Background smart shape or the Queue-For-Processing method in an activity. Tasks can be queued immediately or the queue can be delayed. Run a specified activity on the queued item Automatically manage the read/write transactions on database object 1. when to process immediately or delayed 2. scaling vertical or horizonal, number of threads or nodes 3. standard or dedicated Makes paremeters differ. Standard specify the activity to run on the queued item. Choose a locking option. Specify an optional access group to establish context (optional) Dedicated specify the queue processor. For delayed queuing, provide a Date time property for the queued object, at which time the system processes the queued item

The IACAuthentication activity

requires that the HTTP request provides the following information to create an Operator ID. pyuseridentifier - Operator's identifier pyusername - Operator's full name pyorganization - Operator's organization name pyorgdivision - Operator's division name pyorgunit - Operator's organization unit name

FUA first use assembly

run a process immediately before taking performance readings

Ob-Save (save to a database)

saves the contents of a clipboard page to the database Note that this immediately writes the object to the database only if the Writenow parameter is selected. if its not then Obj-Save becomes a deferred save A valid read to perform a WriteNow is the need to immediately reread the instance before issuing a commit

Obj-Browse (read from a database)

searches the database, retrieves multiple records, and copies them to the clipboard as an array of embedded pages

Associating data instances with rulesets

simplifies application migration and maintenance. When you package an application for migration, you include an application's rulesets. However, a ruleset corresponds to a collection of rules and does not include data instances such as operator IDs, access groups, database tables, and databases. To help make packaging and migration of data instances easier, you associate data instances with rulesets. By doing this, you do not need to specify each data instance in the product rule. When you create the product rule, the system automatically adds the data instances to the archive file automatically. As a best practice, associate data instances with rulesets. As you create data instances of certain classes, either manually or with a wizard, the system automatically associates the instance with one of the application's rulesets. The associated ruleset appears in the rule header. The following example provides an access group that is associated with the Purchasing ruleset. You can change the associated ruleset by clicking Edit. Update the ruleset in the Associated RuleSet pop-up dialog. Can be removed from operator ID to avoid automatic export

Class and access of role to object (ARO)

specifies whether user roles have access or no access for each of six functions open, modify, delete, perform, reports, and history

Obj-Refresh-and-Lock (read from a database)

tests whether a clipboard page is current and if a lock is held if the object is not locked, the activity acquires a lock and refreshes the page if it is stale

The New Application wizard creates the initial application rulesets.

the created rulesets include two rulesets for the application itself and two organizational rulesets.

Localization

the process of adapting a product or service to a particular language and culture so that it takes on a local look and feel

As of date (circumstancing)

the rule variant is effective after a certain date, or during a range of dates. After the specified date or during the specified range, the application applies the circumstanced variant of the rule, rather than the base rule.

Multiple Value (circumstancing)

the rule variant is effective whenever a combination of property values satisfies the circumstancing condition. Multiple value circumstances are based on a circumstance template and circumstance definition. The circumstance template defines the properties on which to circumstance a rule. The circumstance definition defines the combination of conditions in which a property uses a variant of a rule. You apply the circumstance template and circumstance definition to the rule variant. If the case matches a combination in the circumstance definition, the application uses the circumstanced variant of the rule, rather than the base rule.

action area

there is where pega shows the selected flow action

Availability = Not Available

this availability indicates the rule may not be used during the rule resolution process. When a rule set to this is found in the rule cache created during the rule resolution process, the rule in the next-highest version is considered for rule resolution.

ARO

this record defines the access control settings for instances of a specific class. Each identifies the set of actions that a role can perform on instances of the specified class. Unique object record to the users in a particular role

ancestor tree

this refers to a rule's inheritance. Basically another way of saying it

Designing reports with multiple sources

three major techniques subreports class joins reusable association rules

Exclude non-versioned rules (settings rulesets to include product rule)

to exclude rule types that are associated with a ruleset but not with a version, such as class and application rules.

Include associated data (setting applications to include in product rules)

to export any data instances associated with the application ruleset automatically. Instances selected in the Individual instances to include section are not used. Typically, these data instances are derived from the Data- class and include operator ID, access group, database table, and database records.

Delta mode (setting applications to include in product rules)

to include only the current version of the application's rulesets in the archive file. For example, if your application references OrderEntry:02-03-05, the archive file produced from the product rule includes only rules in OrderEntry:02-03-05. This feature is useful when you are migrating a patch update.

Include rule history (setting applications to include in product rules)

to include the instances of History-Rule class. The instances are rows in the standard history rule table. These instances in the History tab of a rule include the date, time, operator, and comments that are added when a developer checks in a rule. This information can be useful for auditing purposes when migrating applications to another development or testing environment.

Include data types (setting applications to include in product rules)

to include the instances of the custom data types (classes) that you have created for your application. For example, you may have created a Customer data type to manage customer contact information. This data type might include information such as the customer name, email, or phone number. The data types are exported even if they are not associated with a ruleset.

Custom/Production rulesets (setting applications to include in product rules)

to include the production rulesets listed on the application rule automatically. Select this check box if you are using delegated or localization rulesets (these are production rulesets).

Addressal of errors returned by a connector

two types Response data transform in a data page Transition condition in an activity You can use a transform or just let the error handler flow get it if the response to be returned by the connector is not immediately needed for further processing. By default, connectors use the standard ConnectionProblem flow. The flow can be copied and customized. You may also choose to create an alternative error handler flow.

Transient errors

typically do not last long; they correct themselves over time. For example, the connector is unable to connect because the application is being restarted and is temporarily unavailable

Permanent errors

typically due to a configuration error or an error in the remote application logic. For example, an invalid SOAP request is sent to a SOAP service. In this scenario, the error persists until the SOAP request message is fixed.

SQL Connect rules (database updates)

used to execute a SQL command or stored procedure. Could be used to invoke Connect SQL rules from an activity using RDB methods. provides four tabs to enter SQL statements that execute during performance 1. Open 2. Delete 3. Browse. Note the history tab provides information about rules history Useful for SQL statements that contain vendor specific syntax and executing complex SQL statements such as a join or stored procedure against an external database

Access Deny

used to explicitly deny access to an action for instances of a class, used mostly for policy needs An Access Deny record overrides an Access of Role to Object record applied to the same class and role.

Model operator (Pega Web Mashup)

using information in the HTTP request header to create an operator ID record for the user.