​Provides a robust management console so you can easily orchestrate, manage and prioritize the queuing of work and processing activity for Pega software robots. Dashboards, reports and drill-downs monitor robot health, work status, SLA compliance, and auditing.

​Provides an automation authoring experience designed for rapid development and delivers the most powerful application automation and integration capabilities available today. The visual design surface makes it easy to create workflows and apply business rules through shapes or by recording workflows. 

Intelligence and robotic automation help enterprises maximize the value of their two biggest investments, people and technology, by understanding how users interact with applications. Pega robotic process automation, desktop automation, workforce intelligence, and case management together to enable more productive employees and a better customer experience. Unlike RPA-only solution providers, Pega offers end-to-end Robotics, CRM, and BPM for any digital enterprise,  giving organizations the power to:

• Identify workflow inefficiencies: As a first step, businesses can quickly and more easily analyze their employee workflows to uncover processes that are causing disruption in customer experience, such as needless and error-prone data rekeying across different apps. This visibility helps pinpoint inefficient processes that could be prime candidates for robotics to digitally transform their operations.
• Automate desktop processes: CSRs suffering from application overload can now benefit from desktop applications operating in a single seamless process—moving data between applications where APIs don't exist. Solutions can be deployed in weeks, quickly simplifying the employee experience, which leads to a better customer experience.
• Reduce repetitive tasks: Outside of customer service, many high-volume, low-complexity tasks traditionally done by employees can now be automated without the need for human intervention. Robotic process automation enables these processes—from reviewing claim details to updating transaction systems—to be run unattended, further freeing representatives to meet the needs of their customers.

Pega provides the only software automation solution capable of simplifying desktops and boosting productivity while enabling full automation of end-to-end processes.

With PRPC Multitenancy, tenants share the entire infrastructure including hardware, database, application server, PRPC applications and frameworks.
This architecture offers significant operational and administrative savings through the reuse and sharing of the application assets. In contrast to a standalone PRPC system, each tenant has access to shared resources and content from which tenant-specific customizations can be made.
​
​When a tenant customizes shared content, it becomes tenant qualified and can only be viewed and used by that tenant.

New landing pages enable a multitenant provider to easily create and manage tenants. Tenant provisioning is fast and customizable with PRPC activities.
​
All tenant administration capabilities can be managed using SOAP services. The remote management capabilities make PRPC Multitenancy well suited to and useful for cloud-based operations.

Summary
Use a data transform (known before PRPC 6.2 as a "model rule") to define how to take source data values — data that is in one format and class — and turn them into data of another format and class (the "destination" or "target").

What a data transform does
​Generally speaking, a data transform defines how to take source data values — data that is in one format — and transform them into data of another format (the "destination" or "target"). In PRPC, you can use a data transform to:

• Normalize data for use with a data page.
• Define, copy, or map data with activities.
  • Copying a clipboard page to make a new page.
  • Mapping properties (and their values) on one page to another, existing page.
  • Mapping properties (and their values) on one page to a new page.
  • On a given clipboard page, defining one or more initial properties on that page and setting their values. A data transform can set many property values on a page in one processing step.
  • Appending pages from one Page List property to another.

Using a data transform speeds development and is easier to maintain than setting property values with an activity, because the data transform form and actions are easier to understand than the activity form and methods, especially when the activity includes custom Java code. We recommend using data transforms instead of activities for normalizing and delivering your application data.

A data transform is a structured sequence of actions. When the system invokes the data transform, it invokes each action in turn, following the sequence defined in the data transform's record form.

The Data Transform record form
​On the data transform's Definition tab, the actions to be taken are presented as a sequence of rows in a tree grid. Except for the conditional types of actions (such as When, For Each Page In, and similar actions) and transitional actions (such as Exit For Eachand similar actions), the system invokes each row in sequence, starting with the first row.
In the example below, the data transform CopyShippingInformationToBilling maps data from the shipping information for an order to the order's billing information.

​ColumnDescriptionActionAn action to be taken. 
TargetA target, if the action requires a target.
RelationA relation, if the action requires a relation to be specified. This relation is a relationship between the specified target and source.
SourceA source, if the action requires a source.

In this post, i would introduce in brief as to what Pega’s CPM framework is about.
Pega Customer Process Manager (CPM) is one of the products in Pega’s CRM suite of solutions. This framework is primarily to guide Customer service representatives (CSRs) in processing customer service inquires and requests from initiation through resolution. In effect, it helps CSR’s to view complete information about the customer in a single view, take customer queries and initiate a workflow process to resolve them. These customer queries are known as ‘service intents’ in pega parlance. 
There are few terminology used in CPM framework that you should be aware of –
1. Composite – this is the area where you view the 360 degree of the customer. Pega’s integration services are used to connect with external systems to retrieve information and thereby shown in separate sections in the composite area
2. Service intents – these are the customer inquiries that i mentioned of. In an OOTB CPM framework, you would see the following service intents. 

The usual flow is that when a customer calls up a CSR, the CSR would ask for his account information, that could be the customer ID, etc. Post this, the CSR would verify the identity of that person by asking few questions. On successful verification, the CSR sees the complete information of the customer. This is to help the CSR view what are the previous complaints, or queries, or services that were requested by the customer. In the above table, within account category, a customer could request for address change. The CSR would launch this service and complete the request.
3. Dialog scripts – The intention of dialogs is to assist CSR in the flow. Basically, these are nothing but scripts that appear along the interaction with the customer. For example – when a customer calls the CSR, the system will show up a dialog saying ‘Hello Mr. XXX, How can i help you today?’ 
Few screenshots to drive the story –

Pega 7 provides two case locking options and capabilities. You make your basic configurations in the Case Designer at the top-level case type. The settings cascade to all the subcase types.

• Default locking – When a case is opened in a Perform harness, it and its parent case are locked. Only one user can view and update the case at a time. You can override the default behavior at the each subcase type level.
• Optimistic locking​ – Multiple users can open a case in a Perform harness at the same time to review or update it. The first user to submit an update "wins;" users who had updated the form but had not submitted changes must refresh the form, re-enter their updates, then submit them.

This article describes how these locking strategies work and how you configure them in the Case Designer.

Approach
To begin, open a top-level case type in the Cases Explorer and open the Details tab. On the Locking option, click the Edit link.

Default Locking
​
Sets to standard locking behavior; the system locks a case when it is opened by a user for a period of up to 30 minutes. No other user can open or work on it. You can change the standard time period in the Custom timeout field.
This conservative approach helps ensure that data can be updated in both parent and subcases with transaction integrity. For example, the parent case may contain properties that count or total values in the subcase. Locking both at once helps keep these counts or totals in sync.
Overriding default lockingIf default locking hampers user throughput in your application, you can override the setting at the subcase level. This lets users concurrently make updates to both parent cases and their subcases without conflict.

To override default locking:

1. Open the subcase type in the Case Designer's Details tab.
2. Open the Locking pop-up dialog.
3. Select the Do not lock the parent case when the child case is being performed checkbox and click the Save button.

Optimistic lockingThe top-level case and all of its subcases can be opened in a Perform user form by multiple users for reviews or updates. This setting applies to all subcases and cannot be overriden at the individual casetype level.

When the first user submits or saves an update, other users who have also opened the case and attempt to submit their updates receive a message indicating that the original form and its data have already been updated; therefore, they cannot submit their updates. In these situations, users can:

• Close their case without submitting the changes.
• Refresh the form to see the other user's updates before submitting their own updates. Users cannot commit changes without using the review option.

Considerations
​In most configurations, use default locking in order to preserve transaction integrity among cases. Optimistic locking may be called for where multiple users need only open and review cases without having to perform updates.

• If it is likely that a multiple users will attempt updates to cases in one or more case types, frequent update conflicts will likely not be desirable.
• Agents and services such as SLAs and bulk actions can update a case that is being worked by an operator. When the user attempts to save work, the update will fail.
• It is possible to create a condition that accepts updates from two operators at same time, although one user's work will not be committed. Audit trail entries for both updates may be present and might actually interleave.
• If a subcase update attempts to update its parent, the system briefly locks the parent to effect the update. If the parent is locked, the updates are queued until a lock can be obtained.

Use the Queue instruction to start asynchronous execution of a second activity. This provides an alternative to the Call instruction, in situations where there is no need to wait for completion of the second activity, or where processing in parallel is feasible and beneficial

BRANCH -- Branching to another activity.Use the Branch instruction to cause the current activity to find another specified activity and branch to it without a return.When the branched activity ends, processing of the current activity ends also; no steps after the Branch step are executed.CALL -- Calling another activity
COLLECT -- Begin execution of a collection rule 
FLOW-NEW -- Start a flow execution
JAVA -- Using Java in an activity step
QUEUE -- Execute another activity asynchronously
RULE -- Using the Rule instruction to implement a custom rule type(Rule instruction is deprecated)

Note:  Rule instruction is deprecated. Instead, call the evaluate Rule activityUse the Rule instruction to cause the current activity to find another activity named evaluateRule that implements a custom rule type. When this instruction executes, control transfers to that activity.