Since the introduction of CRMScript triggers in Sales, we have had a system for executing CRMScript from the Web client (Sales). This system has used a special HTTP(s) communication system from the Sales web client to blogic.fcgi in Service. With the introduction of Service entities in the NetServer API (TicketAgent, etc), we established a better communication system between the two stacks using encrypted HTTP(s). The encryption keys have to be present in both web.config for Sales/NetServer and the config file for Service. When installing and upgrading Service OnSite, the user is prompted for these keys and they are verified (but this step can be skipped).
In version 8.5R06, we have rewritten the CRMScript triggers in Sales to use the same communication system as the Service entities, so that we standardize on one way of doing API calls from Sales to Service. As a consequence, you must verify that this communication system is working when upgrading, otherwise CRMScript triggers from Sales will stop working. Specifically, this means:
- Make sure the authentication keys are present, and equal, in all config files (web.config(s) and config)
- Make sure your network topology allows HTTP(s) communication from the NetServer installation to the Service installation. NOTE: Previously, the connections originate from the Web client, now they originate from NetServer.
We believe this change will resolve some issues that have been experienced with the CRMScript triggers. It should also solve problems related to setups with SSO (Windows Authentication under IIS).