When developing an application to run on top of the Pulsar Platform, developers have the freedom to use the wealth of web technology available in the mobile app environment. Pulsar has been successfully used with several popular web frameworks, allowing developers to use some of the same code and techniques they have used in more traditional web development. However, there are a few technologies and methodologies that can be used to improve the developer experience while building a Pulsar-based app.
General Recommendations
- Start working with the simple examples on GitHub
- Use Promises for continuations
- Keep things modular -- build one library of API calls in the resources
- Use global resources amapas much as possible. This means sharing common functions in common javascript files.
- In code, use 18 character Ids
- Date format should be a valid Salesforce date format
- When building custom HTML pages, be mindful that using a "Submit" button will generally reload the page by default. This may trigger some of your initialization and setup methods to fire an additional time and prevent some asynchronous calls from completing.
- When working with API responses and Salesforce data, always check types and handle errors.
- When working with data expected to contain JSON, be sure to check whether that JSON has already been parsed. Remember that the data you receive has traversed many layers before your code receives it.
Testing/Test Data
We encourage the use of a Salesforce Sandbox to test your code in the Pulsar environment.
...
One of the first obstacles most developers run into is the difficulty of debugging their code in-place while it is running within the Pulsar app.
Coming in Spring 2020 Pulsar release Beginning with Pulsar 3.8 for Android and Windows, you will be able to use can set up a local development server running on your development machine to rapidly iterate on your code.
Viewing Pulsar Logs
You can add extra email addresses to receive logs from users by adding to the pulsar.logs.email.cc Pulsar Setting
On the Windows platform, you can directly view Pulsar logs at the following directory (e.g., from Windows Explorer):
%HOMEDRIVE%%HOMEPATH%\AppData\Local\Packages\E3D1A000.PulsarforSalesforce_ta6n8xy84gcpg\LocalState\Library\Application Support\- Note that the
AppDatadirectory may itself be hidden from Windows Explorer
Mobile Safari Tips
- In order to have smooth scrolling on iOS Safari, any time you would use CSS
overflow: scroll; --
Make sure to include:-webkit-overflow-scrolling: touch;This will ensure that your scrolling performance is smooth.
...
Some developers don't want to see the default Done button and the navigation elements and want to control this themselves. Pulsar provides configuration settings to achieve this. Use the following settings for this purpose.
| Name | Hide the Done button on the custom HTML Page |
|---|---|
Key | pulsar.docs.hideDoneButton |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | By default, a user can click on the Done button to close the custom HTML page and get back to Pulsar Home Page or a Pulsar record screen. In some cases, customers would like to hide the done button on that page. This setting will let enable that behavior. |
| Notes/Comments |
| Name | Hide HTML Navigation Buttons (Back, Forward, Refresh) |
|---|---|
Key |
|
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | This setting will hide the back, forward, and refresh buttons if this setting is specified and set to TRUE. |
| Notes/Comments |
Generating PDF files offline - Some best practices
...
...
...