About the Physical Renderer

Oracle Intelligent Advisor provides the Javascript file opaprenderer.js, which is a generic physical renderer for embedded interviews. All applets that render embedded interviews must use this physical renderer. The physical renderer contains the implementation for starting and resuming interviews, as well as logic to send the integration mapping parameters to Intelligent Advisor. The physical renderer also contains the logic to create the application record for the Screen for Services and Apply for Benefits use case scenarios for Siebel Public Sector Self Service.

The physical renderer uses the following Javascript APIs for starting and resuming the interview. For more information about these APIs, see Oracle Intelligent Advisor documentation.

• OraclePolicyAutomationEmbedded.StartInterview. This API is used to start the interview.

• OraclePolicyAutomationEmbedded.ResumeInterview. This API is used to resume the interview.

Integration parameters are sent to Intelligent Advisor based on the definition of the OIAParamMapping integration mapping parameter, which is described later in this chapter.

You must create manifest entries for all of the applets that display Intelligent Advisor interview content. This task is described later in this chapter.

Custom styling files are packaged with sample policy models (rulebases) and can be accessed from the rulebase project in Oracle Policy Modeling. You can optionally use these files to provide the Siebel CRM application look and feel to interview controls. The files are:

• siebelcustom.css. This style sheet file contains all of the styling rules specific to Siebel CRM.
• siebelcustom.js. This Javascript file applies custom styling to Intelligent Advisor controls.