So the SharePoint 2013 (previously known as ‘SharePoint 15’, the internal name) public beta is finally here. And that means that MVPs, TAP participants and other folks with early access are no longer bound by their non-disclosure agreements and can now talk about the product publicly. No doubt there will be a flurry of blog posts, but I wanted to write up my thoughts on what has struck a chord with me in the next version – partly because I have friends and colleagues who might look to me for this information, but mainly because it helps me crystallize my thinking on some of the new aspects. This started as a “developer perspective” article, but hopefully also gives a sense of what the new version brings for everyone.
In April 2011, Microsoft launched Office 365 – a comprehensive set of Software as a Service (SaaS) solutions that allow any organization to obtain hosted, cloud-based access to Exchange, Lync, Office Web Applications – and SharePoint Online. All offer guaranteed uptime, fault tolerance, contractual service levels and clear, predictable pricing.
SharePoint 2010 is coming up to its 2 year birthday, so it worth talking about Ribbons. Too often solutions concentrate on pages, Web Parts, lists, libraries and workflows. A SharePoint solution should be more than this – each of these components should be combined to provide users with a holistic solution, where the components work together and not as discrete entities.
I guess you all already noticed that Microsoft and all other major players are moving towards cloud computing and offering various online services. SharePoint wasn’t skipped in that movement, so now Microsoft also offers SharePoint Online services as the part of the Microsoft Office 365 service.
The concept of workflows comes from the time when work was rather mechanical. People (and later machines) were supposed to repeat precisely defined steps in a fixed order (or sequence). Any deviation from prescribed path, any thinking and improvising was not welcome. Assembly lines or microprocessors – they were all realizing rigid sequences.
Nintex Workflow 2010 Version 2.3 was unveiled on January 10th. Nintex has improved the integration tools available in Nintex Workflow v2.3, making it even easier to leverage your in-house business data and systems. Nintex Live, www.nintex.com/live an online catalog of powerful cloud services you can use in your workflow designs, has also been added to Nintex Workflow v2.3. With its growing set of cloud-based actions, Nintex Live extends your workflows to Office 365 and allows you to integrate a wide selection of online services directly into your business processes.
T7- This chalk talk session is focused on you and yourcustomers. What do you and your customers need to know about Visio and Visio Services? What are your customers doing with Visio and Visio Services in SharePoint 2010 to build unique SharePoint based applications and dashboards? How can you and your customers use Visio and… READ MORE
After a couple of years of “”Knowledge Management””, the focusand the hope of the IT business and users are on “”Enterprise 2.0″” and “social”. Enterprises spent a lot of time and effort in storing data, implementing Decision Support Systems, building Information retrieval systems, and so on. But more than ever, we search endlessly in our… READ MORE
Use “Check Out” and “Check In” actions with globally reusable workflows in SharePoint Designer 2010 by Kim FreheBlog Posts
I love that SharePoint Designer gives you the ability to create reusable workflows. It’s even better that you can select “All” as the content type. However, I have come across a minor issue with being able to update an item that requires check in and check out via workflow and being able to apply that to “any” list, content type, page or document. You can’t start a workflow on an item that’s checked out, but you can’t update an item that’s checked in. When you try to use the “Check out” action, you are expected to select a list to check out an item from.