Tags: Office 2013, PPM, Project 2013, Project Server 2013, PS2013
A quick post to highlight a couple of great links from Brian Smith for Project Server 2013 / Project Pro 2013 updates / patches. See the links below:
Project 2013 client update reference: http://blogs.technet.com/b/projectsupport/p/msp13.aspx
Project Server 2013 update reference: http://blogs.technet.com/b/projectsupport/p/ps13cu.aspx
Bookmark these links today!
#ProjectServer and #SharePoint 2010 / 2013 December 2014 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProjectDecember 11, 2014 at 12:37 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: Office 2010, Office 2013, Project 2010, Project 2013, Project Server 2010, Project Server 2013, PS2010, PS2013
The Office 2013 December 2014 Cumulative Updates are now available, please see the links below:
Project Server 2013 December 2014 Server Roll up package:
Project Server 2013 December 2014 CU:
Project 2013 December 2014 CU:
Also worth noting, if you haven’t done so already, install the March 2013 Public update: http://support.microsoft.com/kb/2768001 or Service Pack 1 http://support2.microsoft.com/kb/2880556 if installing the December 2014 CU.
The Office 2010 December 2014 Cumulative Updates are now available, please see the links below:
Project Server 2010 December 2014 Server Roll up package:
Project Server 2010 December 2014 CU:
Project 2010 December 2014 CU:
SP2 is a pre-requisite for the Office 2010 December 2014 CUs.
As always, test these updates on a replica test environment before deploying to production.
This script will enable the users to quick find and navigate to the Project Site for a particular project. This is useful if you have many projects in the instance. The script can be downloaded from the script gallery below:
To get the script to work you will need to download the following jQuery library: jquery-2.1.1.min.js – jQuery download Another version of this library may work but this was the one I used / tested with. Upload this library to your PWA site collection then update the script file with the correct location. I uploaded this file to the site collection document library as you can see in the code below:
This example script does use the ProjectData API, so users will need access to that for this to work.
Once the script is downloaded, upload this to the PWA site collection, in this example it was uploaded to the site collection documents library. Choose where you want to script to be accessed, in this example I have placed it on the PWA homepage using a content editor web part:
The content link in my example is: /sites/pwa/SiteCollectionDocuments/Project Site Finder.js
Once loaded, the page will look like this:
The user can then type in part of the project name and click “Find Project”:
The Project Site ULR column will contain the associated project site URL with a clickable hyperlink that will open the project site in a new window / new tab.
This only uses intrinsic fields so should work for any Project Online environment but do test it thoroughly first. You might want to improve the error handling etc. before deploying to a production environment. Also remember this does require the user to have access to the ProjectData API for this to work.
The script is provided "As is" with no warranties etc.