-
This process must be run using the “Execute a Process” job. Job may be scheduled or run on-demand. Process pulls Availability Rate from the Availability blob for each resource, where blob is not null. Then it populates this value into a custom Daily Availability attribute (Number field with 2 decimals) on the Resource object. This field does not have to be displayed to be used for reporting. Because the OOB Availability Rate field is stored only in a blob, it is difficult to include in portlet or report output. The use of this custom attribute makes the value easily reportable. -
This is an automation to adjust the cost in financials (WIP) based on the standard weekly hours for salaried (Exempt) personnel. The process adjusts only the cost in WIP where the hours per week that are posted for a resource are more than the standard work week. The Posted hours in the timesheet and in WIP remain untouched. For the process to calculate correctly, all time in a given week needs to be accounted for, including all non-project time. The process has three input parameters as explained below:- wkStdHour: Standard Weekly Hours; this can be changed in the process gel script. The parameter is based on the organization standard work week. The default is set to 40 hours.
- xogBatchSize: The XOG batch size. This is used to upload data in batches to avoid high memory and performance issues. The default batch size is set to 50 records.
- username: The resource name that the process uses for uploading data. The default is set to admin.
- It will process all the timesheets in posted state provided the timesheet has not been adjusted earlier by this process and there are no pending transactions to be posted for it. Validation is made based on Notes field, which is populated once adjustment is done by the process.
- Notes field should not be modified in Script nor should be worked upon by any other process.
- All the invalid transactions should be cleared and post to WIP should be finished with no pending records.
-
The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago. The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed. -
The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago. The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed.
-
The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago. The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed.
-
The Project Compliance Stalker – PM sends an email to Project Managers (and also their managers if so desired) at a set interval to alert them to project compliance issues. Areas of compliance that are reviewed include: stale project tasks (stale = past due date), late issues and risks (past due date) and late status reports. -
The Project Compliance Stalker – PM sends an email to Project Managers (and also their managers if so desired) at a set interval to alert them to project compliance issues. Areas of compliance that are reviewed include: stale project tasks (stale = past due date), late issues and risks (past due date) and late status reports.
-
The Project Compliance Stalker – PM sends an email to Project Managers (and also their managers if so desired) at a set interval to alert them to project compliance issues. Areas of compliance that are reviewed include: stale project tasks (stale = past due date), late issues and risks (past due date) and late status reports.
-
The Grant Booking Manager Rights to Book Resources workflow provides a resource’s Booking Manager with the rights to hard book a resource to a project. This workflow will remove unused rights, and then grant the rights needed to allow for booking of resources. The workflow also has the ability to add rights to not only the resource but also the resource manager, and resources that are assigned as proxies. If this functionality is not needed, it can easily be removed. -
The Grant Booking Manager Rights to Book Resources workflow provides a resource’s Booking Manager with the rights to hard book a resource to a project. This workflow will remove unused rights, and then grant the rights needed to allow for booking of resources. The workflow also has the ability to add rights to not only the resource but also the resource manager, and resources that are assigned as proxies. If this functionality is not needed, it can easily be removed.
-
The Grant Booking Manager Rights to Book Resources workflow provides a resource’s Booking Manager with the rights to hard book a resource to a project. This workflow will remove unused rights, and then grant the rights needed to allow for booking of resources. The workflow also has the ability to add rights to not only the resource but also the resource manager, and resources that are assigned as proxies. If this functionality is not needed, it can easily be removed.
-
The Unlock Projects workflow process can be run through the "Execute a Process" job. The workflow will execute a query that will automatically unlock projects that have been exported / checked out for over 2 days. This prevents any projects from remaining in the “locked” state for a long period of time, preventing time from posting to these projects.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy