Last updated on JUNE 01, 2016
Applies to:Siebel SmartScript - Version 7.5.3  and later
Currently, we are developing SmartScripts to collect customer data via a custom eCustomer view (containing the html smart script player applet). Our main problem is this: we are collecting both prospect and prospect attribute data in the SmartScript. The prospect data we can collect just fine in a single page. The prospect attribute data is being stored as an Attribute and associated Value. This requires that the Attribute and Value be collected from the same question.
Since you can only collect one piece of data per question, it seems that we must use VB within the Question Leave event to store the question (as a prospect attribute) and answer (as a Prospect Attribute Value).
However, since we are putting VB on each question, the HTML SmartScript player is breaking up each question as a separate page -> users are only being presented with one question at a time and they must hit the next button after each question, which doesn't work well for collecting a great deal of customer info.
We don't have any branching, and the scripts are straightforward. We need one of the following:
(1) A way of catching the session id under which the SmartScript session is stored in Siebel VB (in script events). That way, we can parse all the data and commit it at once at the end of the script.
(2) Some way of not presenting one question at a time whenever you associate a program event with a question (since our code is NOT modifying the SmartScript flow).
(3) Another way out of this issue....
Any bright ideas? We've thought about storing our data in other tables, but since no other data (other than Prospect Attributes) is brought along using the prospect Promote button, we believe this is not an option.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms