- Role – mapping table
- Tables / Columns that need to be updated with Resource ID fields
- Tables / Columns that need to be updated with Role Code fields
- Tables that will need to be deleted
- PRTEAM table should be checked
-
In many instances, having excess information stored within the database can cause poor performance or slowness when retrieving data. Administrators are always seeking out ways to clean and remove unused information. This technical trick on role removal provides the steps necessary to remove roles that would otherwise be unused and eliminating unwanted information. The Role Removal Technical Trick provides the information for the creation of the following tables and columns which are necessary to perform the role removal: -
This Roadmap add-on provides configurable Role-based metrics that can be used in the grid view as targets and constraints. Select your valuable roles in the “targets” and once selected, the “sync” button will bring in any current allocations against projects and allow editing any of the total numbers directly in a scenario. This will provide deeper insights into impacts of plans on teams/resources in addition to the out of the box money and time constraints. -
This is a graphic portlet that pulls the average schedule variance by OBS node of the project. The portlet allows you to choose any OBS that is associated to the Project Object. Users can filter by:- OBS Type
- If the project is financially approved?
- Financial Status
-
This is a graphic portlet that pulls the average schedule variance by OBS node of the project. The portlet allows you to choose any OBS that is associated to the Project Object. Users can filter by:
- OBS Type
- If the project is financially approved?
- Financial Status
-
This is a graphic portlet that pulls the average schedule variance by OBS node of the project. The portlet allows you to choose any OBS that is associated to the Project Object. Users can filter by:
- OBS Type
- If the project is financially approved?
- Financial Status
-
This portlet shows the variance between the schedule finish and baseline finish for projects. The portlet also displays the schedule variance: {(Finish-Start) – (Baseline Finish-Baseline Start)}. -
This portlet shows the variance between the schedule finish and baseline finish for projects. The portlet also displays the schedule variance: {(Finish-Start) – (Baseline Finish-Baseline Start)}.
-
This portlet shows the variance between the schedule finish and baseline finish for projects. The portlet also displays the schedule variance: {(Finish-Start) – (Baseline Finish-Baseline Start)}.
-
The Scheduled Jobs Cleanup process removes all completed job instances that have run before a date set by the administrator. The administrator may use the gel parameter to update the amount of days since each job has run. Based on that date, the workflow will eliminate all jobs that have surpassed that threshold. This workflow helps administrators maintain the job logs and queue by eliminating jobs that users have potentially forgotten to remove on their own. -
The Scheduled Jobs Cleanup process removes all completed job instances that have run before a date set by the administrator. The administrator may use the gel parameter to update the amount of days since each job has run. Based on that date, the workflow will eliminate all jobs that have surpassed that threshold. This workflow helps administrators maintain the job logs and queue by eliminating jobs that users have potentially forgotten to remove on their own.
-
The Scheduled Jobs Cleanup process removes all completed job instances that have run before a date set by the administrator. The administrator may use the gel parameter to update the amount of days since each job has run. Based on that date, the workflow will eliminate all jobs that have surpassed that threshold. This workflow helps administrators maintain the job logs and queue by eliminating jobs that users have potentially forgotten to remove on their own.
-
The Self Assign workflow process updates a selected resource field on an object based on someone checking a boolean field on the same object. Using this process, whomever is editing the object, will be placed in this field automatically eliminating the need for each user to come in and update the field manually. The field will run when the Boolean is ticked and the user saves the page. It is important to note that the page will need to be reloaded to see the changes reflected. This can be used as a fast way to self-assign yourself to an object - you can create a boolean field that is checked and have the process assign you to that item.
