2022.3 Release Summary
  • 14 Nov 2023
  • 16 Minutes to read
  • Dark
    Light
  • PDF

2022.3 Release Summary

  • Dark
    Light
  • PDF

Article summary

HOW TO USE RELEASE SUMMARY

Tier1 2022.3 release is available as of November 2022.

The release notes offer a brief description of the improvements and new features. Tier1 has added more technical documentation such as APIs, feature retirements and data model changes in each release summary based on client feedback. Contact your Tier1 Client Services representative to learn more or provide feedback on what else would be valuable to see in the release summary.

Supported browsers and devices is updated each release to reflect what Tier1 currently supports.

CLIENT CENTER

ADVANCED GRID FILTERING

Client Center is introducing powerful spreadsheet like filtering in key areas of the application to make finding data easier. In Client Center activity manager, contact, account and quick find contact grids and coverage cube, users can click on most column headers to apply a filter on the column and then when they are done, they can use the top filter to either clear one or all the applied filters.

The following column header filters are supported

  • Text: Standard free-form text to filter text columns like contact name, account name

  • Picklist: Drop-down menu of the picklist options or the empty option. Note that administrators can force a text column to become a picklist option such as contact title.

  • Number: Common operator options and a free-form text to enter a number. For example, find contacts with interest score greater than 50.

  • Date Range: From and to date pickers to filter date ranges. For example, filter for interactions newer than 2022-10-01.

Special multi-data grid columns or what Tier1 calls item renderers are not default supported by the advanced grid filtering. Examples include context menu, multi-email, coverage indicator columns.

By default, advanced grid filtering is disabled for all grids and can be enabled on each grid individually Contact Tier1 on how to enable this feature and its configuration options.

FLEXIBLE CALL REPORT NOTIFICATIONS

Client Center is introducing a new flexible call report email notification email template to ensure the most relevant information is shared to users. It offers two notable benefits to the current email notifications.

  1. Administrators can configure the subject and body of the email notification. Examples include removing the contact’s email or telephone or adding custom information such as whether this meeting has a C-Level executive.

  2. Users will see a what’s updated section in the email notification for use cases where users have modified an existing call report. The email notification shows what’s changed first, so users don’t have to guess what has changed in the call report.

The flexible call report notifications are only available for new call reports and rapid interaction form; and mobile will incorporate this new email template in the next release.  

This feature is not supported in quick add interaction, legacy call report, and quick call forms.

By default, the new flexible call report email notification is disabled. Contact Tier1 for the configuration document on all the configurations and restrictions of the new email template.

CLIENT FEEDBACK

ACTIVITY MANAGER NEW INTERACTIONS TAB

To help users prepare for upcoming meetings and review the client interactions and their consumption in a single view, activity manager is introducing a new tab that displays both Tier1 events and call reports in a grid view. For users who prefer a calendar view, activity radar offers the same capabilities in month, week, or day view.

By default, the new tab is disabled.

SIMPLIFIED SEARCH IMPROVEMENTS

Client Center simplified search has been improved based on user feedback.

  • Simplified search can perform single ticker searches, so users no longer need to toggle back to classic top search. For multi-ticker searches, users must continue using the classic top search.

  • Simplified search finds exact matches when users enter phone numbers and emails. This will help users find more targeted results when using contact phone or email.

  • Simplified search retains the search phrase after performing a search. Users do not have to remember what search phrase they entered.

  • Recently searched parameters now work if users typed Enter key or if users click on a search result. It previously only worked if users typed Enter key.

  • Simplified search displays a show more option in cases where there are more results than what is being displayed. For example, if a user searches for “aa”, they can click show more on the contact section and then simplified search will display more contact results and remove account and interest subject results.

  • Simplified search can be configured to have more advanced search scopes in addition to the simple in all accounts and in all contacts. For example, in Europe, in my account coverage, in my contact coverage, in CIB accounts. Administrators must define these additional search scopes.

QUICK ADD INTERACTIONS IMPROVEMENTS

Users can now remove the notification teams in the notification list grid on the quick add interaction form. Note in the previous release, users had to uncheck each employee.

EMPLOYMENT CHANGE SECURITY UPDATE

Performing an employment change no longer requires access to all lists. Any users permissioned to use the employment change can bypass list access and save the changes. Note in the previous release, employment change showed errors if the user did not have access to modify one or more of the lists that the contact was in.

CONTACT INACTIVE DATE

A new datetime field called inactive date has been added to contact object. It is populated with the current datetime when a user inactivates the contact. Note that re-activating the contact does not clear the datetime value.

LIST DEEPLINKING

Administrators and developers can direct users into Client Center with a list pre-selected by appending the following in the page URL: ?listId={SalesforceListId}. For example, providing a URL such as /apex/T1C_Base__ALM?listId= a0I8G000001d3hZUAQ opens Client Center with the specified list pre-selected. 

Tier1 will be providing more deeplinking capabilities in the future and is looking for feedback on this topic.

DEALS

SUPPORT DATETIME FIELDS

Deals now support datetime fields for more granular date tracking. For example, to help compliance track the datetime when users had knowledge of the deal. Administrators can enable datetime fields on deal, deal team members, product tabs by modifying the field sets.

DEAL LISTS GRID IMPROVEMENTS

Deal list grid has been improved to load records faster into the deal list grid. 

  • Query and processing optimizations have been made to load records faster into the deal list grid. Users will see deal records load faster.

  • To reduce accidentally loading all deals, administrators can disable all deals list or configure specific filter clauses to prevent loading of historic deals, for example, exclude all deals created more than 3 years ago.

OTHER IMPROVEMENTS

To help deal coordinators manage deal team members faster, users can add employees to deal team from all teams in the system instead of team members they are on. Administrators can also configure filter conditions to hide teams such as teams from the public side of the markets. By default, this feature is disabled.

EVENTS SELL-SIDE

MEETMAX INTEGRATION

Tier1’s MeetMax integration provides Tier1 users a unified booking event experience. In Client Center, users can view MeetMax conferences alongside Tier1 events in the events cube, they can then register their contacts to a conference.

MeetMax - Events Cube - Register Attendee

Tier1’s MeetMax integration requires an additional enablement fee. Contact Tier1 for more details.

NEW MEETING REQUESTS

Events is introducing the ability for users to request meeting preferences for a specific event. This new feature will help coordinators and sales to solicit interest in an event and then coordinators can plan the appropriate number of meetings. The following workflow is now supported

  1. Coordinators can create an event without any meetings.

  2. Coordinators and sales can solicit meeting preferences from interested clients.

  3. Coordinators can organize the appropriate number of meetings based on interest and then move the attendees into those timeslots.

The following improvements have been made to the booking screen and event summary screen to support the new meeting requests.

  • On the booking screen, users can request a specific event, meeting timeslot or preferred meeting time, and preferred meeting type.

  • On the event summary screen, a new requests tab displays all the meeting requests. Coordinators can select to move the attendees into the meeting timeslots or decline the meeting request.

BOOKING SCREEN IMPROVEMENTS

In addition to meeting requests, the booking screen has been improved based on user feedback.

  • On the add accounts and contacts tab, users can inline edit the attendance type and role.

  • On the add covering professional tab, reason has been added to indicate the reason why a covering professional was added to the meeting. For example, was it based on coverage or was it manual.

  • The application now prompts the user to set a new location if users remove an attendee from the meeting. Any meetings without any attendees will set the location to blank.

  • The application now correctly remembers the meeting location option, venue or attendee office, when editing the meeting.

  • Administrators can disable, re-order, or re-label tabs on the booking screen.

NOTE: In this release, we have identified a gap in which standard users can edit the attendee status and role fields with all the available dropdown options. For example, standard users should not be allowed to confirm an attendee when the meeting is a request only meeting. Therefore, we have removed the ability for standards users to edit any of these fields when booking or requesting attendees. The workaround would be to ask the event coordinators to update the status, role, or attendance type after booking. In the next release, we are providing the solution such that standard users, who are the booking owner, can edit the status, role, or attendance type with a predefined list of allowed dropdown options.

EVENT FEEDBACK

Feedback from event attendees is vital information for corporate access teams to improve future events therefore we have introduced the ability for users to capture event feedback. On the event summary screen, users can view existing event feedback on the event feedback tab or log new feedback on the event attendees tab.

Consider the following before enabling this feature.

  • Log feedback uses a new call report layout which will automatically populate the related to field with the event and all attendees.

  • Existing call reports configurations, sharing, and customizations may impact your log feedback call report form. Plan and work with Tier1 to ensure the form is working to your desired requirements.

By default, this feature is disabled. Note that previous event feedback is deprecated.

EVENT SUMMARY IMPROVEMENTS

Tier1 events summary screen continues to be enhanced to accelerate event coordinator workflows so that they can complete their actions more quickly and effectively. In this release, the following changes have been made.

MEETING DETAILS

Coordinators can navigate between meeting details on the summary screen and quickly book a new attendee or update the meeting information. The following capabilities are available now in summary screen.

  • On the left navigation, coordinators can click on any meeting timeslot and open the meeting details.

  • On the meeting details, coordinators can book or request attendees, inline edit attendees on the grid, add non-CRM attendees into the additional attendees, and add any additional information.

  • The right navigation displays a contact’s itinerary for the event.

  • In addition, coordinators can take the following action from the toolbar

    • Add key participants from the event into the meeting.

    • Set meeting location if the meeting location has changed.

    • Add to calendar will download the calendar (ICS) file for the meeting.

    • Export meeting attendees will download the attendee grid as an Excel file.

    • Email will open a meeting invitation email with the meetings details pre-populated.

    • View meeting link copies a Salesforce URL to this meeting in the clipboard.

    • View attachments lets users manage meeting attachments.

    • View meeting notes lets users manage meeting notes.

    • Context menu for common meeting actions such as book meeting, unbook meeting, edit meeting. In addition to the standard actions, administrators can add custom meeting launch points to open external systems.

ACTION PANE

Coordinators who prefer to mass update attendee status or role without going into the meeting details can do so on the schedule tab action pane. The new action pane replaces the approver view functionality.

Coordinators can select multiple contacts in the grid and then use the action pane on the right to quickly confirm, move, or decline the attendees. They can also mass update the attendees’ role and status to specific values.

OTHER IMPROVEMENTS

Events summary screen has other minor improvements based on user feedback.

  • Expand all and collapse all controls have been added to events and meeting list.

  • A more user-friendly message if the meeting’s capacity has been reached.

CLIENT FEEDBACK

PERFORMANCE

Tier1 is committed to continuing to improve the performance of the Events application. The following forms and workflows were targeted for this release.

  • Application startup: meetings are no longer loaded during startup, while this improves the startup of the events application, the enhanced day view will take longer time to load. In addition, Events no longer checks for additional record access unless an event coordinator is working on behalf of another user; in the previous release it was always performing the record access check.

  • Meeting details: the meeting details screen is now embedded into the event summary screen and its performance has been significantly improved.

  • Attendee sync: query and save optimizations have been made to the attendee sync. When saving attendees, non-valuable information is no longer synchronized. See object model section for more details.

OTHER IMPROVEMENTS

  • To make finding data easier in the list view, users can use the text search and date range search to search for events to display in the list view. Note that users can still use the mini calendar to choose the date range. In addition, users can use key filters at the top to filter by types, topics, or regions.

  • When booking attendees, users can now indicate whether a meeting attendee is attending physically or virtually. Users can update the attendance type on either the booking screen or the event summary screen.

  • Client Center events cube has added support for the new booking screen. It now matches the booking screen in Tier1 events.

  • On the edit meeting screen, if users manually override a location’s address, they can safely revert to the original location address in case they accidentally updated the address.

  • Administrators can configure the fields to display on the summary of the calendar (ICS) file. By default, event name is used, however administrators can configure other fields such as booking type, meeting type, event collection name.

TIER1 FOR OUTLOOK

OAUTH FOR OFFICE365

Tier1 for Outlook has added support for Microsoft OAuth-based authentication.  This update is only applicable for mass emails delivered by EWS to Exchange Online Office 365 environments and not applicable for on-premise Exchange or SMTP/Omnigage.

SUBMIT CONFIRMATION CODE TO START MASS EMAIL

To prevent users from accidentally mass emailing to contacts or to lists, Tier1 for Outlook has added support for a confirmation prompt which requires the user to input a random generated code before starting the mass email process. By default, no confirmation code is required to start a mass email, however administrators can enable this feature by configuring the length of the confirmation code and if enabled, users must enter a randomly generated confirmation code each time to mass email.

SECURITY ENGINE

SECURITY ENGINE CONSOLE IMPROVEMENTS

Security engine console has been improved to display configurations for batch settings, activity security, and disabled triggers without having to navigate to Salesforce. In addition, administrators can export these settings to comma-separated file (CSV).

ARCHITECTURE

LIST REST APIS

In this release, Tier1 has made the following list APIs available for clients and partners to use.

GETTING EXISTING LISTS

There are two new REST APIs to retrieve lists and their contacts and accounts. These are useful if you want to sync lists and their contacts into a third-party system; another use is to store the snapshot of a dynamic list so you can analyze the data over time.

  • getLists: gets all lists in the system or lists for a given user ID. It also provides who the lists are shared with.

  • getListEntries: gets list entries, contacts or accounts, for a given list. Supports all static and dynamic list types.

MODIFYING EXISTING LISTS

There are three new REST APIs to modify a list. These are useful if you want to add, remove list entries on a static list to keep lists in sync or programmatically archive a list that was created by an algorithm.

  • addListEntries: adds contact or account list entries to a static list. Not available for dynamic lists.

  • removeListEntries: removes contact or account list entries from a static list. Not available for dynamic lists.

  • deleteList: deletes or archives a list. Supports all static and dynamic list types.

CREATING A NEW LIST

There is one new REST API to create a new list. This is useful if you want to programmatically create a new list for users such as using Einstein discovery to create the next best call list for each user.

  • addList: creates a new static account or contact list.

Contact Tier1 for the full API documentation on how to interact with the list REST APIs.

ACCESSIBILITY IMPROVEMENTS

Tier1 strives for compliance with Web Content Accessibility Guidelines (WCAG) 2.0 level AA and will be planning to address gaps in the next several releases. In this release, Tier1 has enabled keyboard focus for top search, buttons, text inputs, text areas, dropdown menus, dropdown buttons in Client Center. Users can see a black outline on these components when they are in focus.

DATA MODEL CHANGES

NEW FIELDS AND OBJECTS

OBJECT API

FIELD API

FIELD TYPE

DESCRIPTION

T1C_Base__Call_Report_Data_Quality__c

T1C_Base__Call_Report__c

Lookup(Call Report)


T1C_Base__Call_Report_Data_Quality__c

T1C_Base__Description__c

Long Text Area(32768)

Full description of the data quality check

T1C_Base__Call_Report_Data_Quality__c

T1C_Base__Severity__c

Text(255)

Severity of the data quality check

T1C_Base__Call_Report_Data_Quality__c

T1C_Base__Error_Id__c

Text(255)

Error Id of the data quality check

T1C_Base__Call_Report__c

T1C_Base__Interaction_Class__c

Picklist

Aligned to RIXML, class of interaction

T1C_Base__Call_Report__c

T1C_Base__Is_Billable__c

Checkbox

Indicates whether an interaction is in scope for publication or reporting

T1C_Base__Ace_List__c

T1C_Base__Source__c

Text(255)

This field stores the source where the list was created from, used via the create list API

Contact

T1C_Base__Inactive_Date__c

Date/Time

Datetime at which the contact was last deactivated

T1C_AEM__Request__c

T1C_AEM__Account__c

Lookup(Account)


T1C_AEM__Request__c

T1C_AEM__Requested_Meeting_Address__c

Long Text Area(32000)

A free form address to use when a meeting is created for this request should no office nor venue have been chosen.

T1C_AEM__Request__c

T1C_AEM__Attendee_Count__c

Roll-Up Summary (COUNT Request Attendee)

The total number of Request Attendees associated to this Request.

T1C_AEM__Request__c

T1C_AEM__Is_Completed__c

Checkbox

Marked TRUE once a request has been actioned on by a coordinator

T1C_AEM__Request__c

T1C_AEM__Event__c

Lookup(Aem Event)

The Event for which the request was made

T1C_AEM__Request__c

T1C_AEM__Event_Collection__c

Master-Detail(Event Collection)

The Collection for which the request was made

T1C_AEM__Request__c

T1C_AEM__Meeting__c

Lookup(Meeting)

The Meeting for which the request was made

T1C_AEM__Request__c

T1C_AEM__Notes__c

Long Text Area(50000)

Any additional notes as it relates to the request

T1C_AEM__Request__c

T1C_AEM__Rejection_Reason__c

Long Text Area(32000)

A freeform text field that describes the reason why a particular Request was rejected/declined

T1C_AEM__Request__c

T1C_AEM__Requested_Meeting_Type__c

Lookup(Meeting Type)

When there is no existing meeting selected a Requested meeting type should be set

T1C_AEM__Request__c

T1C_AEM__Requested_Office__c

Lookup(Contact)

Id of the Contact Attendee who's office is selected for the location of the meeting

T1C_AEM__Request__c

T1C_AEM__Requested_Start_Time__c

Picklist (Multi-Select)

When there is no existing meeting selected a Requested meeting time should be set

T1C_AEM__Request__c

T1C_AEM__Requested_Venue__c

Lookup(Venue)

Id of the requested venue

T1C_AEM__Request__c

T1C_AEM__Status__c

Picklist

The current status of the request

T1C_AEM__Request__c

T1C_AEM__Summary_Notes__c

Long Text Area(100000)

Summary notes containing all relevant info for the Request. Internally populated field ONLY for OUR consumption

T1C_AEM__Request_Attendee__c

T1C_AEM__Attendance_Reason__c

Long Text Area(5000)

The reason why this particular person was added to the Internal Attendees

T1C_AEM__Request_Attendee__c

T1C_AEM__Attendance_Reason_Source__c

Long Text Area(5000)

The source data for the reason why this particular person was added to the Internal Attendees

T1C_AEM__Request_Attendee__c

T1C_AEM__Attendance_Type__c

Picklist

A way to categorize Attendees based on the mode by which they are attending a Meeting

T1C_AEM__Request_Attendee__c

T1C_AEM__Booking_Owner__c

Lookup(Contact)

The Booking Owner for the request

T1C_AEM__Request_Attendee__c

T1C_AEM__Contact__c

Lookup(Contact)

The contact the request is for

T1C_AEM__Request_Attendee__c

T1C_AEM__Request__c

Master-Detail(Request)

The request this attendee is part of

T1C_AEM__Request_Attendee__c

T1C_AEM__Role__c

Text(64)

Requested role of the attendee

T1C_AEM__Request_Attendee__c

T1C_AEM__Unique_Id__c

Text(40) (Unique Case Insensitive)

Unique identifier for the Request Attendee (it's a concatenation of the Request Id and the Contact Id, the format is: Request__c:Contact__c)

User

T1C_AEM__WS_Username__c

Text(80)

MeetMax webservice username

User

T1C_AEM__WS_Password__c

Text(80)

MeetMax webservice password

T1C_AEM__Invited_Contact__c

T1C_AEM__Attendance_Reason__c

Long Text Area(5000)

The reason why this particular person was added to the Internal Attendees

T1C_AEM__Invited_Contact__c

T1C_AEM__Attendance_Type__c

Picklist

A way to categorize Attendees based on the mode by which they are attending a Meeting

T1C_AEM__Invited_Contact__c

T1C_AEM__Attendance_Reason_Source__c

Long Text Area(5000)

The source data for the reason why this particular person was added to the Internal Attendees

ATTENDEE SYNC LOGIC UPDATE

OBJECT API

FIELD API

Sync?

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Booking_Owner__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Event_Collection_Location__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__External_Id__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Has_Attended__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Imported_Date__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Is_Attending__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Is_Collection_Active__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Is_Virtually_Attending__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Last_Invited_Date__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Lists__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Non_Compliance_Reason__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Notes__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Reason__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Reason_Additional_Info__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Role__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Status__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Virtual_Attendance_Details__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Was_Invited__c

No

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Contact__c

Yes

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Event_Collection__c

Yes

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Is_Internal__c

Yes

T1C_AEM__Event_Collection_Attendee__c

T1C_AEM__Is_Key_Participant__c

Yes

T1C_AEM__Event_Attendee__c

T1C_AEM__Booking_Owner__c

No

T1C_AEM__Event_Attendee__c

T1C_AEM__Contact__c

Yes

T1C_AEM__Event_Attendee__c

T1C_AEM__Event__c

Yes

T1C_AEM__Event_Attendee__c

T1C_AEM__Event_Collection__c

Yes

T1C_AEM__Event_Attendee__c

T1C_AEM__Imported_Date__c

No

T1C_AEM__Event_Attendee__c

T1C_AEM__Is_Internal__c

Yes

T1C_AEM__Event_Attendee__c

T1C_AEM__Is_Key_Participant__c

Yes

T1C_AEM__Event_Attendee__c

T1C_AEM__Non_Compliance_Reason__c

No

T1C_AEM__Event_Attendee__c

T1C_AEM__Notes__c

No

T1C_AEM__Event_Attendee__c

T1C_AEM__Reason__c

No

T1C_AEM__Event_Attendee__c

T1C_AEM__Role__c

No

T1C_AEM__Event_Attendee__c

T1C_AEM__Status__c

Yes

T1C_AEM__Event_Attendee__c

T1C_AEM__Virtual_Attendance_Details__c

No

FEATURE RETIREMENT

CLIENT CENTER QUICK CALL FORM

WHAT IS CHANGING

As part of the 2023.1 release, the Client Center quick call form will be deprecated and no longer supported by Tier1. As part of the feature retirement, the following fields in the activity object will be available for deletion.

  • Called_Contact_Number__c

  • Notify_Coverage__c

  • Telephony_Message_Id__c

  • Telephony_Message_Label__c

  • Transaction_ID__c

WHY ARE WE RETIRING THIS FEATURE

The rapid interaction form enhances and replaces the functionalities that are available in the quick call form.

WHAT ACTION TO TAKE

  1. Clients currently using the quick call form need to upgrade to the rapid interaction form. Please contact Tier1 for implementation details.

  2. Review any custom solutions built around the fields being deprecated. Once deprecated, these fields can be deleted from Salesforce.


Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Eddy AI, facilitating knowledge discovery through conversational intelligence