This tutorial teaches you how to write a rulebase and its data model, intended for use as a screening interview. The screening interview rulebase is used to collect additional data that is used to create new records in Oracle CRM On Demand.
The example here highlights the use of the connector to collect new Account record and its corresponding Contact records.
The tutorial contains the following steps:
Map CRM On Demand data model for Insert operation
Write rules against the data model
Define the screen flow for the interview
Embed the Connector to CRM On Demand for Screening Interview
The objective is to map the necessary objects and their fields all with the Insert operation. Ideally we should also map the same objects for Load/Save, needed for pre-seeding; discussed in the latter part of this tutorial.
To map the CRM on Demand data model for the Insert operation, do the following:
We now author the rules that are to be applied to the data model we mapped from the CRM On Demand schema. The rules will simply determine the market potential of an account.
To write rules against the data model, do the following:
We now define the flow of the interview once the rulebase is deployed in Web Determinations. The basic idea is to first conduct an interview to collect all of the required information for the top-level object (Account) then save it (Insert) to CRM On Demand. Once the account record is successfully created - the connector will pre-seed the interview from the new Account record - this is where the Load/Save mapping will come in handy. The interview will then proceed to acquire new records for the child component (Contact).
To define the screen flow for the interview, do the following:
Finally, we need to embed the connector to CRM On Demand via a web applet for the Home page of the Account record type. We need to pass "new" as the caseID to tell the connector that we are going to create a blank session.
Embedded web applet calling CRM On Demand Connector:
Start the interview!
Summary screen containing the first goal:
Collected information for the new Account record:
Save button clicked to insert the new Account record (Note that the caseID has changed to the Account Id since it was mapped as the user key for this object):
Resume the interview by clicking the second goal then promptly inputting the required fields for the new Contact record:
Market Potential is now determined. Saving the current interview session will update the Account record and insert the new Contact records:
Showing the new Account and Contact records collected on the interview: