Summer’22 Treasure Hunt a.k.a. My First Easter Egg Hunt

A few days ago my team and I were sharing with our US-based stakeholders we will be off for a few days due to official holidays on Friday and Monday in Bulgaria (Good Friday and Easter Monday). Naturally, this led to the question of how we usually celebrate Easter in our region and if we do Easter Egg Hunt. We explained Egg Hunting is not a popular Easter tradition, at least not like the “Egg Fights”, which provoked quite a laughter as we were misunderstood the tradition involves throwing eggs at each other instead of tapping with eggs 😂

So, this Sunday I woke up with the unusual urge to do an Egg Hunt, which is obviously not that fun if you are the only one who wants to do it and you have to hide the eggs on your own. I had to figure out how to do it on my own and still have fun. This is how I got the genius idea to just give this name to my regular Salesforce Release Treasure Hunt. This is how my Summer’22 Treasure Hunt became My First Easter Egg Hunt.

How did I prepare for My First Easter Egg Hunt / Summer’22 Treasure Hunt?

Simple.

• Salesforce had the Eggs/Treasures hidden already, as the official Release Notes are expected shortly after Easter (on April, 27th)
• I signed up for a Summer’22 Pre-Release demo environment here
• I admit it! I used some hints from the IdeaExchange Winners 😉

Which were the first few eggs in my basket?

Dynamic Related List — Single

We’ve been so patient about this feature and it is finally here. Now admins are able to configure more flexible related lists directly in the Lightning App Builder.

The new standard component “Dynamic Related List — Single” allows admins to configure related lists one by one, utilizing the well-known Component visibility to define if the component should be shown or not. But the most wanted part of it is within the component configuration itself:

• You are able to select the parent record — either the current record or another record related via a relationship field
• You are able to select the related list and even give it a custom label
• You can select either “List” or “Tile” as a Related List Type for the visualization. Note that the “List” option here is pretty much the same as the “Enhanced List” option in the “Related Lists” and “Related List — Single” components.
• You can configure the default number of records shown in the list
• You can decide if you want to show the action bar or not
• You are able to select whichever fields to be shown in the related list (within the standard limitation of 10 fields, visible only for the “list” type, while the “tile” type shows only the first 4 fields)
• You can pick a field to sort the list by and it does not even need to be in the selected fields to display
• And finally… You can filter the list by one or more fields! For now, the filters (if you add more than one) are only applied with an “AND” logic, but probably this will change soon enough.
• And that’s not all! You can even pick the actions available for the list!

So, no more custom components if you want to show “Won Deals” separately from “Open Opportunities”

Median Summary Function in Reports

I’m not sure if I can count how many times I had to explain to stakeholders Salesforce reports can only summarize data as COUNT, MINIMUM, MAXIMUM, AVERAGE, but not as MEDIAN.

Not any more!

Median is now available as a standard summarization function in the Report Builder.

Report Type Selector

While I was after the new summarization functions, I also noticed the new Report Type Selector, giving users much more information about the report type, not just the description.

The new Report Type Selector shows the user:

• if the report type is a standard one or a custom one
• which objects are available in the report type and the user can even browse the fields before starting to build the report
• a list of reports based on this report type created by the user or other users

The user is also able to hide some report types for themself.

Flow Triggers in Object Managers

In addition to the very useful “Flow Trigger Explorer” available since Spring’22, now the Record-Triggered Flows are also shown in the Object Manager. The Flow Trigger Explorer is also available from the same page.

New Entry Conditions for Record-Triggered Flows

When configuring the Entry Conditions for a Record-Triggered Flow, now you can also use a custom formula to determine if the flow will run or not. Previously it was not possible to define the criteria based on a related record’s field values and/or on the running user’s attributes.

Now you can use practically all Global Variables available within the flow to determine if the record should enter this flow or not. Which is very cool and closes the gap between Workflow Rules and Flows. Of course, it was possible to have a decision right after the flow triggers, but having it in the Entry Conditions would be much more effective.

Conclusion

I had quite an interesting “Egg Hunt” this Easter and I am very excited for the official Release Notes and to discover the rest of the new Summer’22 features.