RegoXchange
RegoXchange
  •

    PrLock Clear for Timesheet Locks – Postgres

    $0.00
    The process is built to clear the random timesheet locks that happens occasionally.  There are three Processes and one lookup component and one job definition in the package.
    • PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
      • The Lookup PRLock Check (Timesheet) (Id: REGO_PRLOCK_CHECK) should be used to update the GEL parameters for the above process.
    • PRLock (Timesheets) Record Removal All (ID: rego_prlk_rc_rmv_all) This deletes ALL prtimesheet locks.
    Or
    • Rego Remove Timesheet Locks (ID: rego_rmv_ts_locks). This process is run as a job “PrLock Clear for Timesheet Locks” which performs the same functionality as the above two processes. The process and job definition are separate XOG files.
    Details

  • PrLock Clear for Timesheet Locks – SQL

    $0.00
    The process is built to clear the random timesheet locks that happens occasionally.  There are three Processes and one lookup component and one job definition in the package.
    • PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
      • The Lookup PRLock Check (Timesheet) (Id: REGO_PRLOCK_CHECK) should be used to update the GEL parameters for the above process.
    • PRLock (Timesheets) Record Removal All (ID: rego_prlk_rc_rmv_all) This deletes ALL prtimesheet locks.
    Or
    • Rego Remove Timesheet Locks (ID: rego_rmv_ts_locks). This process is run as a job “PrLock Clear for Timesheet Locks” which performs the same functionality as the above two processes. The process and job definition are separate XOG files.
    Details

  • PrLock Clear for Timesheet Locks – Oracle

    $0.00
    The process is built to clear the random timesheet locks that happens occasionally.  There are three Processes and one lookup component and one job definition in the package.
    • PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
      • The Lookup PRLock Check (Timesheet) (Id: REGO_PRLOCK_CHECK) should be used to update the GEL parameters for the above process.
    • PRLock (Timesheets) Record Removal All (ID: rego_prlk_rc_rmv_all) This deletes ALL prtimesheet locks.
    Or
    • Rego Remove Timesheet Locks (ID: rego_rmv_ts_locks). This process is run as a job “PrLock Clear for Timesheet Locks” which performs the same functionality as the above two processes. The process and job definition are separate XOG files.
    Details

  • Timesheet Split Process – Postgres

    $0.00
    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.
    Details

  • Timesheet Split Process – Oracle

    $0.00
    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.
    Details

  • Populate Resource Calendar Data – SQL

    $0.00
    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.
    Details

  • Populate Resource Calendar Data – Oracle

    $0.00
    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.
    Details

  • RM Stalker – Resource Allocation by Percent – Postgres

    $0.00
    Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks.  Email has links to each resource so that allocation modifications can be made as required.
    Details

  • RM Stalker – Resource Allocation by Percent – SQL

    $0.00
    Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks.  Email has links to each resource so that allocation modifications can be made as required.
    Details

  • RM Stalker – Resource Allocation by Percent – Oracle

    $0.00
    Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks.  Email has links to each resource so that allocation modifications can be made as required.
    Details

  • Resource Over-Allocation Notification – Postgres

    $0.00
    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.
    Details

  • Resource Over-Allocation Notification – Oracle

    $0.00
    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.
    Details

Copyright 2023 •  Rego Consulting Corporation • Privacy Policy

Go to Top