Pocket CRM

In this article
    • Pocket version 8 running directly with Netserver must have remote webservices.
    • Pocket client does not support AD authentication.

    There is only one way that Pocket uses AD to authenticate it's user.

    The user's credentials used to get past the login screen (there is no way around that - Pocket doesn't know how to collect the phones AD credentials) must be in SO Admin setup as an AD user. That's it.

    NetServer web service accepts the user's credentials and tries to authenticate the user the only way it knows how - using a chain of authentication resolvers. If the username passed in is a username with an associate id with a matching credential record of type "ActiveDirectory", then the credentials will be authentiated using the AD authentication routines.

    Pocket CRM receives the result of the process and proceeds past the login screen with the authenticated user's principal and credentials ticket intact.


    Enable logging:
    Enable logging in the web.config file like for CRM Web under SuperOffice->Diagnostics->LogToFile


    Appendix A: Netserver configuration - GSM formatted phone numbers

    When initiating phone calls from Pocket CRM it is important that the numbers are formatted in a way that the phone can use. SuperOffice NetServer has the functionality to return all phone numbers from the SuperOffice database in a clean formatted way, without spaces, commas and including country prefix, like this: +4712345678. To enable this feature in NetServer make sure that Web.config contains this element: 

    <add key="AllwaysUseGsmPhoneStyle" value="True" />


    Appendix B: Client configuration - Setting up an e-mail account
    In order to use and be able to send an e-mail within Pocket CRM an e-mail account needs to be configured. This configuration needs to be performed in the SuperOffice 8.x Web Client.


    Appendix C: Admin configuration - Add a Template for incoming images (jpeg)
    Open SuperOffice Admin client and select Lists section -> Lists tab -> double click “Template” and select “+ Add” bottom of the “Lists items”. Add this List item where filename has extension .jpg. The file may be empty, we use the extension to look up the correct template when a new file is saved.


    Appendix D: Admin configuration - Add a Follow-up type for SMS
    Open SuperOffice Admin client and select Lists section -> Lists tab -> double click “Type (Follow-up)” and select “+ Add” bottom of the “Lists items”. Add this List item SMS as type Appointment and direction Outgoing.

    See the admin helpfile for adding list items.


    Appendix E: Data caching
    Pocket saves data that is accessed in a local SQLite database. This is for all data that is shown in the Pocket application, with the exception of documents.

    Data that the user does not have access to is not saved. The data is initially saved forever, but is periodically updated when accessed again.

    All local data is erased if Pocket is reconfigured to a new installation, or if a new user logs in.

    Both iOS and Android have default support for encrypting all content, if a pin code or password is used to lock the device.


    Appendix F: Expose Netserver to Internet
    In order to connect Pocket CRM to Netserver's webservices, Netserver needs to be accessible from Internet. If you have a setup with remote Netserver on internal network and SuperOffice Web in DMZ, that means only Web server part is available on Internet.

    A solution is to use Reverse proxy to make also Netserver available on Internet. 

    Installing second Netserver in DMZ and connecting it via webservices to the remote Netserver on internal LAN is not supported. The Netserver in DMZ will demand direct access to so_arc and Pocket CRM using this setup will fail to save pictures and documents. 


    Appendix G: Custom Pocket configuration URL
    If you want to change the default Pocket CRM configuration URL, you can do so by setting a configuration value of SuperOffice Web in the Web.config.

    The key name is PocketCrmServiceUrl and the value is the new URL for Pocket connection. You'll find this in the <SoFormsAuthentication> - <Pages> section.

    Example: <add key="PocketCrmServiceUrl" value="http://pocket.customer.com/" />

    Please note the template files we use to generate the email with Pocket configuration sent to users use two template variables:

    • {pccu} variable always points to <CRM.web installation>\PocketConfiguration.aspx and is not configurable.
      The reason this is not a direct configuration link for the Pocket client (soprotocol scheme), is that a lot of users experienced problems on Android, where mail clients did not handle the custom protocol link correctly.

      The custom protocol redirect/configuration url that PocketConfiguration.aspx uses, is attempted retrieved from CRM.web installation web.config.

    • {pcvu} variable is used as the display name for the Pocket configuration URL.