SharePoint Consulting- How to Step Up your SharePoint 2013 Site Performance ?

SharePoint Consulting – Achieve Optimum Site performance by setting Quotas

Congrats! Your SharePoint consultant might have got your SharePoint 2013 site up and running in less two weeks. His SharePoint consulting has helped you put in place a great collaborative foundation to reap the endless benefits the revamped version has to offer. But wait !!… Even though you have successfully deployed your site, your implementation strategy might still crash.

One thing that is often dropped out of your SharePoint implementation plan or while availing SharePoint consulting services from a consultant, is a proper governance control strategy. This has a notable impact on your site performance affecting storage space and processing speed. So, Here’s a context to get you reading.

It is normal for a site collection to grow exponentially as several sub sites will eventually grow out of it over a period of time. There would also be instances where several sites will not be in use, lost and forlorn and sometimes out of control as more and more information will be dumped into it. While these sites will not be in use, they will still consume a lot of system resources affecting storage, networking and processing speed that can hamper site’s performance. Viewing through the lens of history, we have seen many SharePoint site getting into a chaotic mess, due to inefficient site management practices. According to a research almost 40% of the organization have shunned SharePoint because of the lack of knowledge about their SharePoint deployment size. Read more.

So how do you ensure your SharePoint site lives up to your expectations and facilitate the collaboration capabilities you longed for? Here’s how setting quotas help you save storage space.

Setting Quotas in SharePoint 2013

Setting Quotas get you that extra layer of tabs to control how much information a site collection can hold and set a threshold to prohibit information overload on the site when your sites run over the maximum allotted storage space. With quotas you can also govern the amount of resources a site collection can use. Quotas let you set storage limit values and warning limit values as well as resource utilization limits which applications cannot exceed. Read more on best practices for creating, editing and deleting Quotas.

Hence, it is advisable to keep tabs on the storage space (Also Read Document versions save you a fortune with Shredded storage) consumed due to the proliferation of unwanted sites affecting the system. The more time you allot for a proper site maintenance, the better off your site performance will be.

In the next post we will discuss about more tips to keep your SharePoint site in shape. Meanwhile an interesting read on Responsive Web Design in SharePoint 2013 by Subin Babu.

The NAPA” Office 365 Development tool and SharePoint 2013 App Development”

Guess, why SharePoint 2013 Online is humming Nancy Sinatra’s 1967’s tune – “Strawberries cherries and an angel’s kiss in spring, My summer wine is really made from all these things..” ??

Well, meet SharePoint 2013’s Summer Wine – The “NAPA” Office 365 Development tool!!

SharePoint App Development with NAPA – “The New Wine in An Old Bottle”

“Great wine is made in the vineyard” that’s the philosophy of family wine-making in NAPA valley, California. And the SharePoint 2013’s “NAPA” Office 365 Development tool does just that. Just like they harvest home grown grapes in their own vineyard to achieve best in class wines with a variety of flavors and aromas, the latest SharePoint Online has its own app-yard which provides a platform, to develop robust apps with best in class features using its latest NAPA tool. In short, developing apps using inbuilt app. In view of this feature, NAPA definitely is the new wine in an old bottle.

“NAPA” Office 365 Development tool

Napa provides lightweight Cloud platforms, where User Interface and other client-side logic is applied with web standards (e.g. HTML, JavaScript, CSS) and the back-end app logic runs on a server, without installing visual studio. It facilitates developers the freedom to use their choice of development tools, languages, and hosting environments. Put it simply, you don’t need robust software installed for simple SharePoint customization. Without having to create a SharePoint development environment for developing an app in SharePoint which is quite an expensive pursuit, the NAPA office 365 tool is a great way to build apps for office or SharePoint directly out of a browser window. The “Napa” Office 365 Developer Tools make it easy to start building apps for Office and SharePoint without having to invest in installing costly tools for customization or development. It can be used through the browser and enhanced using visual studio. All you need to have is a separate account created in SharePoint 365 and the “Napa” Office 365 Developer Tools app added to your SharePoint Online Developer Site. In a nutshell, it is a great way to leverage cloud based functionality to build robust apps with best in class functionality.

What else can you do with “NAPA” Office 365 Development tool ?

With Napa tool you can manage your projects with a page that can help you create various apps to manage content, tasks, mails and other office functions. It can be used along with visual studio to leverage extended capabilities such as using a modified project in your existing apps. Napa allows you to develop apps with absolute efficiency with the help of syntax highlighting and code completion during programming. If you want to share your code or projects with others you can use NAPA tool which creates a copy of your project in the form of public link. Finally when you are done with your app development and would like to publish it you can use SharePoint publishing apps either in the public office store or in an internal organization app catalog depending upon whether you want your apps to be free or for purchase or for a specific purpose.

Offshore Software Development Tips for Mission Critical Applications

Managing Mission Critical Offshore Projects

Trust Begets Trust – the foundation!
In the past, outsourcing offshore software development services  was limited to tasks that were not mission critical and were therefore  not  considered as threats to business continuity. But, thanks to the competitive dynamics fueled by time, budget and commercially driven deadlines, high tech ISVs and enterprises are seeking end to end IT(Information Technology) solutions that are less expensive but can ensure higher returns.

In view of this trend, enterprises seeking offshore services are wary of the risks and challenges associated while dealing with offshore service providers. Hence, it is imperative for them to understand a simple point – Unless there’s clear cut strategy in place to curtail associated risks, an offshore software development project will run a greater risk of failing.

It is imperative to understand the factors that affect both offshore software service provider and the enterprise seeking offshore IT Solutions

Here’s a comparison of prominent factors that affect both the parties

High Tech Enterprises Offshore Software Service Providers
Business Requirement Clarity Competition
Offshore Service Providers Selection Market Swings – Dollar rates etc.
IPR issues, Compliance etc. Staff management/Managing Attrition
Managing Cost, time and resources Govt. Policies/Compliance/Politics
Effective Communication strategies Requirement Clarity
Managing Quality Quality/Success Rates
Project Management/Meeting Deadlines Meeting Deadlines/Managing resources

We see there are quite a few overlaps in terms of factors that affect both the parties. These are but a few prominent factors that affect both parties. Having a mutual understanding of each others priorities and compulsions help in building the most important foundation of a successful offshore relationship – “TRUST”. Probably, a great foundation that can reap great value in the long run.

Tested and Proven Tips on managing mission critical offshore projects.

1. Shared business objectives and requirement clarity

The purpose of a software is to solve a specific problem – that’s pretty much familiar to all. And, that’s true in the business context as well. Proper assessment of software functionality and the end users adoption is critical to the success of an IT project. This is possible when the offshore software development team has adequate knowledge of clients’ expectations. It is therefore important that the requirements are clearly discussed with the developers and business objectives shared with the offshore software development team for any project.

Whether it’s a desktop application or a web based application, offshore software developers must be in a position to assess end users’ requirements easily and help build intuitive solutions that can have 100% user take up. This calls for proper training that can help developers understand business domains, business requirements and end user behavior. In order to achieve this, a project manager can schedule regular training sessions during the induction phase of a project and can have sporadic training sessions during the project development stage. It is also imperative for the project managers to ensure all developers are on the same page while working on different modules of a software.

These sessions also leverage offshore developers’ understanding of the project and boost their innovative instincts while coding or devising new methodologies for performing a task. A separate session to assess the absorption levels and feedback can go a long way in ensuring the successful execution of the project.

2. Quality Compliance and Code Quality Definition

An offshore software development partner’s quality adherence replicates in its deliverables. For building mission critical applications it is important to assess your partner’s maturity in the industry and processes. Ensuring your selected partners adhere quality standards like CMM, ISO etc. takes half of the pain of your solutions. But, this alone should not be the parameter to expect quality end results. In order to get the desired end result, it is important to drill deeper into the coding aspects of the software project.

Here’s how you set the “Code Quality” acceptance criteria

  • Develop a code standard document
  • Selecting automated code review tools
  • Build code walk-through
  • Feedback from the testing team
  • Document findings and implement improvements

3. Developing communication strategies

Communication plays a vital role in any offshore software development projects. A typical communication plan should span across the following key components:

a. Communication Levels
Building a strong communication road map across strategic, operational and at project levels help cover 360 degree aspect of the project. Communication at the project level which should take place more often may cover coding, development, backlogs etc scenarios and methods to fix them. Similarly communication at strategic level should take place less often covering the business aspect of the software built during the project life cycle.

b. Mode of Communication
It is also important to take into consideration the mode of communication during an on-going offshore software development project. These communications can take place with the help of emails, conference calls, wikis, team sites etc.

c. Objective of communication
The objective of every meetings should be clear and precise so that time can save by eliminating unnecessary meetings. Meetings cost time which is crucial factors to meet the deadlines for developers. Hence, the objective and agenda of the meeting should be clear and widely spread.

4. Client’s Visit

The offshore software development team works on the project inwardly. It is difficult for them to clearly map the business goals associated with the project. Hence, an on site visit can not only help developers know inside out about the client’s business environment but also built a long term relationship with the client. It also works as a non-cash motivator for employees.

5. Sprint regularly and manage backlogs efficiently

Probably the most feared circumstances during a project development life cycle are instances of incremental backlogs and unforeseen regression bugs associated with each modification.

To control backlogs the sprint meeting should be conducted properly and effectively. As each backlogs may result in regression issues, it is imperative to have mature offshore development and testing capabilities that can attenuate these instances by test automation.

6. Test, Test & Test

To ensure maximum code coverage it is imperative to develop holistic test suite consisting test cases for all functionality, prioritization of test cases as high, medium and low or identifying mission critical instances of application failure. It is also vital to have important statistics on bugs occurs like time taken to identify successive bugs, time taken to fix the bugs and so on and so forth. In a nutshell, invest in continually improving the regression test suite and developing metrics to measure code coverage.

In a Nutshell !

Offshore software development teams can deliver much more than just low cost solutions. The success resides on a focus and dedicated effort to the product goals and having a motivated team. It is also necessary to have an environment that facilitates timely feedback, thought leadership and training to turn the opportunity into a life long relationship.

Design SharePoint Site – Responsive web design in SharePoint 2013

There are approximately 250 odd unique screen sizes in mobile itself in production (the smallest being a Nokia phone with 94×44 screen size). Add to this all the sizes available in desktops and laptops, why stop, include TV sizes too as people adopt to “smart”TV.

So where do you start, what size do you build the site for, how many sizes do you plan to test the site in?

Life was easier a couple of years back. The moment the statement is read- break the project into two- UI for desktop/laptop & UI for mobile devices. If the project is in SharePoint, then that translates to 2 sets of UI components, but the challenge still was in identifying and accurately redirecting the user to the appropriate set based on the device. Microsoft worked “hard” and have included the device channel feature in the latest release SharePoint 2013. Does that really solve the problem at hand.

Device Channel in simple term- when a user browses a SharePoint site from a mobile device, the mobile browser submits to the site an HTTP GET request that includes a user agent string. This string contains information about the type of device that is trying to access the site. Based on that device sub string, the device browser can be redirected to a specific master page view which will have its set of css which optimizes view for the user (additional reading). This takes care of the questions- where to start but we still need to plan and create master pages and device channels for the possible screen sizes. This is a very open ended scope. Sure you can do your analysis to identify the most popular sizes and identify the sizes specifically in scope of the project, but that means crappy experience for the select few (like me) who have not upgraded to the latest and greatest. The fact that there are new mobile devices releasing every month with different screen resolutions makes this approach good but not the best.

Whats a better approach, you ask, RESPONSIVE DESIGN.

Responsive Web Design (RWD) adapts the layout to the viewing environment by using fluid, proportion-based grids, flexible images,and CSS3 media queries and pushes a client-side solution presenting an entirely different page structure to different devices, with some original elements hidden or moved around. The key is to keep all elements size relative. Easier said than done in SharePoint, as you have to bring in the responsiveness to various components (navigation, ribbons, layouts…). Plus you have the main issue of rendering images in multiple sizes too.

How to make your life easier. Try below mentioned suggestions

  • Use 3rd party front end framework that supports RWD e.g. Twitter Bootstrap, SimpleGrid, Zurb etc.
  • Test the design and layout for various sizes using simulators like Responsinator, Adobe edge inspect
  • Use responsive image rendition feature of SharePoint 2013.
  • If you are not happy with the native feature, you can try 3rd party tools like adaptive images to help you with rescaling images for screen size.

If you need elaboration on any aspect of RWD or SharePoint 2013 Consulting, get in touch with us

Why SharePoint implementation rather than using Shared Drives ?

Shared Drives vs SharePoint Development

We sift through thousands of documents and files to get the relevant information / documents / content in the shared drives. Searching these information in shared drives is like finding a needle in a haystack. Documents and files which are stored in shared drives, over a period of time duplicates due to multiple versions of the same document being stored.

In such a scenario it becomes difficult to retrieve relevant pieces of content due to the presence of duplicate versions in the shared drives. It takes a lot of effort to find the right document or set of information which consumes a lot of time and man hours.

SharePoint development and customization facilitate better information architecture and hierarchy to make information search as well as collaboration easier using its content management features. Before implementing these features in your SharePoint implementation planning, it is important to have a SharePoint consultant build your information structure using end users feedback and suggestions from existing end users. SharePoint consultants can help enterprises plan better content management solutions that can save time and make information worker more productive.

Find relevant documents at One place

SharePoint can be customized to centrally define and manage the content types by using metadata value that captures properties and characteristics of contents and store it in various departmental sites and help in unique identification of each set of content. This enables the user to search contents in a centralized manner and save more time thereby becoming more productive at managing these sundry tasks. SharePoint can also be customized to eliminate duplication of search efforts and helps users become more productive by retrieving relevant content fast.

What are Content types ?

Once the fundamentals of content types are understood it will be easier to understand the whole concept of content management. A content type is a collection of metadata, that encapsulates the characteristics of content or documents belonging to a particular content type and are assigned to documents. This helps unique identification of content matters and helps users get accurate search results. Content types can be used in a SharePoint site hierarchy and can also be used all together in a document library. Content types help in standardizing contents and make it easy to get accurate results.

MS Dynamics CRM & SharePoint 2013 Integration – Document Versions save you a fortune using Shredded Storage

MS Dynamics CRM & SharePoint Integration – What’s in Store for you ?

Microsoft Dynamics CRM and SharePoint integration enable users to use the document management capabilities of SharePoint from within Microsoft Dynamics CRM. It allows users to store and manage documents in the context of a Microsoft Dynamics CRM record on a server that is running SharePoint.

The best part about this integration is it allows SharePoint users to leverage the SharePoint framework to share, manage, and collaborate efficiently. As the documents are stored on a server that is running SharePoint, it is imperative to understand and optimize server space and cost by managing document versions efficiently.

So here’s a context to set the scene. Suppose you are planning to do a newsletter campaign using Microsoft Dynamics CRM capabilities, where several participants will contribute, modify, review and approve a draft using SharePoint document management capabilities thanks to their integration. Let’s say the file size of the document is 5mb and is supposed to move through various stages of approvals and edits as we discussed earlier. Suppose another employee wishes to edit the newsletter with something as minute as changing the metadata value of the file. As a result a new version is created with these edits whose file size is again 5mb. It is important to note that every time a version is created it consume 5mb (same as the original version size) so now we have consumed 10mb storage space with just a minor edit. Similarly if there are 10 rounds of revisions, edits and modifications from various participants, there will be 50MB of file that will be stored in the content database. Thus we see creating a file of size 5mb can actually end up consuming 50mb of space on the server that is running SharePoint. Isn’t it a costly pursuit ? Can we have a solution to it?

Well the answer comes with the latest Shredded storage feature in SharePoint 2013 that saves only the incremental edits not the whole document time after time thereby save a lot of expensive SQL storage space so that you can effectively utilize MS Dynamics capabilities combined with SharePoint 2013 infrastructure.

What is Shredded Storage in SharePoint 2013 ?

Shredded storage in SharePoint 2013 is the latest feature that helps save expensive SQL server space every time a new version of documents are created. Shredded feature does this by only storing incremental edits or changes in the documents and not the whole document every time a new version is created. Shredded storage finds its importance in collaboration scenarios where a document is exchanged, reviewed and co-authored . With each of these collaborative instances many versions along with the edits are created which consumes a lot of I/O storage space. With Shredded storage we can reduce I/O storage and network space to enable the system to perform efficiently and cost effectively.

Understanding Document Versioning & Why is it important ?

How many times do you edit a document? How many versions of a document are created when a document moves through the workflows or content development stages? How many duplicate versions are created by a minor change in metadata value? Did you know each document version consumes a costly server space equivalent to the size of the original document? Well, that’s how the files were managed by the addition of SharePoint 2013 Shredded storage feature.

In order to understand the importance of Shredded storage it is important to know a little about document versioning and why it is important. Suppose a document has to move across workflows for a review or approval process. There will be instances where many employees would be working simultaneously on that document. The document is edited, updated and reviewed as it moves ahead in the workflow or across content development stages for regular reviews and approvals. Every time if there’s an edit in the document by a workflow participant, a new version will be created and stored in the SQL database. These versions consume a lot of space even if the new version has a minor change. As the document progresses it is assumed that the quality of document is getting better. SharePoint administrator can set limits on the maximum number of versions that can be created in a SharePoint library to save more server space. When the number of versions exceeds the version limits the last draft gets deleted automatically with every incremental version creation above the version limit. Document versioning is important as it helps track the version history and take action in case one has to step back to earlier versions to perform any activity.

How Shredded Storage optimizes incremental Document Versions

Shredded Storage feature in SharePoint 2013 stores changes in the documents (in the form of edits or metadata) as “Shredded BLOBS” in a data table known as DocStreams Datatable which gets created with every fresh content database. Whenever there are changes in a document, the changes are stored as shredded blobs in a row in a table subsequently. In order to uniquely identify these shredded blobs from the source blob a numerical Id is assigned. Then using the blob index all the shredded blobs are merged to create a file. These shredded blobs consume less space in content database which are quite expensive. Hence, shredding the documents in the form of Blobs helps store only the incremental changes and saves extra space in the content database.

Storing these incremental edits or changes in the content database may still be an expensive pursuit especially when you are running both MS Dynamics and SharePoint. Hence, using an external less expensive storage space to manage these changes can greatly reduce your server cost. RBS or remote blob storage which externalizes the shredded blobs in an external less expensive server space can be used optimally along with SharePoint 2013 Shredded Storage feature to save costly content database space.

Visit Trigent’s exclusive report on

SharePoint 2013 Customizations – Solutions or Apps?

Previous versions of SharePoint has promoted solution model for many customization’s. But with the new SharePoint 2013, Microsoft has introduced a new app model. This new app model allows developers to build applications in multiple languages, using standard web technologies, and hosted on cloud or SharePoint. The new app model comes with a new unified API “_api” that is OAuth enabled, fully remote, with over 2,000 classes and 6,000 members.

All these make a very compelling case for building custom solutions in the new app model. But wait…, what happened to the old “solutions” model – including the less popular sand-boxed solutions for SharePoint online? Should we completely abandon the solution model? Can we migrate our existing “solutions” to apps? What is the Microsoft prescribed way for partners to manage SharePoint deployments and customization?

A newly announced Microsoft webinar may answer these questions. Microsoft says:
“Join Senior Product Marketing Manager, Keenan Newton, and special guest Partner Director of Apps Program Management, Robert Lefferts, as we kick off our new site centered around migrating SharePoint solutions to apps. We will discuss the history of SharePoint customization and where the SharePoint development platform is going. We will also highlight the benefits of the cloud app model and answer any questions that you may have.”
The event is on Monday, May 20, 2013 9:00 AM Pacific.

Register at: Microsoft

Also Read an Interesting article on The “Napa” Office 365 Development tool and SharePoint 2013 App Development

SharePoint 2013 – drag & drop file upload limitations

Drag and drop of files from your desktop to SharePoint document library in the browser window is a cool feature that is very much appreciated by many our clients. Unfortunately, this feature utilizes HTML5 and very much browser dependent.

Based on our tests, IE8 and IE9 does not support the drag and drop. However FF and Chrome seem to support this easily.

Drag & Drop

Simple Excel based BI in SharePoint 2013

Excel is here to stay. IT professionals may hate the proliferation of Excel documents containing important information, floating around the corporate file servers. Users love them – the familiar interface and ease of doing simple calculations and filtering has made Excel tremendously popular with people who work with numbers.

With SharePoint 2013 and Office Web App, it is so easy to turn some of the powerful features of Excel to do simple “BI” – that is, Business Intelligence in lower case. We recently helped one of our clients to share some vital information to their partners via SharePoint based extranet. We used Excel 2013’s PowerView feature to create great looking visualizations with ability to filter and drill through the data. This Excel is uploaded periodically to the extranet document library. And with Office Web App, the extranet user is able to view and interact with these powerful charts right in their browser.

This was one of the biggest attractions of our client’s extranet. This and other improved implementation of the extranet tremendously increased their partner participation compared to their previous extranet implementation.

The cool thing about Office Web App is that to view the files, there is no need for any licenses – it is free.

Use Excel 2013 with its new features, many in the BI area. Learn more about Excel 2013.
Use SharePoint 2013 with Office Web App. Learn more here.

SharePoint Development for Investment Consultants/Asset Management Companies

Investment Consultants Functions and Goals

Investment consultants formulate strategies and guide investors to make correct long term or short term investments. They constantly manage and monitor clients’ portfolios to meet financial goals. Their aim is to preserve and grow clients’ investment/asset over a long term and keep them abreast of latest financial products.

Further, they have to manage a large pool of client specific documents/artifacts and seamlessly mentor them over a long period of time.

Challenges for Investment Consultants

With a dynamic economic environment, Investment consultants face a lot of challenges before them both at macro and micro level. They have to review asset allocation more frequently than the fundamental ways owing to concurrent market swings. They have to calculate the magnitude of losses and constantly track macroeconomic variables.Their existing IT infrastructures are obsolete to handle these needs.

Internally, they have to manage a large pool of data, documents, artifacts pertaining to clients and constantly collaborate with them in order to meet their financial goals. At present environment, clients are seeking consultants who can offer personalized and value added services. A high turnaround time in responding client queries often results in competitor switch. Also, the absence of collaborative communication may hamper their relationship with clients.

Apart from the above challenges there are several in-house challenges that linger in current investment consulting firms:

  • Investment Research
  • Investment product evaluation and performance measurement
  • Customer relationship management
  • Lack of Value added services offered to clients
  • Usage of Obsolete/Legacy Systems to manage clients data
  • Un-Structured Data Management
  • Downgraded system performance
  • Single Point Access to Data
  • Low collaboration with clients

How a SharePoint Set-up help?

A SharePoint Set-up renders a collaborative platform in the form of Corporate Intranet for investment consultants to share information related to clients’ activities, better interact and engage with clients, enable value added services by providing customers with research reports, whitepapers etc. It can build a central repository of data and can allow single point access to fetch relevant documents pertaining to clients’ portfolios. Apart from these SharePoint 2010 offers host of other features to manage document types, retention policies etc. Investment consultant can also utilize other SharePoint features like document versioning, task listing etc. to improve task visibility and employee collaboration. Configure indexing services and build custom search service for faster, accurate search results. Learn More about SharePoint Installation.

SharePoint Integration with Existing System

SharePoint Consultant can help integrate existing CRM with SharePoint to overcome native functionality limitations of CRM by creating a central repository of data. They can facilitate integration of SharePoint with other in-house customer LOB application used to generate research col-laterals.

SharePoint integration enables consultants to have a consolidated view of data residing systems to improve TAT and user experience.

SharePoint Customization & Application Development

Apart from host of in-built features, SharePoint can also be customized and developed according to clients requirement. SharePoint Custom Scripts can help monitor database growth and compartmentalize database to keep system performance optimal. It can also help migrate obsolete clients data from legacy systems to SharePoint for better exception handling and control. SharePoint can also be developed using custom codes for data clean up and maintenance to reduced maintenance overheads. To know about our services, Visit SharePoint Consulting

SharePoint Adoption and Social Media Features That Help

SharePoint as a social media platform

Nice article on how Microsoft SharePoint scores as a Social Media platform for internal users. SharePoint evangelist Christian Buckley compares SharePoint with platforms like Facebook, Jive Salesforce, Yammer and Ning.
SharePoint’s Social Media Scorecard.

It is interesting to see how SharePoint has evolved from a simple intranet application to a social media platform for collaboration between employees and partners/vendors. Thousands of web parts are getting added daily, for work and for fun which you can add to your intranet. There is even a free Dilbert Web Part at Amrein Engineering which I thought was fun.

In our experience social media applications dramatically increase SharePoint adoption within organizations. Typical applications are sharing information through wikis, departmental discussion boards, surveys and blogs. SharePoint 2010 Profile Pages can be customized to look similar to Facebook pages with social content like a Facebook wall. Social tagging features include Social tags, which enable users to save and share items of interest, a Note Board, Ratings and Bookmarklets for tagging content that is external to the SharePoint site. A few social features and a couple of daily organizational workflows, all that is needed to get your organization’s users hooked on to SharePoint. Consider this, Microsoft says they are adding 20,000 users a day!

For more web parts and white papers visit here.

Meanwhile enjoy the last week of the fall color season. Just a few more days to go before the mighty trees on the Old Man Of The Mountain shake their leaves off….

Also Read The Birth of Yammer in SharePoint 2013