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. In this release, Tier1 applications now support for Microsoft Edge Chromium, 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.4 releases of Prospector, Security Engine, and Consumption Reporting. The release is available for upgrade on December 13, 2024.
CLIENT CENTER
SAVED VIEWS
Saved views allow users to save column preferences: column visibility, order, width, groups and filters and quickly apply them so that users can access relevant data for call lists, email lists, or reviewing client data. For example, an administrator creates a dynamic list of contacts interested in specific tickers and sectors, and shares it with all users. A user in Europe changes the column preferences so that country is visible and filtered to UK, France, Germany, and then saves this view. They can select this view and then Client Center will apply the column preference.
The following are supported with first version of saved views.
Saved views are available on any contact lists, account lists, and quick find contact grid.
Users can create a contact view and apply them on any contact list. They can create an account view and apply them on any account list. Note that contact views and quick find contact views are separate due to column differences.
Users can create, edit, and delete their own views. They cannot share views.
Ad hoc columns are not saved in a saved view. Users have to re-apply the ad hoc column visibility and filter.
The filters on the main grid for tags, last interaction date are now in the column header. Custom filters are no longer supported. This was moved to support saved views.
The coverage filters on the quick find contact grid are now in the coverage icon column header. This was moved to display more data in the grid and make it consistent as a column filter.
The contact hierarchy menu on the quick find contact grid is now above the grid instead of the at the bottom right for better visibility.
USABILITY IMPROVEMENTS
Client Center has made several usability improvements based on user feedback.
Users can filter out low priority interaction types from the trending topics dashboard. The trending topics dashboard was released in 2023.3 release.
Users can view all portal and email activities in the portal activity cube for Global Source Direct integration. It addition, users can now view the contact name, and the publish date of an article or created date of other activity types. The global source direct integration was released in 2023.5.
Administrators can configure any related list search to use SOSL instead of SOQL. The main use case to configure a SOSL search is if a user needs to search on long text fields.
DEALS
SAVED VIEWS
Saved views allow users to save column preferences: order and filters and quickly apply them so that users can quickly access the most relevant data to view or inline edit. For example, a banker can create a saved view to view and edit M&A deals with relevant deal details and fee fields and then create a separate saved view to view and edit ECM deals with relevant deal details and fee fields.
The following are supported with first version of saved views.
Saved views are only available in the new inline edit grid for both deal and deal product lists. It is not available in the classic deal grid.
Users can create a deal saved view and apply them in deal grid. They can create a deal product saved view and apply them in deal product grid. Users cannot use deal saved views on deal product grid and vice versa.
Administrators must configure the available field sets in deal and deal product grids for users to choose from. Field sets are list of fields users can access on the grid.
Users can create, edit, and delete their own views. They cannot share views.
Users can’t add new products when saved views with filters are applied.
INLINE GRID IMPROVEMENTS
In the inline edit deal product grid, users can now select the deal to open the deal details to edit the full deal. In the previous version, users could only use the deal inline grid to edit full deal.
EVENTS - SELL SIDE
AUTOMATIC CALENDAR SYNC IMPROVEMENTS
Calendar sync has made several improvements based on client feedback.
Semi-automatic sending of calendar invitations - Coordinators can control when to send the initial calendar invite (mass send or selected attendees).
Ability to configure event image to calendar invitations
Sales (booking owner) may accept their copy of the calendar invite and become a meeting attendee.
The following features only work with Office 365.
Administrators can configure the calendar invite to hide attendees in group meetings or configure it to not send group meeting invites. In previous releases, group meetings invites were not sent at all by default.
Administrators can disable the forward and new time proposals options on the meeting response, since the forwarded contacts may not be valid CRM contacts.
Administrators can set the default meeting reminder time on calendar invites. This feature is supported with Outlook recipients and not Gmail recipients. For Gmail recipients, it uses its own default reminders.
CLIENT PORTAL IMPROVEMENTS
Client Portal now supports both event and meeting requests and has made several usability improvements below.
EVENT AND MEETING REQUESTS
Portal users can now submit event level or meeting level request booking. They can specify the event or meeting timeslot, whether they are attending physically or virtually, and any comments to the host.
Portal users can also make updates such as updating the request notes, updating preferred time slot or canceling the booking request.
Any event or meeting request bookings done through the portal are treated the same as the Events application. Coordinators can then allocate the event or meeting requests into a meeting timeslot and confirm their status.
GENERAL IMPROVEMENTS
Portal users receive email notifications to remind them of upcoming events. By default reminder emails are sent to confirmed attendees for events up to 7 days ahead. Administrators can update the configuration to be more/less than 7 days or configure to include additional statuses like tentative, or interested.
Portal users can update their contact information such as name, email address, phone number, event invitation subscription. Administrators can configure specific emails to receive notifications on the contact information updates.
Coordinators can upload an event image for portal users to view on the my events landing page. In the previous release, the event image was only available on the event details page.
Coordinators can exclude meetings from the client portal if they flag a meeting as “Do not display on portal”.
Portal users will see shorten URLs links such as meeting links, playback links or Google Maps links.
Portal users will receive a user friendly error message if the license limit exceeded.
EVENT SUMMARY SCREEN: COLLECTION SUMMARY TAB (FULL RELEASE)
The collection summary tab is now generally available. The event collection summary tab displays a summary of the collection information such as the events, meetings, and other relevant information such as the attendees when you expand on individual events/meetings.
CLIENT FEEDBACK
Tier1 Events has made several improvements based on client feedback.
Sales and coordinators can use the invitation workflow to send personalized event invitations to clients without using the client portal. This tremendously improves the event invitation process by providing the following.
Find target client recipients to send invitations by searching by contacts, searching by account or bulk add by selecting lists.
An invitation template with ability to include your company logo and event image.
A history of the invite list in the event attendees tab.
Coordinators now have a new option to quickly email all the event attendees or meeting attendees. In the event schedule tab, select the individual contacts, the meeting, or the entire event, and then select the Send Attendee Emails option.
Coordinators can launch the Prospector account tear sheets in the events schedule tab. They can select the context menu next to the account and open tearsheet. In previous releases, users had to open Client Center to create the tearsheets. Note that this feature requires subscription to Prospector.
In the contact details pane, users can now access the quick edit contact screen to edit contact information.
Users can use the additional filters to view events on the calendar view to quickly find the events they are looking for. They can filter events by topics, type, attendance type, city, region, status, and visibility. These filters were previously only available on the list view.
Users can now view and update the booking owner directly on the booking screen.
Target list Excel export will now have the invitee status which is based on the event attendee status.
When users add covering professionals into the meeting, the reason value is only being populated during creation. In this release, the reason field will be updated if any contacts are updated or removed.
To make the collection and event edit screens easier to navigate, each tile can now be individually configured to be collapsed by default. The default behaviour of the tiles are not collapsed. Contact your Tier1 representative if you wish to have your tiles configured accordingly.
MOBILE
MOBILE EVENTS
In this release, Tier1 Mobile Now supports more events workflows.
Administrators can enable the meeting lock workflow on mobile. The meeting lock behavior works the same way on Tier1 Events. See below for sample scenarios. If meeting lock is enabled,
When a user views a meeting or is on the book screen on mobile, the meeting is locked for booking for all other users on either mobile or browser.
If a meeting is locked by another user, the user will get a warning indicating that this meeting is locked for booking and the user will not be able to book.
Note that if users switch apps or idle on Tier1 Mobile Now in the background, the meeting will unlock after the configured auto unlock time.
Users can now update the attendee’s status, attendance type, role, or delete the attendee. They can only update or delete attendees they booked.
If a meeting already has maximum number of accounts (1-on-1 meeting has attendees from one account; 2-on-1 meeting has attendees from two accounts), the mobile app will pre-search contacts from those accounts.
MOBILE LIST MANAGEMENT
In this release, Tier1 Mobile Now has made several improvements to list management.
When users finish creating a list, the app will now navigate to the list. In the previous versions, it did not navigate to the newly created list so they had to go and find it again on the my lists screen.
On any contact or account list, users can now perform a contact search or an account search. After the search results appear, users can add one or multiple search results into their current list. In the previous versions, users had to go to search option.
On search results or any contact or account list, the multi-select option appears in the top right corner of the screen. Tapping on this option switches to multi-select mode which allows users to select any number of contacts or accounts to perform actions such as create a new call report or copy selected results into another list. In the previous version, users had to tap on the contact or account icon to enable multi-select mode, which was not obvious to many.
On any contact or account list, users can now perform quick actions using the … menu such as add to list, call, email, or log a call report without having to navigate to the contact or account to perform those actions.
On the contact and account details, users have a new add to list menu.
CLIENT FEEDBACK
Tier1 Mobile Now has made several improvements based on user feedback.
Users can use the same rich text editor on call reports internal and external notes. On mobile, only bold, italics, underline, strikethrough, bullet lists, numbered lists, and links are supported.
Administrators can configure what related objects users can pick when relating a task or meeting. For example, configure task related to, to allow users to relate a task to opportunity or deal or call report; configure meeting related to, to allow users to relate a meeting to opportunity or deal.
PLATFORM CHANGES
Upgrade from Salesforce SDK 10.2 to 12.0.1
Fixes for iOS18 and Salesforce 12 SDK. Click on the respective links to view more.
Permanent fix to the theming workaround is included in this release.
DATA MODEL CHANGES
NEW OBJECTS
OBJECT LABEL | OBJECT API | DESCRIPTION |
|---|---|---|
Datagrid View Filter | T1C_Base__Datagrid_View_Filter__c | Captures the associated filtered values of a column associated to a Datagrid View. |
Deal Saved View | T1C_Base__Deal_Saved_Views__c | Store the filter criteria for a saved view. |
Deal Saved View Filter | T1C_Base__Deal_Saved_View_Filters__c | Stores custom view information for deals grid. |
Mass Email Interest Subject | T1C_Base__Mass_Email_Interest_Subject__c | Contains Interest Subjects discussed relating to a mass email. |
NEW FIELDS
OBJECT API | FIELD API | FIELD TYPE | DESCRIPTION |
|---|---|---|---|
T1C_Base__Datagrid_View__c | T1C_Base__Datagrid_Id__c | Text(255) | An unique identification of the data grid which this record applies to. This is specifically used for saved view. |
T1C_Base__Datagrid_View_Filter__c | Name | Text(80) | Concatentation of datagrid view and field name. |
T1C_Base__Datagrid_View_Filter__c | T1C_Base__Datagrid_View__c | Lookup(Datagrid View) | The lookup relationship field with the associated Datagrid View. |
T1C_Base__Datagrid_View_Filter__c | T1C_Base__Filter_Control_Type__c | Text(255) | The filter control type used in the column header for filtering. |
T1C_Base__Datagrid_View_Filter__c | T1C_Base__Filter_Values__c | Long Text Area(5000) | A formatted JSON string containing the filter value(s) which varies based on the filter control type. |
T1C_Base__Datagrid_View_Filter__c | T1C_Base__Column_Id__c | Text(255) | The client side column identifier which the filter value gets applied to. This can be the AFR feature name of the column. |
T1C_Base__Deal_Saved_Views__c | Name | Text(80) | Name of view. |
T1C_Base__Deal_Saved_Views__c | T1C_Base__Dashboard_Fieldset__c | Text(255) | Name of fieldset to load for dashboard section. |
T1C_Base__Deal_Saved_Views__c | T1C_Base__Record_Type__c | Text(255) | Record Type ID for the deals showin in this view. |
T1C_Base__Deal_Saved_Views__c | T1C_Base__Details_Fieldset__c | Text(255) | Name of fieldset to load for details section. |
T1C_Base__Deal_Saved_Views__c | T1C_Base__Economics_Fieldset__c | Text(255) | Name of fieldset to load for economics section. |
T1C_Base__Deal_Saved_Views__c | T1C_Base__Header_Fieldset__c | Text(255) | Name of fieldset to load for header section. |
T1C_Base__Deal_Saved_Views__c | T1C_Base__Type__c | Picklist | Define if the view is for a Deal or a Product view. |
T1C_Base__Deal_Saved_Views__c | T1C_Base__User__c | Lookup(User) | User ID for the user who owns this view. |
T1C_Base__Deal_Saved_View_Filters__c | Name | Text(80) | Id of the view filter. |
T1C_Base__Deal_Saved_View_Filters__c | T1C_Base__Deal_Saved_View__c | Lookup(Deal Saved View) | Reference to View object. |
T1C_Base__Deal_Saved_View_Filters__c | T1C_Base__Field_Name__c | Text(255) | Field Identifier generated by the grid. |
T1C_Base__Deal_Saved_View_Filters__c | T1C_Base__Field_Type__c | Text(255) | Control type that is used for filtering the field. |
T1C_Base__Deal_Saved_View_Filters__c | T1C_Base__Value__c | Text(255) | Filter value. Comes directly from Grid filters. JSON structure. |
T1C_Base__Mass_Email__c | T1C_Base__Job_Id__c | Text(255) (External ID) (Unique Case Insensitive) | The unique job assigned to this particular mass email. |
T1C_Base__Mass_Email__c | T1C_Base__Sub_Type__c | Picklist | Optional third level categorization of type. Can be used to categorize reach such as 1x1 or Group. |
T1C_Base__Mass_Email__c | T1C_Base__Type__c | Picklist | Optional second level categorization of type. Can be used for type of email it is such as Sales, Research. |
T1C_Base__Mass_Email__c | T1C_Base__Related_To_Type__c | Text(255) | Represents mass email related object type. |
T1C_Base__Mass_Email__c | T1C_Base__Related_To_Id__c | Text(18) | Represents mass email related object Id. |
T1C_Base__Mass_Email__c | T1C_Base__Total_Links__c | Number(18, 0) | Total trackable links in the mass email. |
T1C_Base__Mass_Email__c | T1C_Base__Deal__c | Lookup(Deal) | Represents the Deal associated with this mass email |
T1C_Base__Mass_Email__c | T1C_Base__Visibility__c | Picklist | The visibility of the mass email. |
T1C_Base__Mass_Email_Interest_Subject__c | T1C_Base__Interest_Subject__c | Lookup(Interest Subject) | Lookup to interest subject |
T1C_Base__Mass_Email_Interest_Subject__c | T1C_Base__Mass_Email__c | Master-Detail(Mass Email) | The mass email in which this internal subject was discussed |
T1C_AEM__Event_Collection__c | T1C_AEM__Deal_Id__c | Text(18) | When the Event Collection is related to a Deal, this field will be populated with the Deal Id as plain text. This is mostly so we can use the field in Sharing Rules (since the lookup cannot be used). |
T1C_AEM__Event_Collection__c | T1C_AEM__Deal__c | Lookup(Deal) | Deal Id for the event collection related to. |
T1C_AEM__Meeting_Invitation__c | T1C_AEM__Deal_Id__c | Text(18) | When the parent Meeting has the Deal Id field populated, it will rolldown to this field. This is mostly so we can use the field in Sharing Rules (since the lookup cannot be used). |
T1C_AEM__Meeting__c | T1C_AEM__Deal_Id__c | Text(18) | When the parent Event has the Deal Id field populated, it will rolldown to this field. This is mostly so we can use the field in Sharing Rules (since the lookup cannot be used). |
T1C_AEM__Meeting__c | T1C_AEM__Hidden_From_Portal__c | Checkbox | Whether the meeting will be visible in the Client Portal for portal users or not. |
T1C_AEM__Invited_Contact__c | T1C_AEM__Deal_Id__c | Text(18) | When the parent Invitation has the Deal Id field populated, it will rolldown to this field. This is mostly so we can use the field in Sharing Rules (since the lookup cannot be used). |
T1C_AEM__Invited_Account__c | T1C_AEM__Deal_Id__c | Text(18) | When the parent Invitation has the Deal Id field populated, it will rolldown to this field. This is mostly so we can use the field in Sharing Rules (since the lookup cannot be used). |
T1C_AEM__Aem_Event__c | T1C_AEM__Deal_Id__c | Text(18) | When the parent Event Collection is related to a Deal, this field will be populated with the Deal Id as plain text. This is mostly so we can use the field in Sharing Rules (since the lookup cannot be used). |
T1C_AEM__Invited_Attendee__c | T1C_AEM__Deal_Id__c | Text(18) | When the parent Invitation has the Deal Id field populated, it will rolldown to this field. This is mostly so we can use the field in Sharing Rules (since the lookup cannot be used). |
T1C_AEM__Event_Attendee__c | T1C_AEM__Is_Declined__c | Checkbox | Flag denoting whether the Event Attendee has declined event. |
T1C_AEM__Event_Attendee__c | T1C_AEM__Attendance_Type__c | Picklist | A way to categorize Attendees based on the mode by which they are attending an Event. |
T1C_AEM__Portal_Meeting_Ticket__c | T1C_AEM__Attendance_Type__c | Picklist | the reserved attendance type. Virtual still checks Account capacity if applicable but not physical capacity. |
FEATURE RETIREMENT
Click here to view the article for all feature retirements.
MOBILE INAPP TASK NOTIFICATIONS
WHAT IS CHANGING
Effective 2024.4 release, the in-app popup notification for tasks are no longer available. In previous releases, administrators can enable in-app popup notification using the feature ACE.Mobile.ALMMobile.DeviceNotifications.
WHY ARE WE RETIRING THIS FEATURE
The in-app popup notification were a major nuisance to users, especially if they had multiple tasks due the day of. Users would have to cancel the notification multiple times just before they can use the app. In the future, we will introduce a less intrusive method to notify users of overdue tasks.
WHAT ACTION TO TAKE
Once your organization has been upgraded to 2024.4 mobile app, delete the deprecated feature ACE.Mobile.ALMMobile.DeviceNotifications.