A lot of information concerning this and other migration features can be found in the Oracle documentation. (http://docs.oracle.com/cd/E28280_01/user.1111/e15175/bpmug_alt_flw_mig.htm#CHDBFJJA)
However after having generated the report which is bascially an XML file you will end-up with something like this.
Basically a lot of xml tags which are difficult to interpret. To give you a little indication, the file generated contains 75 lines for a simple BPM process without any integration and that has two instances. You can imagine the output for a production system...
This can all change by creating a very simple XSLT file that will transform your xml into a generated html page showing you more information that the xml could.
By using a little bit of color it will be very easy to find non-migrateble instances.
The only thing that needs to be done is add one line to your generated xml with a link to your custom MigrationReport xsl file :
<?xml-stylesheet type="text/xsl" href="migrationReport.xsl"?>After this the xml can be loaded into any modern browser and you will see it displayed.
Note: The "layout" of my generated report is very poor but seeing that it generated html a very flashy report could be within reach.
