Hotlists
Hotlists, also referred to as longlists, are a way to group together a set of contacts that you want to keep track of. You can create as many hotlists as you want, and add as many contacts as you want to each hotlist. Hotlists are a convenient way of bucketing contact records together to perform actions on them. Similar to the Search and Match screens, hotlists can be viewed and managed in either split or table view. A packaged Standard Hotlist record type is included in the product and can be used in conjunction with custom record types.
All custom Hotlist lookups in Seven20 components support lookup customisation.
Hotlist Members
Contacts are added to hotlists by creating new Hotlist Member (seven20__List_Member__c) records. A Hotlist Member record is a junction object between a Hotlist and a Contact, and contains the following fields:
| Label | API Name | Type | Description |
|---|---|---|---|
| Hotlist | seven20__List__c | Master-Detail | The Hotlist that the member belongs to |
| Contact | seven20__Contact__c | Lookup | The Contact that is a member of the Hotlist |
| Status | seven20__Status__c | Picklist | A customisable picklist for tracking a member's status within the hotlist; discrete sets of available values can be achieved through the use of record types, if required |
| Key | seven20__Key__c | Text | An automatically generated, unique identifier for a hotlist member, used to prevent duplicates. It is an external Id, made by concatenating the Contact and Hotlist field values. Do not set this field to any other value |
There is no restriction on custom fields being added to the Hotlist Member object as required
Creating new Hotlists
Throughout the Seven20 product there are various actions which allow the user to add Contacts to Hotlists, both individually and en masse. The lookup field for selecting the desired Hotlist on these actions also includes a 'Create New' option to facilitate the process. When using the 'Create New' option the available fields can be configured by creating a Seven20 Configuration Settings metadata record as below:
| Field Label | Field Api Name | Value |
|---|---|---|
| Developer Name | DeveloperName | Hotlist_creation_form_fieldset (Must match exactly) |
| Label | Label | Hotlist creation form fieldset |
| Active | seven20__Active__c | True |
| Value | seven20__Value__c | API Name of a field set against the Hotlist object containing the desired fields |
Hotlist Name and Type (seven20__Type__c) fields are not included by default and should be added to the field set
Permissions
Read access to the following objects is required to utilise the hotlists functionality:
- seven20__List__c
- seven20__List_Member__c
Additionally, read access is required for the following fields as a minimum:
- seven20__List__c.Name
- seven20__List__c.seven20__Type__c
- seven20__List__c.CreatedDate
- seven20__List_Member__c.seven20__Contact__c
- seven20__List_Member__c.CreatedDate
Additionally configured fields that a user does not have read permissions for will not be displayed