When you deploy the oc-cn-op-job-helm-chart Helm chart to create the PDC WebLogic domain, it now creates the following PDC groups:

• PricingDesignAdmin: This group's users have administrative privileges on PDC. They can perform operations on all PDC UI screens, pricing components, and setup components.

• PricingAnalyst: This group's users have administrative privileges for pricing components and view-only privileges for setup components.

• PricingReviewer: This group's users have view-only privileges for all pricing and setup components.

When you create PDC users, you add them to one of these groups to control their access to PDC operations. For example, to create a user that can perform all operations in PDC, you can configure these new values.yaml keys for the oc-cn-op-job-helm-chart Helm chart:

ocpdc:
   wop:
      users:
         name: JohnDoeAdmin
         description: New Pricing Administrator
         password: EncodedPassword
         groups: PricingDesignAdmin

For information, see "Creating PDC Users (Release 15.0.1 or later)" in BRM Cloud Native System Administrator's Guide.

PCC now supports WebLogic Kubernetes Operator for its cloud native deployment.

For more information on the configuration and testing of the PCC's integration with the WebLogic Operator for cloud-native environment (CNE) deployment, see "Configuring Pipeline Configuration Center" in the BRM Cloud Native Deployment Guide.

The BRM cloud native documentation has been updated to include instructions for doing the following:

• Optimizing the PDC system's CPU and memory usage for requests and limits during runtime. See "Using Resource Limits in PDC Domain Pods" in BRM Cloud Native System Administrator's Guide.

• Changing the language displayed in your PDC UI screens, XML import files, and XML export files. See "Managing Language Packs in PDC Pods" in BRM Cloud Native System Administrator's Guide.

• Migrating PDC from an on-premises release to a cloud native release. See "Migrating from PDC On Premises to PDC Cloud Native" in BRM Cloud Native Deployment Guide.

• Setting up ingress and egress flows for ECE cloud native deployments. See "Setting Up ECE Cloud Native Ingress and Egress Flows" in BRM Cloud Native Deployment Guide.

• Performing a zero-downtime upgrade of a BRM cloud native active-active disaster recovery system. See "Performing Zero-Downtime Upgrades of Disaster Recovery Cloud Native Systems" in BRM Cloud Native Deployment Guide.

• Creating, editing, deleting, and retrieving custom storable classes and storable class fields in your BRM cloud native database. See "Creating Custom Fields and Storable Classes" in BRM Cloud Native System Administrator's Guide.

BRM cloud native images are now available on Oracle Container Registry (https://container-registry.oracle.com).

For more information, see "Pulling BRM Images from the Oracle Container Registry" in BRM Cloud Native Deployment Guide.

BRM cloud native includes the following enhancements:

• BRM cloud native now supports Podman for building container images.

• The real-time and batch rating engines now support SSL-enabled communication with BRM.

• BRM cloud native now supports the BRM SDK, which allows you to make and compile customizations for your BRM system.

For more information, see BRM Cloud Native Deployment Guide.

You can now use Kubernetes jobs to do the following during ECE runtime without requiring you to restart ECE pods:

• Reload configuration information from the charging-settings.xml file into ECE cache

• Change grid-level logging options

For more information, see "Changing the ECE Configuration During Runtime" in BRM Cloud Native System Administrator's Guide.

PDC cloud native includes the following enhancements:

• Deploying and configuring Pricing Design Center cloud native services no longer requires manual post-installation tasks. These tasks are now automated in the PDC cloud native deployment process.

• PDC cloud native images have been decoupled from Fusion Middleware images, reducing the overall size of the PDC images. To use PDC cloud native, you now download the Fusion Middleware images and provide their location in your PDC override-values.yaml file.

For more information, see "Configuring Pricing Design Center" in BRM Cloud Native Deployment Guide.