RegoXchange
  • 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:
    • 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:
    • 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.
  • The Timesheets by Resource portlet gives the ability to highlight the time periods where resources are working overtime or working less than 25 hours a week. The filter requires timesheet Start Date and End Date to be provided. Additionally, the information can be filtered by Resource, Resource ID, OBS Unit, Employment Type, Resource Manager, Open for Time, and Active status. This portlet displays Resource, Resource ID, Active (yes/no), Employment Type, Primary Role, Resource Manager, and Timesheet Hours Flag. The flags are set with the logic
    • Yellow = timesheets not posted / zero hour timesheets
    • Green = where number of hours posted is > 25 and less than 45
    • Red = where number of hours posted is < 25 or > 45
    The thresholds can, of course, be modified.
  • The Timesheets by Resource portlet gives the ability to highlight the time periods where resources are working overtime or working less than 25 hours a week. The filter requires timesheet Start Date and End Date to be provided. Additionally, the information can be filtered by Resource, Resource ID, OBS Unit, Employment Type, Resource Manager, Open for Time, and Active status. This portlet displays Resource, Resource ID, Active (yes/no), Employment Type, Primary Role, Resource Manager, and Timesheet Hours Flag. The flags are set with the logic
    • Yellow = timesheets not posted / zero hour timesheets
    • Green = where number of hours posted is > 25 and less than 45
    • Red = where number of hours posted is < 25 or > 45
    The thresholds can, of course, be modified.
  • The Timesheets by Resource portlet gives the ability to highlight the time periods where resources are working overtime or working less than 25 hours a week. The filter requires timesheet Start Date and End Date to be provided. Additionally, the information can be filtered by Resource, Resource ID, OBS Unit, Employment Type, Resource Manager, Open for Time, and Active status. This portlet displays Resource, Resource ID, Active (yes/no), Employment Type, Primary Role, Resource Manager, and Timesheet Hours Flag. The flags are set with the logic
    • Yellow = timesheets not posted / zero hour timesheets
    • Green = where number of hours posted is > 25 and less than 45
    • Red = where number of hours posted is < 25 or > 45
    The thresholds can, of course, be modified.
  • The REGO Timesheets - WIP portlet displays timesheet information for timesheets that have a status of posted but have not been posted to the WIP tables. This does not include records hung up in invalid transactions. Users can further narrow their search by Project Name, Resource Name, Timesheet Status, Start Date, and Finish Date.
  • ** No Download - Do not Add to Cart ** As Clarity's Modern UX continues to evolve with each release, so has the transition conversation among Clarity Product Owners and Administrators. It's no longer a question of "if" and "when;" the question is, how? In this webinar, we'll explore some best practices that enable a successful shift from Classic to Modern. Through a collaborative discussion of overarching strategies to a step-by-step checklist, this session is designed to help you quickly position your users to take advantage of Clarity's latest and greatest capabilities. Nothing to Download - See Link below. http://info.regoconsulting.com/when-to-move-to-modernux-aug-2020
Go to Top