Q regarding XML document structure of library components e.g. BusinessObject1.MBO

Hello,

Could you please advise if there is a documentation and / or schema definition for the XML document structure of the underlying XML files contained inside a Metastorm v9 library e.g. the file "BusinessObject1.MBO"?

Thanks.

Your help on this is much appreciated!

Regards,

Christoph

Find more posts tagged with

BPM

Comments

Paul_York

It looks like they're not quite the "open" format that they used to be. Whilst they are still xml it looks as if it's just the .NET classes that have then been serialized to a file.

Jerome_Pearce

You seriously want to mess with the XML inside the Metastorm solution files?

Paul_York

Not mess with it - understand it!

Jerome_Pearce

For what purpose, though?

[edit] Or is this related to the dynamic connection?

Paul_York

I'm not sure of Christoph's reason but we have a product called ProcessRunner which analyses any Metastorm process and allows you to build automated tests for them. For this to work successfully you need to be able to understand all of the components of a map from the stages and actions to the forms, variables and data stores etc.

In V7 all of these files were open in an understandable xml file format - Metastorm actually promoted this "open" format however in practice we didn't really see anyone use it. Now in V9 all the files are effectively serialized .NET classes which make it much harder to work through (however it is possible) .

So whilst you don't want to mess with them - I agree 100% on that, to maintain the openness of V7 it would have been good if this had been kept rather than serialisation. Because of this I suspect there isn't a formal document describing the structure.

(Edit: Not quite related - we had to go through this process when rebuilding ProcessRunner for V9, but I do have 1 more form within the product that needs converting - hence the dynamic grid q)

Jerome_Pearce

I would consider rewriting it in / for the Designer now that it is much easier (in theory). The downside is you cannot get access to all solutions at once, I guess.

BTW, we definitely 'used' the open format in v7 for the Procedure Documentation tool that also allows you to edit the alert list sand action roles in matrices (through the files).

Christoph Aussieker

Actually we would like to provide Metastorm v9 Designer with Business Objects programmatically embedded inside libraries.

For this purpose it would be very helpful to understand how XML schema files containing business object meta data information like "BusinessObject1.MBO" are created correctly.

Is there any information available regarding this approach / process?

Maybe there is some kind of MBO-Schema-Writer inside SDK? Thanks in advance for your responses!

Paul_York

I seriously doubt it but would love to hear the opposite. Perhaps someone from Metastorm could comment?

Bets of luck!

Jerome_Pearce

Scripted Business Objects will be arriving in 9.1.

More here:

http://metastorm.processmapping.com.au/post?id=5016997

Christoph Aussieker

Thank you very much for your answers!

Could you please let us know where to find roadmap information regarding upcoming Metastorm releases, features included and dates?

Grzegorz Lag

Hi XML format is now a "little" bit more complicated, but it is still readable. But you have to remember, that this could be changed, so you shouldn't have anything hardcoded (this is our opinion)

We have prepared procedure documenting tool which generate Word/PDF documentation of the process based on solution definition, now we are working on migrating our graphical history from v7 to version 9.

About BO, you can now populate BO via code, but you have to use sometimes tricks. I heard this will be much more flexible in next release.

achopra

Hi,

Where can we find the procedure documentation tool? Also at what time do you think the VPAT for v9 will be ready?

Grzegorz Lag

Ari
I hope you have vpat working right now on your vm.
about document generation tool. if you are interested I can prepare some demo for you.