-
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project. -
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in. -
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. -
The Timesheet Approval - RM and PM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Grant RM Timesheet Edit Rights workflow process can be run through the "Execute a Process" job. The workflow will execute a query that gives a Resource Manager Timesheet Edit rights for their resources. Timesheet Edit rights are not inherent for Resource Managers when they are named as an individual’s resource manager. -
The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request. -
Do you want to report on TCO for your organization by business function, application, or service? This should be the financial management goal of every organization. This class will discuss a path and some architecture choices to make this a reality. We will highlight want some customers are doing today and share some best practices on the journey. -
Course Description: Are your reports and portlets performing well? This class will walk you through specific SQL tuning tricks to make queries run faster, increase end user satisfaction, and smooth-out system performance. This is an easy way to promote efficient future development and make a huge, positive impact on user experience. -
Course Description: If I build a process in the Classic UI, does it still get triggered in the Modern UX? If I add a new attribute in the Classic UI, how will it be exposed in the Modern UX? This class will focus on the setup of Clarity PPM's Modern UX. It will include topics like turning on the Modern UX, setting up links, using blueprints, and configuring tiles and objects. We will explain how the Modern UX and the Classic UI interact when it comes to administration.

