When should you use a record action or related action to make a process available to business users?

Using a record action or related action is appropriate when business users work in the context of a record list. In this scenario, these actions enhance the user experience by allowing them to interact with specific records directly. Record actions can be invoked from a record view, enabling users to perform tasks related to that particular data entity without navigating away from the context of the record list. This streamlined approach not only promotes efficiency but also ensures that users are focused on relevant data, making it easier for them to complete their tasks.

Contextually, the other choices highlight scenarios where record actions might not be the best fit. For instance, if users do not need access to a site or lack permissions to view a record list, they might require an alternative interface for task completion. Additionally, if a user needs to initiate a new request without further action, different mechanisms beyond a direct record action might be necessary to facilitate that workflow effectively. Overall, the focus on the context of a record list is crucial for leveraging the full potential of record and related actions in Appian.