Alerts - Fluid Topics

End-users can activate an alert to receive an e-mail notification when content matching their search criteria is added or changed.

Alerts are based on the ft:lastEdition metadata and happen on Mondays by default. Users with the ADMIN role can change this day or select multiple days in the Alerts tab of the Notifications section of the Administration menu. Content is considered to be new or updated when the value of its ft:lastEdition metadata postdates the last alert check.

Refer Manage Last Edition Date for DITA Topic Alerts to learn how to prevent unexpected alerts for DITA content.

Use case

The following use case shows why it is recommended to set a backdated value for a document's ft:lastEdition metadata key:

On Day +0, a user activates an alert for a search for which Document A was one of the results.
On Day +1, a content administrator updates Document A. This in turn updates the ft:lastEdition metadata for Document A.
On Day +3, Fluid Topics verifies the ft:lastEdition metadata for all documents in the corpus. Since Document A has been updated, Fluid Topics sends an email notification to the user who activated an alert for Document A. Fluid Topics set the lastAlertTimeStamp for Document A to Day +3.
On Day +10, Fluid Topics verifies the ft:lastEdition metadata for all documents in the corpus. For Document A, it has not changed. Fluid Topics does not send an alert to the user who activated an alert for Document A and does not update the lastAlertTimeStamp for Document A.
On Day +12, a new document (Document B) is added to the corpus. Document B matches the user's search criteria for alert.
On Day + 17, Fluid Topics sends an email notification to the user who activated an alert. Fluid Topics sets the lastAlertTimeStamp for Document A and Document B to Day +17.

Alerts - Fluid Topics - Latest

Manage Dates in Fluid Topics