Add ablitly to connect all data exports within Blueworks Live

Thanks for following up Jessica!

Our first priority will be the BPMN2 Diagram Interchange export described in RFE 148912. It's not intended just for standardization. Rather, it would allow customers to extract the visual information currently not available with the pure BPMN2 export.

At that time, we would then reassess to see what more is needed and what gaps still remain.

Please note that the BPMN2 format is our recommended format for customers wishing to extract metadata out of the product.

Thanks!

The Blueworks Live team

Please provide an update when possible. Repsonse submitted 3/23/21. Thank you.

after reviewing the other RFE mentioned. It has been confirmed that this RFE is still needed. The other RFE is more specific to standardize perspective. The RFE I submitted is intended to allow us to have a common data point to connect all exportable data together, currently this common point/thread is missing.

private Thanks for your patience, and we apologize for the delay in our response!
We were discussing another enhancement request with Citi, one that appears to have a high degree of overlap with this one.

Could you please review RFE 148912 (http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=148912) to see if satisfies the use-case that you're trying to address.
That RFE requests support for the BPMN2 Diagram Interchange, which would supplement our existing BPMN2 export with graphical information (such as coordinates, etc). With that, we believe you'd get everything that you need, but we would appreciate your perspective.

Thanks!

Please provide an update if possible.

Please advise if any additional information is requested at this time, thank you.

1) Can you clarify how you envision combining them into a single file?
As we need to integrate bpmn with our internal application, We will be expecting all the relevant data points are in one specific format. Currently coordinate, height, width, pool & transition information are present in xpdl format but node graphic info like style, milestone, inter process linkage information available in bpmn and excel format. Apart from this, excel data contain linked decision, linked policies, stack holders, Cost information etc. We envision that if you can include all this info which is mentioned in these different formats in a single format then for a particular entity like a node or milestone etc we will be able to fetch this info consistently for our internal use which currently is not possible.

2) Can you elaborate on what you mean by a "common data point linkage"?
Related to the above mentioned points, All the artifacts are spread across multiple files. We are try to map the data points from across the formats with some unique identifier. We observe that, there is no common factor or link information to combine this files apart from name like activity_name, artifact _name, pool_name etc. So name or labels of entities are not trusted channel to fetch information related to same because it might get duplicated and cause redundant. So it would be great if you can provide the IDs of the entities like activity_id, lane_id, entity_id, milestone_id etc unique in all these three format in case you don't want to provide a single format which will contain all these information.

Thanks for your request.
Each of the exports listed were designed for specific purposes and use-cases. Can you clarify how you envision combining them into a single file? And can you elaborate on what you mean by a "common data point linkage"?
Can you also describe the purpose of your process mapping inventory? How is it used - e.g. for backup purposes, for report generation, for something else?
Thanks!