...

The Update Process

Pulsar follows a standard AppExchange update process. We recommend nothing special other than what Salesforce recommends for their customer base regarding how to install or update AppExchange packages.

Releases

Release Schedule

Pulsar AppExchange Package updates occur on the same schedule as the mobile app release schedule.

Release Types

Pulsar AppExchange Packages only have major releases. We have not had any instances where we needed to release minor or point releases. They are configuration packages and are not very complex by nature.

Release Notes

You can find the release notes here:

1. Previous Release Notes (old)

2. Release Notes (Pulsar SFS)

3. Release Notes (Pulsar App)

Timing

No need to upgrade every time, but a good practice is to update at regular intervals like every year or two. It is entirely under your control. If we require an update of the Pulsar AppExchange Package to deliver a feature within the mobile app, we will include that in the release notes notification.

The backend package (Pulsar Premium) is essentially a way to accommodate configuration settings. It doesn’t change dramatically from release to release. We will include specific notes for Pulsar AppExchange packages in the release notification emails.

Testing

Testing Beta packages in the Salesforce environment is not easy. This is why we include the FSL beta file for testing in our release notes. This is how most of our customers beta test the changes coming in the Pulsar for FSL package.

User Actions After Upgrading

We don’t have any special instructions for users, but it is a good practice for users to perform a quick refresh settings and sync now after an upgrade.

Best practices

We have developed a set of best practices for Pulsar.