-
Course Description: Are you tracking your vendor contracts outside of Clarity PPM? Have you considered moving the data into Clarity PPM? This session will review a set of use cases where Clarity PPM is being used to manage vendor contracts and how they are linked to resources, projects, and time to drive efficiencies in monitoring contracts and comparing actuals to invoices.
-
The Convert Incident to Task workflow process allows users to quickly create tasks from incidents without the need to input the information twice. It utilizes a newly added checkbox and project fields on the incident object. The user will need to select the project that he or she wants the task added to using the “Project” field on the incident object. Next, the “Convert to Task” checkbox will kick off the process. Once ticked, the process will perform the necessary actions to create a task on the specified project.
-
The Convert Incident to Task workflow process allows users to quickly create tasks from incidents without the need to input the information twice. It utilizes a newly added checkbox and project fields on the incident object. The user will need to select the project that he or she wants the task added to using the “Project” field on the incident object. Next, the “Convert to Task” checkbox will kick off the process. Once ticked, the process will perform the necessary actions to create a task on the specified project.
-
The Convert Incident to Task workflow process allows users to quickly create tasks from incidents without the need to input the information twice. It utilizes a newly added checkbox and project fields on the incident object. The user will need to select the project that he or she wants the task added to using the “Project” field on the incident object. Next, the “Convert to Task” checkbox will kick off the process. Once ticked, the process will perform the necessary actions to create a task on the specified project.
-
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.
-
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) - 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.
-
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) - 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.
-
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) - 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.
-
This training document is a Rego Consulting Quick Reference Guide to assist with creation of agreements in Clarity’s Modern User Experience. Agreements can be created between Project, Ideas and Custom Investments. The Agreement can convey things needed for predecessors and successors while defining appropriate dates to meet the agreement. Blueprints can be leveraged to customize the agreements as required.