by Martin Laukkanen | Aug 29, 2015 | How to
Despite the best efforts of Microsoft with the UI design of SharePoint / PWA, I frequently get requests from customers to make changes / additions to the standard UI elements such as the ribbon menu, which – if you’re reading Microsoft – people very often still just “don’t get”.
(Note this is not a post about ribbon customisation, see Alex’s great post series here if that’s what you’re after.)
Example: ever wanted buttons at the bottom of a long form?
Simple yet effective.
<input type="button" value="< Previous Page" onclick="PDPInfrastructure.GotoPreviousPDP();">
<input type="button" value="Next Page >" onclick="PDPInfrastructure.GotoNextPDP();">
<span style="float: right;">
<input type="button" value="Save Project" onclick="PDPButton.SaveData();">
To use: simply save this as a html file somewhere in your site collection and then reference it in a Content Editor Web Part, see here for an example of how to do that.
It may go without saying but I will anyway: This is using undocumented and unsupported internal functions that will undoubtedly change at some point in the future whenever Microsoft feels like it.
You have been warned. But in the meantime keep giving customers what they ask for. :)
by Martin Laukkanen | May 29, 2015 | How to, Project 2016, Project Online, Workflow
One of the nice new features recently released on Project Online that will also be available for on-prem sometime in the future (PS 2016 or maybe if we’re lucky 2013 sp2?) is the ability to create custom fields via workflow using the new API CreateProjectSite. While on its own this may be a rather small change what it opens up is the possibility to completely control the Project Site creation which previously had only the out-of-the-box options i.e.; on or off!
So using this new feature I have created a walk-through here to resolve an often asked customer requirement:
How can we create the Project Site using a name other than the Project Name, e.g. a Project Number?
Note: This solution can be used today on Project Online, but as of yet will not work on Project Server 2013 on-premises.
In order to fulfill this requirement we will need to create a simple two stage workflow and associated Enterprise Project Type to be the default project type.
Stage 1: Project Registration
Used to collect project details including “Project Number” which will be a required field. Other PDP’s such as the project schedule will not be available.
In this stage no project site is available.
Stage 2: Project Execution
First thing upon entering this stage the project site is created using the details from the previous stage (site URL = “Project Number”), then other PDP’s, etc are shown to allow for the project to continue.
Project Online Configuration
I will go through the configuration of PWA for the workflow in brief, if you are not familiar with creating workflows or need further information then I’d recommend the following MSDN How to: How to: Create a Project Server workflow for Demand Management.
Firstly you will need a custom field called “Project Number” that is configured as a Project entity, type Text and Workflow-controlled enabled, as so:
Next create / edit the “New Project” PDP, and add the Project Number field to the PDP.
Optionally leave the field out of the PDP and go and install the Nearbaseline ID App which will set the project number in the background once the project is created (ahem shameless plug).
Now create the required Stages and Phases as follows:
Note that in the Project Registration stage the “Project Number” field must be marked required.
Now create an Enterprise Project Type using the New Project Page created above and for now leaving everything else default / blank as you’ll have to come back and associate the EPT with your workflow after the next steps.
Finally configure the default settings to NOT create project sites automatically from PWA Settings > Connected SharePoint Sites > Settings, as follows:
With that all setup we’re ready to create our workflow in SharePoint Designer.
Workflow Creation in SharePoint Designer
The workflow creation is based on the steps documented in the MSDN guide: Project Online: Bulk update custom fields and create project sites from a workflow, as such I will skip some of the details and suggest you review that article if you have any problems.
Open SharePoint Designer, create a new SharePoint 2013 Workflow – Project Server workflow and add the following:
- Insert two stages Project Registration & Project Execution
- Optionally set the stage status in the Project Registration stage to WaitingForInput.
- Set the transition to go to the Project Execution stage.
No additional wait for submit event is really required here as the workflow will automatically wait for all required custom fields to be entered before allowing submit.
- Now in the Project Execution stage add a step in which you can add the Create Project Site call as documented in the MSDN article.
- Finally terminate the workflow as the final transition.
Your workflow should look something like this:
The only change from the steps outlined in the MSDN article is in the forth step where the URL is constructed for the CreateSite call, in our case we want that to reference our “Project Number” custom field in the parameter in CreateProjectSite(parameter), so your URL should look like:
Note: Don’t try to cut and paste those URLs if you do so you will lose the special [%tags%], use the Add or Change Lookup button to insert the tags.
Once your workflow is done, save, publish and return to PWA and associate it with your EPT that you created then test!
Find attached below the SharePoint Designer Workflow solution created above exported as a Visio diagram, note that I cannot provide any guarantees or support for this downloaded Visio file.
Download: Demo Create Project Site from ECF
Screen shot of the workflow in Visio:
Hope this is useful to someone out there!
by Martin Laukkanen | May 8, 2015 | Project 2016, Project Online
A week of Ignite in Chicago is coming to an end and I thought it is about time to share some of my thoughts and discoveries over the last week, firstly though it’s been great to see a lot of familiar faces amongst the 23,000 or so people here in Chicago!
I’m not going to do a full write up of every session I’ve seen, the great thing about the blog-o-sphere is I can point you to the great write-up’s done by others (@PWMather‘s posts here, here and here are a great place to start!). What I will do is focus on some of the details that have interested me most.
New Project 2016 features
First up of course is what can we expect from Project 2016 / Project Server 2016 and Project Online in the next release; hmm how do I say this diplomatically? – Not that much.
Write support in MS Project client side API
I really really wish this feature was available six months ago considering the work I have been doing for customers lately! Good riddance VSTO I say! :)
Resource Engagement – Request / Review / Approve resource assignments
This is a long awaited feature for Project Server, however for some reason it didn’t get much air-time here at Ignite, fortunately I’ve had a chance to see most of during my day job working with some TAP customers and it goes a long way to addressing the typical need for managing / controlling and monitoring resource usage and over-allocation in a typical organisations.
I have to say though, with a major disclaimer (as I am an employee of TPG – The Project Group), that this new feature doesn’t quite come close to what is available in TPG’s TeamManager App, but then again I think that’s great as it really shows the the benefits of the App Model that Microsoft has created!
No more Project Server database – Project database to merge with the Content DB
This is already happening in ProjectOnline, but the interesting thing is what does this mean for reporting directly from the RDB as it is not supported to report from the SP Content DB’s? Well the good news is that according to at least one MS product manager for Project it will still be supported, so allow me to quote @mikemcleanlive; “You will be able to report directly against the new consolidated db if it’s on a dedicated server” (I’m just going to ignore that little “if” in there for now)
- OData limit changes are good to see, specifically for Timephased data the max rows per request has been increased to 2,000, apparently this can improve performance by 10x, but more importantly however it will make it possible to actually report on timephased data via OData. (No sorry 2-3hours to wait until Excel times-out or crashes when loading those datasets in the past was not a viable solution)
- Zero-downtime patching, this is a great and very well received new feature on the SharePoint side.
- PowerBI, PowerBI, PowerBI, seems to be a popular topic here this week. Well seriously seeing what can be done using it connected to OData from Project is pretty cool, shiny responsive dashboards are cool (excuse my hint of sarcasm).
- No more Project Service Application – goodbye one more configuration step – details TBA. :)
- Small API changes previously announced (but now documented!) include BulkCustomField updates and ProjectCreate methods enabling faster custom field updates and controlled Project site create via workflows.
I was really hoping to see more cool new features both for Project and SharePoint, much of the latter focused on Delve and Office Graph API which I have yet to see any relevance in the Project space. Additionally the push to be mobile first, cloud first for most of Microsoft seems to have been neglected in parts of SharePoint and especially Project Server, I expect it will be a very long time before we see PWA usable on a mobile phone for instance! :(
Having said that, the good thing about Microsoft’s online story with Office365 and Project Online is that all that hard work MS have put into making the software fast, responsive, stable and fully integrated across the full stack of MS products are all now going to be available on-premises as well, so this might mean Project Server 2016 is not going to be a major release (2003 -> 2007 or 2007 – 2010 for example) but it will be a solid upgrade for existing and new customers.