Embedding published ProVision HTML to SharePoint

Can someone explain how to embed the models themselves into SharePoint? I can upload the files to a document library and have them function as links, but is it not possible to actually have the .htm Provision files displayed and navigatable within SharePoint?

Any help would be appreciated.

Thanks

Find more posts tagged with

BPM

Comments

Matt_Michael

Hi Murray,

From my preliminary testing, I have not found a way to make the HTML output from ProVision navigable in Sharepoint. You could setup an Announcement, and select to 'edit HTML' and copy and paste the HTML tags from the published output. Unfortunately, there is a lot of cross referencing in our HTML publish so this likely won't yield what you're looking for.

Another thing you could try is setting up another sub-site and modify everything using the HTML editor. You can read more about that here: http://office.microsoft.com/en-us/sharepoint-designer-help/create-html-editor-styles-HA010174140.aspx . This will most likely yield what you're looking for.

Regards,

Matt Michael

Kent_Strickland

I've moved compiled HTML's (.chm) files to SharePoint, but you have to be careful of the size. I've had to split the models into groups to keep them under the 20MB limit we have on SharePoint.
Alternatively, if using a Knowledge Exchange server, then Read Only users can be set up to access your notebooks via their browser, assuming your security is such to allow them to access the KE Repository. Ours is a little clunky regarding the access.

Murray Turin

Thanks for the suggestions. I finally got it working. I had to load all of the published .htm files and image files to our document library. I then created a web page within our SharePoint site and specified the default.htm URL within the web page. Clicking on this brings up the models as I was hoping.

I also tried creating it as a web part page, but like the size of the web page better.

Thierry Tastet

That's indeed the best slution (uploading to a document library). Then you can use the search engine to find any object or model.
The Web page viewer web part is ok but the size needs to be fine tuned manually. We're working on ways to automate some of this process.
In addition to this, you may create share point lists to reference & index objects which are not visually present on models but are attached behind the scenes (artifacts or systems for instance).
Thanks,
Thierry.