Scenarios – Rationale for automation

We will explore a real-world scenario in this section, starting with defining high-level requirements and going more granularly into low-level requirements. With the aid of a process flow, we will discuss the rationale behind the steps we plan to automate.

High-level requirement:

The user will be able to request and gain access to accounts and related records such as contacts, opportunities, and cases. Users not within specific business groups need compliance approval before they can be granted access to the account and related records.

Low-level functional requirements:

1. The sales analyst requests access to Salesforce data.
2. The sales manager/sales operations will be able to add users to the account team.
3. Compliance needs to approve user access if they do not belong to the same group. Example: Sales users in Zone 1 can be granted access to any of the records owned by users from Zone 1, whereas if a Zone 2 user needs...