How do related actions differ from list actions?

Related actions are designed to function within a particular record context, which allows users to perform operations on the record they are currently viewing. This context is essential because it ensures that the actions available are relevant to the specific record, providing a seamless user experience when interacting with that record. For instance, if a user is viewing information about a specific customer, related actions might include options to update customer details, view transaction history, or escalate issues, all of which pertain directly to that customer.

In contrast, list actions do not operate within a specific record context but rather affect a collection of records or a dataset as a whole. This means that while related actions are closely tied to individual records and how users can manipulate them, list actions are more broadly concerned with overarching lists or groups of records.

Thus, the defining feature of related actions is their operation within the context of a specific record, enabling a tailored and context-sensitive interaction with individual records in the application.