-
Portlet to show the stage of any Action Item triggered by Timesheet submission. Portlet allows for a period start date input, filters by Resource, Approver, Action Item Status and Timesheet Status. A link to the action item is provided for direct action by review if needed. This portlet is only for the clients who have established a process that triggers on Timesheet Status change to Submitted and to send Action Items to the person responsible for timesheet approval/validation i.e. PM for project tracking and/or RM for overall approval of the timesheet. The portlet won’t display any data if there are no timesheet Action Items. Examples of such processes would be CA’s OOTB Project Manager Approval or the Timesheet Approval - PM and RM process found on RegoXchange. -
JasperSoft as two font databases – one for display and one for pdf exporting. Not all fonts in the display database are in the exporting database. If you find you are not getting the proper fonts when exporting to PDF from JasperSoft this tech trick will show you how to add the missing font so your report exports as expected. -
This video describes the process to baseline a project using OWB. The video is available in both .m4v and .wmv formats. -
This video describes the process to assign resources to tasks within OWB. The video is available in both .m4v and .wmv formats. -
The Allow PM to Give Certain Rights modification allows the project manager to delegate rights (chosen by the administrator on the PM Rights object) on his or her projects. This modification eliminates the need for project managers to request additional rights through the PMO/management and simplifies the entire process for everyone involved. The system administrator is able to customize the PM Rights object to pick which rights should be granted to users by the process. The process begins when a change is made on the newly created “Grant / Revoke” field on the project object. The process will then grant or revoke (depending on what option is selected) any rights listed in the PM Rights object to the user in the “Assign PM Rights” field on the project object. -
This Process sends an email to every Action Item Assignee where the Due Date/Time has passed and the Status is either Open, or In Progress. Users may want to modify this stalker to include Status = Deferred. In addition, the Resource Manager for the Assignee receives a copy of the email. In order to generate emails, the SMTP gateway must be up and running and Resources must have a valid email address. -
Notify the PM with a list of tasks for their project as soon as the Timesheet is submitted. This is a good substitute for PM approval. When a timesheet is submitted, then the PM knows the time entered by person. This is an Auto-start process in Clarity named PM Time Notification - On Timesheet Submission and will be automatically spawned when a Timesheet is submitted. When the process is started it will be seen in the Initiated on the Processes tab. The process status can be monitored from Running to the Completed stage. The Progress when 100% and the Status is Completed, an email would have arrived to the Project Manager with subject: “Resource <Name> has entered the following time on your Investment(s) for the week starting <Timesheet Start Date> ”. This email will list the Investments managed by the PM where task was entered by the Resource submitting the timesheet. Each PM would get a separate notification. PM for project X notified, and PM for project Y gets notified in another email. Therefore, one timesheet may spawn out multiple emails. But, if both the Projects have the Same PM, then only a single email gets sent out. “Opt-out Timesheet Notifications" checkbox is provided on the Project for PM’s who do not want to get notified on those projects. -
The Roadmap Cloning process creates a clone of any existing roadmap. It should be run using the “Execute a Process” job. To specify a roadmap to clone the Start Step Action’s Custom Script Parameters need to be updated to include the proper roadmap ID in the templateCode field. -
The Populate Timesheets process converts task level ETC into time entered on the timesheet. The process relies on the resource “opting in” to the process by checking a new attribute called “Auto Populate Timesheet?”, as well as the project manager “opting in” at the project level via a new attribute called “Auto Populate Timesheet?” Once the resource opts in and the PM opts in, the process will create a timesheet for the resource, pulling in the ETCs for the tasks that week and moving them to the actual hours. Once the process runs, an email will be sent to the resource letting them know the hours have been applied. -
This can be used to remove all automatic permissions (Resource Manager Auto) granted to users as a result of becoming a resource 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
-
This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date. Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox. The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date. Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE: The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar. The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account. For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy