@AMITTUTUN Thanks for reaching out. You would need to move to the next step and pick the technical documentation which are generated. You should be able to find those documents in your S3 bucket where you have hosted your source code which was consumed by transform. In the S3 bucket, there should be a “transform-output” folder. There would be folders for each job you have ran labeled by job id. if you dig into a jobid directory, you’ll find the documentation that is in both pdf and xml format. You can select the PDF files as input while creating your Blueprint.
@SumanKumarThanks for the reply. In a big project that means we have several files that needs to be uploaded. Is there any limit how many files can be uploaded. If yes, then do we need human touchpoint to judge what files that are need to be uploaded. Do we have any documentation for mainframe migration to pega so that we can have a direction of how to leverage AI and features of blueprint for migration.
@AMITTUTUN We have a limit of 15 files. You can combine and create larger documents as well. When documents are too large, Blueprint takes care of breaking them down. To know more about the mainframe app modernisation using Blueprint, you can have a look at this article: The new methodology for mainframe modernization.