OpenAPI specification import to create data types

Blueprint and App Design
1

Dear Team,

I’ve observed that importing OpenAPI specification YAMLs into Blueprint to generate data types works reliably only for smaller specs. When attempting to import a larger spec containing around 80 data objects, the process stalls. To work around this, I had to split the spec into smaller chunks, which did import successfully. However, Pega treats each import as a separate System of Record (SOR), requiring manual reassignment of the System association afterward.

The main issue now is that cross-references between data types are not recognized during the import process;primarily due to the spec being chunked. As a result, the associations between objects remain incomplete. While these can be manually corrected, it would be highly beneficial if Pega could better support large OpenAPI imports with interlinked object references.

Any guidance or suggestions on how to handle this more effectively would be greatly appreciated.

Best , Midhun

2

Hello @MidhunKrish,

Thank you so much for sharing your feedback and bringing this issue to our attention. We truly appreciate your efforts and understand how important it is for your team to be able to import Open API Specifications smoothly.

We will work on improving this experience so that you will be able to import large OAS files without issues. Additionally, we are working on functionality that will allow users to import specifications while continuing to use existing SORs. This will help ensure you don’t have to manually reassign the SOR when importing in chunks, as you had to do in this situation.

Thank you for your cooperation.

3

@nvkap Thank you! Highly appreciate it.