Last Updated on June 24, 2020 by Rakesh Gupta
This is the fifth week of posting a ‘use case a day’ so that a newbie can practice. These five weeks also gave me some time to relax – for, because I was posting a ‘use case a day’, I did not write any blogs. Now, it is time to go back to my regular fix – writing blogs!
During these five weeks, I received many emails requesting detailed answers to ‘one use case a day’ questions! The answer is ‘No’.
Sorry to disappoint – for several reasons: (1) the intent of these exercises is to help you think through a solution; (2) providing detailed answers will defeat the very purpose of these exercises; and, last but not least (3), coming up with ‘use case a day’, editing them for publishing etc., is pretty time consuming. My editor, Munira Majmundar, and I spend several hours working on each post – be it a ‘use case a day’ or a full-fledge blog. Unfortunately, neither she nor I have extra bandwidth to provide detailed answers – notwithstanding the fact that providing answers, as mentioned, defeats the very vision and mission of these exercises. So, do yourself a favor – think! Think through the steps and reach out to us for guidance.
With that said, next week is the last week of posting a ‘use case a day’ series. If you have any suggestion, feedback – please reach out to me via this form.
I am posting a ‘use case a day’ because I strongly believe that one of the streamlined ways to master Salesforce is to take a requirement, think how to design and develop various solutions and then, chose the best solution. By so doing, I want to help my fellow Trailblazers to work on solving challenges and learn something new daily! Empower yourself with Salesforce skills so you too can be a ‘Giver’ and not just a ‘Taker’.
Yes, true! Certainly. Why just me? It is very likely that a fellow-trailblazer may be your guide instead; or, in the near future, you may be a guide to someone else! For remember, when one teaches, two learn!! So, get the ball rolling and, knock out the following use cases!!
Before that check out the previous exercises:
- Admin Excercise – 1
- Admin Excercise – 2
- Admin Excercise – 3
- Admin Excercise – 4
- Admin Excercise – 5
- Admin Excercise – 6
- Admin Excercise – 7
- Admin Excercise – 8
- Admin Excercise – 9
- Admin Excercise – 10
- Admin Excercise – 11
- Admin Excercise – 12
- Admin Excercise – 13
- Admin Excercise – 14
- Admin Excercise – 15
- Admin Excercise – 16
You can also use this landing page to find all the exercises in one place. So, without further ado, let us untangle the following use cases!!
Donna Serdula’s confidence, as a System Administrator at GoC, continues to build – amazing stuff!! In a short time-span, she has been inching from being a novice to becoming a pro! Donna now has the following requirements to tackle:
Donna is in the process of creating a validation rule to make sure that, whenever lead is marked as Unqualified the Reason (reason__c) field is required. She has a task to make sure that the validation rule shouldn’t trigger for cloned and new records.
Help Donna to solve this requirement. Not only that, share with her different ways via which this requirement can be solved in Salesforce. And, last but not least, identify the best solution and explain why you believe it is the best solution!
Note: – I am grateful to Resco.net for sponsoring my blog.
Proofreader: - Munira Majmundar