2024.3 Release Summary
- 03 Sep 2024
- 8 Minutes to read
- Print
- DarkLight
- PDF
2024.3 Release Summary
- Updated on 03 Sep 2024
- 8 Minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
HOW TO USE RELEASE SUMMARY
The release notes offer a brief description of the improvements and new features. Contact your Tier1 Client Services representative to learn more or provide feedback on what else would be valuable to see in the release summary. See article for full details on what browsers and platforms we support. Supported browsers and devices is updated each release to reflect what Tier1 currently supports.
There are no 2024.3 releases of Mobile. The release will be available for upgrade on September 9, 2024.
CLIENT CENTER
MASS EMAIL IMPROVEMENTS
In the previous release, a new mass email tab was introduced in activity manager to view users’ own mass email statistics. In this release, users can now toggle to view all mass emails they have access to so that they can see other users’ email statistics.
Below feature is part of the new paid Tier1 mass email option, which was introduced in the previous release as a pilot. Contact Tier1 for further details.
Improve the deliverability of emails with a new email validation check on contact management. In this release, quick add contact and quick edit contact across Client Center, Deals, Events, Tier1 Mobile Now, and Tier1 for Outlook provides a real time email validation to give you information on the validity of the email addresses. For example, here are some sample email validation messages: Email is invalid, Suggested correction: gmail.com, Email address is likely a distribution list or does not exist, Company domain is invalid, Email address is likely disposable.
CLIENT FEEDBACK
Client Center has made several improvements based on user feedback.
Administrators can configure to exclude certain tasks from the task tab in activity manager.
Administrators can configure to exclude certain meetings from the meeting tab in activity manager.
Administrators can configure to exclude certain call reports from the call reports tab in activity manager.
Administrators can configure to exclude certain call reports and Tier1 events from the interaction tab in activity manager.
Administrators can configure to exclude certain mass email and mass email contacts from the mass email tab in activity manager.
Administrators can configure multiple Lightning, PowerBI, and Tableau dashboards on the Client Center home page. Users can then use the hamburger menu to navigate between these dashboards. Note that this feature has an accelerator package ReportLink which is managed by Tier1 services team to help quickly import your PowerBI or Tableau dashboards. Contact the services team for more information.
In the previous releases, we introduced Google Maps integration to help users quickly populate addresses. In this release, administrators can now configure the specific behavior for city, state, and country based on Google’s geocoding service. For example, administrators can change between short name and long name for states and countries; administrators can specify the priority order from Google to populate for city field in Tier1.
Users now receive home page notification and end of week email notifications for new contacts created within their account coverage. The notification message differentiates contacts created by users and by Prospector’s update service.
TIER1 FOR OUTLOOK
CLIENT FEEDBACK
In the last release, Tier1 for Outlook introduced the ability to configure SMTP credentials in Salesforce instead of having the user enter them for each mass email. In this release, administrators instead configure the encrypted SMTP credentials and Tier1 for Outlook client will decrypt using a deterministic encryption scheme.
PROSPECTOR
OWNERSHIP CUBE IMPROVEMENTS
To improve the actionability of the update service suggestions, the following improvements have been made to the ownership cube.
On any unlinked accounts and contacts, ownership cube offers suggestions from Prospector to link to and in addtion, users can search for accounts and contacts in Prospector if the suggestions are not valid and then link them. In the previous release, ownership cube just displayed an error message indicating account or contact is unlinked. Note that a unlinked account or contact means that the account or contact has not been matched with a Datahub Id.
On a linked account or contact, users can now see basic contact information such as title, phone, email.
On a linked account or contact, users can view the history of past changes and who did them. Users can also receive daily or weekly email notifications; see below section on what is available to receive email notification on.
On a linked account or contact, users can action on suggested account field changes, contact field changes, or contact employment change by either accepting them or ignoring them. Accepting a change means saving the suggested field change into the standard field. For example, if a user accepts a contact phone number change, the application will overwrite the new phone into the standard contact phone field. Ignoring a change simply removes the notification for the user only; other users will still see the suggested change notification.
On a linked account or contact, users can unlink from Prospector if they accidentally linked the wrong account or contact. Note that unlinking an account will unlink all contacts. Also unlinking an account or contact removes all Datahub fields from that account or contact, however it will not remove any standard fields.
UPDATE SERVICE REPORTS
To improve visibility of the suggested update service changes, users can now receive daily or weekly email notifications on the changes. Prospector has introduced several Salesforce reports for users to subscribe to. When subscribing, users can choose to receive updates daily or weekly and at what time. The following reports are available to subscribe to.
Duplicate Prospector account Ids.
Duplicate Prospector contact Ids.
Inactive contacts last 7 days.
Inactive accounts last 7 days
Inactive tickers last 7 days
New accounts created last 7 days
New contacts created last 7 days
New tickers created last 7 days
Prospector account changes last 7 days
Prospector contact changes last 7 days
Note that administrators and users can clone these reports and change the filter criteria to their preferences before subscribing. For example, if a user only cares about new hedge funds created in last month, they can clone the report, update the filters to filter for hedge fund account types and then update the date criteria to last 30 days and then save the report.
Lastly, as part of this change, Update Service Reports tab has been deprecated and will be removed.
ARCHITECTURE
ACCESSIBILITY
Tier1 strives for compliance with Web Content Accessibility Guidelines (WCAG) 2.1 level AA. As part of that commitment, the following improvements have been made in Client Center and Deals: increased keyboard accessibility to navigate through the screen; enhance screen reader usability by providing more explanatory messages; fixes to several screen contrast for text and icons.
TEST AUTOMATION
Tier1 has implemented a unique object identifier called testId on several forms in Client Center.
DATA MODEL CHANGES
NEW OBJECTS
OBJECT LABEL | OBJECT API | DESCRIPTION |
|---|---|---|
Account Fields History | T1C_DH__Account_Fields_History__c | Account Fields History records are created in conjunction to Update Service Acc Altered Fields records. An Account Field History record is created when a user either accepts or ignores a pending account field change. Creation of this record upon ignoring a change will allow the pending field change to be hidden from the user who ignored the change but available to others going forward. For acceptances, the change will be implemented and no longer be up for review for anyone. |
Contact Fields History | T1C_DH__Contact_Fields_History__c | Contact Fields History records are created in conjunction to Update Service Cont Altered Fields records. A Contact Field History record is created when a user either accepts or ignores a pending contact field change. Creation of this record upon ignoring a change will allow the pending field change to be hidden from the user who ignored the change but available to others going forward. For acceptances, the change will be implemented and no longer be up for review for anyone. |
User Contact Unsubscribe | T1C_Base__User_Contact_Unsubscribe__c | Related Object to indicate if a user has unsubscribed from a certain users mass emails |
Mass Email List Relationship | T1C_Base__Mass_Email_List_Relationship__c | Specifies a list that was targeted for the associated mass email |
NEW FIELDS
OBJECT API | FIELD API | FIELD TYPE | DESCRIPTION |
|---|---|---|---|
T1C_DH__Update_Service_Acc_Altered_Fields__c | T1C_DH__Status__c | Picklist | Three new statuses, to indicate how the suggested field change is handled. Automatic meaning that Update Service automatically made the change. Open means it is pushed to the users to either ignore or accept the change. Each record in the account fields history table will indicate an action taken by a user (ignore or accept). Finally, manual means a user has accepted the change, thus being the final record for that associated update service account altered fields object. |
T1C_DH__Update_Service_Cont_Altered_Fields__c | T1C_DH__Status__c | Picklist | Three new statuses, to indicate how the suggested field change is handled. Automatic meaning that Update Service automatically made the change. Open means it is pushed to the users to either ignore or accept the change. Each record in the contact fields history table will indicate an action taken by a user (ignore or accept). Finally, manual means a user has accepted the change, thus being the final record for that associated update service contact altered fields object. |
T1C_DH__Contact_Fields_History__c | T1C_DH__Interaction_Date__c | Date/Time | Date record is created. |
T1C_DH__Contact_Fields_History__c | T1C_DH__Update_Service_Cont_Altered_Fields__c | Master-Detail | Each Contact Fields History record is related to a parent object Update Service Cont Altered Fields through a Master-Detail relationship. |
T1C_DH__Contact_Fields_History__c | T1C_DH__Action__c | Picklist | Can be ignored, accepted or automatic. Action taken on the associated contact altered field record. |
T1C_DH__Contact_Fields_History__c | T1C_DH__Updated_By_User__c | Lookup (User) | Lookup to User for who created the record. |
T1C_DH__Account_Fields_History__c | T1C_DH__Interaction_Date__c | Date/Time | Date that the record is created. |
T1C_DH__Account_Fields_History__c | T1C_DH__Update_Service_Cont_Altered_Fields__c | Master-Detail | Master-detail relationship to parent object Update_Service_Acc_Altered_Fields. Each account fields history object must be related to a usaaf object. |
T1C_DH__Account_Fields_History__c | T1C_DH__Action__c | Picklist | Can be ignored, accepted or automatic. Action taken on the associated account altered field record. |
T1C_DH__Account_Fields_History__c | T1C_DH__Updated_By_User__c | Lookup (User) | User responsible for creating the record by either accepting or ignoring a cont change. |
T1C_DH__Update_Service_Entity_Log__c | T1C_DH__Reason_Code__c | Picklist | Reason code to identify entity log records that are detailing an account or contact duplicate. All other records have null value. |
Contact | T1C_Base__ProfileURL__c | URL | URL type field for Contact's external profile link. For example, LinkedIn |
T1C_Base__Mass_Email__c | T1C_Base__Email_System_Id__c | Long Text Area (32,768) | Stores the Email Ids of SendGrid and Omnigage. Used to retrieve email metrics. |
T1C_Base__User_Contact_Unsubscribe__c | T1C_Base__Contact__c | Lookup (Contact) | Record linking an unsubscribe preference to a user |
T1C_Base__User_Contact_Unsubscribe__c | T1C_Base__Is_Unsubscribed__c | Checkbox | Boolean to indicate if the contact is unsubscribed from the users mass emails |
T1C_Base__User_Contact_Unsubscribe__c | T1C_Base__User__c | Lookup (User) | Lookup field to tie the unsubscribed contact to a user |
T1C_Base__Mass_Email_List_Relationship__c | T1C_Base__Ace_List__c | Lookup (Ace List) | Association to a particular list that the mass email was sent to |
T1C_Base__Mass_Email_List_Relationship__c | T1C_Base__Mass_Email__c | Master-Detail | The mass email sent to this list |
T1C_Base__Mass_Email_Contact__c | T1C_Base__Ace_List__c | Lookup (Ace List) | The ace list from which the contact was sourced |
DEPRECATED FIELDS
OBJECT API | FIELD API | FIELD TYPE | DESCRIPTION |
|---|---|---|---|
T1C_Base__Mass_Email__c | T1C_Base__Engagement_Id__c | Text(255) | Id from email delivery system |
FEATURE RETIREMENT
UPDATE SERVICE REPORTS
WHAT IS CHANGING
Effective 2024.3 release, the update service report tab is no longer available. It has been replaced by new a report folder T1 Update Service with multiple Salesforce reports with the same information.
WHY ARE WE RETIRING THIS FEATURE
Users have told us that they would like to receive alerts on the update service reports rather than going to a report to run it themselves. We have therefore moved all the report capabilities to use Salesforce reports and use native Salesforce report subscription to push out email notifications based on the user’s own email notification preference.
WHAT ACTION TO TAKE
Once your organization has been upgraded to 2024.3 packages, share the T1 Update Service report folder or resave the new reports into an existing public folder. Let users know they can subscribe to these reports and make any report configuration adjustments based on their requirements.
Was this article helpful?