Automatic Code Refresh in the Browser

By default you are required to manually update your client resources each time you make a code change.

However, you can specify a folder location on the computer hosting FICO ^® Xpress Insight server as a place for a particular app to get its client resources from. This is an optional element that can be added to the companion file as follows:

<client>
  <view-group title="Main">
    <html-view title="Welcome" path="welcome.html"/>
  </view-group>
  <client-resources-local-path>C:\dev\example-app\client-resources</client-resources-local-path>
</client>

To configure the Xpress Insight server to use local paths to client resources, when specified, edit the following file:

<installdir>\insight\server\wildfly-x.y.z\bin\standalone.conf.bat

Add the following line anywhere in the file:

set INSIGHT_SERVER_MODE=development

You will need to restart the Xpress Insight server for this change to take effect.

Once the server is restarted, and the browser is showing a view in development then a query parameter needs to be added:

?debug=true

This needs to be inserted into the browser URL after insight/ and before the string of characters that begins with the hash symbol #.

For instance:

http://localhost:8860/insight/?debug=true#...

This enables you to see local changes with only a browser refresh.

If theXpress Insight server is not set to run in development mode, then the <client-resources-local-path/> element will be ignored and client resources will be served from the uploaded app bundle as normal. However, if you are running the Xpress Insight server in development mode and the local path does not contain the requested client resource, you will get 404: page not found errors.

When distributing a copy of your app, remove the <client-resources-local-path/> element from the companion file as it may cause unexpected behavior in a demo or production environments.

Contents

Index

Glossary

Search Results

Automatic Code Refresh in the Browser