Metadata Checker

Enable the metadata checker to reduce sync time and API calls and, during the mixed synchronization, download only metadata that has been updated. To create the metadata archive:

Collecting Metadata Archive

Metadata archive is created for the whole Salesforce organization, i.e., for General Settings, configured and non-configured profiles.

  1. When some metadata changes, a value in the clm__MetadataLastModifiedDate__c field of the Mobile Application Setup record is updated for the current user profile (or organization if there is no the Mobile Application Setup record for the current user’s profile).

  2. If configured, the metadata archive will be created automatically. Otherwise, it should be manually collected.

  3. The modified metadata archive with actual metadata will be downloaded during the current user’s synchronization.

A metadata archive may not exist, for example, if the metadata checker was not launched before in the Salesforce organization or if the cloud token is invalid. In these cases, the mobile application downloads metadata via the Metadata API using administrator credentials.

To understand metadata download criteria, consider the example with the Salesforce organization. The Mobile Application Setup record exists for General Settings, Profile A, and Profile B.

  1. For Profile A:

    If a value in the clm__MetadataLastModifiedDate__c field has changed on the Mobile Application Setup record for Profile A, the metadata archive is downloaded during mixed synchronization.

  2. For Profile B and C:

    If a value in the clm__MetadataLastModifiedDate__c field has changed on the Mobile Application Setup record for Profile A, mixed synchronization is not applicable.

  3. For Profile C:

    If a value in the clm__MetadataLastModifiedDate__c field has changed on the Mobile Application Setup record for General Settings, the metadata archive is downloaded during mixed synchronization.

  4. For Profile A and B:

    If a value in the clm__MetadataLastModifiedDate__c field has changed on the Mobile Application Setup record for General Settings, the mixed synchronization is not applicable.

To collect the metadata archive, one of the below is necessary:

  • Enable the metadata checker.

  • Customize automatic or manual metadata archiving.

If changes are made in the picklist values, it is necessary to launch manual metadata archiving and then synchronize it.

Enable Metadata Checker

On the Salesforce side, the metadata checker is intended:

To enable metadata checker:

  1. Go to CT Mobile Control Panel: Tools.

  2. Enable Scheduled metadata check.

The metadata checker is enabled.

The system launches Apex class once per hour to track changes in the metadata components.

  • If any metadata component has changed since the previous Apex class launch, the process of the ZIP archive creation will be initialized, and the value in the clm__MetadataLastModifiedDate__c field of the Mobile Application Setup record will be updated.

  • The metadata checker will also be triggered if the changes have been made to reports and dashboards that are added:

    • To the Home screen of the CT Mobile app.

    • If created, in a custom folder that starts with the CLM keyword.

Set up a Schedule For Creating Metadata Archive

It is possible to modify the default schedule of the metadata checker launch. To schedule the metadata archive generating:

  1. Go to the CT Mobile Control Panel: Tools tab.

  2. Disable Scheduled metadata check.

  3. Go to Setup → Custom Code → Apex Classes and click Schedule Apex.

  4. Enter any Job Name.

  5. Find Schedule_LastModifiledDate in the Apex Class field.

  6. Set a schedule.

  7. Click Save.

The schedule is set up.

Manually Create Metadata Archive

To manually create the metadata archive, we recommend using the Refresh metadata archive button on the CT Mobile Control Panel: Tools / CTMobile Control Panel 2.0: Tools tab.

If the metadata checker is disabled or the metadata archive needs to be created off the schedule, manually collect the metadata in the ZIP archive.

The manual metadata archiving is intended:

  • For tracking any changes in metadata components used in the CT Mobile app.

  • For archiving metadata components.

  • For auto-updating a value in the clm__MetadataLastModifiedDate__c field of the Mobile Application Setup records.

To manually archive metadata components:

  1. Go to Setup → Developer Console.

  2. Press CTRL + E to open Execute Anonymous Apex Window.

  3. Enter the code below:

    List<clm__ApplicationSetup__c> listDates = [SELECT id, clm__MetadataLastModifiedDate__c FROM clm__ApplicationSetup__c limit 50000];

for(clm__ApplicationSetup__c aps : listDates){
    aps.clm__MetadataLastModifiedDate__c = null;
}

update listDates;

clm.Schedule_LastModifiledDate.doCalloutFromFuture();

  4. Click Execute.

The process of archive creation is commenced and will be finished in several minutes.

``