Financial-Services-Cloud Exam Dumps : Salesforce Financial Services Cloud (FSC) Accredited Professional (AP) Exam (SU24)

Record alerts are a feature of Financial Services Cloud that let users create and display alerts on record pages to highlight important information or actions. Record alerts are based on OmniStudio, a low-code platform for building digital experiences in Salesforce. To access or extend permissions for record alerts in Financial Services Cloud, users need to have one of the following permission sets:

• FSC Standard permission set: This permission set grants access to the core features of Financial Services Cloud, including record alerts. Users with this permission set can view and create record alerts on supported objects, such as accounts, contacts, financial accounts, and opportunities1.
• FSC Foundations permission set: This permission set grants access to the common features of Financial Services Cloud that are shared across subverticals, such as retail banking, wealth management, and insurance. Users with this permission set can view and create record alerts on supported objects2.
• OmniStudio User permission set: This permission set grants access to the OmniStudio features, such as OmniScripts, DataRaptors, Integration Procedures, and Record Alerts. Users with this permission set can view and create record alerts on any object that has the Record Alert component enabled3.

References:

• FSC Standard Permission Set
• FSC Foundations Permission Set
• OmniStudio User Permission Set

The order of uploading Salesforce objects during an FSC data migration is important to ensure data integrity and avoid errors. The recommended order is:

• Accounts and contacts: These are the core objects that store the basic information about the customers and their relationships. They should be uploaded first to establish the foundation for the FSC data model4.
• Financial accounts: These are the custom objects that store the financial information about the customers, such as balances, interest rates, fees, and transactions. They should be uploaded after the accounts and contacts, and linked to them using lookup fields5.
• Account groups and households: These are the custom objects that group the accounts and contacts based on common attributes or relationships, such as family members or business partners. They should be uploaded after the financial accounts, and linked to them using junction objects6.

References:

• Financial Services Cloud Data Model
• Data Migration Best Practices
• Accounts and Contacts
• Financial Accounts
• Account Groups and Households