| Column Label | Description |
| From | Who the email is coming from |
| Sent To | Individual users the message should send to |
| Send to Group | Security groups the message should send to (users within the security groups) |
| Message Project Team | Should this message be sent to a project team |
| Associated Investment | If Message Project Team is checked, which project should the team list be pulled from |
| Message Subject | Subject line of the email |
| Message Content | Body of the email (html) |
| Message date | Internal code used by the query |
-
The Communications Object allows a user to send an html-based email to all users on a project, in a security group, or to individual users directly from Clarity. An email can be sent by creating a new entry on the Communication List page, upon saving a new entry the email process with trigger and send the email. Auto Start Solution: An email can be sent by creating a new entry on the Communication List page, upon saving a new entry the email process with trigger. On Demand Solution: All emails could be sent together as a broadcast communication by running the process manually from the Organizer. This process could also be scheduled to run on a specific time using Jobs The table below describes the available columns on the object.
Either of the on-demand process or auto start process should be active at a time. The package provides two Processes: 1. Send Notification (ID:rego_send_notification) This is an auto start process. The notification is sent immediately when a new entry is created on the Communication object. Only one email notification will be sent for one entry. Any updates to the same entry will not trigger any new notifications. 2. Email Communication (ID:rego_email_comm) This is an on-demand process that could be run from the Organizer. This send notification to all the entries on the Communication objects for which a communication was not already sent. This process does not have a Primary object. The processes are designed to work both in Oracle and Postgres environment. If the DB vendor information from Properties.xml is Postgres the SQL query for Postgres will be called. If not, the default SQL is Oracle. Important Note: Either of the processes should be active for an Implementation. If both the processes are active the on-demand process has no effect and will never send any communication. All object entries have a sent flag which will be marked whenever a notification is sent. Both the processes set the same flag on the object instance. Only with admin DB rights this flag could be overwritten. Object Name:Communication Object ID: rego_communication Flag Attribute Name: Sent (Id: rego_sent) -
Part of the Business Transformation Content collection, this bar chart portlet displays count of ideas per business unit. This provides a holistic view of the idea pipe-line in an organization providing them a high-level of ideas converted, approved, unapproved per business unit. -
The My Missing Time portlet displays all open time periods for which the logged in user (assuming they are open for time entry with a track mode of Clarity) has a timesheet that is not posted (accommodates for hire and termination dates). The portlet is used as a quick reference for users to view their missing time. -
A Quick Reference Guide to assist in entering financial transactions into Clarity’s Classic UX. The guide reviews the basics of transactions entry, create voucher header, entering the line item - details, and entering the line item - transaction. -
Horizontal Bar Graph displays total number of projects for each Business Owner/Sponsor for a selected Project Parent Stage (only Project Investments included). Vertical Axis displays Business Owner name. Horizontal Axis displays number of projects. Filter selectable for any Project Parent Stage. Color coding of bar and legend are synchronized to detail stage under the parent. Total for each detail stage displays on each segment of the bar. A mouseover displays a percent of total for each detail stage. -
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. -
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.
-
Part of the Business Transformation collection, this pie chart portlet displays realized benefit, grouped by type of project, for portfolio investments. It uses System Provider: Portfolio Investment Provider. -
This is a standalone process that can be run by an admin to change the ownership of MUX views from a specified user to another specified user. The process contains a single custom script, which has the following parameters that must be updated prior to running the process:- currentOwnerId (required): Resource ID for the current Owner (unique_name from srm_resources table)
- newOwnerId (required): Resource ID for the new Owner (unique_name from srm_resources table)
- viewCode (optional): Code for the specific view to update - leave blank if you want to transfer ownership for all views (odf_ui_views.code)
- Navigate to the process called Admin - MUX Views - Change Ownership.
- Navigate to the Start Step tab, Click on the Update Owner action, and click the Custom Script Parameters tab.
- Enter the Resource ID for the current view owner into the currentOwnerId parameter.
- Enter the Resource ID for the new owner into the newOwnerId parameter.
- If you want to update a specific view only, enter that in the viewCode parameter.
- Run the process via Organizer in Classic.
-
A Quick Reference Guide to assist in the process of creating a table in a Jaspersoft Ad-Hoc Report. Uses screenshots to walk you through the process. -
A Quick Reference Guide to assist in managing a Custom Investment in Clarity’s Modern UX. Reviews accessing the Custom Investment Link and navigating the tabs. -
The Project Storyboard report is a transaction based Jaspersoft report that does not require the Load Jaspersoft Datawarehouse job to be run. The report will pull real-time data from the transaction tables in Clarity. This report can be run from either the Advanced Reporting or Reports and Jobs area within Clarity. The Project Storyboard report shows key aspects of a project that is organized in separate frames. Each frame in the report displays project information such as project dates, project objective, the amount, and cost of resources that are planned and actual, key accomplishments, upcoming activities, current issues and risks, and the project progress toward goals. This report can be used to analyze the project earned value and track work performance to account for cost and schedule variances.
