Shop - Page 78 of 168

Roadmap Cloning – SQL

$0.00

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.

Details

Roadmap Cloning – Postgres

$0.00

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.

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

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 – 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

Copy Documents – Oracle

$0.00

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.

Details

Copy Documents – SQL

$0.00

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.

Details

Copy Documents – Postgres

$0.00

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.

Details

Create Forecast from Actuals and Allocations – Oracle

$0.00

A process creating a new Cost Plan. Cost Plan properties:

Name	Cost Plan created on: yyyy/mm/dd hh:mm:ss
Grouping attributes	Charge Code, Transaction Type
Start Period	The earliest fiscal period with Actuals (from PPA_WIP table) or current period, if there are no actuals
Finish Period	The latest fiscal period with a non-zero allocation (from PRJ_BLB_SLICES table, SLICE_REQUEST_ID = 6
Period Type	Monthly
Plan of Record	True
Planned Cost	For periods in the past – from Actuals (Charge Code, Transaction Type, Quantity (Units), Cost (Amount) taken from Transactions (PPA_WIP & PPA_WIP_DETAILS); For current and future periods – from Allocations (Charge Code taken from the Project, Transaction Class from the Resource, Quantity from allocation slices, Cost from the Rate Matrix (NBI_PROJ_RES_RATES_AND_COSTS table)

Pre-conditions:

the Project must be financially enabled.
if a new Team Member is added, Rate Matrix job must be run, so the rates are populated in the NBI table.
if the Allocation changes, allow the timeslice job to finish before running the process.
the Project should have the Charge Code set.

Details

Create Forecast from Actuals and Allocations – SQL

$0.00

A process creating a new Cost Plan. Cost Plan properties:

Name	Cost Plan created on: yyyy/mm/dd hh:mm:ss
Grouping attributes	Charge Code, Transaction Type
Start Period	The earliest fiscal period with Actuals (from PPA_WIP table) or current period, if there are no actuals
Finish Period	The latest fiscal period with a non-zero allocation (from PRJ_BLB_SLICES table, SLICE_REQUEST_ID = 6
Period Type	Monthly
Plan of Record	True
Planned Cost	For periods in the past – from Actuals (Charge Code, Transaction Type, Quantity (Units), Cost (Amount) taken from Transactions (PPA_WIP & PPA_WIP_DETAILS); For current and future periods – from Allocations (Charge Code taken from the Project, Transaction Class from the Resource, Quantity from allocation slices, Cost from the Rate Matrix (NBI_PROJ_RES_RATES_AND_COSTS table)

Pre-conditions:

the Project must be financially enabled.
if a new Team Member is added, Rate Matrix job must be run, so the rates are populated in the NBI table.
if the Allocation changes, allow the timeslice job to finish before running the process.
the Project should have the Charge Code set.

Details

Create Forecast from Actuals and Allocations – Postgres

$0.00

A process creating a new Cost Plan. Cost Plan properties:

Name	Cost Plan created on: yyyy/mm/dd hh:mm:ss
Grouping attributes	Charge Code, Transaction Type
Start Period	The earliest fiscal period with Actuals (from PPA_WIP table) or current period, if there are no actuals
Finish Period	The latest fiscal period with a non-zero allocation (from PRJ_BLB_SLICES table, SLICE_REQUEST_ID = 6
Period Type	Monthly
Plan of Record	True
Planned Cost	For periods in the past – from Actuals (Charge Code, Transaction Type, Quantity (Units), Cost (Amount) taken from Transactions (PPA_WIP & PPA_WIP_DETAILS); For current and future periods – from Allocations (Charge Code taken from the Project, Transaction Class from the Resource, Quantity from allocation slices, Cost from the Rate Matrix (NBI_PROJ_RES_RATES_AND_COSTS table)

Pre-conditions:

the Project must be financially enabled.
if a new Team Member is added, Rate Matrix job must be run, so the rates are populated in the NBI table.
if the Allocation changes, allow the timeslice job to finish before running the process.
the Project should have the Charge Code set.

Details

PM Task Time Notification – Oracle

$0.00

Notify the PM with a list of tasks for their project as soon as the Timesheet is submitted. This is a good substitute for PM approval. When a timesheet is submitted, then the PM knows the time entered by person. This is an Auto-start process in Clarity named PM Time Notification - On Timesheet Submission and will be automatically spawned when a Timesheet is submitted. When the process is started it will be seen in the Initiated on the Processes tab. The process status can be monitored from Running to the Completed stage. The Progress when 100% and the Status is Completed, an email would have arrived to the Project Manager with subject: “Resource <Name> has entered the following time on your Investment(s) for the week starting <Timesheet Start Date> ”. This email will list the Investments managed by the PM where task was entered by the Resource submitting the timesheet. Each PM would get a separate notification. PM for project X notified, and PM for project Y gets notified in another email. Therefore, one timesheet may spawn out multiple emails. But, if both the Projects have the Same PM, then only a single email gets sent out. “Opt-out Timesheet Notifications" checkbox is provided on the Project for PM’s who do not want to get notified on those projects.

Details