zevenseas


 

Trying to solve the problem of deploying a workflow created in SharePoint Designer

I really want to solve this problem for everyone that needs to deploy a Workflow designed in SharePoint Designer to another site (without doing a site template). I know different people have blogged about this before but it isn’t the solution I have in mind. We want to solve it once and for all by putting it inside ProduShare and I have the feeling it is doable. I’m investigating a one click (or two clicks) solution that can be deployed from our catalog onto a SharePoint online site. And before all the devs start sending me emails, no server side code please (my dev skills are out of date, before you know it I delete it).

What I want to accomplish is to find a way to:

    • create the Workflows library (is it a special library?);
    • dynamically bind the new GUIDs to the workflow;
    • “push” the workflow files into the site.

The last two is a piece of cake I think (from within ProduShare) but I have no idea if we can create a Workflow library that is actually seen by SharePoint as a Workflows library. On top of that, we need to do this through the web services.

If you have an idea on how to do it, just let me know. Maybe we can solve this problem once and for all!

Dutch version of Nintex Workflow is available

Finally it is there (on top of all other languages) and we are happy to welcome a Dutch version of Nintex Workflow. We have been involved in the first translations but we will not take credits for finalizing because another Dutch partner was involved in that.

We have had some requests for a Dutch version in the past and if you read our blog don’t hesitate to download the Dutch trial here.

So it’s time to talk about “werkstromen” instead of workflows :-)

Coolness for SharePoint – samples (geocoding, weather and corporate Twitpic, Mobypicture)

Yes, this works with BPOS too.

Update: make sure to check out http://demo.zevenseas.com/sites/tunnelpoint

Last week I was a little bit nasty with my post on the SharePoint eco system and my complaints about “boring” applications. Immediately after that post I was thinking about my own “cool” apps for SharePoint and I could not remember my last cool app in a developer role (not developing myself anymore) for SharePoint. This weekend I had some thoughts on that and because of the availability of TunnelPoint and some stuff that we are testing internally, I have come up with some cool stuff.

First however, I need to tell you about two new Google services we are adding (or have already been adding) to TunnelPoint, Geocoding and Weather. With the Geocoding service you can easily add Latitude and Longitude to any entry in a list that contains an address, city and country (like your contact list). This service is live now on TunnelPoint. See a screenshot below:

image

The second service is weather provided by TunnelPoint and the Google Weather API. I must confess, the weather API isn’t a fully documented one but we use it either way because it is easy and fast. Right now we are testing it but we are on track for releasing it somewhere this week. I think a weather service speaks for itself and I show you the screenshot below:

image

I think it is awesome and because all data is in a list you can do your own magic with it (DataView web part or workflow).

These two services in one week prove that TunnelPoint is flexible and easy to extend and that was our goal in the first place.

So, now some more cool stuff!

I still have some skills in mobile development (using a very simple tool called Basic4PPC, it creates native WM solutions) and I wanted to create something that connects my mobile to SharePoint by using some internal TunnelPoint services. It took me around 24 hours this weekend to built a demo that can post information (message, Latitude, Longitude and picture from camera) to a SharePoint list by leveraging something that we are testing inside TunnelPoint. By no means it is something that we are selling right now but the direct connection to TunnelPoint could be something that we are going to open up in the future. Maybe someone wants to pickup the challenge with an Android or iPhone application?

The end result is a small mobile app. and you can see the result below:

image

The biggest challenge was of course the mobile application but I'm happy to say that it works on my HTC and Omnia. Luckily I had some old code lying around to deal with the GPS and it all works nicely.

My goal was to create a combination of a corporate Twitter mobile client and a Twitpic or Mobypicture service for SharePoint. It turned out to be easy because of the TunnelPoint technology. TunnelPoint provides the transparent connection to the list and the Twitter service in TunnelPoint can even publish my internal messages to Twitter.

When selecting the camera icon I get the following screen:

image

In this screen I can do two things: fill out a message and hookup a image from my camera. If I click on the camera it will open up my camera and I can take a shot. After the shot the image is saved. When I click the check button it will send the picture to a temporary storage location (for now outside SharePoint) but the message will be saved in a SharePoint list together with the Latitude and Longitude and the picture URL. See below screen:

image

Basically this mimics services like yFrog, Mobypicture, Twitpic etc. But this time inside your SharePoint environment.

Even President Obama uses the same web services that are used by TunnelPoint

Am I kidding? Not really and I'm not drunk either :-) Our SMS service partner Clickatell provides SMS on a global scale and the US Department of State decided to use their services to receive SMS highlights of Obama’s speech in Cairo. Click here for more information on this solution on the TunnelPoint blog.

The status of the SharePoint eco system and how we can help

One of the things we talked a lot about when I was partnering with Skype (many years ago) was the eco system. For Skype it was important and it contained the users, partners, the core platform and extra’s. It was functioning really well and everyone profited from it (although there have been discussions about that).

For any product such an eco system is important because it keeps the vibe alive.

My questions is if there is a SharePoint eco system? I’m actually not sure because in my opinion something is missing, the needed dynamic interaction with end users! Let me explain a little more.

When I look around there are a lot of solutions for SharePoint, stuff like: generic web parts (better versions of what SP offers), backup tools, collaboration+ tools, enhanced versions of out of the box sites etc. Most are useful but IMO, a lot of times boring for end users. Boring? Yes, boring and not specifically tailored for what they need in their daily work. Don’t get me wrong, we need all these tools too!

We, the technical people, expect them to “get” web parts and how to use them without a proper education but in the back of our mind we all know that user adoption isn’t probably that great in the end. Do we really know that many end users that mix and match web parts and build their own useful site? I know a few but that’s it. If I'm wrong please correct me because I'm trying to tease a little to get a good open discussion on this subject.

SharePoint has all the potential to become the most important Enterprise collaboration platform of the last 10 years and all partners make good money with it (we too). But that is not what I’m talking about. What am I talking about? I talk about end users that buy vertical SharePoint solutions that are tailored for their needs. Right now this is missing IMO. There is no dynamic marketplace where people take a look to see if it can solve their daily problem. And if they would see something they would need to go through their IT department to purchase it because most of the solutions need to be installed on the front end web server. End users don’t have much freedom when it comes to buying SP solutions. Is that a big problem? You bet! IT departments are busy running all their systems and new functionality can be a pain because you also need to know how to support it (what if the installation on the server goes wrong).

Now I’m going to do what you probably expected, I’m going to plug our own products :-) But, I do this with the best intentions because I want to give end users choices and solutions for their problems without overloading the IT department! It is a win-win for everyone in the end!

We think we can help to create a better eco system by offering a platform that brings flexibility but also binds groups of people. The end result is different type of solutions (think out of the box) that are available in two tastes:

  • no-assembly installable solutions
  • services (dynamic data, API’s) that connect to SharePoint lists.

The first one is done by using ProduShare (produce and share) and its framework to install things easily. A vertical solution can be something very simple like a list that contains very important information for a financial department. Period ending tasks for a financial period could be something like that. Sure you can create it yourself but why would you, it takes time. I can come up with plenty of other examples for this. Another one could be a branding package. Your site looks ugly when you create it? Download and install a branding package and voila a better looking site.

The second one, services, is done by using TunnelPoint. TunnelPoint is the middleman and it makes sure that interesting and up-to-date information can be seen inside your SharePoint site. This information is offered by calling web services/APIs (very abstract and difficult to understand for end users) and transforming that to information that can be offered to lists inside a SharePoint site. We have developed several services and we are planning to develop much more the coming months.

For both products we believe in the eco system. A system that has: partners that co-develop new services, solution builders and end users that buy it from us (subscription or one time payment).

Let me share one thing with you before I end this post. It is a sample of the status of SharePoint. Sometimes people ask me what I do and when I say Enterprise Collaboration portals with SharePoint people gaze and then turn their head to talk to other cool people :-) This could mean a few things:

  • they never heard of SharePoint
  • they don’t like collaboration (probably a lot);
  • they use folders and network shares;
  • they just ignore me because they don’t like me :-)
  • they think I'm an alien from a planet far far away.

But what if I could have said, “I have built an awesome social application for SharePoint, just like Facebook”. Probably that would have caught their attention.

Overall I think we need much more exciting and useful applications for end users to increase user adoption. We are ready to help all people in the eco system to fulfill this!


 
 
 

© 2009 Community Kit For SharePoint