Steps to create a SharePoint 2013 App with Ruby on Rails

The SharePoint model is quite new to everybody and the recent launch of the 2013 version had made it even more ambiguous to developers around the world. Now, when it comes to creating an application pertaining to the software with Ruby on Rails, most developers seem to have a tough time in embracing the appropriate approach. Well, here is a guide for all Rails developers looking forward to creating an app successfully on the particular framework. However, please note that this particular guide should never be used as the best practice of Ruby on Rails development.

Well, before beginning the process, you must register a new application in Office 365. Ensure that a Site Collection has been created by making use of the Developer Site Template. This can be done from the Office 365 admin screens. Following the creation of the same, browse site collection and register the SharePoint application with Office 365 as well as Azure Access Control Services (ACS). For any sort of development purpose, the registration of the new app can be easily done through appregnew.aspx page present within Office 365. Since there is no such link available for the actual page, you need browse the URL directly.

Always remember that since the registration of the application is done through appregnew.aspx, the secret of the particular app will only be known by the ACS and you. Therefore, the series of characters that will be generated will be specifically used for decoding information coming from ACS/SharePoint. Always make sure to take note of the id of the app, as you will not be having any access of the same again.

Since the application will be only used for testing and development purposes, registering it through appregnew.aspx comes across as a wise choice. If there arises a need of making the app thoroughly and widely available or list in the official store of SharePoint, then an account must be registered at the Seller Dashboard.

1. Visual Studio

The next step of work rests with Visual Studio where an application package must be created, which would eventually be uploaded to SharePoint. To make this happen, you need to follow the following steps:

• Open Visual Studio (through ‘Run as Administrator’) for creating a new project. Go for project creation using the template ‘App for SharePoint 2013’. You will find this under the SharePoint /Office project node.
• Following this, you will be asked about the type of SharePoint app that you would like to create. Always remember to offer your app a similar name to that you have given in the appregnew.aspx and submit the URL of the Developer site collection. Ensure choosing an application type of Provider – hosted as the hosting model.
• In the last screen, leave the top option by selecting ‘Use a client secret’. Once, you click on the button OK, you will get to see the creation of 2 projects in Solution Explorer.
• It is to be noted that the first project usually implies to the SharePoint App that generates the application package. This particular app will be uploaded.
• The following step requires you to double click AppManifest.xml that consists of all the details related to the app. Upon opening the Manifest Designer, you need to remember to insert some specific values.

Always remember that the application needs to take permissions for being able to read and write data to the SharePoint site where the application is installed. This can be easily done through the permission tab. All you need to do is request just the permission that is actually needed. Always note that the more permission the app would request, the more it will run the risk of not being installed as users will be concerned about the security risk. Always remember to save and then close the AppManifest designer.

2. Ruby on Rails and Apple MacOS

To be able to work with SharePoint 2013, there stands a requirement of installing Ruby Gems to make things easier. Here is a look at the needs:

• jwt – this helps in decoding the JSON web token that emerges from the application software
• rest-client – this enables placing rest requests
• nokogiri – a library that helps querying XML that is usually returned from the SharePoint

the next step of action lies in creating a new application based on Ruby on Rails in your preferred code folder. All you need to do is type into Terminal. Rails is now ready for getting a MVC web application.

Open the gemfile and under the gem stated as ‘jquery-rails’, integrate the gems that were downloaded as pre-reqs.

• gem ‘jwt’
• gem ‘rest-client’
• gem ‘nokogiri’

This particular step is quite similar to the task of adding new reference in Visual Studio assembly.

3. Https Configuration

You must have noticed that while registering the application in appregnew.aspx, a Redirect URL is set that is https://localhost:3001. The app will be making use of the OAuth for being able to authorize the user and the application. Remember, that the for ensuring OAuth specification, both ends of communication must be https. After all, you would definitely not want any poor interception of unencrypted tokens to be transmitted over the Internet and have an access to the Office 365 or SharePoint site. Rails usually make use of WEBric, which is developed in web server. This is quite similar to the IISExpress of the Visual Studio.

To get the SharePoint 2013 mobile development right, you would have to follow the steps above. Then hopefully, you will be able to successfully create a SharePoint app with Ruby on Rails.

We provide SharePoint portal development services. If you would like to know more about the expertise of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.

SharePoint Apps will change the way you work

“SharePoint Apps” refers to add-ons or pieces of software which enhances the features of an application developed using SharePoint. These ‘apps’ can be written using a number of languages like PHP, HTML, Javascript etc. Another basic thing about apps is that they can be hosted in either the SharePoint environment or outside, in the cloud. Outside part can be at two different places – either Microsoft Azure or any other cloud service provider.

As done by mobile apps, SharePoint apps also increased the options of things that developers can do. That in turn has translated into providing a large number of smart options for a developer building an application using SharePoint. Suppose earlier a developer wanted to have a feature to enable viewing of SharePoint application using tablets or smartphones, he/she would have had to develop it on his own and that might have taken a really long time. But now all the developer has to do is use an app called Shareplus. This app is available for iOS and Andrioid based tablets and enables a user to browse, edit documents directly from SharePoint via the tablet directly.

Similarly there are many such apps or applications which provide the developer with the option to make applications smarter. Apps like OurCRM, DocAve, MyView etc are quite popular. For your reference OurCRM is a CRM that runs on MS SharePoint – it basically allows organizations to edit the customer relationship management software as per their need.

DocAve is a data and document management platform for SharePoint.

MyView the winner of Best SharePoint App 2013 award (at the European SharePoint Community Awards), enables users to focus on productivity and important ongoing projects by collating and synchronizing SharePoint and Microsoft Outlook tasks and calendar items, presented through online, mobile, or desktop based Microsoft Exchange applications.

Similarly there are many such ‘apps’, based on the need one can search for those and use the one best suited. A simple Google search can fetch you the app that you might be looking for, for example I was looking for “Top iPad apps for accessing SharePoint” and I found this Techrepublic link which lists out details of best apps for iPads – http://www.techrepublic.com/blog/tablets-in-the-enterprise/top-ipad-apps-for-accessing-sharepoint/.

My interest primarily in SharePoint Apps has been in applications related to Marketing and Social aspects of a business. These days Social media constitutes a major part of marketing and this area has to be handled effectively to ensure active participation of people in your products, which in turn would lead to increased revenue. The top 5 social media SharePoint apps, as per me, are the following:

• Social Squared : Social Squared is an app which gives organizations the choice of providing a large forum environment to its members for them to discuss projects or other topics. This provides as a nice space for sharing and brainstorming of ideas.
• eLocker Solutions : eLocker Solutions is the perfect social SharePoint solution for teachers and students. It allows them to interact without worrying about security within the SharePoint environment. It can be customized for a specific school or district and allows teachers to assign projects, track progress and interact with students.
• SharePoint twitter web part : The Twitter Web Part allows users to tweet right from their SharePoint environment as well as display the latest Twitter posts and search based on hashtags. This is a great option for companies who want to control everything (including social media) from their SharePoint environment.
• Blog Rollup webpart : The Blog Rollup Web Part allows organizations to display a blog roll of the most recent blog posts created within the SharePoint environment. This is a very useful tool, which is perfect for seeing at a glance the most recently published posts.
• SP Community : SP Community utilizes SharePoint’s existing social features and transforms them into a complete user experience that organizations and businesses can take advantage of. It offers groups, user home pages and profile pages, discussion boards and much more.

You can hire developers from top sharepoint development companies in India who can help you in your project within allocated budgets and time schedules.

We provide sharepoint application development services. If you would like to discuss with our certified sharepoint programmers, please get in touch with us at Mindfire Solutions.

Migrate a SharePoint Team Wiki to an Enterprise Wiki

An Enterprise Wiki (EW) refers to a publishing site that offers updating and sharing huge volumes of information within an organization. In case an organization requires a centralized, large knowledge repository which is designed to both share as well as store information over an organizational scale, the use of EW can be considered. They make use of the Enterprise Wiki site template, developed over the publishing infrastructure of Microsoft SharePoint Server 2010. This particular infrastructure makes room for a number of means for controlling content. For instance, permissions can be assigned or workflows may be used for establishment of an approval procedure.

The EW Site template can be leveraged for the creation of sub-sites or site collections. The site created through this template is focused on the content. The “Pages” Library is the main component of the site. Again, there is the “Wiki Page Library” list template. It has the potential to host wiki pages and can be utilized to create various kinds of sites. In fact, Wiki Library list template serves as the default pages library for the “Team Site” template.

Planning for an Enterprise Wiki
Before implementation of an EW, the concerned organization must determine whether it is the right solution. It is a perfect solution when the business is in need of manifold users for contribution to the knowledge repository. But in case a means to establish one-to-many communication regarding an area of interest or a project is required, a Team Site should be preferably used.

While deciding whether to go for it, the following things should be considered:

• Purpose to be served: It should have a clear-cut purpose. For instance, a particular business goal can be addressed or it can be a centralized knowledge body regarding particular business problems, processes or topics. The aim is to offer a space wherein members belonging to a virtual community can remove, change or create content, including content created by previous authors. However, in case you need to have a knowledge exchange means that is more structured where one-to-many communication is mostly used, a blog or a team site comprising Web Edit facility can be used.
• Number of users who would be contributing: A number of factors influence this decision. These are- whether there is potential to support enhanced growth coupled with the need for enhanced server and network capacity, whether legal consideration regarding contribution are there, whether key contributors from each business area should be determined.
• Control of EW access: Ideally, each member of the organization should have access to update, edit or contribute content. In case there is the need for information separation with respect to groups, blog or team site with Web edit can be used.
• Implementation of control over content: Blogs are designed in order to provide structured knowledge exchange while a wiki makes room for informal contributions. However, there are requirements and guidelines with respect to an organization for handling of particular content regarding specific subjects. Addressing inaccurate or inappropriate entries can also be considered.

Before creation of an Enterprise Wiki, the following tasks must be completed:

• In order to provide storage for notes and social tags, a Managed Metadata serve application should be created.
• For the management of the site collection wherein the EW is located, administrator permission pertaining to site collections must be there.
• A User Profile Service Application must be developed in case the EW is intended to be used with My Sites.

Migration of Wiki Library
The following methods may be followed for migration:

• The Enterprise Wiki may be linked to the existing Wiki library without moving the same. In this case, navigation must be well structured.
• This involves linking to the existing Wiki Library. Here, the entire library is moved or copied to the EW site. This facilitates links to other pages and lists because they belong to the same site always.
• Old wiki pages can be migrated into new EW Pages. This implies copying the wiki page content within the “Page Content” field. This can be manually done but may take a long period of time.
• Migrating to Enterprise Wiki may indeed prove beneficial for your organization. The steps should be carefully followed and it should be properly done to ensure maximum success.

We provide custom sharepoint development services. In addition we can assist you in migration to and from Sharepoint. If you would like to speak to one of our certified sharepoint programmers, please contact us at Mindfire Solutions.