A recent change to Project Online for customers on “First Release” is related to the Settings for Project Sites, which were previously under “Connected SharePoint Sites” page in PWA Settings.
These settings were global to the whole PWA and were applicable to all Enterprise Project Types, while this worked fine there were two major drawbacks to this approach:
- There was no straightforward way to define the project site creation behaviour at the EPT level, hence customers were forced to stick to one setting for all their project types, e.g. if a customer wanted a project site to be automatically created for all their IT projects but not for their BAU project, this was not supported without customization.
- If Auto Project site creation was turned on, it had a significant impact on the performance of the solution and project creation was slower.
Therefore, Microsoft made this significant change to allow Project Creation settings to be decided at the EPT level. Now, when you add/edit an EPT you will see these new options:
The main change in Automatic Site Creation is that it has changed from Automatically create a site on first publish to Automatically create a site on next publish. This means that if this is selected, the Project Site will not be created when a project is created but you have to publish the project after its creation for Project Site to be created.
The following demonstrates this process:
- We created a new Project
- On Project Server Queue, we notice that there are no Project Site related activities
- When the Project is successfully created, we notice that the project site is not yet created
- We can now publish the project through Schedule PDP or MS Project
- This triggers the Project Site creation jobs in the queue
- and the site was created successfully
If the requirement is to keep this process completely automated, one workaround is to trigger a publish at the start of the project site workflow (if exists).