Projects

These settings are organized on two tabs.

Importing projects from Maconomy is described in detail in the Deltek People Planner Integrations Guide, including the descriptions of the settings that relate to this.

Table	Descriptions
Task Type Parameters	These settings are shared among every task specification that imports projects.
Default Local Parameters	When you create a task specification for importing projects, these parameters are used to set the defaults. You can then edit the task specification where you want something other than the default.

Field	Description
Setting: Allow Deletion of Tasks with Planning and/or Actuals	You can enable the deletion of budget lines that no longer exist in Maconomy as part of a project import from Maconomy to People Planner by using the Allow deletion of tasks with planning and/or actuals task type parameter. If this parameter is selected, budget lines that no longer exist in Maconomy are deleted from People Planner, even if they contain planning or actuals information that was created in People Planner. Warning: If the Allow deletion of tasks with planning and/or actuals task type parameter is selected, and no corresponding budget line exists in Maconomy, the tasks and summary lines are deleted during any project import, even if the task or summary line has assignments or allocations, such as planned hours, that were created in People Planner. When this information is deleted, it is lost, and the deletion cannot be undone. If you do not select this parameter, the default behavior is to delete only those budget lines that do not have planning information.
Setting: Delete Project if Deleted in Maconomy	With this setting, projects are automatically deleted in People Planner when they are deleted in Maconomy. When—and only when—you have selected the Delete project if deleted in Maconomy checkbox, you get access to a new Task Specification type, Delete Projects Deleted (and Optionally Closed). You can use this to set up a scheduled task that performs the actual deletions of the projects in People Planner. Setting: Delete Project if Closed in Maconomy (After Period) The option to automatically delete projects from People Planner when they are closed in Maconomy is useful to avoid the accumulation of a large number of projects in People Planner over time. This functionality deletes all project history, including all planning, and you cannot restore that history later. However, you can specify that a period of time after the project was closed in Maconomy must elapse before the project is deleted from People Planner. Note: This setting is only enabled if you also select the Delete Project if Deleted in Maconomy check box. If you do not select that setting, the value of the Delete Project if Closed in Maconomy (After Period) setting is always Never. To enable this setting: Go to Settings > Maconomy Integration > Projects > Task Type Parameters. Select the Delete project if deleted in Maconomy checkbox. Select one of the options in the drop-down list: Never Immediately One week One month Three months Six months One year Two years Three years The default value is Never, which means that projects are not deleted-even if they are closed in Maconomy. This is the normal behavior before People Planner 3.8, where this setting was introduced. If the Delete project if closed in Maconomy (after period) value is set to anything other than Never, and you click Save, the following warning is displayed: Warning: The setting Delete project if closed in Maconomy (after period) will permanently delete ALL project data for all relevant jobs. Click Yes to confirm, or No to cancel. Click Save. After you have set selected the setting, you must set up a scheduled task to do the actual deletion of the projects. See the Delete project if deleted in Maconomy setting for information about how to do this. The "after period" that you specify for the Delete project if closed in Maconomy (after period) setting is relative to a project's close date. Depending on when the task is executed, the project might not be deleted exactly after the specified period; thus, the specified period is the earliest time when the project will be deleted. For example, if you close a project in Maconomy on January 31, and you select the Delete project if closed in Maconomy (after period) setting, and you set the After Period value to 3 months, the project will be deleted from People Planner the first time that the Delete Projects Deleted (and Optionally Closed) in Maconomy task is executed on or after May 1. This setting has no dependency on the Allow deletion of tasks with planning and/or actuals setting. Closed projects that have planning are deleted regardless of whether or not you selected the Allow Deletion of Task with Planning setting.
Set the Import Project Default Parameters	Using the Web Admin Tool, you can set default values for the import project local parameters that are used by the Update from Maconomy button in the Project Gantt (PG) and the default parameters that are used in the Import Project view. You can set default values for these parameters: Use dates from Maconomy: Select this checkbox to use dates from Maconomy. The value that you set here is used as the default value when tasks are created in People Planner. However, the Update from Maconomy button does not use this setting. Budget type: Choose a budget type from the dropdown list. The dropdown values are those that have been imported via Master Data import. If no Master Data import has been performed, the dropdown list is empty. If you reimport budget types through a Master Data import that no longer contains the budget type that was specified as the default value here, the Master Data import creates a warning in the log file so that you can update the default value to a valid value. The value that you set here has no effect when you create import project task specifications or when you use the Update from Maconomy button. To set import project default parameters: Go to Settings > Maconomy Integration > Projects > Task Type Parameters. Select the appropriate setting for the parameter(s) as described in the preceding section Click Save.
Set an Imported Project as Read-Only	Using the Web Admin Tool, you can set default values to determine whether a project imported from Maconomy should be read-only for all users. You can set up a job in Maconomy as read-only using a Customer PopUp 1-5 or Boolean 1-5 field before it is imported to People Planner, or you can set this up manually in People Planner for each job. Note: This setting overrides all other privileges to edit projects, even when the user is a project manager or project manager substitute. However, if the Allow editing of read-only projects in Project Management setting is enabled, certain users can edit read-only projects in the project management workspaces. Refer to the description on the Allow editing of read-only projects in Project Management setting below for more information. You can set default values for these parameters: Value of field to denote that the project is not editable - Select one of the following options from the drop-down list: None: Choose this option if you do not want to enable the read-only functionality. Customer PopUp 1-5: Select the field used in Maconomy to determine whether this project should be read-only. Boolean 1-5: Select the field used in Maconomy to determine whether this project should be read-only. Text value of field to denote that the project is not editable - This field is enabled only when you select a Customer PopUp 1-5 field in the Value of field to denote that the project is not editable parameter. If the value of this field is the same as the Customer PopUp 1-5 fields on the project from Maconomy, it should be read-only. Boolean value of field to denote that the project is not editable - This field is enabled only when you select a Boolean 1-5 field in the Value of field to denote that the project is not editable parameter. Select this checkbox to enable the read-only functionality. If the value of this field is the same as the Boolean 1-5 fields on the project from Maconomy, it should be read-only.
Allow Editing of Read-Only Projects in Project Management	In People Planner, the ability to edit projects is limited to specific users based on: Their user role (for example, a project manager or project manager substitute). Enablement of the Value of field to denote that the project is not editable setting. Those who have the Edit projects where you are not Project Manager privilege. When you enable the Allow editing of read-only projects in Project Management setting, anyone can edit projects in the Project Management workspaces. This applies to projects that are set as read-only due to the Value of field to denote that the project is not editable setting, as well as projects that cannot be edited because the user does not have a project manager or substitute user role or editing privileges. This allows you to effectively make designated projects read-only when accessed in the Resource Management workspace, while making them editable only in the Project Management workspaces for users with relevant access.

JavaScript must be enabled in order to use this site.Please enable JavaScript in your browser and refresh the page.

Projects

These settings are organized on two tabs.

Importing projects from Maconomy is described in detail in the Deltek People Planner Integrations Guide, including the descriptions of the settings that relate to this.

Table	Descriptions
Task Type Parameters	These settings are shared among every task specification that imports projects.
Default Local Parameters	When you create a task specification for importing projects, these parameters are used to set the defaults. You can then edit the task specification where you want something other than the default.

Field	Description
Setting: Allow Deletion of Tasks with Planning and/or Actuals	You can enable the deletion of budget lines that no longer exist in Maconomy as part of a project import from Maconomy to People Planner by using the Allow deletion of tasks with planning and/or actuals task type parameter. If this parameter is selected, budget lines that no longer exist in Maconomy are deleted from People Planner, even if they contain planning or actuals information that was created in People Planner. Warning: If the Allow deletion of tasks with planning and/or actuals task type parameter is selected, and no corresponding budget line exists in Maconomy, the tasks and summary lines are deleted during any project import, even if the task or summary line has assignments or allocations, such as planned hours, that were created in People Planner. When this information is deleted, it is lost, and the deletion cannot be undone. If you do not select this parameter, the default behavior is to delete only those budget lines that do not have planning information.
Setting: Delete Project if Deleted in Maconomy	With this setting, projects are automatically deleted in People Planner when they are deleted in Maconomy. When—and only when—you have selected the Delete project if deleted in Maconomy checkbox, you get access to a new Task Specification type, Delete Projects Deleted (and Optionally Closed). You can use this to set up a scheduled task that performs the actual deletions of the projects in People Planner. Setting: Delete Project if Closed in Maconomy (After Period) The option to automatically delete projects from People Planner when they are closed in Maconomy is useful to avoid the accumulation of a large number of projects in People Planner over time. This functionality deletes all project history, including all planning, and you cannot restore that history later. However, you can specify that a period of time after the project was closed in Maconomy must elapse before the project is deleted from People Planner. Note: This setting is only enabled if you also select the Delete Project if Deleted in Maconomy check box. If you do not select that setting, the value of the Delete Project if Closed in Maconomy (After Period) setting is always Never. To enable this setting: Go to Settings > Maconomy Integration > Projects > Task Type Parameters. Select the Delete project if deleted in Maconomy checkbox. Select one of the options in the drop-down list: Never Immediately One week One month Three months Six months One year Two years Three years The default value is Never, which means that projects are not deleted-even if they are closed in Maconomy. This is the normal behavior before People Planner 3.8, where this setting was introduced. If the Delete project if closed in Maconomy (after period) value is set to anything other than Never, and you click Save, the following warning is displayed: Warning: The setting Delete project if closed in Maconomy (after period) will permanently delete ALL project data for all relevant jobs. Click Yes to confirm, or No to cancel. Click Save. After you have set selected the setting, you must set up a scheduled task to do the actual deletion of the projects. See the Delete project if deleted in Maconomy setting for information about how to do this. The "after period" that you specify for the Delete project if closed in Maconomy (after period) setting is relative to a project's close date. Depending on when the task is executed, the project might not be deleted exactly after the specified period; thus, the specified period is the earliest time when the project will be deleted. For example, if you close a project in Maconomy on January 31, and you select the Delete project if closed in Maconomy (after period) setting, and you set the After Period value to 3 months, the project will be deleted from People Planner the first time that the Delete Projects Deleted (and Optionally Closed) in Maconomy task is executed on or after May 1. This setting has no dependency on the Allow deletion of tasks with planning and/or actuals setting. Closed projects that have planning are deleted regardless of whether or not you selected the Allow Deletion of Task with Planning setting.
Set the Import Project Default Parameters	Using the Web Admin Tool, you can set default values for the import project local parameters that are used by the Update from Maconomy button in the Project Gantt (PG) and the default parameters that are used in the Import Project view. You can set default values for these parameters: Use dates from Maconomy: Select this checkbox to use dates from Maconomy. The value that you set here is used as the default value when tasks are created in People Planner. However, the Update from Maconomy button does not use this setting. Budget type: Choose a budget type from the dropdown list. The dropdown values are those that have been imported via Master Data import. If no Master Data import has been performed, the dropdown list is empty. If you reimport budget types through a Master Data import that no longer contains the budget type that was specified as the default value here, the Master Data import creates a warning in the log file so that you can update the default value to a valid value. The value that you set here has no effect when you create import project task specifications or when you use the Update from Maconomy button. To set import project default parameters: Go to Settings > Maconomy Integration > Projects > Task Type Parameters. Select the appropriate setting for the parameter(s) as described in the preceding section Click Save.
Set an Imported Project as Read-Only	Using the Web Admin Tool, you can set default values to determine whether a project imported from Maconomy should be read-only for all users. You can set up a job in Maconomy as read-only using a Customer PopUp 1-5 or Boolean 1-5 field before it is imported to People Planner, or you can set this up manually in People Planner for each job. Note: This setting overrides all other privileges to edit projects, even when the user is a project manager or project manager substitute. However, if the Allow editing of read-only projects in Project Management setting is enabled, certain users can edit read-only projects in the project management workspaces. Refer to the description on the Allow editing of read-only projects in Project Management setting below for more information. You can set default values for these parameters: Value of field to denote that the project is not editable - Select one of the following options from the drop-down list: None: Choose this option if you do not want to enable the read-only functionality. Customer PopUp 1-5: Select the field used in Maconomy to determine whether this project should be read-only. Boolean 1-5: Select the field used in Maconomy to determine whether this project should be read-only. Text value of field to denote that the project is not editable - This field is enabled only when you select a Customer PopUp 1-5 field in the Value of field to denote that the project is not editable parameter. If the value of this field is the same as the Customer PopUp 1-5 fields on the project from Maconomy, it should be read-only. Boolean value of field to denote that the project is not editable - This field is enabled only when you select a Boolean 1-5 field in the Value of field to denote that the project is not editable parameter. Select this checkbox to enable the read-only functionality. If the value of this field is the same as the Boolean 1-5 fields on the project from Maconomy, it should be read-only.
Allow Editing of Read-Only Projects in Project Management	In People Planner, the ability to edit projects is limited to specific users based on: Their user role (for example, a project manager or project manager substitute). Enablement of the Value of field to denote that the project is not editable setting. Those who have the Edit projects where you are not Project Manager privilege. When you enable the Allow editing of read-only projects in Project Management setting, anyone can edit projects in the Project Management workspaces. This applies to projects that are set as read-only due to the Value of field to denote that the project is not editable setting, as well as projects that cannot be edited because the user does not have a project manager or substitute user role or editing privileges. This allows you to effectively make designated projects read-only when accessed in the Resource Management workspace, while making them editable only in the Project Management workspaces for users with relevant access.