Overview

Adding new components to layouts within the amplo managed package requires a few considerations before you start. Before you start, make sure you're familiar with the following Salesforce concepts:

• Page Layouts

• Lightning Pages

• Deciding When to Use Lightning App Builder or the Page Layout Builder

You'll also want to know where your component should display. Consider the following:

• What object should this component appear on?

• Are there specific record types the component should be associated with?

• Should specific personas have access to this component?

Visibility is controlled through page layouts and component visibility within the lightning page itself. Expand the menu to learn more:

Page layouts

Objects can have multiple page layouts that display information based on context.

For example, the Account object has eight default layouts assigned based on profiles and record types.

Component visibility

Next, review the component visibility settings on the Lightning Page. In the Lightning App Builder, an Account page has five configurations based on account type:

1. Record > Account Record Type > Name Contains Customer

2. Record > Account Record Type > Name Contains Vendor

3. Record > Account Record Type > Name Contains Prospect

4. Record > Account Record Type > Name Contains Carrier

5. Record > Account Record Type > Name Contains Employee

Add or confirm the component is on the page layout

1. Click the gear icon and select Setup.

   

2. In Quick Find, search and select Object Manager.

   

3. Select the object where you want to add the component.

   

4. Then, click on Page Layouts.

   

5. Find the page layout where you want to add the component.

6. Confirm the component you wish to add is available, then drag and drop it into the desired section.

   

7. If you made any changes, click Save.

   

Configure the Lightning App page

1. Navigate to a record where you would like to see the new component.

2. Click the gear icon and select Edit Page.

3. Find the component(s) you wish to add in the left hand panel, and drag it onto the page where you wish to see it.

   

4. Save.

   

Adding a related list

Schedules related lists on policies

By default, the Policy object displays Schedules using a managed-package component with non-configurable fields. Follow the steps below to add a standard Schedule related list that allows field customization.

Determine if you will be adding Schedules on a commercial or personal lines policy.

1. Click the gear icon and select Edit Page.

2. Select Related Lists.

   

3. Drag and drop Schedules into the Related Lists.

   

4. Select Save.

   

5. Select Lightening Record Pages.

   

6. Select the page you want to edit.

   

7. Then, select Edit.

   

8. Select the Schedules tab.

   

9. Use the Search to find Related List- Single.

   

10. Then, drag and drop Related List - Single under the Additional Interest component.

    

11. In the Related List dropdown, search and select Schedules.

    

12. Under Set Component Visibility, select Add Filter.

    

13. Select Advanced under Filter Type.

    

14. Click on Select under Field.

    

15. In the Select field modal, select the following:

    1. Record

    2. Record Type

    3. Record Type Name

    4. Then, click Done.

       

16. In the Value field, enter:

    1. CL (for commercial lines)

    2. PL (for personal lines)

       

17. Then, select Done.

    

18. Click Save.

    

    1. Drag "Related List - Single" under the Schedules component.

       1. On the right side, change the Related List to "Schedules".

       2. Click "Upgrade Now" in the Dynamic Related List box.

       3. Scroll down and add the additional fields.

19. Add the component visibility filter.

Troubleshooting

If you encounter issues with this setup:

• Related list shows deleted schedules: Ensure you've added the "Schedule Junction equals 1" filter to exclude vehicles that are no longer associated with the policy.

• Related list not visible: Check that you've properly configured the component visibility filters and that the user has appropriate permissions.