Back in late 2005 I asked
What Would You Want From ColdFusion Microsoft Exchange Integration?. That post generated over 100 comments, and the ideas and suggestions and use cases in that thread were in a large part responsible for the powerful and sophisticated Exchange integration tags in ColdFusion 8.
So, I'd like your input again. We've been hearing some rumblings about Microsoft SharePoint and integration with ColdFusion, and I'd like you to weigh in on this idea. Are you a SharePoint user, or is it used anywhere in your organization? If yes, what is it being used for? And do you see any value in ColdFusion SharePoint integration? What type of integration would you like, and how would you use it? As before, I am less interested in simple "yes please" or "no, but you should support x instead" comments. I need specifics, and the more detail the better.
And no, I am not promising features. This is a brainstorming exercise for now. ;-)
Thanks!
1) Get a listing of sites a specified NT username is a member of (My Sites)
2) Return SharePoint lists with the ability to specify a view
3) Return Document Libraries with the ability to specify a view
4) Add/edit list items via CF
5) Create new sites via CF (I currently do this in CF via SharePoint webservices, but it's clunky and stopped working when we upgraded to WSS 3.0). We have a CF app to manage new site requests, and once a site is approved we just click a button and the site is automagically created. Save a nice bit of time over manually creating sites.
I'd be happy with any integration though, as SharePoint is now a critical tool used at our company (Large Aerospace).
See this post on auth issues: http://cfsilence.com/blog/client/index.cfm/2008/3/...
<cfsharepoint action="retrieveUsersFromGroup" group="myGroup" result="usersFromSharePoint" />
<cfloop query="usersFromSharePoint">
<cfsharepoint action="removeUserFromGroup" user="#name[currentRow]#" />
</cfloop>
<cfloop query="someQueryFromCFDSN">
<cfsharepoint action="addUserToGroup" user="DOMAIN\#userID#" group="myGroup" />
</cfloop>
Would have made the process much nicer then dealing with SOAP requests...
Not sure what you mean. The auth was working in WSS 2 by passing a username/password in cfinvoke. I never really had time to research why it stopped working when we upgraded to 3.0
As I said, I could be off base - but perhaps MS changed the auth between 2 and 3?
In sharepoint you can open an Office document and make changes. Then hit Save in Office, and it saves it directly to the server. Not having to re-upload the file is a HUGE plus to a lot of users. If you could add this option to Coldfusion it would be very beneficial!
Basically make the web services SharePoint exposes much easier. Dealing with Caml is a pain.
We basically dropped sharepoint since none of our .Net developers could get a grasp on writing webparts. It would be great if you could write webparts in CF and have sharepoint use them. I guess we would need a gateway for sharepoint or something.
- start a new workflow
- read a workflow status
- tell a workflow a step is complete
- cancel a workflow
- others?
Thanks.
I worked in a french school in Montreal and I worked since 6 month with MOSS 2007 to build an intranet to connect admin/teachers/students/parents together.
Being able to create custom webpart in CF would be my dream. I am not a .net developer and I don't want to be just for my work in this school.
Since everything in Sharepoint can be view in RSS, I guess I can use a lot of information in MOSS from Coldfusion.
Since I have a LOT of sites in MOSS ( 1 per department, 1 per level, 1 per class, 1 per teacher/class ) I could very much use CF to program a config site to set permission on all those site at the beginning of the year.
I saw that there is a conference at webmaniac on Sharepoint integration, what are the topics covered ?
I'm aware you can extend with CFX, Java, CORBA et al, but something more accessible to Johnny Coldfusion developer might be more useful
To keep ColdFusion alive and kicking around here, we need to continue to find ways that ColdFusion can shine, and integration with SharePoint would be one. Having the ability to easily develop custom Web Parts would certainly be attractive, as would many of the other items mentioned in the responses above. We have a more robust BPMS in place today, but because of it's size, we may want to leverage SharePoint for small workflow processes. Perhaps there is a place for ColdFusion in the integration between these two? Not really sure, just thinking out loud. Bottom line is, we believe ColdFusion integration with SharePoint is a good thing here and are looking forward to seeing where this leads.
I have to respectfully disagree. We've all heard time and again that ColdFusion is the language that makes difficult things easy. Sure there are other improvements that can be made, but leaving behind the true vision should not come at the expense of those improvements. Look at the amazing integration features we got in 8 - *AND* - the performance improvements.
SharePoint is something a lot of companies are embracing nowadays, and if CF can make it super simple by giving us a few tags to handle talking to it on our side then I'm all for it.
2) CFQuery integration with Sharepoint Lists? Some other way of accomplishing "CRUD" on them
3) Ability to list/read/extract URL to/and possibly update Document libraries. Possibly some sort of CFFile integration with Document Libraries.
- Write web parts
- Query lists and document libraries (perhaps the latter with a cfdirectory-like functionality?)
- As Jared Legg Mentions, the ability to open a document and then save from Office back to the server is really key to SharePoint's value
- Manage and detect alerts. I'm sadly short on details with this one, but the "alert" functionality in SharePoint is really limited and difficult to use. Being able to "watch" a list for changes through some type of gateway and then trigger CF handlers would be awesome.
Lastly, count me in as one more vote towards integrating at all. Yes, I want language enhancements and new features, but SharePoint is increasingly popular in the enterprise, and in my experience it's a big "first step" towards moving to .NET. When all your documents and resources are stored in SharePoint, it becomes vital that other applications can integrate - or they go away. Integration with SharePoint will help keep CF in the enterprise.
Would I rather a CF-base portal solution? Of course. But SharePoint Team Services comes with Windows 2003 Server, and it's really easy to set up and get started with it (not so easy down the road when you want to customize...) so businesses are doing it - it's the path of least resistance. I don't necessarily advocate bundling applications with CF - but on the other hand, if there was another viable option, it would probably get used.
I'm thrilled to see SharePoint integration considered as a possible feature for future versions of CF.
The status query would be pretty easy as you can do that direct form the tables but a nicer interface wouldn't hurt. What would be really rather useful is some method of getting progress messages from the workflow. Sending emails is already supported and I guess you could do that already with some CF code but an MSMQ or a Notification Services interface would be fairly easy to roll in sharepoint and a Notification Services interface for CF would also enble it to tie in to events generated in SQL Server 2005 and potentially Biztalk.
Why would a company that is using Microsoft technologies like Sharepoint be interested in bringing in a Java Application server? I think it might be easier to sell ColdFusion to them if it ran on dot net instead.
Of course, you would then alienate 25% of your developer community who use Macs and would rather not see so much integration with Microsoft technologies since it sends shivers down our spine.
It seems to me that Adobe is trying to find a place for ColdFusion to fit and that in the future what may be good for ColdFusion may not be good for many of its developers.
Sadly, the CTO for our corporation has literally swallowed the Redmond kool-aid on this, and has proclaimed we will be moving toward this to the exclusion of Cold Fusion. This is a potential catastrophe for our group, so I would be a lot less concerned about this latest Redmond cancer if we could have some method of integration.
At the very least, we should have the ability to use our existing ColdFusion templates/widgets/functional modules within the Sharepoint environment in the same vein as a "web part", so that we don't have to wrestle with .NET programming. SP and CF need to co-exist, or we are in danger of losing Cold Fusion as our primary intranet development platform.
Rather than hoping for some Sharepoint integration with ColdFusion, you should probably look for a new job. I have heard nothing but horrible things about Sharepoint. I wouldn't want to use it even if there was some sort of integration from ColdFusion.
When the managers make the technical decisions, its time to find another job.
1) Deeper authentication integration - our current security integration depends upon a shared datasource & passing keys within the query string
2) How about a ColdFusion webpart? I'd like to see SharePoint & ColdFusion living on the same box and be able to write CF code inside of a SharePoint webpart to be compiled at runtime
3) Ability to use the SharePoint web services as native CF tags, similar in function to the CFExchange tags
4) Ability to register CF components to custom UI modules as SharePoint webparts - this means I can create some piece of user interface code, such as a widget in CF, but add it to my SharePoint webpart library to be deployed to any site or page
5) Ability to create new SharePoint functionality in ColdFusion to actually extend SharePoint - MOSS 2007 comes with about 40 "applications", I would like the ability to create new applications in CF and deploy them as templates for SharePoint so that other users can use them throughout the portal
This is just a number of ideas, but I'm sure we, as well as the rest of the user community, would have plenty more. We've already tackled creating custom tags and components against the native SharePoint Services, but a deeper level of integration would always be appreciated. Likewise if you're looking for any beta partners, we would love to be on the list!
1. A Coldfusion webpart for sharepoint where coldfusion applications can act normally within Sharepoint structure. I would love to save some of our current CF applications and utilize them within SharePoint. I believe I've seen a project case study online that mentioned that they had created a custom webpart to display CF.
2. A CF tag that would help add a list item to a list in sharepoint. I think the big stumbling block to adding a list item is some proprietary code that MS puts into a list item record. Determining the appropriate value for the code would be the main thing necessary, I think.
Thanks Ben. I am excited to see an interest in what I thought was a fairly unique situatioon that we were in.
I would also like to see a CF Tag that would help add a list item in sharepoint.. Great idea.
Maybe you make a tag in CF for each SharePoint web service (or the most common ones). Maybe you can add web services to CFOutput or better yet cfquery then you can use it from cfoutput or cfloop. Maybe there is a special tag to add and edit data in a list.
It would also be great if Coldfusion could be used to make up for several of SharePoint’s short falls. SharePoint is good at getting something up and running quickly, but as soon as you want to start customizing something you run into problems.
http://download.microsoft.com/documents/customerev...