Hi community,

I have a question regarding how Pega created the OpenAPI specification (particularly the YAML) documentation in the OpenAPI tab of a Service. We are using this document to provide service specification to a 3rd party app that will use it to define the Pega service in that system.

The issue we have is the naming of the schemas in the YAML documentation, which includes some text "PEGA_INTERNAL", as below. The consuming service sees this as the name of the object, and classifies every schema as "PEGA_INTERNAL" in their system, making them difficult to distinguish.

As per the below example, we would like it to be something like "Customer" rather than "PEGA_INTERNAL", but cannot find a way of changing this, or even work out how it is being generated for clues.

Example:

RULE-OBJ-CLASS.MyOrg-MyApp-API-DATA-CUSTOMER.XML.false.PEGA_INTERNAL:       title: "MyOrg-MyApp-API-Data-Customer"       type: "object"       properties:         CREATION_DATE:           title: "CREATION_DATE"           type: "string"         CUSTOMER_ID:           title: "CUSTOMER_ID"           type: "string"         CUSTOMER_NAME:           title: "CUSTOMER_NAME"           type: "string"         CUSTOMER_NUMBER:           title: "CUSTOMER_NUMBER"           type: "string"