Format and validation issue for OpenAPI specification generated for the REST services in YAML format using latest feature in Pega
We are on Pega 8.7. We are leveraging the automatic swagger generation feature for REST APIs.
The swagger payload is created via request mapping while creating REST service in Pega. For case creation, we are using the JSON data transform to map the request body. This generates the OpenAPI specification for the API in YAML format. The same is used to publish the API to API management platform of the customer (in this case, it is Azure APIM).
The OpenAPI specification (OAS) generated by Pega was validated by customer’s integration COE. We received the below feedback.
1> The OAS does not include a working example
2> The OAS does not include validation rules. (e.g., there are dates in the swagger without proper date-validation rule)
Did anyone use this feature and have come across these scenarios?
Question to Pega product team: Is this capability available in 8.8 or planned in future version of Pega.