-
The Email Process Instance Errors workflow process will email a selected group within Clarity informing them of process errors that are currently in the system. The selected group is input through a gel parameter so it may be easily changed. This workflow helps to resolve errors quickly by emailing group members of the errors within the system so they may take action immediately. -
The Email Process Instance Errors workflow process will email a selected group within Clarity informing them of process errors that are currently in the system. The selected group is input through a gel parameter so it may be easily changed. This workflow helps to resolve errors quickly by emailing group members of the errors within the system so they may take action immediately.
-
The Email Process Instance Errors workflow process will email a selected group within Clarity informing them of process errors that are currently in the system. The selected group is input through a gel parameter so it may be easily changed. This workflow helps to resolve errors quickly by emailing group members of the errors within the system so they may take action immediately.
-
The Enhanced Time Tracking Stalker – Resource workflow process is used to notify resources who failed to submit a timesheet for the prior time period they must take action. The workflow checks for active resources (by using the hire and termination dates, their track mode and that they are open for time entry). Each resource who meet the criteria receives an email asking them to submit their outstanding timesheet(s). The email includes a table that contains this information: time period, timesheet status and any hours currently saved on the timesheet. All outstanding timesheets are included in the table with links to the timesheet in the Modern User Experience side of Clarity. This process helps to ensure the timely submission of timesheets. -
The Enhanced Time Tracking Stalker – RM workflow process automatically sends a single email to Resource Managers which contains a list of any of their resources that have not submitted their timesheet for a prior open time period. The email informs the RM if their resources are submitting their timesheets on time. The email includes a table that provides this information for each resource: Resource Name, Time Period, Timesheet Status and Total Hours saved on the timesheet with links to the timesheet in the Modern User Experience of Clarity. These notifications will help to ensure that time is being posted and approved in a timely manner. -
The Enhanced Time Tracking Stalker – RM workflow process automatically sends a single email to Resource Managers which contains a list of any of their resources that have not submitted their timesheet for a prior open time period. The email informs the RM if their resources are submitting their timesheets on time. The email includes a table that provides this information for each resource: Resource Name, Time Period, Timesheet Status and Total Hours saved on the timesheet with links to the timesheet in the Modern User Experience of Clarity. These notifications will help to ensure that time is being posted and approved in a timely manner.
-
The Enhanced Time Tracking Stalker – RM workflow process automatically sends a single email to Resource Managers which contains a list of any of their resources that have not submitted their timesheet for a prior open time period. The email informs the RM if their resources are submitting their timesheets on time. The email includes a table that provides this information for each resource: Resource Name, Time Period, Timesheet Status and Total Hours saved on the timesheet with links to the timesheet in the Modern User Experience of Clarity. These notifications will help to ensure that time is being posted and approved in a timely manner.
-
This document provides an overview of how hierarchical portlets can be exported to MS Excel. The code of a sample hierarchical portlet is explained. The included sample portlet shows a list of projects and the tasks under each project along with actual and assignment hours. The portlet can also be filtered by project and project manager. -
This document provides an overview of how hierarchical portlets can be exported to MS Excel. The code of a sample hierarchical portlet is explained. The included sample portlet shows a list of projects and the tasks under each project along with actual and assignment hours. The portlet can also be filtered by project and project manager.
-
This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object. The solution is comprised of:- Sub-Object (Benefit Plan Details, Parent = Project)
- Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
- Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
- Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
- Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
- Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
- Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
-
This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object. The solution is comprised of:
- Sub-Object (Benefit Plan Details, Parent = Project)
- Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
- Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
- Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
- Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
- Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
- Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
-
This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object. The solution is comprised of:
- Sub-Object (Benefit Plan Details, Parent = Project)
- Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
- Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
- Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
- Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
- Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
- Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
Copyright 2023 • Rego Consulting Corporation • Privacy Policy