-
This notification process sends an email to the Manager of an investment (Project, Application, Idea, etc) when the resource assigned to the team has been hard booked. The process should be scheduled to run on a daily basis as the logic in it looks to all resources where their Booking Status has been changed from Soft to Hard on the day that the process is run. It compares the audit trail date change field to the system date. If the process is not scheduled to run daily no notification will occur on hardbookings from previous days. -
This notification process sends an email to the Manager of an investment (Project, Application, Idea, etc) when the resource assigned to the team has been hard booked. The process should be scheduled to run on a daily basis as the logic in it looks to all resources where their Booking Status has been changed from Soft to Hard on the day that the process is run. It compares the audit trail date change field to the system date. If the process is not scheduled to run daily no notification will occur on hardbookings from previous days.
-
Based on the pre-determined schedule frequency, this job will send an email to Resource Managers that have a Resource meeting the criteria of: Average allocations are less than 100% where Resource(s) and Project(s) are active over the next two weeks. This serves as a reminder to Resource Managers to monitor and manage allocations. The contents of the email include a message indicating the Resource Manager has at least one Resource meeting this criteria and a table indicating the Resource and that resource’s average, next 90 days allocations. -
Based on the pre-determined schedule frequency, this job will send an email to Resource Managers that have a Resource meeting the criteria of: Average allocations are greater than 120% where Resource(s) and Project(s) are active over the next 90 days. This serves as a reminder to Resource Managers to monitor and manage allocations. The contents of the email include a message indicating the Resource Manager has at least one Resource meeting this criteria and a table indicating the Resource and that resource’s average, next 90 days allocations. -
The Grant Resources Timesheet Edit Rights process will grant each resource timesheet edit instance rights to his or her own timesheets. This process will not remove any existing timesheet edit instance rights. -
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project. -
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project.
-
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in. -
The Unlock Projects workflow process can be run through the "Execute a Process" job. The workflow will execute a query that will automatically unlock projects that have been exported / checked out for over 2 days. This prevents any projects from remaining in the “locked” state for a long period of time, preventing time from posting to these projects. -
The Timesheet Approval - RM and PM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Time Tracking Stalker – Resource workflow process is used to notify resources that fail to submit a timesheet in a prior week. The workflow checks for active resources, hire/termination dates, track mode, and open for time entry. This process helps to ensure resources submit timesheets in a timely manner. In version 13, the email can be enhanced to include colors, bold, underline, and other HTML formatting. -
The Status Report Publish workflow process pushes values from the status report sub-object to the parent project object. The process is started when the user ticks the “Publish” Boolean field on the status report (custom field added). This workflow will update the project object with the overall status indicator, the status comment, the previous overall status, and the as of date. This eliminates the project manager having to update the fields in both the status report and the project overall.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy