RegoXchange
  • The PM Stalker – Submit Status Report workflow process will email any project manager that has not submitted a status report in the last two weeks. This process will ensure that all status reports are kept up-to-date and provide management with a reliable overview of the status on the project.
  • The PM Stalker – Submit Status Report workflow process will email any project manager that has not submitted a status report in the last two weeks. This process will ensure that all status reports are kept up-to-date and provide management with a reliable overview of the status on the project.
  • Notify the PM with a list of tasks for their project as soon as the Timesheet is submitted.  This is a good substitute for PM approval. When a timesheet is submitted, then the PM knows the time entered by person. This is an Auto-start process in Clarity named PM Time Notification - On Timesheet Submission and will be automatically spawned when a Timesheet is submitted. When the 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 Project Manager with subject: “Resource <Name> has entered the following time on your Investment(s) for the week starting <Timesheet Start Date> ”. This email will list the Investments managed by the PM where task was entered by the Resource submitting the timesheet.  Each PM would get a separate notification. PM for project X notified, and PM for project Y gets notified in another email. Therefore, one timesheet may spawn out multiple emails. But, if both the Projects have the Same PM, then only a single email gets sent out. “Opt-out Timesheet Notifications" checkbox is provided on the Project for PM’s who do not want to get notified on those projects.
  • Notify the PM with a list of tasks for their project as soon as the Timesheet is submitted.  This is a good substitute for PM approval. When a timesheet is submitted, then the PM knows the time entered by person. This is an Auto-start process in Clarity named PM Time Notification - On Timesheet Submission and will be automatically spawned when a Timesheet is submitted. When the 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 Project Manager with subject: “Resource <Name> has entered the following time on your Investment(s) for the week starting <Timesheet Start Date> ”. This email will list the Investments managed by the PM where task was entered by the Resource submitting the timesheet.  Each PM would get a separate notification. PM for project X notified, and PM for project Y gets notified in another email. Therefore, one timesheet may spawn out multiple emails. But, if both the Projects have the Same PM, then only a single email gets sent out. “Opt-out Timesheet Notifications" checkbox is provided on the Project for PM’s who do not want to get notified on those projects.
  • Notify the PM with a list of tasks for their project as soon as the Timesheet is submitted.  This is a good substitute for PM approval. When a timesheet is submitted, then the PM knows the time entered by person. This is an Auto-start process in Clarity named PM Time Notification - On Timesheet Submission and will be automatically spawned when a Timesheet is submitted. When the 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 Project Manager with subject: “Resource <Name> has entered the following time on your Investment(s) for the week starting <Timesheet Start Date> ”. This email will list the Investments managed by the PM where task was entered by the Resource submitting the timesheet.  Each PM would get a separate notification. PM for project X notified, and PM for project Y gets notified in another email. Therefore, one timesheet may spawn out multiple emails. But, if both the Projects have the Same PM, then only a single email gets sent out. “Opt-out Timesheet Notifications" checkbox is provided on the Project for PM’s who do not want to get notified on those projects.
  • 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 Populate Prior Periods Forecast From Actuals in Cost Plans process updates Cost Plans for Active Projects, it updates the Forecast for previous months = Posted Actuals, to remove variances from past periods.   This is an On Demand process in Clarity named Populate Prior Periods Forecast From Actuals in Cost Plans and can be manually executed from the Organizer or scheduled through the “Execute a Process” job. If there are number of processes in the Organizer – Available Processes, this process can be filtered and then checked to Start. When the 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 process is very flexible and supports Cost Plans with any given grouping and it also works without any dependency on timeslices or other jobs. The process fetches Cost plan of records for all active projects in the system that have Actuals transactions in WIP table. It then process those cost plans to update all of the prior monthly forecast periods with the corresponding monthly Actuals.
  • The Populate Prior Periods Forecast From Actuals in Cost Plans process updates Cost Plans for Active Projects, it updates the Forecast for previous months = Posted Actuals, to remove variances from past periods. This is an On Demand process in Clarity named Populate Prior Periods Forecast From Actuals in Cost Plans and can be manually executed from the Organizer or scheduled through the “Execute a Process” job. If there are number of processes in the Organizer – Available Processes, this process can be filtered and then checked to Start. When the 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 process is very flexible and supports Cost Plans with any given grouping and it also works without any dependency on timeslices or other jobs. The process fetches Cost plan of records for all active projects in the system that have Actuals transactions in WIP table. It then process those cost plans to update all of the prior monthly forecast periods with the corresponding monthly Actuals.
  • The Populate Prior Periods Forecast From Actuals in Cost Plans process updates Cost Plans for Active Projects, it updates the Forecast for previous months = Posted Actuals, to remove variances from past periods. This is an On Demand process in Clarity named Populate Prior Periods Forecast From Actuals in Cost Plans and can be manually executed from the Organizer or scheduled through the “Execute a Process” job. If there are number of processes in the Organizer – Available Processes, this process can be filtered and then checked to Start. When the 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 process is very flexible and supports Cost Plans with any given grouping and it also works without any dependency on timeslices or other jobs. The process fetches Cost plan of records for all active projects in the system that have Actuals transactions in WIP table. It then process those cost plans to update all of the prior monthly forecast periods with the corresponding monthly Actuals.
  • 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.
Go to Top