Hi,

I've been doing small POC Freshdesk custom app to integrate information from our public facing API to Freshdesk. The eventual app will allow our support agents to check if contacts are authorized from our in-house mini-CRM, but for now, we're just doing a POC to check if its viable.

The POC app is very simple, it should only try to get a message form our public configuration API.

I've had no luck being able to local test this. I've tried the solution you mentioned here:

https://support.freshdesk.com/support/discussions/topics/314311

Unfortunately, in the latest Google Chrome, setting "Load unsafe content" has no effect on this. Please see the attached GIF screencast for a demonstration.

The Chrome version I am trying to test on is: Version 58.0.3029.96 (64-bit)

We have also had no luck local testing libraries being included as assets. As this app may grow in complexity over time, we would like to build it in ES6. We've tried building our app.js using browserify/babel transpiling as suggested here:

https://support.freshdesk.com/support/discussions/topics/315098/page/last

Directly building app.js that way does not work, as it will not pass `frsh validate`. We then tried building our ES6 code as a separate library and sending the built code to assets/, so that our app.js (in ES5) could include that library, where all the logic would live.

We'd prefer building the app that way, as building up everything we need using jQuery would be very long winded.

We also found that was impossible to test locally, due to the same problem with the local test plugin.

We are also required by internal procedures to be able to prove we have unit test coverage for all new code. Testing jQuery interactions is technically possible, but very time consuming, so we would much rather be able to build a third party library based on something like React, which is easier to test, and just include that as an asset.

Further, we are required to cover all business software with automated acceptance tests, to ensure no deployments break any important interactions in our systems. We can use the CodeceptJS framework to control a Chrome instance with your extension pre-installed, but there is no way in that case to automatically enable "Load unsafe content", so even if that did work in the current version of Chrome, it would not be possible for us to use it in our acceptance tests.

So, for this to work, we will need the local testing server to support HTTPS, that way, there will be no need to enable "Load unsafe content" in the browser, and it would benefit everyone by having a more robust and realistic test environment.

Is there any possibility of implementing that change in the local testing server, and what sort of time frame would we be looking at?

We need to develop this app quite urgently for our own business needs. Our developer account is dev@synaq.com, and our Freshdesk instance is synaq.freshdesk.com.

Also, the POC app as it is now is on GitHub for you to test. We've reverted it to ES5 and jQuery only, just to test the Request API for now. As it stands, local testing of that is not possible.

You can view the POC Git repository here:

https://github.com/synaq/freshHello

Please let us know as soon as possible.

Willem Viljoen

SYNAQ