There are three parts to this example:
- A very simple rulebase with a single base-level attribute and a single input screen for that attribute
- A custom screen plugin which replaces the Web Determinations screen for the attribute by a call out to an external application
- A simple external application.
The flow of the application is:
- User starts an investigation
- User encounters the custom screen, which redirects the user's browser to the external application for input
- The external application redirects the browser back to the custom screen, which integrates input from that application
- Flow continues normally
To see this example in action, you must have a Java enterprise server such as Tomcat available:
- Compile the custom screen plugin to a jar file (or use the precompiled .jar included)
- Add the plugin jar to the deployed Oracle Web Determinations WEB-INF/classes/plugins directory
- Deploy the test external application to the same server.
- Point your web browser to <server address>/web-determinations/startsession/TestCustomScreen