...
Name | Prompt the user to confirm leaving a custom HTML page. |
---|---|
Key | pulsar.docs.leavePageConfirmation |
Value | <Confirmation message to display when the user tries to leave the page> |
Default Value (if any) | |
Compatibility |
|
Description | By default, a user can click on the Done, Refresh, Back, and Forward buttons on a custom HTML page without restrictions. In some cases, customers may want to ask the user to confirm leaving the page. For example, if the page is setup for data entry, an admin may want to prevent the user from accidentally moving away from the page and losing any unsaved data. |
Notes/Comments |
...
Name | Create/log a Task on sending files from Content Library |
---|---|
Key | pulsar.docs.enableSendLogging |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
Description | If set to TRUE, this will enable a user to create a Task associated with the event of sending files from the Content Library to Contacts or Leads. |
Notes/Comments | NOTE: On Android and Windows there is no explicit way for Pulsar to tell if the files were actually sent or received. |
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. To do this for all HTML documents use the setting without the docId. For example: pulsar.docs.hideNavigation). You can also use it on a per document basis (pulsar.docs.<docID>.hideNavigation). |
Notes/Comments | Be aware: In addition to hiding the navigation buttons when displaying this document, enabling this setting on a content document will result in the addition of query parameters to the URL returned by getContentDocument for this docId. Specifically it will add "?hideNavigation=true" as the query string on the end of the URL. This may affect your custom documents that attempt to pass query parameters to other documents. |
...