To configure the Project Request process you can click the Configure Process tile on the site home page, or click the Project Requests link on the Quick Launch and click List | Configure Process.
The Project Request Manager Configure Process is where you can make changes to your project request process. You can customize the labels and values of each stage to better fit your own internal processes, or you can alter security and other settings to better suit your organization.
The Project Request Configure Process page works like a wizard. Use the Back and Next buttons to move through the sections. When you have completed making your changes, click Finish to save and return to your Project Request Manager site home page.
These changes are not global and only apply to the current Project Request Manager site.
These settings change the status display values throughout the Project Request site.
You can change the names of each stage in the process and change the values of the actions that move the process along.
The Status Display Value affects the status values in the view.
The Action Display Name affects the values in the ribbon and call-out controls.
The Back Action Display Name affects the values in the ribbon and call-out controls.
Check the box to put the index value before the display name, e.g. (0) Draft or (1) Review.
You can choose which actions are available during which status. For example, you might want to stop people from Approving a project request during the Review stage, or you may want to make sure a Draft is Sent for Review before it can be Recommended.
You can change the names for each role to better suit your process. Changing a Role Name on this page affects all Notification and Action Status values.
Note: If you change a value here, you will need to update the related value on the Status Settings page.
You will also need to update the column headings in the list to reflect the new names.
You can define a default Reviewer for each department in your Departments list.
Check the box to require that the department column contains information.
Note: The default reviewers in your departments can be configured by using the Departments tile on the Project Request Manager home page.
You can choose whether to restrict access to certain actions like Ranking, Bulk Approving or Rejecting, or Bulk Change Assignee to nominated people. Only these people will be able to use the feature or access the page where the feature is available. All other users, including Site Collection Administrators, will not be able to use the features.
Add people to the user fields to restrict the specific actions to those people alone.
You can apply referencing numbering to your project requests to give them unique ID's.
You can choose what sort of reference numbering you want to apply to new requests. The default value is 'PR-'0000, where the 0000 will be incremented, ie. PR-0001, PR-0002.
You can configure which email notification options are checked by default when performing actions like Approve or Send back to Requester.
Choose which notification actions are checked by default in action dialogs.
Default notification states.
New project requests are given a default ranking value of 100 so they will appear at the bottom of the list. If you change this number to 1, for example, all new project requests will appear at the top of the ranking list.
Tip! You can set the ranking value from 0-999.
You can choose the columns you want to show on the Rank Items page and the left to right position of the column.
Choose whether the Create Project process is available for Approved projects.
Choose whether the logged in user will default to being the project manager for the created project site.
Choose whether to use the reference value of the project request as the default URL name.
Choose which notification options are checked by default when you create a new project.
Use the Browse icon to pick a default parent site for new projects.
Use the Browse icon to pick a default template for new projects.
Note: If Project URL, Parent Site and Project Template all have a value by default, when creating a project you will be brought to the last step, Review Project Summary.
You can map certain columns in the project request to columns in the project statement. Mapped columns in the Project Statement in the newly created project site will pull the contents of the corresponding column in the Project Request.
Tip! You can use either the internal column name or the column display name.
The default columns you can map are:
Columns in different templates may want the same mapped data, but may have different names. You can use | to separate the column names for different columns in the project statement. For example, if you want to map the Due Date column in the project request to either the Due Date or Required Date columns in the project statement, enter: Due Date|Required Date.
Column mappings generally work on a like-to-like basis: i.e., Text - Text, User - User.
However, there are some alternative mappings that you can use:
|Calculated Field||Calculated Field with the Same Type|
Notes: Choice columns default to only allowing values that exist in the list of choices. Set the choice column to "Allow 'Fill-in' choices" to map new values.
Column mappings for the Project Manager/Owner override the 'Default Project Manager - Use the logged in user as the default project manager' setting.