Close popover

Table of Contents

Customizations in client Pega Cloud Services environments

Pega requires that clients leverage Pega Platform™ for customizations in their Pega Cloud® environments. This ensures you are able to keep your application current with the latest Pega Platform and Pega Cloud features and functionality.

Pega Cloud does not support customizing Pega Cloud environments outside the use of Pega Platform, because these types of customizations can impact your application performance, reliability, and compatibility with future releases.

Pega Platform offers robust functionality for customizing your Pega Cloud deployment. Review the following examples for supported methods to expand Pega Platform capabilities to meet your specific needs. If your deployment needs a customization that is not currently supported in standard Pega software functionality, you can request Pega to include such functionality in future Pega software releases by selecting New request in My Support Portal or call the Pega Support Contact Information hotline listed for their region. For the latest documentation on making requests, see My Support Portal: New Design, Streamlined Features.

Additional connection parameters for external databases

Pega Cloud Services only support additional connection parameters for external databases; Pega Cloud Services cannot apply additional connection parameters to the internal Pega Platform database. This includes connections to the PegaDATA, PegaRULES, and PegaRULESReadOnly schemas.

You can request to add additional connection parameters specific to your external-database vendor by contacting your regional Pega Support representative by using the Support Requests tab in My Support Portal. The additional database parameter goes into effect upon the restart of your Pega Cloud environment.

For more information about parameters for your external database, refer to your database documentation.

For more information about configuring connectivity parameters for external databases, see Configuring connectivity parameters for an external Pega Platform database.

Internal JNDI servers and JMS resources for usage in Messaging Service models

You can request to add a JNDI server or JMS resources for usage in a Java Messaging Service model in your instance of Pega Platform by using the Support Requests tab in My Support Portal. The internal JNDI server and JMS resource goes into effect for usage in your JMS model upon the restart of your Pega Cloud environment.

For more information about using JMS resources and internal JNDI servers in your JMS model in your instance of Pega Platform, see Messaging Service Overview.

Custom Login Screen

You can edit your application login screen to display a new logo or background image for your application, to maintain design consistency according to your enterprise style guide, or to change the single sign-on button appearance.

To create a Custom Login Screen, follow the steps provided in Customizing login screens for your Pega application.

Role-based Access Control

You can configure Pega Platform to access external systems to retrieve data and perform application processing. Similarly, you can allow external systems to access services in Pega Platform.

To configure role-based access control, follow the steps provided in Controlling access to and from external applications.

Setting Log Levels

With Pega Platform, you can set log levels for categories and for individual loggers. For more information on how to configure this, see Understanding logs and logging messages.

Managing X.509 Certificates

Beginning with Pega Platform 8.4, you can import your X.509 certificates directly into the Pega Platform truststore in order to authenticate external server hosts.

For details on how to configure this, see Managing X.509 certificates.

Custom Fonts

Pega Platform supports importing web fonts for use in your Pega application. For details on how to configure this, see Customizing fonts for your Pega application.

Custom Java archives and classes

You can incorporate third-party Java functionality into Pega Platform by importing a Java archive (JAR) file or class.

The Client assumes all responsibility for files imported into Pega Cloud. Pegasystems Inc. is not responsible for clients importing files that may contain malicious code. The Client can refer to the Pega Cloud Acceptable Use Policy to understand the client responsibilities model.

For support details and step-by-step instructions, see Importing custom Java archives and classes.

Custom XML files for input streams

You can use custom XML files for use as an input stream by importing the XML files as a Java archive (JAR) and extracting the files using an activity. 

The client assumes all responsibility for files imported into Pega Cloud. Pegasystems Inc. is not responsible for clients importing files that may contain malicious code. The client can refer to the Pega Cloud Acceptable Use Policy to understand the client responsibilities model.

For support details and step-by-step instructions, see Importing custom XML files for input streams.

Suggest Edit

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.