RegoXchange
  • 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:
    1. The timesheet has less than 40 hours.
    2. The timesheet has 40 or more hours.
    3. The resource’s availability is less than 8hrs/day.
    If the user has submitted a timesheet with less than 40 hours, then the process will email the user informing him/her of issue, unlocks the timesheet, and changes the status to “Returned”. If the user has an availability of less than 8hrs/day or the timesheet has 40 or more hours, then an action item will be sent to the resource manager informing him/her of the timesheet. If the resource manager (RM) AND project manager (PM) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM or PM selects “Return” on the action item, then the process will return the timesheet, mail the user that informing him/her that the timesheet has been returned, and unlock the timesheet.
  • The Time Tracking Stalker - RM workflow process automatically sends an email to Resource Managers for each one of their resources that have not submitted their timesheet for a prior open time period, thus informing the RM if their resources are submitting their timesheets on time. Project Managers will also benefit since the notifications will help to ensure that time is being posted against their projects in a timely manner, helping to provide them with an accurate view of time expended on the projects.
  • The Time Tracking Stalker - RM workflow process automatically sends an email to Resource Managers for each one of their resources that have not submitted their timesheet for a prior open time period, thus informing the RM if their resources are submitting their timesheets on time. Project Managers will also benefit since the notifications will help to ensure that time is being posted against their projects in a timely manner, helping to provide them with an accurate view of time expended on the projects.
  • The Time Tracking Stalker - RM workflow process automatically sends an email to Resource Managers for each one of their resources that have not submitted their timesheet for a prior open time period, thus informing the RM if their resources are submitting their timesheets on time. Project Managers will also benefit since the notifications will help to ensure that time is being posted against their projects in a timely manner, helping to provide them with an accurate view of time expended on the projects.
  • 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 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 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.
  • 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.
  • The Self Assign workflow process updates a selected resource field on an object based on someone checking a boolean field on the same object. Using this process, whomever is editing the object, will be placed in this field automatically eliminating the need for each user to come in and update the field manually. The field will run when the Boolean is ticked and the user saves the page. It is important to note that the page will need to be reloaded to see the changes reflected.  This can be used as a fast way to self-assign yourself to an object - you can create a boolean field that is checked and have the process assign you to that item.
  • The Self Assign workflow process updates a selected resource field on an object based on someone checking a boolean field on the same object. Using this process, whomever is editing the object, will be placed in this field automatically eliminating the need for each user to come in and update the field manually. The field will run when the Boolean is ticked and the user saves the page. It is important to note that the page will need to be reloaded to see the changes reflected.  This can be used as a fast way to self-assign yourself to an object - you can create a boolean field that is checked and have the process assign you to that item.
  • The Scheduled Jobs Cleanup process removes all completed job instances that have run before a date set by the administrator. The administrator may use the gel parameter to update the amount of days since each job has run. Based on that date, the workflow will eliminate all jobs that have surpassed that threshold. This workflow helps administrators maintain the job logs and queue by eliminating jobs that users have potentially forgotten to remove on their own.
Go to Top