The customers steps to update their Postcode software. Note a check by CallScripter is required before passing these instructions to the customer.
CallScripter staff need to confirm that the Postcode software runs in a separate IIS Application Pool for the below customer advice to be relevant.
- Open IIS
- Under "Sites" expand the relevant CS Site
- Expand the "Executer" folder
- You will see a Postcode folder with a different icon
- Right Click on it and select "Manage Applications" > "Advanced Settings"
- In the "Advanced Settings" popup window check that for the "Application Pool" entry there is an App Pool listed that is not the main CallScripter website one. generally this will be called "Postcode".
If any of the above does not confirm as expected then it is likely the customers CS is not configured in the standard way and so this will need to be escalated for a technical review of their integration.
The below instructions and brief explanation can be passed to the customer assuming the CallScripter Check is all normal:
Before doing these stages please confirm with your Postcode software supplier that no additional steps beyond the Postcode Data files not being in use are required for updating their software/postcode data.
Your CS system runs the postcode elements in a dedicated application pool, meaning it runs independently to the CallScripter system at a processing level.
Stop the applications that are using the postcode so the files are unlocked:
Stop the IIS Application Pool called "Postcode".
Update the Postcode Data files as per your suppliers instructions
Restart the applications that use the postcode:
Start the IIS Application Pool called "Postcode".
After doing this test the postcode via CallScripter. It may take it up to a minute to respond on first use as the postcode files are reloaded by IIS.