App Launcher for SharePoint 2013

-

Got a SharePoint 2013 environment but you need to demo 2016 look and feel?

Seen the SharePoint 2016 app launcher and want it on 2013?

Seen the Office 365 App Launcher and thought that would be great on my SharePoint 2013 environment?


This one's for you... a SharePoint 2013 app launcher !


Get the download here

Before you run the PowerShell script to install it you should probably read below



The launcher can be run using the PowerShell included in the root folder
use .\DeployAppLauncher.ps1 -url <SITE URL TO DEPLOY>

  1. Run this on a test site, if you are running it on a Publishing site you'll need to enable the "Wiki Home Page" site feature, this can then be deactivated if you don't want it enabled... It creates the "Site Assets" library where the launcher is deployed to.
  2. It relies on a custom masterpage, so it'll change this to the new one included. These are the additional lines in the masterpage (jquery, the launcher js file, some styling and some fonts!):
    1. <!--SPM:<SharePoint:ScriptLink language="javascript" name="~sitecollection/SiteAssets/applauncher/jquery-1.11.3.js"  runat="server" Localizable="false"/>-->
    2. <!--SPM:<SharePoint:ScriptLink language="javascript" name="~sitecollection/SiteAssets/applauncher/applauncher.js"  runat="server" Localizable="false"/>-->
    3. <!--SPM:<SharePoint:CssRegistration runat="server" ID="CssRegAppLauncher" Name="&#60;% $SPUrl:~sitecollection/SiteAssets/applauncher/applauncher.css %&#62;" After="corev15.css"/>-->
    4. <!--SPM:<SharePoint:CssRegistration runat="server" ID="CssRegFontAwesome" Name="&#60;% $SPUrl:~sitecollection/SiteAssets/applauncher/font-awesome-4.5.0/css/font-awesome.css %&#62;" After="corev15.css"/>-->
  3. It uses jquery, the file is included!
  4. It uses Font Awesome to get the app launcher icon on the ribbon, there's a lot of files in this so it'll upload them to the Site Assets folder. These can probably be trimmed down, I've left them as standard
  5. You need to update the links in the applauncher.js file to get to your My Sites location
  6. No warranties! Try it out on a dev Virtual Machine first :)
Hope it's useful

Full credit to :

http://www.jqueryscript.net/demo/Google-App-Launcher-Style-Dropdown-Plugin-with-jQuery-CSS3/

I just did the stick it on SharePoint bit

Also thanks Font Awesome!! for the launcher icon, I should reference this because I've included a copy in the files
https://fortawesome.github.io/Font-Awesome/

This is all javascript injection, there's no wsp solution file to install, no server downtime, and you can modify it on the fly!

Comments

  1. Unknown15 August 2016 at 05:01

    Hi,
    The master page is missing in the given package :(

    ReplyDelete
    Replies
    1. Unknown15 August 2016 at 05:05

      Sorry it was outside the files folder
      found it thanks :)

      Delete

Post a Comment

Popular posts from this blog

Use Power Automate to create a Document Set – The easy way!

-
Image
NOTE: This makes a “pseudo” document set, use the VTI bin method to create a full blown document set, however perhaps some of the steps could be useful to you. I’ve recently been working with improving some workflows which use Document Sets and stumbled into a problem. Online when you search for “Document Sets using Power Automate” you get posts such as:  https://karinebosch.wordpress.com/2018/11/08/microsoft-flow-create-a-document-set/ https://knowhere365.space/microsoft-flow-sharepoint-document-set-creation/ Now these posts have helped a lot of people but there is one drawback to them and most of the others I can find online. They rely on the use of _vti_bin (sometimes referred to as SP 2010 REST API) If you don’t know much about the history of VTI go check this out: https://www.spjeff.com/2009/03/13/history-of-_vti_bin/ It’s pretty vintage now. The customer I’ve been working with has a handful of SharePoint 2010 workflows we discovered using the SharePoint Modernisation Scanner  
Read more

Power Automate - Get SharePoint items using Created By/Modified By

-
Image
Recently I had an interesting request where someone was trying to filter items based on the Created By field in SharePoint using Power Automate. I thought, that should be pretty straight forward, make a claim or something similar and I headed to Google. Surprisingly there's not actually that many hits and it took quite a bit of digging. The answer once you realise is pretty straight forward. SharePoint holds a hidden(ish) list, the "User Information List" you can view it by adding the following to a Site Collections URL:  /_catalogs/users/simple.aspx This list holds all the "Ensured Users" on the site - you can google that one if you want to find out more. It also holds the information on which you can use in the filters for People Fields. Here are all the useful filters you can use: "ItemInternalId":"11", "ID":11, "Title":"Martin Pyman", "Name":"i:0#.f|membership|martin@marnotechnology.com",
Read more

Handling British Summer time when querying SharePoint from Power Automate

-
Image
This also applies to other TimeZones. When you query SharePoint in Power Automate using steps like "Get Items" the raw information that is returned when you are working with dates and currently inside British Summer Time will be out by an hour. Below I've created a step which runs Get Items and I add a compose to check the Created date: Going into SharePoint you can see the date time returned is an hour out (I'm currently inside British Summer Time and my laptops date/time is set as such). Whenever you are handling dates from SharePoint in Power Automate you have to remember that the original value stored in SharePoint for date/time is the UTC value. Depending on your regional settings the value is converted for you when it's rendered. Fear not! Power Automate has conversions, here's one way: In the example above I'm taking the source Created date/time which is in UTC and converting it to my location - Dublin, Edinburgh, Lisbon, London. The expected Create
Read more