Pulsar Settings Manager

The Pulsar Settings Manager tab exposes various administrative tasks.

Upload/Download

From the Pulsar Settings Manager tab, you can export/import Pulsar Settings for your organization.

Uploading the Pulsar Settings file will not delete newly-added settings (added since the prior download), but uploading will overwrite settings where there is a key+priority match.

We strongly suggest that you download your current settings to save as a backup file prior to importing any new settings.

The processing options will delete all of your existing auto generated Pulsar Settings, with no Undo option. So, before clicking any of the processing options, back up all of your Pulsar Settings. In case any of your settings have issues during processing and do not behave as you intended, you will be able to restore your settings from your backup file.

 

Process ValidationRules and Profiles

If you do not wish to run ValidationRules offline in the Pulsar mobile app, you can safely ignore this section.

Salesforce prevents standard users from querying ValidationRules.  Because the Pulsar app runs with the users' level of permission, Pulsar doesn't automatically have access to these rules.

In order to allow Pulsar to perform validation offline, you as the Salesforce admin need to run a processing step here to expose the data as auto-generated Pulsar Settings.  This processing step needs to be run once (and for every subsequent change) to Validation Rules (and Profiles) for objects specified in the pulsar.sync.objects setting.

  • To run the processing step, first make sure you added the correct endpoint shown to your Remote Site Settings.

  • Click 'Process ValidationRules' button to begin processing.  Note that for some organizations it can take some time to complete...

  • After rules are processed, you will see new auto-generated Pulsar Settings show up with the key prefix pulsar.~auto.ValidationRule.  Profile information will be in the pulsar.~auto.profile.info Pulsar Setting.

  • Please do not directly edit the auto-generated settings.

  • Please see more information about how to configure Validation Rule processing

Process Roll-up Summary Fields

If you do not wish to process Roll-up Summary Fields offline in the Pulsar mobile app, you can safely ignore this section.

Similar to ValidationRules, normal users cannot directly query data for Roll-up Summary Fields.  Perform the pre-processing step here once (and for every subsequent change) to Roll-up Summary Fields for objects specified in the pulsar.sync.objects setting.

  • Click 'Process Roll-up Summary Fields' button to begin processing.  This may take some time to complete...

  • After processing, you will see new auto-generated Pulsar Settings with the key prefix pulsar.~auto.RollupField. – please do not directly edit these

  • Please see more information about how to configure Roll-up Summary Fields processing

Process Custom Labels

If you do not wish to access Custom Labels offline in the Pulsar mobile app, you can safely ignore this section.

Similar to ValidationRules and Roll-up summary fields, normal users cannot directly query Custom Labels.  Perform the pre-processing step here once (and for every subsequent change) to Custom Labels (including translations).

  • Click 'Process Custom Labels' button to begin processing.  This may take some time to complete...

  • After processing, you will see new auto-generated Pulsar Settings with the key prefix pulsar.~auto.CustomLabels. – please do not directly edit these

Process Quick Action Predefined Fields

If you do not wish to run Quick Actions offline in the Pulsar mobile app, you can safely ignore this section.

Similar to both ValidationRules, Roll-up Summary Fields, and Custom Labels, these also need to be pre-processed for use by Pulsar offline.  This step needs to be performed once (and for every subsequent change) to Quick Action Predefined Fields.

  • Click 'Process Quick Action Predefined Fields' to begin

  • After processing, you will see new auto-generated Pulsar Settings with the key prefix pulsar.~auto.QuickActionPredefinedField. -- please do not directly edit these

If you encounter the error "Web service callout failed: WebService returned a SOAP Fault: INSUFFICIENT_ACCESS" ... you will need to enable unrestricted API Access to the PulsarSettings package.  Go to Setup > Installed Packages > click on the PulsarSettings package ... For the API Access field, click Disable Restrictions.

Clear All Auto-generated Pulsar Settings

To clear all auto-generated Pulsar Settings, click the 'Clear Settings' button.