Anyway, the best part of the process is that the storage of the connection details happens in the Hub – so it is much easier to manage access to it. Here is an example showing the Hub, and the new (secure!) options that include custom root certificate (which you would need to have in the Hub certificate list, or client certificate. We can also use Basic Authentication.
Notice the Health Check URL above, which is not required but is used to provide a ping address if your service supports it. If it does not, you will see this warning everywhere:
Another side effect of this 20D New Feature, with it’s Hub-managed world is that you will need to Deploy the Interview to be able to test it properly. Once the Connection is set up, the extension code can call the external service, using the new fetch() method on the interview object. After that, it’s up to the developer to decide what to do with it.
For example, here is some code to call a Covid 19 database using this 20D New Feature:
Note in the example above, the Connection on the Hub is referenced in the options object which also contains other information about how to call your Service, including relativeUri which is useful to append to the root Uri of the Connection. Be aware that should you make mistakes in this, they will appear in the Hub Message Log:
Finally, if you have deployed the Interview, you can expect to see the results in the browser instance :
The code is tidier, the management of the connection is better, in fact this is an all-round improvement from the hackathon techniques used previously. Good Job team!
Also in this release 20D:
The Deployment REST API includes the ability to retrieve object mapping data from the deployment.
Deployment statistics – charts now show the combined data for all versions of the deployment by default, instead of only showing the data for the active version. This improves the default experience – see view deployment-specific statistics
Finally through a new configuration parameter db_message_log_filter (on premise) or a new SR to request a change (cloud) you can get rid of all those validation warnings (OPA-VAL-001) from the Message Log that are caused by minor irritations such as missing field data in a Connector exchange. You can find out more here.