| 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 -
This training document is a Rego Consulting Quick Reference Guide to assist with creation of agreements in Clarity’s Modern User Experience. Agreements can be created between Project, Ideas and Custom Investments. The Agreement can convey things needed for predecessors and successors while defining appropriate dates to meet the agreement. Blueprints can be leveraged to customize the agreements as required. -
Course description: “What can leaders do after a CA PPM deployment to ensure continued success of the product? This session will discuss how sponsors can drive compliance within the organization through continued involvement. Strong sponsorship is the key to long term success.” Download file is the slide deck used during the presentation. -
Do you want to add interfaces to your CA PPM instance? This class will review the pros and cons of various integration methods and provide best practice on how to handle various interfaces. We’ll walk you through specific interface examples and showcase Rego’s pre-built interface sets you can leverage to reduce the time and cost of implementation. -
Plan your future work by comparing different scenarios, including in-flight work, and determine the best course of action for your organization. Report Views include:- Roadmap Details
- Resource Investment Demand
- Roadmap Financials
- Roadmap Investment Gantt
- Roadmap Item Gantt
- Roadmap Overview – Default Scenarios
- Roadmap Overview – Single Roadmap Selection
- Scenario Comparison

