#ProjectOnline Resource Engagements now include #email reminders #PPM #Office365

February 12, 2016 at 9:19 pm | Posted in Administration, Configuration, Customisation, Functionality, Information | 1 Comment
Tags: , , ,

The recently released (September / October 2015) Resource Engagement feature in Project Online now has email reminder capability for pending resource requests. If you missed the posts on the Resource Engagement feature they can be found here:

https://pwmather.wordpress.com/2015/10/15/projectonline-resource-managements-feature-ppm-pmot-pmo-office365-office2016-ps2016-part-1/

https://pwmather.wordpress.com/2015/10/29/projectonline-resource-management-feature-ppm-pmot-pmo-office365-office2016-ps2016-part-2/

This post highlights the new email reminder capability. Recently Microsoft also enabled email alerts and notifications in Project Online, the Resource Engagements email alerts can now be included. See the steps below.

Once the Notification Email Settings is enabled on the PWA site collection as seen below (PWA Settings > Additional Server Settings):

image

In the resource centre you will then see a new button:

image

There are 3 options on this button:

image

To add resources for email reminders, select them in the resource centre grid then click Request Reminders > Subscribe to selected resources. An alert will pop up to advise you the subscriptions have been updated:

image

Now the resources have been added you need to enable the email alerts and the frequency. Navigate to PWA Settings > Manage My Resources’ Alerts and Reminders > My Resource Requests:

image

Check the check box and choose the frequency:

image

image

That’s it, you will now get email reminders for pending resource requests.

#ProjectServer and #SharePoint 2010 / 2013 / 2016 February 2016 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

February 11, 2016 at 8:02 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , , , ,

The Office 2016 February 2016 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3137471

Project 2016 February 2016 update:
https://support.microsoft.com/en-us/kb/3114714

The Office 2013 February 2016 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3137471

Project Server 2013 February 2016 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3114723

Project Server 2013 February 2016 update:
https://support.microsoft.com/en-us/kb/3114737

Project 2013 February 2016 update:
https://support.microsoft.com/en-us/kb/3114739

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the February 2016 CU.

The Office 2010 February 2016 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3137471

Project Server 2010 February 2016 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3114754

Project Server 2010 February 2016 update:
<no update this month>

Project 2010 February 2016 update:
https://support.microsoft.com/en-us/kb/3114568

SP2 is a pre-requisite for the Office 2010 February 2016 updates.

For details, see the post below: https://blogs.technet.microsoft.com/projectsupport/2016/02/10/project-server-2010-2013-and-2016-february-2016-pu-announcement/

As always, fully test these updates on a replica test environment before deploying to production

Getting started with #ProjectOnline #Workflow Part 1 #PS2013 #Office365 #Project #PPM #PMOT

February 9, 2016 at 1:09 am | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information, Workflow | 2 Comments
Tags: , , , ,

Following on from a very popular series of posts on getting started with Project Online, Microsoft’s Office 365 PPM cloud offering, round up found here. I started a mini series towards the end of last year where I covered getting started with the Portfolio Analysis functionality, part 1 here and part 2 here. I mentioned here that I would also do the same for workflow. I have finally got around to creating the workflow version – sorry for the delay, it has been a busy few months.

In this series of posts I will touch on some of the workflow capabilities that are available for Project Online and show you how to getting started.

For the purpose of this post I have already configured a project ideas type list in my PWA site collection, the portfolio strategy / analysis piece, some enterprise project types and have some custom fields.

The first post in this series will look at creating a project from the project ideas list. The workflow will assign a task to a SharePoint group for the approval, once approved a project will be created in Project Online using the correct Enterprise Project Type.

The project ideas list on my test environment looks like this:

image

image

Very simple, with a couple of SharePoint fields. I have mapped these fields to Project Online custom fields:

image

This is so that the metadata captured from the idea is copied over to custom field when the project is created.

I have also created some new Enterprise Project Types in this test environment:

image

Some of these will be used in later posts for this getting started series.

We will now look at creating an approval workflow for this ProjectIdeas list. Launch SharePoint Designer 2013 and open the target PWA site.

image

Click Workflow from Navigation pane:

image

Click List Workflow then choose the list:

image

Complete the details as required:

image

Click OK.

image

Now you can start creating the workflow in the designer. For this example I will firstly insert two more stages using the Stage button:

image

Then rename the stages:

image

Starting with the Initiated stage, click where is states “Start typing…” and more options will be enabled in the ribbon:

image

Click the Action button and scroll down to the “Assign a task” action and click:

image

Now click this user:

image

In the dialog box that appears complete the details, for the Participant I selected the Administrators group:

image

For the task title I used the string builder and added the following with a lookup to the item:

image

For the description I used the string builder to create the following:

image

Once the details are completed:

image

Click OK.

Now click in the transition to stage section:

image

Using the condition ribbon menu button, select if any value equals value:

image

Now click the first value:

image

Then click the fx button:

image

In the box that appears set the following:

image

Click OK.

Click the second value and choose Approved:

image

Now select the Insert go-to under the If and select Go to a stage on the Action menu:

image

image

Click a stage and select Approved:

image

Do the same for Else but select the Rejected stage:

image

In the Approved stage I will insert a parallel block:

image

In this parallel block I will insert four If conditions:

image

The If conditions are then configured like below:

image

The action for each If will be “Create Project from Current Item”:

image

Then you can choose the Enterprise Project Type:

image

Set this up to match to correct EPTs:

image

I then added two further actions:

image

To send ad email and to set a field on the list.

The email was configured as below:

image

The workflow then set the Approval Date field to Today:

image

The transition to stage was then update to end the workflow:

image

The final stage to configure is the Reject stage, in this stage we just send and email to the user that created the item then end the workflow:

image

Once completed, save the workflow and check for any errors.

Using the navigation bar, click the workflow name:

image

Then set the start options for the workflow:

image

Once you are happy with it publish the workflow to the list.

Back in SharePoint, if we look at the Workflow settings for the list we should see the workflow name:

image

Now if I create a new item on the list the workflow will fire and create a task for one of the administrators to approve, the item shows as in the initiated stage:

image

As a PWA administrator I would receive a email notifying me that I had a task assigned, I could then approve that item or reject it. In this example I will approve it:

image

When the workflow fires the item will update to Approved, a project will get created in Project Online, an email will be sent to the user who created the idea and the Approval Date will be set on the list item.

The updated project idea item can be seen below:

image

The project can be seen below in the project center with the correct Enterprise Project Type:

image

The data from the Project Ideas list has been copied to the correct Project Custom fields:

image

That’s it for the simple project ideas list workflow – there is lots more that can be done but hopefully that gives you a good idea on how to get started. Next up we will take a look at getting started with the project life cycle workflow and progress a project through various stages and phases.

#ProjectOnline CSOM DLL now available in #SharePoint NuGet package

February 5, 2016 at 9:32 am | Posted in .Net, Add-on, Administration, App, Customisation, Functionality, Information | Leave a comment
Tags:

Quick post to highlight that the Project Online CSOM DLL ‘Microsoft.ProjectServer.Client.dll’ is now available via the NuGet package for SharePoint, see the blog post below for details:

http://dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-february-2016

Direct link to the package: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM

#ProjectServer and #SharePoint 2010 / 2013 / 2016 January 2016 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

January 12, 2016 at 8:40 pm | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , , , ,

The Office 2016 January 2016 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3131245

Project 2016 January 2016 update:
https://support.microsoft.com/en-us/kb/3114538

The Office 2013 January 2016 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3131245

Project Server 2013 January 2016 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3114493

Project Server 2013 January 2016 update:
https://support.microsoft.com/en-us/kb/3114507

Project 2013 January 2016 update:
https://support.microsoft.com/en-us/kb/3114510

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the January 2016 CU.

The Office 2010 January 2016 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3131245

Project Server 2010 January 2016 CU Server Roll up package:
https://support.microsoft.com/en-us/kb/3114556

Project Server 2010 January 2016 update:
https://support.microsoft.com/en-us/kb/3085610

Project 2010 January 2016 update:
<no update this month>

SP2 is a pre-requisite for the Office 2010 January 2016 updates.

As always, fully test these updates on a replica test environment before deploying to production.

Want to query cross #project site #SharePoint lists in #ProjectOnline / #ProjectServer ? #PowerBI #PowerQuery #BI #Office365 #Excel #PPM

January 5, 2016 at 3:00 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Reporting | Leave a comment
Tags: , , , , , , , ,

As you may know or not know, creating a report that contains data from a custom SharePoint list from all Project sites, for example a Lesson Learned list or Change list is not that simple. The default lists for Issues and Risks are simple as the data is synchronised to the reporting schema and available in the Project OData reporting API. In this blog post I will show you a simple example using Power Query to access the list data and create a simple cross project report consuming data from the SharePoint list APIs on the Project Sites.

In this example I use the Issues list but the same principle will apply to any SharePoint lists on the project sites. I have used Power BI Desktop to author this report but the same would work in Excel using Power Query. First load Power BI Desktop and click Get Data >  ODATA Feed and enter the REST API for the list using an example Project Site:

image

The URL I used was: https://TenantURL/sites/PSP/Acquisition%20Target%20Analysis/_api/web/lists/GetByTitle(‘Issues&#8217;)/Items()?$Select=Title,Priority

In this example I am only getting the item title and priority from the Issues list. To use a different list update GetByTitle(‘Issues’) with the name of your list and then update the Select to include the correct columns.

Click OK and you will see the data from this list:

image

Click Edit to load the query editor.

image

Rename the query to something meaningful;

image

Access the Advanced Editor:

image

Change the Power Query code to add in the following code to turn this into a parameterised function:

image

The top and bottom lines were added and the OData.Feed URL updated the remove the reference to the example site we used to load the initial data, this was replaced with the site parameter. Click Done and you will see the following:

image

Don’t invoke the function as this will edit the code. Now we need to add in the query to get the list of projects. So within the query editor on the Home tab click New Source > ODATA Feed and enter the URL to get you list of Projects and Project Site URLS:

image

The URL I used was: https://TenantURL/sites/PSP/_api/ProjectData/Projects()?$Filter=ProjectType ne 7

This filters out the Timesheet row, the properties will be selected in the next step. Click OK to load the data:

image

Click OK and click Choose Columns:

image

I only selected ProjectName and ProjectWorkspaceInternalUrl, other columns can be added but only these were required for this example:

image

Click OK and rename the Query to something meaningful:

image

We now need to add in a custom column to call the function. Click Add Column > Add Custom Column and enter the following:

image

So above we are calling the LoadIssueData function and passing in the ProjectWorkspaceInternalUrl. This will be used in the site parameter value. Click OK and the data will load:

image

The column needs to be expanded to show the data, click the expand button next to the column name and chose the columns to expand:

image

Click OK to load the data and expand the columns to see Title and Priority columns from the Issues list:

image

Now click Close & Apply from the Home tab to load the data model:

image

We can now create a report that displays the data, a simple table example can be seen below:

image

The expanded column can be renamed to something more meaningful, for example:

image

Depending on the number of projects / project sites the data load might take a while as it has to traverse all of the project sites and get the SharePoint data using the list REST APIs. Each Project requires a separate REST call to get the list data from the associated Project Site.

Hopefully that will open up your reporting options for getting data from those custom SharePoint lists or the Project sites or even if you want to use the default Issues and Risks list but have custom columns on those lists.

#ProjectOnline auto generated unique #Project ID #Office365 #MSProject #PMO #PMOT

December 31, 2015 at 6:38 pm | Posted in Administration, Configuration, Functionality, Information | Leave a comment
Tags: , , , ,

Following on from the announcement a while back and the details on the Office 365 roadmap, you might see the unique Project ID feature now available on your tenant. The link to the roadmap notification is below:

http://success.office.com/en-us/roadmap#R-26705

This feature enables you to create a unique Project ID for each project in a particular Enterprise Project Type (EPT). To access the configuration for the unique ID click PWA Settings > Enterprise Project Types and click on the EPT that you require a unique ID for each project. This is an EPT setting and not a global setting. Once navigated to the EPT page you will see the following section – Project Id:

image

The starting number and minimum digit padding settings are required but you can also set a prefix and post fix. On my demo environment I set the following:

image

This feature adds a new default Project ID field as seen on my PDP:

image

This field is also added to all the default Project Center views such as the Summary view as seen below:

image

It can be added to new Project Center views too:

image

The project id is set when the project is created using that EPT, so for existing projects a Project ID will not be set even if you edit it and publish it. The “Pauls Test Project 001” existed before the feature was available on my PWA instance, as you can see this has a blank Project ID field:

image

You can type an ID in there if needed, for example I manually typed the next number available (00003):

image

I then created another new project but this duplicated the Project ID as seen below for project “Pauls Test Project 4”:

image

You can also modify a Project ID that was auto generated, see project “Pauls Test Project number 002” below:

image

This new field is available in the Odata Reporting API (_api/ProjectData/Projects), it is called ProjectIdentifier as seen below:

image

It is also available in the JSOM REST API (_api/ProjectServer/Projects) as well:

image

This is a great new addition to Project Online, just be aware that existing Projects wont get an ID generated and the Project ID can be set / updated manually.

Update multiple #ProjectOnline PWA Instances using c# .Net console app #Office365 #csharpe #PPM #PMOT

December 23, 2015 at 4:12 pm | Posted in .Net, Add-on, Administration, App, Configuration, Customisation, Functionality, Information | Leave a comment
Tags: , , , , ,

Following on from a post I wrote over a month ago regarding checking entities from multiple Project Online PWA instances, this post covers updating multiple Project Online PWA instances. The first post can be found below:

https://pwmather.wordpress.com/2015/11/04/check-entities-from-multiple-projectonline-pwa-instances-using-powershell-and-csom-office365/

In this post I demonstrate a way in which you can manage configuration across multiple PWA instances, for example you might want to create a new custom field on more than one instance. This is a simple example just to show you the idea. As this is very much an example, I haven’t released any code or solution but you can see the core code further on in the post.

For the purpose of this blog post I created a C# .Net console application. Once you have a new visual studio console app project you will need to add the references to the following DLLs:

image

I used the v15 SharePoint and Project Server dlls here.

In the program add these dlls:

image

The first part of the code is to capture the custom field name and description plus the number of PWA instances to update:

image

It then goes into a loop to create the custom field on the specified PWA site:

image

The code below is used to secure the password in the console input:

image

That is it. This example will create a Project level custom field but you could easily update the code to get the user to enter the entity type (task / resource etc.)

To see this in action see below:

Enter the custom field name:

image

Enter the custom field description:

image

Enter the number of PWA instances to update:

image

Enter the first PWA site URL:

image

Enter the username for an account that has access to create custom fields:

image

Enter the password for that account:

image

After pressing enter it will go off and create the custom field on the first PWA instance:

image

Press any key and it will go back to ask for the 2nd PWA instance:

image

It will then prompt for the username and password as before. It will keep looping through depending on how many PWA sites needed to be updated.

On one of those PWA instances we can see the field was created:

image

Nice and easy, saves navigating around multiple PWA site collections for a simple change you might want to roll out across multiple instances.

#ProjectServer and #SharePoint 2010 / 2013 / 2016 December 2015 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

December 9, 2015 at 7:34 am | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , , , ,

The Office 2016 December 2015 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-gb/kb/3121650

Project 2016 December 2015 update:
https://support.microsoft.com/en-gb/kb/3114393

The Office 2013 December 2015 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-gb/kb/3121650

Project Server 2013 December 2015 CU Server Roll up package:
https://support.microsoft.com/en-gb/kb/3114341

Project Server 2013 December 2015 update:
https://support.microsoft.com/en-gb/kb/3114360

Project 2013 December 2015 update:
https://support.microsoft.com/en-gb/kb/3114366

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the December 2015 CU.

The Office 2010 December 2015 updates and cumulative updates are now available, please see the links below:

https://support.microsoft.com/en-gb/kb/3121650

Project Server 2010 December 2015 CU Server Roll up package:
https://support.microsoft.com/en-gb/kb/3114405

Project Server 2010 December 2015 update:
<no specific Project Server 2010 update>

Project 2010 December 2015 update:
https://support.microsoft.com/en-gb/kb/3114419

SP2 is a pre-requisite for the Office 2010 December 2015 updates.

As always, fully test these updates on a replica test environment before deploying to production.

Want to capture your #Project team / staff morale? #ProjectOnline #ProjectServer / #SharePoint #PPM #JavaScript #jQuery

December 1, 2015 at 8:58 pm | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information | Leave a comment
Tags: , , , , ,

This is a supporting blog post for a new JavaScript file I have published to the Microsoft Gallery, it can be downloaded here:

https://gallery.technet.microsoft.com/Capture-Morale-in-9702d380 

This script enables you to capture the the team / staff morale each day – your team members just need to click one of the smiley faces:

image

In the example above I am logged in with the tenant admin account called “admin admin”. When a user clicks one of the icons it creates an item in the “ProjectTeamMorale” list in the PWA site:

image

If they click the happy faces it sets the item status to Happy, if they click the sad face it sets the status to Unhappy.

This list will need to be created manually with the following details:

List Name: ProjectTeamMorale

Columns:

image

The Date column setting defaults to Today:

image

Once the list is set up the script can be added to the PWA homepage using a content editor web part:

image

Reference the location of the project_team_morale.js file – in this example I added the JavaScript file to the Shared Document library in the PWA site:

image

That is it. The script can easily be updated to use different images or include more than two statuses etc. In this example I have done this for PWA but this could be added to a SharePoint intranet site to capture the staff members morale rather than just the project team in this example.

You can then generate a report to view the team / staff morale over time.

Try it out :)

Next Page »

Blog at WordPress.com. | The Pool Theme.
Entries and comments feeds.

Follow

Get every new post delivered to your Inbox.

Join 974 other followers