To ensure extra steps only appear when creating open house records for condominiums, an administrator can use two methods: create two page layouts; and use business processes and record types to display appropriate picklist values. A page layout is a feature that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. An administrator can create two page layouts for open house records - one for houses and one for condominiums - and include different fields or sections for each page layout based on their requirements. A business process is a feature that allows administrators to define and enforce stages that records must go through based on their record type such as lead status or opportunity stage. A record type is a feature that allows administrators to offer different business processes, picklist values, page layouts etc., to different users based on their profile or role. An administrator can create two record types for open house records - one for houses and one for condominiums - and assign different business processes and picklist values for each record type based on their requirements. Reference: https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm&type=5

Setup audit trail is a tool that allows administrators to review recent configuration changes made in their org. It shows a list of up to 180 days of setup changes made by anyone in the org, including the date, time, user, and type of change. It can help administrators track who made what changes and when, and troubleshoot any issues caused by configuration changes. Critical updates are notifications that inform administrators of new features or enhancements that may impact their org; they do not show configuration changes made by users. Debug logs are records of database operations, system processes, and errors that occur when executing a transaction or running unit tests; they do not show configuration changes made by users either. Field history tracking is a feature that allows administrators to track changes to the values of certain fields on records; it does not show configuration changes made in setup. Reference: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm&type=5

Contacts to multiple accounts is a feature that allows you to associate a single contact with multiple accounts, both business and person accounts. This way, you can maintain the historical accuracy of the contact record without creating duplicate records for each account. Reference: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.htm&type=5

To capture the expiration date of warranty based on installation date and warranty length (1 year by default), the administrator should use a formula as the default value of Warranty Expiration Date field on Installation object. The formula can calculate one year from installation date using DATE function or DATEVALUE function. For example, DATE(YEAR(Installation_Date__c) + 1 , MONTH(Installation_Date__c) , DAY(Installation_Date__c)) will return one year from installation date. Creating a formula field, adding a validation rule, or including Warranty Expiration Date field on mobile page layout will not capture expiration date based on installation date and warranty length. Reference: https://help.salesforce.com/s/articleView?id=sf.formula_using_date_datetime.htm&type=5

Utility bar is a feature that is available in a Lightning app where visibility is limited to the Salesforce mobile app. Utility bar allows users to access common productivity tools, such as notes, history, recent items, and more, from any page in the app. Reference: https://help.salesforce.com/s/articleView?id=sf.app_builder_utility_bar.htm&type=5