Comments on: Why PLM Need to Learn about SharePoint 2010 Composites?

By: olegshilovitsky

olegshilovitsky — Thu, 22 Oct 2009 14:05:21 +0000

Chris, Maybe … Btw, SharePoint is pretty much web based. However, I can use your answer … – devil in details. All conversations related to integration sounds similar and all companies doing integration looks similar, but on the ground provide some different capabilities. I indeed see SharePoint 2010 composites (including all technical components and buzzwords behind as BDC, BCS etc.) as a step forward from what was done in MOSS 2007. Personally, I don’t believe this framework can operate as NO CODE for end-users. But for consulting and service companies, this is can be excellent framework and it looks like provide a lot of goodies you can use to develop collaborative apps. Best, Oleg.

By: Chris

Chris — Thu, 22 Oct 2009 12:25:01 +0000

Haven’t we heard this before? Is this a little bit lipstick on the same old pig ? This sounds alot like the old enterprise integration story that has been told over and over again and tried with different types of technologies. Remember EAI, not the grpahics company, but the market? The only technology platform that has truely proven capable of a mashup is WEB technology, yes/no?

By: olegshilovitsky

olegshilovitsky — Thu, 22 Oct 2009 12:04:55 +0000

Chris, of course, devil in details! Not everything can be supported with NO CODE. But WCF and other protocols can serve programming framework to implement it. With appropriated API support from Windchill (or any other system), you can run into required sequence of operation. Bottom line in my view – there are situations when you cannot do with NO CODE, but framework SharePoint 2010 provides for composites looks like big step forward. This is can be potentially sufficient customization environment for working scenarios running across different systems. Best, Oleg

By: Chris

Chris — Thu, 22 Oct 2009 11:29:02 +0000

This is certainly very interesting but aren’t there some real devilish details missing? Lets imagine I have a composite which is a list of Parts and these Parts are really WindChill Parts. Within the composite I delete a Part. How in the world does the composite deal with the workflow related to deleting a Part in WindChill and do this with NO CODE? Based on the chart you could imagine the same scenario with a list of CAD features and we all know there is no side effect when you delete a feature…