Configure Resource Requests

Information

Resource Planning with Requests/Approvals They can be configured in three ways:
- globally
- per project
- per resource
Furthermore you can configure e-mail notifications for resource requests/approvals.

globally

Information

In the Global Settings module you can configure whether resource requests/approvals are to be activated globally.
Furthermore you can set the time grid within which resource requests can be created or approved.

Information

Via the Resource requests active parameter in the Global Settings module you can configure whether resource requests/approvals are to be activated globally.
The selected setting is automatically selected for newly created projects.

Values

0: resource requests/approvals are inactive, i.e. all resources can be planned freely in the schedule. Modules and buttons which belong to resource requests/approvals are not visible.
1: Project resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved at project level via the request/approval process.
2: task resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved at task level via the request/approval process.

Note

The parameter will be overwritten by the setting in the Resource requests field in the Project Core Data module.
If the setting is changed retroactively, this change only affects projects which are newly created after the change has been made.

Information

Via the Exclude requested resources from planning parameter in the Global Settings module you can configure whether the requested (generic) resource is automatically removed from the task when a resource approval is adapted in the schedule.
- This setting is activated by default.
If the setting is deactivated, the project manager must remove the previously requested resources manually from the planning after approvals are adapted.

Information

Via the Resource requests: time grid parameter in the Global Settings module you can configure in which time grid resource requests can be created or released.

Values

Set to months by default (value: 4).
Depending on the selected time grid, the resources will be loaded with the corresponding load profile.
2: Day (PM_DAY load profile)
3: Week (PM_WEEK load profile)
4: Month (PM_MONTH load profile)
5: Quarter (PM_QUART load profile)

Notes

The time grid setting also has an influence on default values for the display period of the time scale in the resource request modules.
- Start of the time scale: Date of the first request
- End of the time scale:
  - 2: Date of the first request + 27 days
  - 3: Date of the first request + 96 days
  - 4: Date of the first request + 364 days
  - 5: Date of the first request + 454 days
If the setting is to be changed after requests have already been created, a query will be displayed asking whether the existing requests are to be archived. The setting will only be saved upon confirmation.
- When changing the setting, the auxiliary ApplyResourceRequestCustomizingChanges migration packet, which adapts the modules to the selected setting, will be run automatically.
- When changing the setting, existing approval exceedance will be marked as read. You can see them in the Approval exceedance module.

Information

The Resource requests parameter can be configured per project in the Edit Planning Objects module.

Details

inactive: resource requests/approvals are inactive, i.e. all resources can be planned freely in the schedule. Modules and buttons which belong to resource requests/approvals are not visible.
active at project level: Project resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved at project level via the request/approval process.
active at task level: task resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved at task level via the request/approval process.

Notes

The listbox is only displayed in the Edit Planning Objects module if resource requests are activated at global level (Resource requests active = 1 or 2).
For new projects, the global setting is used by default. In the Edit Planning Objects module, the setting can be changed per project.
If the setting is to be changed after requests have already been created, a query will be displayed asking whether the existing requests are to be archived. The setting will only be saved upon confirmation.
If resource requests are activated in the project after resources have already been planned, no requests will be generated retroactively for these resources.

Information

For each resource you can configure via the Approval required parameter in the Resource Data Sheet whether there must be an approval for the resource when resource requests/approvals are activated.

Details

If the parameter is activated, the resource can only be planned if there is an approval at project or task level.
If the parameter is not activated, the resource can also be planned without approval.
The parameter is activated for person resources by default and is deactivated for all other resources.
- In such a case, the department resource can be planned and requested, however the corresponding employees can only be planned and requested after approval.
- If the parameter is deactivated for person resources, they will not be included in resource requests accordingly.

Information

In order to be able to use e-mail notifications for Resource Planning with Requests/Approvals, several requirements must be met.

Details

In the recipient’s e-mail client, HTML mails must be supported and activated so that the resource request journal can be received.
In the Global Settings (Project) module, the IP address of the smtp-server must be specified in the SMTP server address parameter (the address which can be accessed externally).
In the Time-Controlled Events module, the time-controlled Send automatic e-mails for resource requests event must be activated.
In the Global Settings (MOD009ABF) customizing module under Customizer → Master Data
- , the e-mail address of the sender must be specified in the Resource request journal: e-mail sender parameter.
- the e-mail format can be adjusted if required.
  - Here, HTML must be used.
For sender and possible recipient, the Message via e-mail parameter must be activated in the Users module.
A department manager must be specified for the requested department in the Resp. for department parameter in the User field.