| Column Label | Description |
| Timesheet Period Start | Range of time periods to display filtered by start date |
| Timesheet Period Finish | Range of time periods to display filtered by finish date |
| Resource | Resource(s) to display |
| Type | Note on a timesheet or time entry (task specific) |
-
The Timesheet Notes portlet displays all timesheet notes split out by resource, investment and task. This is very useful in situations where you want to review multiple notes as you do not have to open each note separately. The table below describes the available filter fields in the portlet. -
The Timesheet Notes portlet displays all timesheet notes split out by resource, investment and task. This is very useful in situations where you want to review multiple notes as you do not have to open each note separately. The table below describes the available filter fields in the portlet.
Column Label Description Timesheet Period Start Range of time periods to display filtered by start date Timesheet Period Finish Range of time periods to display filtered by finish date Resource Resource(s) to display Type Note on a timesheet or time entry (task specific) -
The Timesheet Notes portlet displays all timesheet notes split out by resource, investment and task. This is very useful in situations where you want to review multiple notes as you do not have to open each note separately. The table below describes the available filter fields in the portlet.
Column Label Description Timesheet Period Start Range of time periods to display filtered by start date Timesheet Period Finish Range of time periods to display filtered by finish date Resource Resource(s) to display Type Note on a timesheet or time entry (task specific) -
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 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 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.
-
This process workflow with gel script forces billable hours on timesheet down to 40 hours, and sets overtime hours to non-billable. Timesheets with 40 or fewer hours are not touched. Process kicks off upon submission of timesheet. Steps are:- Determine if timesheet has > 40 hours. If so, proceed.
- Create a SPLIT row for each timesheet row, with Input Type Code = Non-Bill.
- Divide 40 by total timesheet ours. Store this value.
- Multiply each timesheet cell by the stored value, and enter the result into that cell.
- Take the difference (original cell value – new cell value), and enter in same cell on Split row.
- The end result will be 40 hours total on Billable rows, and overtime hours on Non-Billable rows.
-
This process workflow with gel script forces billable hours on timesheet down to 40 hours, and sets overtime hours to non-billable. Timesheets with 40 or fewer hours are not touched. Process kicks off upon submission of timesheet. Steps are:
- Determine if timesheet has > 40 hours. If so, proceed.
- Create a SPLIT row for each timesheet row, with Input Type Code = Non-Bill.
- Divide 40 by total timesheet ours. Store this value.
- Multiply each timesheet cell by the stored value, and enter the result into that cell.
- Take the difference (original cell value – new cell value), and enter in same cell on Split row.
- The end result will be 40 hours total on Billable rows, and overtime hours on Non-Billable rows.
-
The Timesheets by Resource portlet gives the ability to highlight the time periods where resources are working overtime or working less than 25 hours a week. The filter requires timesheet Start Date and End Date to be provided. Additionally, the information can be filtered by Resource, Resource ID, OBS Unit, Employment Type, Resource Manager, Open for Time, and Active status. This portlet displays Resource, Resource ID, Active (yes/no), Employment Type, Primary Role, Resource Manager, and Timesheet Hours Flag. The flags are set with the logic- Yellow = timesheets not posted / zero hour timesheets
- Green = where number of hours posted is > 25 and less than 45
- Red = where number of hours posted is < 25 or > 45
-
The Timesheets by Resource portlet gives the ability to highlight the time periods where resources are working overtime or working less than 25 hours a week. The filter requires timesheet Start Date and End Date to be provided. Additionally, the information can be filtered by Resource, Resource ID, OBS Unit, Employment Type, Resource Manager, Open for Time, and Active status. This portlet displays Resource, Resource ID, Active (yes/no), Employment Type, Primary Role, Resource Manager, and Timesheet Hours Flag. The flags are set with the logic
- Yellow = timesheets not posted / zero hour timesheets
- Green = where number of hours posted is > 25 and less than 45
- Red = where number of hours posted is < 25 or > 45
-
The Timesheets by Resource portlet gives the ability to highlight the time periods where resources are working overtime or working less than 25 hours a week. The filter requires timesheet Start Date and End Date to be provided. Additionally, the information can be filtered by Resource, Resource ID, OBS Unit, Employment Type, Resource Manager, Open for Time, and Active status. This portlet displays Resource, Resource ID, Active (yes/no), Employment Type, Primary Role, Resource Manager, and Timesheet Hours Flag. The flags are set with the logic
- Yellow = timesheets not posted / zero hour timesheets
- Green = where number of hours posted is > 25 and less than 45
- Red = where number of hours posted is < 25 or > 45
-
The REGO Timesheets - WIP portlet displays timesheet information for timesheets that have a status of posted but have not been posted to the WIP tables. This does not include records hung up in invalid transactions. Users can further narrow their search by Project Name, Resource Name, Timesheet Status, Start Date, and Finish Date. -
This allows users without admin access to see the timeslice settings and also allows the data to be exported to excel easily. Many organizations like to document their timeslice settings which is a manual process as you cannot export the timeslice page to excel. This allows them to periodically export the portlet results to excel to meet their documentation requirements. -
This allows users without admin access to see the timeslice settings and also allows the data to be exported to excel easily. Many organizations like to document their timeslice settings which is a manual process as you cannot export the timeslice page to excel. This allows them to periodically export the portlet results to excel to meet their documentation requirements.
-
This allows users without admin access to see the timeslice settings and also allows the data to be exported to excel easily. Many organizations like to document their timeslice settings which is a manual process as you cannot export the timeslice page to excel. This allows them to periodically export the portlet results to excel to meet their documentation requirements.
-
The Transaction Adapter – is a text based CSV file which automates the importing of monthly non labor financial data into Clarity directly from your financial system. This integration eliminates the need to create non-labor transactions manually in Clarity and will provide more accurate project, program, and portfolio financial reporting. -
The Rego: Transfer Primary Skill process updates the primary skill on the team object by running the process with the execute process job. The process takes the primary skill that is on the resource object and moves it to all of that resource's team records where the primary skill on the team record is null. Utilizing these fields and process provide a quick way to determine what skill each resource is bringing to the project. This process makes the transition seamless from resource primary skill to team primary skill. -
The Rego: Transfer Primary Skill process updates the primary skill on the team object by running the process with the execute process job. The process takes the primary skill that is on the resource object and moves it to all of that resource's team records where the primary skill on the team record is null. Utilizing these fields and process provide a quick way to determine what skill each resource is bringing to the project. This process makes the transition seamless from resource primary skill to team primary skill.
-
The Rego: Transfer Primary Skill process updates the primary skill on the team object by running the process with the execute process job. The process takes the primary skill that is on the resource object and moves it to all of that resource's team records where the primary skill on the team record is null. Utilizing these fields and process provide a quick way to determine what skill each resource is bringing to the project. This process makes the transition seamless from resource primary skill to team primary skill.
-
By its very nature, the shift to Product Funding is going to require that tracking of that funding. Agile tools do not have much, if any, financial capabilities, so it is important to create an eco-system that can support this value stream—from funding, through delivery, and finally to tracking the realization of financial value. Learn how Rally and Clarity PPM do this very well together. -
The Turn off Notifications process disables all Email, SMS and Alerts notifications for all users. This process is helpful if users would not like to receive emails from the system regarding actions items, timesheet submissions, etc. The script may be modified to include all users or all users that have been created within the last day. -
The Turn off Notifications process disables all Email, SMS and Alerts notifications for all users. This process is helpful if users would not like to receive emails from the system regarding actions items, timesheet submissions, etc. The script may be modified to include all users or all users that have been created within the last day.
-
The Turn off Notifications process disables all Email, SMS and Alerts notifications for all users. This process is helpful if users would not like to receive emails from the system regarding actions items, timesheet submissions, etc. The script may be modified to include all users or all users that have been created within the last day.
-
The Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again. -
The Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again.
-
The Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again.
-
This process updates the team, assignment and timesheet roles with the primary role where they do not match. This way, the PM can push all roles to team and assignment for that project before they do a cost plan. -
This process updates the team, assignment and timesheet roles with the primary role where they do not match. This way, the PM can push all roles to team and assignment for that project before they do a cost plan.
-
This process updates the team, assignment and timesheet roles with the primary role where they do not match. This way, the PM can push all roles to team and assignment for that project before they do a cost plan.
-
The User Activity portlet is in essence an expansion of the out of the box User List by License Type portlet, which only display the Last Logged In date of resources. This portlet offers several additional fields to help admins dig deeper into user activity within the tool. The table below describes the available filter fields for the portlet.Column Label Description OBS OBS the resource(s) belong to Resource Full Name Resource’s First and Last Name Resource ID Resource’s ID First Name Resource’s First Name Last Name Resource’s Last Name Date Last Logged In Date the Resource last logged in Date Last Time Investment Updated Date the Resource last made an Investment update Resource Active The Resource’s active status Employment Type Resource’s Employment Type Financial Location Resource’s Financial Location Email Resource’s Email Address Date Last Time Financial Plans Edited Date the Resource last made a Financial Plan edit Date of last entry on a Timesheet Date the Resource last made an entry on a timesheet Created Date Date the resource was added to the system Date of Hire Resource’s Date of Hire Date of Termination Resource’s Date of Termination Financial Department Resource’s Financial Department Home Page Resource’s Home Page Language Default Language of the Resource Primary role Resource’s Primary Role Resource manager Resource’s Manager Track Mode Resource’s Track Mode User Name Resource’s Username -
The User Activity portlet is in essence an expansion of the out of the box User List by License Type portlet, which only display the Last Logged In date of resources. This portlet offers several additional fields to help admins dig deeper into user activity within the tool. The table below describes the available filter fields for the portlet.
Column Label Description OBS OBS the resource(s) belong to Resource Full Name Resource’s First and Last Name Resource ID Resource’s ID First Name Resource’s First Name Last Name Resource’s Last Name Date Last Logged In Date the Resource last logged in Date Last Time Investment Updated Date the Resource last made an Investment update Resource Active The Resource’s active status Employment Type Resource’s Employment Type Financial Location Resource’s Financial Location Email Resource’s Email Address Date Last Time Financial Plans Edited Date the Resource last made a Financial Plan edit Date of last entry on a Timesheet Date the Resource last made an entry on a timesheet Created Date Date the resource was added to the system Date of Hire Resource’s Date of Hire Date of Termination Resource’s Date of Termination Financial Department Resource’s Financial Department Home Page Resource’s Home Page Language Default Language of the Resource Primary role Resource’s Primary Role Resource manager Resource’s Manager Track Mode Resource’s Track Mode User Name Resource’s Username -
The User Activity portlet is in essence an expansion of the out of the box User List by License Type portlet, which only display the Last Logged In date of resources. This portlet offers several additional fields to help admins dig deeper into user activity within the tool. The table below describes the available filter fields for the portlet.
Column Label Description OBS OBS the resource(s) belong to Resource Full Name Resource’s First and Last Name Resource ID Resource’s ID First Name Resource’s First Name Last Name Resource’s Last Name Date Last Logged In Date the Resource last logged in Date Last Time Investment Updated Date the Resource last made an Investment update Resource Active The Resource’s active status Employment Type Resource’s Employment Type Financial Location Resource’s Financial Location Email Resource’s Email Address Date Last Time Financial Plans Edited Date the Resource last made a Financial Plan edit Date of last entry on a Timesheet Date the Resource last made an entry on a timesheet Created Date Date the resource was added to the system Date of Hire Resource’s Date of Hire Date of Termination Resource’s Date of Termination Financial Department Resource’s Financial Department Home Page Resource’s Home Page Language Default Language of the Resource Primary role Resource’s Primary Role Resource manager Resource’s Manager Track Mode Resource’s Track Mode User Name Resource’s Username -
The Customized Object/Portlet Views portlet displays all user edited object/portlet views and the resource(s) that have edited them. This can assist in identifying users who need to be notified prior to publishing view changes. The table below describes the available columns on the object.Column Label Description Resource Name Name of the resource Resource ID ID of the resource Type Object or Portlet Portlet Code ID of the portlet Portlet Name Name of the portlet Object Associated Object Object View ID of the modified view on the object Object Code Internal code used by the query pkid Internal code used by the query portlet_dbid Database id of the portlet res_dbid Database id of the resource -
The Customized Object/Portlet Views portlet displays all user edited object/portlet views and the resource(s) that have edited them. This can assist in identifying users who need to be notified prior to publishing view changes. The table below describes the available columns on the object.
Column Label Description Resource Name Name of the resource Resource ID ID of the resource Type Object or Portlet Portlet Code ID of the portlet Portlet Name Name of the portlet Object Associated Object Object View ID of the modified view on the object Object Code Internal code used by the query pkid Internal code used by the query portlet_dbid Database id of the portlet res_dbid Database id of the resource -
The Using Consistent Colors technical trick shows how management can create a uniform color pallet for all charts within the system. This trick, not only makes charts more professional when delivering to management, but also creates a uniform pattern throughout the Clarity environment. -
When a team member is added to the Team tab of the project, this process will add Project - View Management and Resource – Hard Book instance access right to the team member’s profile. This allows the team member to add their own allocations. NOTE: The process is NOT auto-start, and hence, needs to be run manually from Home > Organizer > Processes > Available
