-
Based on the pre-determined schedule frequency, this job will send an email to Resource Managers that have a Resource meeting the criteria of: Average allocations are greater than 120% where Resource(s) and Project(s) are active over the next 90 days. This serves as a reminder to Resource Managers to monitor and manage allocations. The contents of the email include a message indicating the Resource Manager has at least one Resource meeting this criteria and a table indicating the Resource and that resource’s average, next 90 days allocations.
-
The Timesheet Approval - Auto process is an auto-start process that begins once the resource submits his or her timesheet. This process bypasses a Resource Manager approval and allows the user to post his or her timesheet. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:
- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Time Tracking Stalker – Resource workflow process is used to notify resources that fail to submit a timesheet in a prior week. The workflow checks for active resources, hire/termination dates, track mode, and open for time entry. This process helps to ensure resources submit timesheets in a timely manner. In version 13, the email can be enhanced to include colors, bold, underline, and other HTML formatting.
-
The Grant RM Timesheet Edit Rights workflow process can be run through the "Execute a Process" job. The workflow will execute a query that gives a Resource Manager Timesheet Edit rights for their resources. Timesheet Edit rights are not inherent for Resource Managers when they are named as an individual’s resource manager.
-
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 Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request.
-
Course Description: Do you already have a basic understanding of Jaspersoft Studio development? This session will include advanced topics like duplicating and modifying an OOTB report, multiple datasets, subreports, charting, widgets integration, and crosstabs. The detailed agenda is as follows: Jaspersoft Advanced – Out-of-the-Box Customization (2 hours) • Discover how to use OOTB reports, OOTB domains, resource bundles, and security access grant schemas. Jaspersoft Advanced – Chart Development (2 hours) • Explore multiple advanced charting techniques and types using built-in charting components, including properties (colors, plot options, sizing, gauges, etc.), dual pie chart, time series, and heat map. Jaspersoft Advanced – Scriptlets (2 hours) • Understand the basics of Jaspersoft Studio scriptlet development, utilizing Java libraries in custom Java classes to perform complex tasks in a simple manner. Jaspersoft Advanced – Roundtable (1 hour) • Understand crystal capabilities missing in Jaspersoft Studio, including sharing examples, report bursting needs, automation needs, and working with internal BI groups.