Change Pocket URL

Hi

If the Pocket CRM URL is made from the Base URL i Pref.

how do I change it, so the mail send from SO web is correct ?

At this Point the Customer have a Internal and external DNS to SuperOffice WEB, 

SuperOffice is working, but the URL in Pocket CRM the customer can send to own email, is the Internal URL, not the External URL ???

-Rune

Base URL

RE: Change Pocket URL

Hi Rune,

This can be changed in the web.config file. Add/change the following section to point to the etter external URL for your site.

<SoFormsAuthentication>

      <Pages>

        <add key="LoginUrl" value="~/Security/Login.aspx" />

        <add key="InternalLogoutUrl" value="~/Security/Logout.aspx" />

        <add key="DefaultUrl" value="~/Default.aspx" />

        <add key="PocketCrmServiceUrl" value="http://pocket.superoffice.com/NetserverPocket/remote/Services80" />

      </Pages>


/Jan

Av: Jan Andersen 15. nov 2016

RE: Change Pocket URL

hey Jan

It looks ok, the url in the mail send

however If I edit the the Hyperlink in #3, the it still points

to the Int Superoffice e.g. http://SuperOffice.Liberty.int/PocketConfiguration.aspx

and not the Ext SuperOffice ?

 

1.....

2....

3.Click this link: http://Superoffice.Liberty.com/Remote/Services80.



Av: Rune Næss Elleskov 16. nov 2016

RE: Change Pocket URL

Hi Rune,

Not sure if I understand what the issue is now..

If you change the URL in the Web.config file to point to the correct URL for your site the Pocket CRM settings in the web client should change as well. If not try a ?flush to see if it updates correctly.

When you click on that link in an email on ayour phone ( must be done on the smartphone) Pocket CRM should configure itself with the new setting.

 

 

Av: Jan Andersen 16. nov 2016

RE: Change Pocket URL

Hi,

The problem is that the mail is generated from a somail-template in SO-ARC

Inside that there is template variable <pccu> that points to:

<RunningHost><InstallFolder>\pocketconfiguration.aspx

The URL is correct by setting it by:
<PocketCrmServiceUrl>

but there are also this key:

<pocketconfiguration> it is under <IgonreList> in web.config
As default it will then not look into:
SoPocketSettingsPage.config  (That can also be manipulated instead of setting PocketCrmServiceUrl) if moving it to <Pages>

Then there is also a javascript involved PocketSettings.js

That fetches a value from:

    ns.initDialog = function () {
        var checkBox = getCheckBox();
        var emailField = getEmailField();
        var link = $.fromSoId("PocketConnectionUrl");
  //var link ="https://pocketcrm.kund.se"
        var duration = 200;

 

I have asked SO support how we can shange the <pccu> variabel in the mail-template. Have aslo tested to add thees keys to web.config with out success

<PocketClientConfigurationUrl>
<PocketConnectionUrl>

/Anders

Av: Anders Larsson 9. des 2016

RE: Change Pocket URL

Actually there are one other varaiable in the template {pcvu}

That is the Service URL...

  <body>
    <p>
      Here is how you connect SuperOffice Pocket CRM to your SuperOffice installation:
    </p>
    <ol>
      <li>Make sure you have installed the SuperOffice app on your device.</li>
      <li>Open this e-mail on your device.</li>
      <li>Click this link: <a href="{pccu}">{pcvu}</a>.</li>
    </ol>
    <p>You will now be redirected to the SuperOffice Pocket CRM logon screen.</p>
 <p>And that's it!
    </p>
  </body>
</html>

Av: Anders Larsson 9. des 2016

RE: Change Pocket URL

Follow up:

the variables {pccu} and {pcvu} used in the mail template for pocket info can not, as it is now, be altered anywhere accordning to SuperOffice Support.

Hardcoding / changing the somail.template with notepad++ with correct URL values for standalone pocketNetserver works.

 

/Anders

Av: Anders Larsson 14. des 2016

RE: Change Pocket URL

The <pccu> variable inside the mail template 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.

Adding the "PocketCrmServiceUrl" property to this web.config file, with a custom value, should work.

Av: Jomar Johansen 14. des 2016

RE: Change Pocket URL

What is the latest update when it comes to this kind of adjustment?

I have a customer case where we are to use a separate NetServer for integrations and Pocket-access.

We' re looking at upgrading to SO 8.4 R08 Onsite from SO 8.4 R02 Onsite.

How much changes in the configuration do I need to do in the latest releases and is there any official documentation for this? Based on this post it seems that there are a bunch of details that aren't handled nicely right out of the box. :)

/Marcus

Av: Marcus Svenningsson 2. apr 2019

RE: Change Pocket URL

Hi

As far as I know there are no changes to this? RND perhaps can clarify?

I would do like this:

Just add the service-url, note that from 8.2 no need to specify netserver-version

Change mail-template so it matches your config

Check pocket configuration in SM-client (QR-code should be updated)

I have also created for some customers a simple html-config page that can be sent to end-users so they just click and it will configure the client. (or add that link in the mail-template)

config url in such page to set new value in pocket

soprotocol:///?netserverUrl=https://pocketcrm.company.se/PocketNS/

Best regards
Anders

Av: Anders Larsson 3. apr 2019

RE: Change Pocket URL

For SuperOffice 8.5R06 link should be:

<SoFormsAuthentication>

      <Pages>

        <add key="LoginUrl" value="~/Security/Login.aspx" />

        <add key="InternalLogoutUrl" value="~/Security/Logout.aspx" />

        <add key="DefaultUrl" value="~/Default.aspx" />

        <add key="PocketCrmServiceUrl" value="http://pocket.superoffice.com/NetserverPocket/remote/Services84" />

      </Pages>

i.e. Services84, otherwise it doesn't recognize it.

The scan of QR is working fine, will check later if the email is with a correct link.

Av: Boyan Yordanov 4. nov 2019