Checkpoint challenge

Original, scenario-based practice. Never modeled on actual exam questions. It’s written in the “What I Would Architect” style: the point is making your judgment visible, not picking a letter. This challenge comes at the end of chapters 11 to 13: sharing in code and flows, the data that isn’t a record, and testing. My walkthrough is Checkpoint 2: Build It, Then Prove It, so try it first.

Where you start

You start from Checkpoint 1: Steve Trucking’s own staff, with private deliveries, coordinators who see only their own DC through Field Service’s User Territories, a role hierarchy built for access with the integration users outside it, two owner-based rules, a criteria-based rule per DC for the manifests, and account teams on the DC accounts. If you designed it differently, start from your own design.

Read the Steve Trucking brief, sections 1 to 8 again. Leave section 9 (the late changes) alone. And still only Steve Trucking’s own staff: the Retail Partners’ users, the crews and the Recipients come in Checkpoint 3.

What’s new

• Account managers by partner. Each Retail Partner has its own account managers in Steve Trucking’s sales team. They need that partner’s deliveries, in all three of its DCs, to run the relationship, and never another partner’s (S2).
• The manifests keep growing. Checkpoint 1 used one criteria-based rule per DC for Manifest__c: nine today. Steve Trucking expects three times today’s volume in five years, and a new DC in weeks (O1, O3).
• Photos and claim files. About four photos a delivery, four to five million a year, and they can show the inside of a home and sometimes people (S5). Retail Partners send files with their damage and install claims.

Your task

1. The partner rule (chapters 7 and 13, the internal half of SV1): give each partner’s account team that partner’s deliveries. Which mechanism? Write the rule, its source and its target. How many rules is that today, and at the tenth DC? How will you prove it, given that Salesforce says you “can’t test criteria-based sharing using Apex”?
2. The manifests (chapter 11): keep a rule per DC, or share each manifest in a flow or in Apex? If you write shares, say the share object, the reason, the target, both doors, and what happens when a DC is added.
3. Photos and claim files (chapter 12): where does each kind of file live, who can see it, and how? Which file settings do you choose, and which doors into a file do you close?
4. The test plan (this chapter): for each persona, write the rows: what they should see, what they shouldn’t, the expected result, and the evidence you’ll record. Use three users for every requirement, and include the null test and the side effects.
5. The changes to test again: list the events that should rerun your tests, and which tests each one reruns.

Write each decision as both options, then your choice: “in my professional opinion…”

Discussion

My walkthrough is Checkpoint 2: Build It, Then Prove It. Compare your reasoning, not just your boxes. Where you chose differently, can you say what you’d gain and what you’d give up?