A new capability in Release 18C will allow you to be more flexible in defining dynamic layouts in Engagement Cloud. I realized I never took my time to discuss dynamic layouts themselves. This makes it harder to describe the added value of the new 18C capability … which I will not mention yet …
So here goes !
Layouts
Layouts in Engagement Cloud are defined in App Composer They are collections of user interface components that are needed for users to interact with a type of information. Engagement Cloud uses 3 main types of layouts:
- Landing Page Layouts describe what list pages in Engagement Cloud look like
- Creation Page Layouts hold the page layout definition for creation pages
- Details Page Layouts are the main pages and describe how users can discover all details and related information to any type of information
For each of these layouts, App Composer, administrators can define what the layouts exactly need to contain. The example below shows how the detail page for opportunities can be defined:
- What fields need to be available to capture information on opportunities
- Which buttons / actions need to be available to interact with the opportunities
- Which related types of information should be available to add context to the opportunities (team, contacts, competitors, …)
- Add Mashup Content
These layouts are always defined in the same way, which leads to a very consistent and intuitive user experience.
Dynamic Layouts
Not everybody wants or needs to see the same details about opportunities though. Not everybody needs to consume information through the same layouts. That is where dynamic layouts in Engagement Cloud add value. Administrators can define Dynamic Layouts to provide users under certain conditions a different layout from the default layout. The example below shows how:
- Layouts can be different depending on the ‘Record Type’ field i.e. Renewal opportunities can be managed through a different layouts than any other type of opportunities
- Layouts can be different depending on the role of the end user i.e. a channel manager might want to see different information on opportunities than a sales rep or a sales manager
- For more sophisticated conditions, Layouts can be defined that are only used when a condition expressed in Groovy is met i.e. closed opportunities probably require a different layout than open opportunities.
Conclusion
Dynamic layouts allow Engagement Cloud to be tailored to different user roles or cater for multiple use cases without overflowing the layouts with unneeded information. But definitely look into my next blog post as 18C brings new capabilities to create a flexible but consistent and intuitive user experience.
