RegoXchange
  • Based on the pre-determined schedule frequency, this job will send an email to Project Managers that have a project meeting the criteria of: project(s) are active and scheduled finish date is less than the current date. This serves as a reminder to Project Managers to keep their schedules true. The contents of the email include a message indicating the project manager has at least one project meeting this criteria and a table indicating the Project ID, Project Name and Scheduled Finish Date.
  • 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 Enhanced Time Tracking Stalker – RM workflow process automatically sends a single email to Resource Managers which contains a list of any of their resources that have not submitted their timesheet for a prior open time period.  The email informs the RM if their resources are submitting their timesheets on time.  The email includes a table that provides this information for each resource: Resource Name, Time Period, Timesheet Status and Total Hours saved on the timesheet with links to the timesheet in the Modern User Experience of Clarity. These notifications will help to ensure that time is being posted and approved in a timely manner.
  • 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 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 Timesheet Approval - RM 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) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM 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 Timesheet Approval - Auto process is an auto-start process that begins once the resource submits his or her timesheet. This process bypasses a Resource Manager approval and allows the user to post his or her timesheet. 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 the issue, unlock the timesheet, and change 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 user as a last step before the timesheet is approved. Once the timesheet is approved, then the script will set the status of the timesheet to “Approved” and unlock the timesheet.
  • 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 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 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.
  • The Give RM Calendar & Time Rights workflow process can be run through the "Execute a Process" job.  The workflow will execute a query that gives a Resource Manager Calendar Edit and Timesheet Edit rights for their resources. These rights are not inherent for Resource Managers when they are named as an individual’s resource manager.
  • The Grant Project Edit Rights workflow process allows a project manager to grant project edit rights to another user without contacting an administrator. The workflow uses the Out-of-the-box field for Business Owner. The script starts when the field is updated. It will assign project edit rights to whichever user is added to the Business Owner field.  This process can be modified to grant project edit rights to any user within a project field.
Go to Top