-
The Time By Resource and Investment - PM portlet shows time spent on projects where the logged in user is the project manager. This portlet is used to get a snapshot of investments and the time that has been put against them at the individual resource level for the projects that user has access to. This portlet is used for determining what resources have put time against specific investments and can be used to see where resources are spending their time or to help rationalize ETCs for remaining work for planning purposes. The portlet may be filtered by time-scale, date, resource or investment to narrow the search results. -
The Time by Task portlet displays time logged to tasks for all investments the logged in user has security rights to view - pulling data from the timeslices. It is capable of displaying the data by weekly, monthly, quarterly or annually segments. The portlet may also be filtered by investment and resource OBS. -
The Time by Task portlet displays time logged to tasks for all investments the logged in user has security rights to view - pulling data from the timeslices. It is capable of displaying the data by weekly, monthly, quarterly or annually segments. The portlet may also be filtered by investment and resource OBS.
-
The Time by Task portlet displays time logged to tasks for all investments the logged in user has security rights to view - pulling data from the timeslices. It is capable of displaying the data by weekly, monthly, quarterly or annually segments. The portlet may also be filtered by investment and resource OBS.
-
Connect with user and get familiar with them via Office 365/Azure Profile photos synced with the Clarity PPM Avatars. This is a good way to collaborate with the team and users for any quick update or interaction. This is a scheduled process in Clarity named Sync Profile Photo from Office 365 and will be scheduled to run as a job. When the process is executed, it will be setting the Microsoft O365 profile photo into the users Avatar photo in Clarity PPM and optionally, sync custom attribute of the Resource with profile photo, which can be used for quick identification of the user. Sync Process come with some parameters for the Support team, which they can use as per there environment configurations. These some important Gel parameters for quick configuration are:- msProfilePicField : Custom Resource Field to store Photo, if not provided process will skip syncing the custom field.
- msTenantId: Microsoft Azure Tenant Id
- msClientId: Microsoft Azure Application client Id
- msClientSecret: Microsoft Azure Application client Secret
- msTeamPhotoSize: Define size of the photo to be fetched
- syncPPMAvatar: Parameter to Sync PPM User Avatar photo from MS Team
-
Launch a Team chat with your users directly from the Clarity PPM tool. This is a good way to collaborate with the team and users for any quick update or interaction. This is a scheduled process in Clarity named Sync MS Team Launching Chat URL and will be scheduled to run for various frequency. When the process kick in it will be setting the Team link into the custom URL attribute of the Resource, which can be used to Launch Team chat from the tool. Sync Process come with two parameters for the Support team, which they can use as per there environment configurations. These two Gel parameters for quick configuration are:- launchMSTeamField: parameter for the Custom Resource Field to store Launch URL
- emailAddressField: parameter for field to pick mail address in SRM_RESOURCES table
-
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.
-
The Auto-Approve Old Timesheets workflow process can be run through the "Execute a Process" job and may be used to quickly close out timesheets for a specified timeframe for period closure. The workflow will execute a query that will automatically approve ALL (no matter the status of the timesheet) timesheets that have a time period start date before the Approve Date specified within the process itself. -
The Auto-Approve Old Timesheets workflow process can be run through the "Execute a Process" job and may be used to quickly close out timesheets for a specified timeframe for period closure. The workflow will execute a query that will automatically approve ALL (no matter the status of the timesheet) timesheets that have a time period start date before the Approve Date specified within the process itself.
-
The Auto-Approve Old Timesheets workflow process can be run through the "Execute a Process" job and may be used to quickly close out timesheets for a specified timeframe for period closure. The workflow will execute a query that will automatically approve ALL (no matter the status of the timesheet) timesheets that have a time period start date before the Approve Date specified within the process itself.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy