The following tables illustrate two scenarios where a set of project tasks is used to generate resource requests: firstly by Role and secondly by both Milestone and Role.
| Project Task | Project Milestone | Internal Resource | External Resource | Resource Role |
|---|---|---|---|---|
| Task 1 | Milestone A | Developer | ||
| Task 1 | Milestone A | Java Developer | ||
| Task 2 | Milestone A | Consultant | ||
| Task 3 | Milestone B | Robert | ||
| Task 4 | Milestone D | Daniel | Developer | |
| Task 5 | Milestone B | Daniel |
| Target Resource Request | Resource Role | Project Milestone | Project Tasks |
|---|---|---|---|
| RR1 | Developer | Milestone A, Milestone D | Task 1, Task 4 |
| RR2 | Java Developer | Milestone A | Task 1 |
| RR3 | Consultant | Milestone A | Task 2 |
| RR4 | Robert's role on Contact record | Milestone B | Task 3 |
| RR5 | Daniel's role on Contact record | Milestone B | Task 5 |
| Target Resource Request | Resource Role | Project Milestone | Project Tasks |
|---|---|---|---|
| RR1 | Developer | Milestone A | Task 1 |
| RR2 | Developer | Milestone D | Task 4 |
| RR3 | Java Developer | Milestone A | Task 1 |
| RR4 | Consultant | Milestone A | Task 2 |
| RR5 | Robert's role on Contact record | Milestone B | Task 3 |
| RR6 | Daniel's role on Contact record | Milestone B | Task 5 |
You can set how long to allow between consecutive project task assignments before FinancialForce PSA generates separate resource requests or assignments based on your selected attributes. The following tables illustrate a scenario.
You created two project tasks on a project and assigned two Architect roles to the tasks.
| Project Task Assignment | Project Task | Resource Role | Project Task Start Date | Project Task End Date |
|---|---|---|---|---|
| PTA-652 | Planning | Architect | 04/28/2014 | 04/30/2014 |
| PTA-677 | Implementation | Architect | 06/28/2014 | 06/30/2014 |
On the Generate Resource Requests from Project Task Assignments page, you preview resource requests based on Role but do not specify a value for Longest Gap Allowed (Days). One resource request is shown:
| Resource Role | Start Date | End Date |
|---|---|---|
| Architect | 04/28/2014 | 06/30/2014 |
Architects are not required to work on the project from May through end of June 2014. Therefore:
10 for Longest Gap Allowed (Days), but do not select Ignore Saturdays or Ignore Sundays.| Resource Role | Start Date | End Date |
|---|---|---|
| Architect | 04/28/2014 | 04/30/2014 |
| Architect | 06/28/2014 | 06/30/2014 |
The following tables summarizes the mappings used to generate task-driven resource requestsDescribes a resource request that has been generated based on information on project tasks and their associated project task assignments. If you use a bottom-up approach to manage your projects, you can generate task-driven resource requests on the Generate Resource Requests From Project Task Assignments page (accessed from Project Task Gantt or the Project detail record). .
Key: * – Mandatory field
| Resource Request Field | Project Task Field | Project Task Assignment Field | Resource Field | |
|---|---|---|---|---|
| Start Date | - | Project Task Start Date lookup | - | |
| End Date | - | Project Task End Date lookup | - | |
| Notes | - | Resource (if attribute(s) other than Resource are selected on generation page) | - | |
| Requested Hours | Sum of Duration (Hours) field on all project tasks. | - | - | |
| Role | * | - | Resource Role (first choice mapping) | Resource Role (second choice mapping if role unspecified on project task assignment) |
| Suggested Resource | * | - | Resource | - |