-
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.
-
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.
-
When a team member is added to the Team tab of the project, this process will add Project - View Management and Resource – Hard Book instance access right to the team member’s profile. This allows the team member to add their own allocations. NOTE: The process is NOT auto-start, and hence, needs to be run manually from Home > Organizer > Processes > Available -
When a team member is added to the Team tab of the project, this process will add Project - View Management and Resource – Hard Book instance access right to the team member’s profile. This allows the team member to add their own allocations. NOTE: The process is NOT auto-start, and hence, needs to be run manually from Home > Organizer > Processes > Available
-
This is an automation to adjust the cost in financials (WIP) based on the standard weekly hours for salaried (Exempt) personnel. The process adjusts only the cost in WIP where the hours per week that are posted for a resource are more than the standard work week. The Posted hours in the timesheet and in WIP remain untouched. For the process to calculate correctly, all time in a given week needs to be accounted for, including all non-project time. The process has three input parameters as explained below:- wkStdHour: Standard Weekly Hours; this can be changed in the process gel script. The parameter is based on the organization standard work week. The default is set to 40 hours.
- xogBatchSize: The XOG batch size. This is used to upload data in batches to avoid high memory and performance issues. The default batch size is set to 50 records.
- username: The resource name that the process uses for uploading data. The default is set to admin.
- It will process all the timesheets in posted state provided the timesheet has not been adjusted earlier by this process and there are no pending transactions to be posted for it. Validation is made based on Notes field, which is populated once adjustment is done by the process.
- Notes field should not be modified in Script nor should be worked upon by any other process.
- All the invalid transactions should be cleared and post to WIP should be finished with no pending records.
-
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 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.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy