Policy Automation for B2C Service

Get Involved. Join the Conversation.

Topic

    albert hua
    how to pass Contact data into application with embedded...
    Topic posted May 16, 2018 by albert huaRed Ribbon: 250+ Points 
    122 Views, 2 Comments
    Title:
    how to pass Contact data into application with embedded interview
    Content:

    Hi there,

    We use a login widget to redirect to an application called Form2 page in which we embedded an interview “FutureLearn_tst” using <div>:

    <div style="display: inline-block; width:100%">

        <div id="future_learn" style="width: 100%; display: block; margin-left: auto; margin-right:auto; float: left"></div>

    </div>

    <script>

        var el = document.getElementById("future_learn");

        var webDeterminationsUrl = "https://murdoch-opa--tst1.custhelp.com/web-determinations";

        var deploymentName = "FutureLearn_tst";

        function doRedirect(){

                    window.location = "http://www.murdoch.edu.au";

        }

        OraclePolicyAutomationEmbedded.StartInterview(el, webDeterminationsUrl, deploymentName, undefined, undefined, undefined, undefined, undefined, doRedirect);

    </script>

    Right now we would want to retrieve some user information such as surname/firstname from DB based on user’s login, so that those data can be pre-populated in the embedded interview column. 

    Is this going to be possible?

    Many thanks,

    Albert

    Version:
    2017

    Comment

     

    • Scott Berry

      The new version of the OPA Widget shipping in 18B uses a new version of the embedded interview API which has additions to make the embedding on Service Cloud simple and as easy as the previous widget (all the same parameters!).

      Using the embedding API with a web-determinations pre-18B you may experience some rendering issues as discussed through the new documentation, which is why we hadn't shipped a new version of the widget yet which used the existing API.

      I would start by taking a look at the code in the new V3 1.3 OPA Widget but remember it uses a different API call which doesn't exist pre-18B  (but you could try it out in an 18B test environment). You could modify the code from the 18B widget I linked which uses the new 18B API (OraclePolicyAutomationInterview) to pre-18B (OraclePolicyAutomationEmbedded) but be aware that we hadn't released the widget using that old API because the embedding page's CSS could (definitely did on some Service Cloud pages) affect some of the interview elements.

      'Contact Data' should be mapped between Service Cloud fields to interview attributes within OPM, but the API needs to pass Contact credentials to allow this data seeding to occur between Service Cloud and the deployed interview on OPA. The new example widget demonstrates this.

    • Pedro Viglione

      hello Albert

      There is another, more rustic way to do it.

      Just include surname and first name as named attributes and include them in the url call.

      Then in the OPA interview seed them from de URL


      As I said before is a quite primitive method but it works