Versions Compared

Old Version 22

changes.mady.by.user Jodie Miners

Saved on

compared with

New Version 23

changes.mady.by.user Jodie Miners

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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).

  • Bring your Related Lists out onto separate tabs for different Departments

    • Include field sections for that department only.

    • HOWEVER note that those fields WILL be shown twice on Edit and New IF they are on the Department Tab and the main Tab, and that may be disconcerting to users.

Things to Consider

In Training and whether it is the right time to unleash this to users.

  • Don’t do this too quickly, yes, I am sure the users have been hassling you for this since 2018, or 2020, but if it’s not rolled out well, they will not want to do it for any other objects and then they may lose some excellent benefits. This is especially if you don’t get the Record Type behaviour 100% matching what they have now.

  • For teams that rely on Mobile devices heavily, I would be even extra cautious, and test everything super well before making Dynamic Forms live.

  • What will it look like when you jump from a record with Dynamic Forms to a record without Dyanamic Forms? Will it be too disconcerting for the users?

    • Read Michael’s blog post around consistency of page layouts. I think if the fields are consistently laid out, it could be OK.

  • What will your maintenance overhead be? Is it worth it?

    • No matter what you think, you will have to maintain both Page Layouts and Lightning Pages. There will be something you need that is controlled by Page Layouts. And you do want your Page Layouts to be at least a little consistent with the Lightning Page, and not just dumping everything in the one section.

    • What will be the effect of being “gaslightninged” every single day when you go to the Page Layout and change a field position, or add a button, then go to the Lightning Page and refresh, and take 10 refreshes, and 5 minutes to realise that Oh, this is Dynamic Forms!?

Other Things to Fix whilst you’re at it

...