Recently I had two presentations about Office Business Applications (OBAs) and OBA Composition Reference Toolkit. A few days ago I wrote about my presentation on Hungarian Architecture Forum, but I didn't mention the second one: on the Visual Studio 2008 Launch ("Heroes Happen Here") I had two presentations: the first was a case study with SharePoint workflow, Records Center, custom ASPX task forms etc.
My second demo was the longer and bigger (and more better 
) one: OBA Solutions to mashup applications. In my introduction I presented what does "OBA" mean in fact, what does this picture tell for us:
![]()
Here is my surprise: I've started to record some demos about OBA, OBA Composer and related topics: Financial Services, Sample Application Kit for SAP, etc.
In the first part of this series you can see the OBA Composer and it's functions: I'm searching for an expression ("insurance"), and the OBA Composer gives me back the appropriate OBAs. I can choose whin one (or more) is fitting to my expectations. In this example it's the Insurance Endorsement. After choosing this one I can see in the middle of OBA Composer the parts of this OBA: one SharePoint site and two document libraries. The document units are stored In the Endorsement Sections library. We can insert these sections to out documents with help of a VSTO Word add-in. After all, the finished documents will be stored in the other library named "Endorsement Documents". During this demo, I'm starting the document creation from this library as well.
When I finished to compose my OBA, I can save and provision it, and finally my new OBA site will be started with the "Start" function. Here we can find the VSTO add-in to install in a SharePoint list. Click on this, install and let's go with Word! Voilá, here is a new Ribbon named "Insurance Document Management", and it has a function: "Endorsements". With the help of this we can insert the Endorsement Sections (stored the document library mentioned above).
When I save my new document, it'll be stored in the Endorsement Documents library, with a unique name generated automatically.
(To show the demo click on the picture.)
In the next demo I'll show you how can give a new component to the model, and how can our documents "live": using data from LOB Systems, filling out their properties automatically, etc.