RegoXchange
  • This is workflow that allows you to copy documents from one item to another. This can be altered to move documents from any place they are stored to another. In this particular instance, the focus is on moving documents from one risk to another. When creating a risk that you want to copy from, utilize the attachments section of the page and the associated lookup. The lookup is filtered to only show those risks that already have documents associated with them. Upon clicking the save button, a process runs in the background to copy the requested documents from the requested risk to this newly created risk.
  • This is workflow that allows you to copy documents from one item to another. This can be altered to move documents from any place they are stored to another. In this particular instance, the focus is on moving documents from one risk to another. When creating a risk that you want to copy from, utilize the attachments section of the page and the associated lookup. The lookup is filtered to only show those risks that already have documents associated with them. Upon clicking the save button, a process runs in the background to copy the requested documents from the requested risk to this newly created risk.
  • This is workflow that allows you to copy documents from one item to another. This can be altered to move documents from any place they are stored to another. In this particular instance, the focus is on moving documents from one risk to another. When creating a risk that you want to copy from, utilize the attachments section of the page and the associated lookup. The lookup is filtered to only show those risks that already have documents associated with them. Upon clicking the save button, a process runs in the background to copy the requested documents from the requested risk to this newly created risk.
  • 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.
  • 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.
  • 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.
  • The Roadmap Cloning process creates a clone of any existing roadmap.  It should be run using the “Execute a Process” job.  To specify a roadmap to clone the Start Step Action’s Custom Script Parameters need to be updated to include the proper roadmap ID in the templateCode field.
  • The Roadmap Cloning process creates a clone of any existing roadmap.  It should be run using the “Execute a Process” job.  To specify a roadmap to clone the Start Step Action’s Custom Script Parameters need to be updated to include the proper roadmap ID in the templateCode field.
  • The Roadmap Cloning process creates a clone of any existing roadmap.  It should be run using the “Execute a Process” job.  To specify a roadmap to clone the Start Step Action’s Custom Script Parameters need to be updated to include the proper roadmap ID in the templateCode field.
  • The Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource.  You first choose the resource who currently has the action item(s) sitting in their queue.  Next, you choose the resource you want to reassign the action item(s) to.  Finally, you select one to many action items you want to re-associate before running the process.  After all the fields are set, the process can be run which will re-associate the action items from one resource to the other.
  • The Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource.  You first choose the resource who currently has the action item(s) sitting in their queue.  Next, you choose the resource you want to reassign the action item(s) to.  Finally, you select one to many action items you want to re-associate before running the process.  After all the fields are set, the process can be run which will re-associate the action items from one resource to the other.
  • The Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource.  You first choose the resource who currently has the action item(s) sitting in their queue.  Next, you choose the resource you want to reassign the action item(s) to.  Finally, you select one to many action items you want to re-associate before running the process.  After all the fields are set, the process can be run which will re-associate the action items from one resource to the other.
Go to Top