Build a Customized SharePoint Team Site Without Writing Any Code

This video training course is all about going through the entire process of planning, and then building a solution with the out of the box tools for SharePoint 2010 without the use of code.
Course info
Rating
(132)
Level
Intermediate
Updated
Jun 21, 2013
Duration
1h 10m
Table of contents
Description
Course info
Rating
(132)
Level
Intermediate
Updated
Jun 21, 2013
Duration
1h 10m
Description

This video training course is all about going through the entire process of planning, and then building a solution with the out of the box tools for SharePoint 2010 without the use of code. The course uses a trouble ticketing system as an example that can be used to demonstrate the entire process from start to finish. This solution is meant for training purposes and not intended for production deployment, but the process of going through the course will teach students the process of how to approach SharePoint as a solution platform. Taking this approach will leverage the feature set of SharePoint 2010 to its fullest potential.

About the author
About the author

Spike has been working in depth with SharePoint since 2007. When he is not teaching SharePoint he is writing books, courseware, blogs, and articles on SharePoint, or implementing it as a consultant. He is the head of the Arizona SharePoint User group that meets monthly. He is in the final stages of writing a new course for SharePoint 2013, as well as his first SharePoint 2013 book.

More from the author
Section Introduction Transcripts
Section Introduction Transcripts

The Use Case
In this module, I'll go over the creation of the use case document used to create this no-code solution. The use case at its core is the description of a solution. It can be done at a high level or it can cover the most minute details. So in many situations, you cannot do one at all. But I found it a useful tool when creating no-code solutions for SharePoint. If nothing else, it forces me to think through the entire solution start to finish and all the parts that will come into play. The process of taking a business problem or group of problems and pairing them with SharePoint's built in functionality allows us to move through the cycles of planning and preparing to deploying a working solution. When I have taken the time to construct a use case document, I will have actually done most of the work. Going through this process expedites the move from planning to reality. I normally start with a skeleton document to make sure that I cover all the important sections, and then I go through and fill each section in. Some parts of the use case document are at a fairly high level, but most are pretty specific. When it's all finished, it's like an instruction manual on how to put together the solution. Let's take a look at moving from the skeleton or starting document to the finish use case.

Customizing The Site
In this module, I will do some site customizations. When you say that in SurePoint it can mean many different things. I'm not talking about look and feel here. I'm not changing CSS or creating custom master pages. I'm doing things in the browser to hopefully simplify and enhance the user experience. I'll be doing this in three separate areas. First, I'll customize the Quick Launch Bar by removing some links and rearranging things a bit. Second, I'll create a view on the IT Service Ticket List. Third, I'll adjust the content on the Home page, so that it is focused on the IT Service Ticket List. Let's get started.

Security
This section will cover the customization of security settings for the trouble ticketing site collection. When we speak of security in this application, we are not talking about preventing hackers from accessing our network. We are speaking about which levels of access to grant to whom within SharePoint, to allow our users to perform what they need, and our application to get done what it needs to get done. In this case, we're going to put authenticated users into the groups. However, while the out of the box groups and permission levels will work almost perfectly, we want our Support Techs to have their own SharePoint Group, and we want this group to be given a custom permission level called Contribute Without Delete. This is because we want our support text to be able to add an edit tickets, but not delete them this permission level will be a copy of the contribute permission level minus the delete items permission.

Conclusion
Congratulations. You have reached the end of this course. Now, the chances of this solution being exactly what you need to solve your specific business problem are quite frankly slim. However, at this point, it would be a matter of taking the skills you already have, creating a use case, and banging it out. There are always tweaks and fixes and adjustments that can be made to your solutions. The important part of doing a course like this is understanding a process that takes all of your current share point skills and knowledge and actually, build something start to finish with them. This is a big step. It's one thing to know what site collections, sites, workflows, navigation, content types and permission levels are. It's another thing to put all the pieces together to build something useful. The process of putting the pieces together is the skill we aimed for with this course. I hope that you enjoyed the course and good luck.