Here at Decisions, we often show potential customers a Musical Instrument Insurance demonstration project, which covers many facets of the product. This repository illustrates how Decisions can be used as a back end for any other UI client.
The goal of this project is simply to illustrate how a UI hosted anywhere could interact with Decisions as a back-end resource. As such it demonstrates running flows and rules via API call, and one way to authenticate those calls.
This project was created using create-react-app, and because we use TypeScript internally, uses TypeScript. Because it's a fairly trivial app, there are no state management libraries involved and is mostly vanilla React, with the exception of React Router.
This project was not configured to run Cross Domain, but has some example hooks for doing so. However, the Decisions web host will need to be configured to accept remote origin requests by modifying the web.config file.
To do so add the following to <decisions install>\Decisions Web Host\web.config in the <system.webserver> section:
<httpProtocol>
<customHeaders>
<add name="Access-Control-Allow-Origin" value="*"/>
<add name="Access-Control-Allow-Methods" value="GET,PUT,POST,DELETE,OPTIONS"/>
<add name="Access-Control-Allow-Headers" value="Content-Type"/>
</customHeaders>
</httpProtocol>This Demo uses React Router, which rewrites URLs and requires subsequent URLs
to be forwarded to the index.html of this little app via the web.config. This would be true for any client-side routing an embedded UI might need.
The other not-so-obvious requirement is an additional IIS URL Rewrite extension. Make sure to download the version that matches your processor architecture. A more detailed explanation can be found here.
None of this is IIS configuration is necessary if your UI is hosted elsewhere.
- Clean up for best practices.