Skip to main content
Getting started with the Lightning Page view

Guidance on how to use our Lightning Page view to improve the deployments of Lightning page components.

Sam Youatt avatar
Written by Sam Youatt
Updated over 3 months ago

What license do I need to use this feature?

You'll need a Deployment Starter, Teams, or Enterprise license to use the Lightning Page view.

It's often difficult to understand the changes in your Lightning Pages when viewing the XML. Due to the way the Lightning Pages are structured in the XML it can also be tricky to ensure that you have all the changes you need when performing precision selections in Gearset.

Gearset's Lightning Page view makes it easy to see where the changes are, with a familiar view of your record page, and simplifies the process of making precision selections.
โ€‹
You can select the new view on any Lightning record pages.

Understanding your Lightning Page

Gearset's Lightning Page view displays your Lightning Page in a way that is familiar to using the Lightning App builder.

The Lightning App builder in Salesforce


Preview of the Lightning page in our comparison results:

The Lightning Page view in Gearset

Properties

Certain items in Salesforce have additional properties that allow for customisation of their behaviour. Clicking on any item in the Gearset Lightning Page view will reveal information about those properties.

Viewing the properties of this highlights panel

Gearset will display any changes in those properties as well as making them available for precision deployments.

This changed property is available for precision selection

Visibility rules

More complex Lightning Pages will have visibility conditions set up to control what information is shown on the page under a number of conditions.

Gearset will indicate which items have visibility rules and clicking on any item will display more details about those conditions.

Gearset is indicating that this path component has a visibility rule configured

Clicking on the path item will reveal information about the visibility rule

Gearset will also indicate if there is a new rule, deleted rule, or changes to an existing rule.

This field section has a new visibility rule

Using the mini-map

The mini-map is designed to help you navigate around the different regions that make up your Lightning Page.

The mini-map shows that the header and main regions are currently being viewed

The mini-map shows regions as they appear on your Lightning Page in Salesforce, which depends on which template you've selected. The regions are highlighted in blue when they are visible in the Lightning Page view to the right.

If you click on a region on the mini-map, you'll be taken to the corresponding region on the right.

Precision Deployments

Gearset understands which changes in the XML correspond to changes in the Lightning Page and are required in order for the deployment to succeed.

The Lightning Page view makes it easier to select these changes than the XML view.

Selecting all the XML changes that were required for a new Field Section would previously have been error prone. It would have required searching for identifiers and making a wide range of selections - missing any of these would have likely resulted in a deployment failure.

With the Lightning Page view it only takes one click to select a new Field Section and all its included fields. This greatly reduces the chances of deployments succeeding while still giving control over what items you may not want to include in a deployment.

Only one click is required to include the new field section and all of its records

Gearset still offers control over more fine grained selections. Property and visibility changes can be selected independently of one another, for cases when certain work may be ready but others are not ready for deployment yet.

The change to the tab title has been chosen for this deployment but the new visibility rule has been left out

Precision selections using the XML view

The release of the Lightning Page view will not affect the behaviour of the XML view that you may be used to.

However, it should be noted that once precision selections have been made in the Lightning Page view, changes to those selections in the XML view should be made with caution.

The new Lightning Page view aims to make precision selections easier, and if care is not taken, you may reduce the chances of deployment success by changing the selections in the XML view.

Did this answer your question?