...

• Firstly, Clone your Lightning Page that you just finished with.

• Start with the low hanging fruit

  • Sections that don’t need to be there on Closed Won

    • Go back to the old idea of a Closed Case Page Layout and only show things that are needed on Closed records.

  • Sections that don’t need to be there until a Stage is met.

    • Ensure they are still there at every later stage, (unless absolutely not necessary).

      • If you have sequential stages, then create a “helper formula” of IsProposal, that includes the stage of Working and Proposal, or IsNegotiation that contains Working, Proposal and Negotiation.

      • Or use Probability instead (if it 100% tracks with Stage).

      • Or create your own probability style field - Stage Number so you can stay Stage < 4 or Stage > 3. This may be useful where there are the same number of Stages between Record Types, but with different Names.

  • Now, remember you can have a field on the page multiple times. So you might have a field that belongs in a section that is only visible as Stage X, but you could display it in another section if it sometimes gets filled out earlier, and also include it in that Stage section. Especially if you are using Conditional Tabs.

  • Clean up that ugly System fields section.

    • This is the FIRST section to move onto Conditional Tabs.

    • Your users do not ever want to see the Opportunity Name? Sure, move it to another tab.

    • Name the Tab “Settings” or “Structure” or something useful

    • ENSURE YOU KEEP Created Date, Last Modified Date, Owner, Record Type.

      • Removing these breaks “Salesforce” (as in you may as well have any old Database in the cloud).

• Create a Tab for each Document, or Integration. Conditionally display the Tab only when the user would click the button to send the Integration or build the Document.

  • Include every field on that page that is in the Document or sent over to Integration.

  • Often these are fields that are not visible on the page layout.

  • Include them in the order they are in the document. This is actually a good use of single column fields.

  • Make them editable still.

  • Include fields from other records using Related Records or Dynamic Lists

    • Unfortunately Opportunity Contact Roles are NOT available in Dynamic Lists

  • The user can then quickly scan down the fields to see what is missing on the document or in the integration, and edit it then and there before clicking the button.

  • For bonus points find a way to add the button to the Tab (see above).

Questions

• Do Narrow Columns on pinned pages still show non compact layout. ?

Good Things

I can’t say when these good things happened since I haven’t looked for them in every single release because there was no way I was putting this much effort in without blank spaces and aligned field sections.

...