| 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) -
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)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 -
Often, you would want to disallow users from making edits to stay on the same page after changing the data by clicking Save. By forcing the users to click Save and Return, they are forced out of the page. For the above-mentioned reason, the Clarity admin can add the code in the attached tech-trick document, and that will hide the Save button from being displayed. -
In order for Jaspersoft Studio to interact with your Clarity instance, Jaspersoft Studio needs information to connect to your Clarity instance’s Jaspersoft repository. This Tech Trick provides Instructions on how to get this information from within your Clarity Admin menu. -
This tech-trick defines how to run a Jaspersoft report using Rest API -
The Transaction Adapter – is a text based CSV file which automates the importing of monthly non labor financial data into Clarity directly from your financial system. This integration eliminates the need to create non-labor transactions manually in Clarity and will provide more accurate project, program, and portfolio financial reporting. -
The Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource. You first choose the resource who currently has the action item(s) sitting in their queue. Next, you choose the resource you want to reassign the action item(s) to. Finally, you select one to many action items you want to re-associate before running the process. After all the fields are set, the process can be run which will re-associate the action items from one resource to the other. -
This process updates the team, assignment and timesheet roles with the primary role where they do not match. This way, the PM can push all roles to team and assignment for that project before they do a cost plan. -
The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago. The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed. -
The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago. The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed.
-
The Timesheet Approval - RM and PM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. 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.
-
Do you want to understand the OOTB configuration and functionality of financial management? In this class, we will review the OOTB objects, views, views, and functions of financial plans, rates, and other related areas. We will cover both classic and new UX highlighting differences.
