Loading
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Synchronization Management Guidelines and Best Practices

            You are here:

            1. Salesforce Help
            2. Docs
            3. Agentforce Life Sciences

            Synchronization Management Guidelines and Best Practices

            To secure data in the Life Sciences Cloud mobile app, manage object sharing and DBSchema records. For optimal performance, always include a WHERE clause in DBSchema settings and monitor the Transactions queue daily. Ensure efficient synchronization by quickly resolving errors and using Simulation Mode to proactively find and fix potential problems before they affect users. Limit record access to necessary users only and keep all required DBSchema settings enabled for the mobile app.

            Required Editions

            Available in: Lightning Experience
            Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package.

            Objects and Security

            Life Sciences Cloud includes several objects preconfigured to download data to the mobile app. Each object has a DBSchema setting that is active and named with the prefix: DbSchema_. These settings are accessible through the Admin Console under the Mobile tile and then Object Metadata Cache Configuration in the left navigation. If you don’t need to transfer data for a certain object, deselect Is Active on the associated DBSchema record.

            To enhance data security, configure the sharing settings for objects regularly synced from the mobile device to Salesforce.

            Daily Monitoring

            Review the Transactions queue daily in the Admin Console to make sure no transactions remain in the New status for more than one day. If transactions for a user remain in the New status for an extended period, contact the user and instruct them to do a full manual sync by selecting Sync Database from the gear icon in the Life Sciences Cloud mobile app.

            Error Handling

            Transaction failures require thorough error analysis. Common causes include record locking, processing timeouts, heap size exceptions, and CPU time limit exceptions. These problems often arise from hitting governor limits due to high loads or nonbulkified code. Validation rules can cause additional errors. Database validation rules differ from UI logic and include field-level uniqueness or non-null constraints. When a transaction encounters an error and remains pending, all subsequent transactions will be placed in the New status.

            Proactively identify potential issues with Simulation Mode. Use Simulation Mode to test transactions in a virtual environment and assess the probability of transaction success or failure. Correct the identified problem and start a new transaction using the Admin Console.

             
            Loading
            Salesforce Help | Article