- Determine if timesheet has > 40 hours. If so, proceed.
- Create a SPLIT row for each timesheet row, with Input Type Code = Non-Bill.
- Divide 40 by total timesheet ours. Store this value.
- Multiply each timesheet cell by the stored value, and enter the result into that cell.
- Take the difference (original cell value – new cell value), and enter in same cell on Split row.
- The end result will be 40 hours total on Billable rows, and overtime hours on Non-Billable rows.
-
This process workflow with gel script forces billable hours on timesheet down to 40 hours, and sets overtime hours to non-billable. Timesheets with 40 or fewer hours are not touched. Process kicks off upon submission of timesheet. Steps are: -
This process must be run using the “Execute a Process” job. Job may be scheduled or run on-demand. Process pulls Availability Rate from the Availability blob for each resource, where blob is not null. Then it populates this value into a custom Daily Availability attribute (Number field with 2 decimals) on the Resource object. This field does not have to be displayed to be used for reporting. Because the OOB Availability Rate field is stored only in a blob, it is difficult to include in portlet or report output. The use of this custom attribute makes the value easily reportable. -
A Resource Calendar sub-object is populated by a non-object-specific process, executed by the “Execute a Process” job, which can be scheduled. The first 7 rows of the sub-object display the standard week from the base calendar, including columns for Day of Week, Is Workday (checked/unchecked), Shifts, and work Hours available. The remaining rows display calendar exceptions, including columns for Day of Week, Exception Date, Is Exception (checked), and work Hours available. If exception changes to a workday, Is Workday column is checked, and Shifts also display. If exception changes to a non-workday, Is PTO column is checked. Resource Calendar object is filterable by Calendar Entry Type (All, Calendar Exception, Day of Week), Day of Week, Exception Date Range, Is Workday, Is Exception, Is PTO, and power filter. -
A Resource Calendar sub-object is populated by a non-object-specific process, executed by the “Execute a Process” job, which can be scheduled. The first 7 rows of the sub-object display the standard week from the base calendar, including columns for Day of Week, Is Workday (checked/unchecked), Shifts, and work Hours available. The remaining rows display calendar exceptions, including columns for Day of Week, Exception Date, Is Exception (checked), and work Hours available. If exception changes to a workday, Is Workday column is checked, and Shifts also display. If exception changes to a non-workday, Is PTO column is checked. Resource Calendar object is filterable by Calendar Entry Type (All, Calendar Exception, Day of Week), Day of Week, Exception Date Range, Is Workday, Is Exception, Is PTO, and power filter.
-
Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks. Email has links to each resource so that allocation modifications can be made as required. -
Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks. Email has links to each resource so that allocation modifications can be made as required.
-
Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks. Email has links to each resource so that allocation modifications can be made as required.
-
This process updates the team, assignment and timesheet roles with the primary role where they do not match. This way, the PM can push all roles to team and assignment for that project before they do a cost plan. -
This process updates the team, assignment and timesheet roles with the primary role where they do not match. This way, the PM can push all roles to team and assignment for that project before they do a cost plan.
-
This process updates the team, assignment and timesheet roles with the primary role where they do not match. This way, the PM can push all roles to team and assignment for that project before they do a cost plan.
-
The process notifies resource who has been added to investment today and allocation is greater or equal to 100%. The process is on-demand and would require the user to have appropriate rights to run the process. Process should be scheduled as daily once job. -
The process notifies resource who has been added to investment today and allocation is greater or equal to 100%. The process is on-demand and would require the user to have appropriate rights to run the process. Process should be scheduled as daily once job.
-
The process notifies resource who has been added to investment today and allocation is greater or equal to 100%. The process is on-demand and would require the user to have appropriate rights to run the process. Process should be scheduled as daily once job.
-
This process pulls in the total hours tracked, by resource, by task, for a given project for the weekly time period that ended. The information is sent to the Project Manager listed on the project. This process can be scheduled via the Execute a Process job. -
This process pulls in the total hours tracked, by resource, by task, for a given project for the weekly time period that ended. The information is sent to the Project Manager listed on the project. This process can be scheduled via the Execute a Process job.
-
This process pulls in the total hours tracked, by resource, by task, for a given project for the weekly time period that ended. The information is sent to the Project Manager listed on the project. This process can be scheduled via the Execute a Process job.
-
The Pending Contractor Termination Stalker process sends email to Resource Manager if the Contractor(s) termination date is 3 weeks or less. This is an On Demand process in Clarity named Contractor Reminders and can be manually executed from the Organizer. If there are number of processes in the Organizer – Available Processes, this process can be filtered and then checked to Start. When Contractor Reminders process is started it will be seen in the Initiated on the Processes tab. The process status can be monitored from Running to the Completed stage. The Progress when 100% and the Status is Completed an email would have arrived to the Resource Manager with subject: “Contractor(s) With Termination Date in 3 weeks or less”. This email will list the Contractors whose contracts will terminate on the identified date. -
The Pending Contractor Termination Stalker process sends email to Resource Manager if the Contractor(s) termination date is 3 weeks or less. This is an On Demand process in Clarity named Contractor Reminders and can be manually executed from the Organizer. If there are number of processes in the Organizer – Available Processes, this process can be filtered and then checked to Start. When Contractor Reminders process is started it will be seen in the Initiated on the Processes tab. The process status can be monitored from Running to the Completed stage. The Progress when 100% and the Status is Completed an email would have arrived to the Resource Manager with subject: “Contractor(s) With Termination Date in 3 weeks or less”. This email will list the Contractors whose contracts will terminate on the identified date.
-
The Pending Contractor Termination Stalker process sends email to Resource Manager if the Contractor(s) termination date is 3 weeks or less. This is an On Demand process in Clarity named Contractor Reminders and can be manually executed from the Organizer. If there are number of processes in the Organizer – Available Processes, this process can be filtered and then checked to Start. When Contractor Reminders process is started it will be seen in the Initiated on the Processes tab. The process status can be monitored from Running to the Completed stage. The Progress when 100% and the Status is Completed an email would have arrived to the Resource Manager with subject: “Contractor(s) With Termination Date in 3 weeks or less”. This email will list the Contractors whose contracts will terminate on the identified date.
-
The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago. The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed. -
The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago. The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed.
-
The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago. The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed.
-
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 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.
