Pega Cloud Services support for the AWS Asia Pacific (Mumbai) region
Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) Asia Pacific (Mumbai) region. Deployment across multiple availability zones within a geographical region protects against zone faults and localized service disruptions, and ensures high availability.
For more information about regions and availability zones, see Pega Cloud Services capabilities.
New My Pega Cloud portal with enhanced functionality available
You can use the My Pega Cloud self-service portal to restart an environment, download log files, or view high-level details about an environment. For more information, see Managing Pega Cloud environments from My Support Portal.
To access this portal, you must have the appropriate site credentials. To manage your support contacts, see the Support Contact Administrator Guide for additional information.
Archival support added to cases in Pega Cloud
Valid from Pega Version 8.1
You can now create an archival policy to move inactive cases from Pega Cloud to secondary storage. By periodically purging entries from your database, you can improve application performance.
For more information, see Case archiving.
Support for Data streaming service for Pega Cloud Marketing 7.4 applications
Valid from Pega Version 2.1
Pega Cloud Marketing 7.4 applications support the Kafka-based Stream service featured in Pega Platform 7.4.
Enhanced support for the Kibana platform
Pega Cloud Services began running Kibana 4.6.x. In addition to this version update, the Kibana viewer now includes:
- “DEBUG” level messages in PegaRULES log
- The PegaRULES-SecurityEvent log
Pega Cloud Services support for the AWS EU (Paris) region
Valid from Pega Version Pega Cloud
Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) EU (Paris) region. Deployment across multiple availability zones within a geographical region protects against zone faults and localized service disruptions, and ensures high availability.
For more information about regions and availability zones, see Pega Cloud availability and resiliency.
This additional region is available as of QI 2019.
Automatic redirection to HTTPS for Pega Cloud Services environments
Valid from Pega Version Pega Cloud
Pega Cloud Services now redirects HTTP to HTTPS automatically for applications that run in Pega Cloud Services environments. This automatic redirection ensures that your network traffic is always encrypted.
Pega Express methodology in App Studio for successful Microjourneys
Valid from Pega Version 8.4
App Studio now supports the Pega Express™ methodology to help you visualize the key factors of your Microjourneys™ - case types, personas, and data objects. With Microjourneys, you can analyze and clearly communicate who the parties that interact with your cases are, what channels of communication they use, and what data they need to resolve a case. Associating personas and data objects with case types also helps you manage your development team's workload by using a list of the draft elements that they need to develop.
For more information, see Plan successful microjourneys in App Studio (8.4), Creating a microjourney for customer success.
Upgrade impact
During a Pega Infinity™ upgrade to 8.4 and later, clients using App Studio are asked to update their applications to support use of the Pega Express™ methodology. Without this application update, the Persona landing page and Data objects and integration landing page are empty. For more information, see Pega 8.4 Deep Dive: Pega Express methodology in App Studio.
What steps are required to update the application to be compatible with this change?
In order to utilize the Pega Express methodology in App Studio and use the Inventory page, click Start now to complete the update of your application and add the required rules to it. If you choose to cancel, App Studio continues to work as expected without the Pega Express methodology features; you can click Start now at the top of your application overview page at any time to install the required rules in your application.
Relationships between elements of Microjourneys in application inventory
Valid from Pega Version 8.4
A new Inventory page in App Studio helps you manage a delivery of your projects by giving you an overview of the elements of your application and how they interact with your Microjourneys™. The new Inventory page lists draft relationships between the case types, personas, and data objects that you want to implement through development. By checking releases that correspond to the items that you need to develop, you can prioritize your work accordingly.
For more information, see Plan successful microjourneys in App Studio (8.4), Creating a Microjourney for customer success, Managing application inventory.
Upgrade impact
During a Pega Infinity™ upgrade to 8.4 and later, clients using App Studio are asked to update their applications to support use of the Pega Express™ methodology. Without this application update, the Persona landing page and Data objects and integration landing page are empty. For more information, see Pega 8.4 Deep Dive: Pega Express methodology in App Studio.
What steps are required to update the application to be compatible with this change?
In order to utilize the Pega Express methodology in App Studio and use the Inventory page, click Start now to complete the update of your application and add the required rules to it. If you choose to cancel, App Studio continues to work as expected without the Pega Express methodology features; you can click Start now at the top of your application overview page at any time to install the required rules in your application.
Consistent search experience in App Studio
Valid from Pega Version 8.5
Pega Platform™ now supports a unified search mechanism in App Studio. Instead of manually locating a single item, such as a case type, a channel, or a data object, you can simply use the Search option in the navigation pane. You can also use Search in case types and personas landing pages, to conveniently access the information that you need, for example channels and case types associated with a persona.
For more information, see Plan your Microjourneys more conveniently in an improved Case Designer (8.5), Creating a Microjourney for customer success.