-
Course description: “It’s easy to focus on the “cool” new features of the latest release and overlook the impact on specific End Users, and how they actually use new features and modules. Focusing on what Users need and want may not be easy, but it will lead to greater engagement, strong adoption and increase value of CA PPM. Join Empowered Networks for this session to discuss how to leverage User Personas in configuring CA PPM.” -
Course description: “What can leaders do after a CA PPM deployment to ensure continued success of the product? This session will discuss how sponsors can drive compliance within the organization through continued involvement. Strong sponsorship is the key to long term success.” Download file is the slide deck used during the presentation. -
The Timesheet Smoothing Process Workflow kicks-off when an individual timesheet is Submitted. It splits each transaction on the timesheet when total timesheet actuals exceed total weekly availability for the resource. Total weekly availability is determined by multiplying resource availability rate by the number of workdays in the week. Non-workdays include weekends, holidays, PTO, and other scheduled days off, as set on the resource calendar. If timesheet actuals <= total weekly availability, then the timesheet remains unchanged. But if timesheet actuals > total weekly availability, then the following occurs. Each timesheet transaction is reduced by a calculated percentage that will reduce the total regular hours to equal the total weekly availability. Then the remaining transaction hours are placed in a “Split” row for that task on that day, with an Input Type Code set based on a process parameter (which parameter can be set within the script action on the process). Note: If a single day has overtime hours, but the total timesheet actuals <= total weekly availability, no splitting occurs. -
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.
- 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.
- PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
-
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.
- 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.
- PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
-
This can be used to remove all automatic permissions (Project Manager Auto) granted to users as a result of becoming a project manager. NOTE: The ability to remove the right is with the admin only. -
A process that removes all the group assignments for inactive users after execution of process. The following are removed for all inactive users:- Group assignments
- Instance rights
- Global rights
-
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 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