I have added a new post to my blog. It is part 1 of 2. These two posts will step through the process of using the new Export and Import-PWProjectAccessControl cmdlets.
Please take a look and let me know if you find it useful.
I've been playing around with the Export-PWProjectAccessControl cmdlet as I would like to use this to export a whole projects permissions in order to generate a script to fully automate project and folder hierarchy creation. However I have discovered that using the delivered BS1192 template as a test bed that some permissions are omitted from the export as they are workflow permissions assigned at a top level discipline folder without any workflow assigned and intended purely for inheritance. E.g.
In the report we never see this shown:
Even though I see the permissions set when looking at a sub folder using the workflow in PW:-
I don't see any way of seeing this inherited permission set no matter what level I run the report from as it is set on a folder with no workflow... Purely designed for inheritance use only.
So the idea of using this export in the combination of a script that uses folder / project creation and the corresponding import is not possible if using the export to produce a template as it stands in the case of my BS1192 example.
Any one any thoughts?
Just wondering if anyone else has BS1192 and using Powershell has managed to replicate this issue of none implicit workflow security rules (i.e. workflow rules applied to be inherited further down once the workflow state is assigned to a sub folder) not being reported when running "Export-PWProjectAccessControl"
Hey Chris, I did not include workflow settings unless they are explicitly applied to a folder and a folder has a workflow set. May need to revisit this and modify the cmdlet if the need is there.