-
Course description: “Do you have users that just want an XLS or CSV file emailed to them with data? This session will be a hands-on lab to create a workflow process that will pull data from CA PPM and email that data in a file to a user or group of users.” Download file is the slide deck used during the presentation. -
Course description: “How are other companies storing or managing documents? This session will discuss options for using native CA PPM, linking to SharePoint, connecting directly to SharePoint, using Google docs, as well as other options. This session will also discuss options for document approval workflows within CA PPM for both collaborative documents and attachment fields.” Download file is the slide deck used during the presentation. -
Course description: “Are you struggling with deploying Jaspersoft reports between environments? This class will walk through the process and provide some tips and tricks from the experts.” Download file is the slide deck used during the presentation. -
Course description: “Do you want to learn how to get basic data out of CA PPM for use in portlets? This class will review the basic CA PPM data model and provide training on how to write queries within CA PPM for use in your portlets and reports.” Download file is the slide deck used during the class. -
Course Description: “For clients that have both ServiceNow and CA PPM, passing information between the systems becomes vital for the enterprise with both ITSM and PPM toolsets. One of the biggest areas of interaction is around Demand Management. Come and see Rego's Integration solution which flexibly allows for ServiceNow records (Incident, Problem, Idea, Enhancement, and Demands) to generate CA PPM Ideas or Projects. This lets you control where you want to perform Demand Management, and the work lands in CA PPM's Project either way.” Download is the slide deck used for the presentation. -
- Introduction to Power BI and its components
- Getting Data
- Mockup – PM and RM Dashboard
- Publishing and Sharing
- Best practices and its limitations
- Tableau Introduction
-
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 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. -
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.
-
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.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy