@delee the question as to what file formats are (or aren't) supported to be imported into Pega is a bit besides the point, in my opinion. It would be great if you could ingest the latest BPMN format into Pega, but where does that get you? Several years ago, I was involved in a large corporate effort to import thousands of ProVision business models into Pega. While we were eventually successful ingesting models in CIF format the results was just thousands of flow rules in Pega. Now what? Everyone who's ever worked in Pega knows that flows are but a small component of BPM. At Pega, the case is at the heart of the application. Case types are organized hierarchically, i.e. the main case usually has child cases that are created at certain events. Every case type is defined as a series of steps and stages; every step represents a sub-flow. Flows, in turn, have flow shapes such as assignments, decision steps, utility steps, connectors, and a dozen more. Assignments have routers (determining who is going to perform the step), as well as SLA's and can have multiple outcomes. Most importantly, assignments are associated with harnesses and sections, the building blocks of the Pega UI.

Importing CIF files and creating flows didn't get us far at this Pega client. We ended up with flow rules, but we had no case types let alone a case hierarchy to put them into. We had to manually create the case types, and the stages and steps that went with them. We had to create decisioning rules, SLA rules, plumbing such as activities and connectors, and most importantly: the UI. In short, we ended up using the flow rules as blueprint for stages and steps, but we never directly used the flow rules we had created. The flows ended up as documentation artifacts.