RegoXchange
RegoXchange
  •

    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

  • 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

  • Proactive Insights and Analytics for TCO | Tools and Data Sources to Help Calculate TCO – RegoU 2019

    $0.00
    Course Description:   Does your organization struggle to understand your fully burdened TCO for the applications that enable your business? Do you use spreadsheets and disparate data sources to manually calculate TCO? This session explores the data sources needed to calculate the fully burdened TCO for applications. We will also cover marketplace tools that allow you to track spending, providing trends of applications broken down by run and development costs.
    Details

  • Process Instance Errors – Oracle

    $0.00
    The Process Instance Errors portlet will show all processes that error. This portlet will assist the administrator with determining which processes are in error and whether to skip, retry, or cancel. It will display the process name, code, start date, and who initiated the process. You may also filter by any of the criteria listed in the grid.
    Details

  • Process Instance Errors – Postgres

    $0.00
    The Process Instance Errors portlet will show all processes that error. This portlet will assist the administrator with determining which processes are in error and whether to skip, retry, or cancel. It will display the process name, code, start date, and who initiated the process. You may also filter by any of the criteria listed in the grid.
    Details

  • Process Instance Errors – SQL

    $0.00
    The Process Instance Errors portlet will show all processes that error. This portlet will assist the administrator with determining which processes are in error and whether to skip, retry, or cancel. It will display the process name, code, start date, and who initiated the process. You may also filter by any of the criteria listed in the grid.
    Details

  • Process Run Metrics – Oracle

    $0.00
    For each process, the Process Run Metrics portlet shows the Process Name, Process Code, Description, # Running, # Completed, # Errored, and Last Run Date. This portlet is ideal for system administrators and support staff needing to monitor the health of the environment. Viewers of this portlet can get a sense of the complexity & health of the environment with the # of processes running and visibility into processes that errored out. The table below describes the available filter fields in the portlet.
    Column Label Description
    Process Name Name of the process
    Start Date Start date of the process’s last ran date
    End Date End date of the process’s last ran date
    Description Description of the process
    Process ID ID of the process
    Details

  • Process Run Metrics – Postgres

    $0.00
    For each process, the Process Run Metrics portlet shows the Process Name, Process Code, Description, # Running, # Completed, # Errored, and Last Run Date. This portlet is ideal for system administrators and support staff needing to monitor the health of the environment. Viewers of this portlet can get a sense of the complexity & health of the environment with the # of processes running and visibility into processes that errored out. The table below describes the available filter fields in the portlet.
    Column Label Description
    Process Name Name of the process
    Start Date Start date of the process’s last ran date
    End Date End date of the process’s last ran date
    Description Description of the process
    Process ID ID of the process
    Details

  • Process Run Metrics – SQL

    $0.00
    For each process, the Process Run Metrics portlet shows the Process Name, Process Code, Description, # Running, # Completed, # Errored, and Last Run Date. This portlet is ideal for system administrators and support staff needing to monitor the health of the environment. Viewers of this portlet can get a sense of the complexity & health of the environment with the # of processes running and visibility into processes that errored out. The table below describes the available filter fields in the portlet.
    Column Label Description
    Process Name Name of the process
    Start Date Start date of the process’s last ran date
    End Date End date of the process’s last ran date
    Description Description of the process
    Process ID ID of the process
    Details

  • Process to Reschedule Projects – Oracle

    $0.00
    This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date.  Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox.  The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date.  Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE:  The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar.  The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account.  For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero.
    Details

  • Process to Reschedule Projects – Postgres

    $0.00
    This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date.  Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox.  The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date.  Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE:  The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar.  The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account.  For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero.
    Details

Copyright 2023 •  Rego Consulting Corporation • Privacy Policy

Go to Top