User Guide

TimelinePlus has been designed to be as close to the standard Timeline in look and feel as possible, to make it easy for users to transition to the new component. Here we're going to detail how users can take advantage of the additional features of TimelinePlus.

General Functionality

TimelinePlus is very similar to the standard timeline component in terms of displaying data and the basic functionality. Users will see their activities (and optionally other records) in a date ordered list, with overdue items hightlighted in the same way and showing the same basic information for each record. Users can click a record to go to the detail page in order to see full details for the record.

Activities can be closed by clicking the checkbox against the record - the same as the standard timeline component.

Timeline Filters

The key feature of TimelinePlus is the ability to create custom filters to reduce the volume of records and organise timelines, which can often run to tens or hundreds of items, particularly where automated records such as emails are included. We can filter on just about any field(s), and there's some additional functionality which makes this easier for fields like picklists or record types.

Creating a new filter

TimelinePlus filters look and work very similarly to filters used elsewhere in Salesforce.

  1. Create a new filter by clicking New in the dropdown menu
  2. Give your filter a name. The current version of TimelinePlus does not have sharing functionality so all created filters will be available to all users:
  3. Your new filter will now appear in the drop down list, but we haven't yet specified filter criteria. Click the dropdown again and choose Edit List Filters:
  4. From here you can specify which objects will appear in the timeline. If you want Tasks to appear in the timeline put a checkbox against 'Show Tasks', similarly for Events. If an administrator has specified a different object to appear in the list while setting up TimelinePlus you'll see a checkbox for that object here too.
  5. Any criteria already specified on this filter will appear below the object checkboxes, but because this is a new filter it will be blank. Click the Add Filter Criteria link to add criteria, then click the box which appears to show the filter criteria parameters:
  6. You can now select a field to filter on:
  7. Choose the operator and the value to filter for. Depending on the field type some assistance is provided here - for example Record Types are displayed as names rather than Ids, and picklist values are displayed in a list to select from:
  8. Click Save, repeat the above steps to add any additional criteria, and once you're finished click the main Save button at the top to save all your changes:

Important Notes

Filters on multiple objects

Filters are potentially operating on a list which is displaying data from multiple objects. TimelinePlus has been designed and built to only filter records for the object which the selected filter field is on. For example, if we filter on the CreatedDate on the Event object (Event:CreatedDate in the dropdown) all records from Task and any other object will still be displayed, only the Event object records will be filtered.

No support for creating new records

TimelinePlus has been designed with simplicity in mind, so we do not provide functionality to create new records. It's straightforward to create a new Quick Action to support creating new data (if you don't want to run the standard timeline alongside TimelinePlus) so this is the preferred setup if creating new records is needed.

Complex Criteria

Multiple criteria fields are currently always AND'ed, we don't support complex logic for filter criteria. If this is a high demand feature we'll consider this in a future release.

Filter Sharing and Update Restrictions

Filters are visible to all users and there are no restrictions on who can update filters and criteria. Salesforce features such as component visibility or multiple lightning pages could be used to support these features if they are needed, or if there's high demand we'll build this into the component in a future release.