Salesforce Case Object for Consulting and Customer Service

Image Capture Requirement

• A consulting company wants to capture images of customer sites while editing case records during customer site visits.
• The Director of TI wants to minimize customization and promote reusability of code artifacts.
• Recommendations:
  • Use Lightning Component as an override for "Edit" action on mobile view, allowing image capture feature.
  • No change required for desktop users.
  • Alternatively, create a separate button "Edit in Mobile", which opens a custom lightning component that allows field consultants to add an image.

Role Hierarchy and Access Control

• Mary is Joe's manager in the Role Hierarchy.
• Organization-wide default for a custom Invoice object is Public Read-Only.
• Mary's profile is not granted the Read permission for the Invoice object.
• Mary can only view Joe's invoice records.

Sharing and Access Control

• Universal Containers (UC) has a team that analyzes customer orders for fraud.
• To grant sales managers access to shipment records, Apex managed sharing was used.
• IT team is worried about improper access to records.
• Recommendations:
  • Use runAs system method in test classes to test using different users and profiles.
  • Use isAccessible keyword in Apex classes to assure record visibility will be followed.

Field Level Security

• A banking company wants Date of Birth field searchable by Banking Reps, but only editable by Customer Support Reps.
• Recommended approach:
  • Set field level security for the Date of Birth field to be Visible to Customer Support Rep Profile, and set the Date of Birth field Visible and Readonly to Banking Rep profile.

Master-Detail Relationship and Access Control

• A custom Invoice object has a master-detail relationship to Account.
• Accounts receivable (AR) team needs access to invoice records.
• AR users neither own nor have access to account records.
• The account organization-wide default is set to Private.
• AR team is unable to find invoices in list views, reports, and Global Search.
• Reason: A sharing rule is missing to share invoices with the AR team.

Criteria-Based Sharing Rule

• Criteria-based sharing rule on Case shares to the Role Manager and above when a custom field Assigned Agent (subject of the complaint) is not blank.

Role Hierarchy Realignments

• Recommended advanced tool for large-scale Role Hierarchy realignments: Granular Locking.

Access Control and Team Management

• Universal Containers (UC) delivers training in 500 different regions.
• Operations users team manages course setup, scheduling, and trainer setup.
• Operations manager requested access to edit ALL scheduled courses owned by the operations users team.
• Recommended approach:
  • Create an ownership-based sharing rule and share the scheduled courses with the operations manager.

Access Control and Case Management

• If a Case requires involvement from one of the Legal team, the Case owner adds one of the corporate lawyers to the Legal SME field on the case.
• Since cases are private, how can we grant a lawyer access to a specific case when their assistance is needed?
• Recommended approach:
  • Use Apex Managed sharing in a case Trigger that shares the record to the user identified in the Legal SME field.

Community and License Management

• Universal Containers uses 75,000 distributors that have close to 1 million total users.
• Distributors need to use the community to see closing opportunities assigned to their distributor for delivery.
• Recommended license: Partner Community.

Community Function and Sharing Settings

• If Site User Visibility is turned off in Sharing Settings, it impacts the community function of searching for other external users.

Collaboration and License Management

• To allow community users to collaborate on Opportunities, users must be given a Customer Community Plus license.

Access Control and Geographic Location

• Universal Containers (UC) requested that branch managers and UC branch staff should only see customers and related information in their geographic location.
• Recommended approach:
  • Configure organization-wide defaults of the Account object and create sharing rules.
  • Alternatively, configure Role Hierarchy and create sharing rules.

Access Control and Custom Object

• Universal Containers (UC) sales managers are complaining that they cannot access their teams' Shipment records (a custom object).
• Reason: The Grant Access Using Hierarchies option on Shipment Sharing Settings was incorrectly disabled by the admin.

List View Management

• Sales operations at Universal Containers (UC) wants to create list views to filter opportunities for certain geographies.
• To hide list views that are not relevant to an individual user, recommended approach:
  • Share the list views with the appropriate role and internal subordinates.

Access Control and Auditor Team

• At Universal Containers, there's a team of auditors distributed throughout the organization that all need access to high-value opportunities.
• With a Private sharing model, recommended approach:
  • Create a public group and assign the auditors to the group.

List View Management and Access Control

• Sales executives at Universal Containers (UC) want to create list views to filter opportunities for large at-risk opportunities.
• These list views should only be available to certain executives who specialize in closing problematic deals.
• Recommended approach:
  • Share the list views with the appropriate individual users.

Organization-Wide Defaults and Access Control

• Universal Containers' organization-wide defaults model is Private for the Account object.
• A sales rep owns two opportunities in one Account.
• Sales Rep profile has Create/Edit access to opportunity records.
• Sales rep has Read access to the related Account record.

Data Retention and Recovery

• Universal Containers (UC) is in a legal dispute regarding several orders.
• UC has found out that these records were removed from the system.
• Recommended approach:
  • Use a data retention and recovery strategy to ensure that records are not deleted from the system.