Sales

Get Involved. Join the Conversation.

Topic

    Matias Buonavolonta
    Invoke Engagement via URL (GET Method)Answered
    Topic posted January 29, 2019 by Matias BuonavolontaBronze Medal: 1,250+ Points, tagged Architecture, Configuration, Core SFA, Groovy, Industry Solutions, Integration, PaaS/SaaS, Security, Workflow 
    133 Views, 11 Comments
    Title:
    Invoke Engagement via URL (GET Method)
    Summary:
    Contextualize in an Account via URL and add logic in case it does not exist
    Content:

    Hi All,

    I need to be able to call Engagement via URL (GET Method) and contextualize in an Account Summary.

    I tried the DeepLink function but if the Account does not exist the screen remains blank. I need that if the Acount does not exist this same invocation believes it as new.

    Do you know if there is any functionality or customization to do this?

    Thanks in advance!

    Regards.

    Version:
    18B

    Best Comment

    Matias Buonavolonta

    Hi all,

    With my technical team we found a WA for this integration and I want to share. It is based on the following sequence of development:
    1) We create an HTML with JS that can receive parameters via GET and store them in variables.
    2) We consume an OEC API to validate if the Account exists.
    3) If the account exists, we obtain the ID and set up a "DeepLink" style url to navigate to the Account Summary and perform a HREF.Location to replace the html url.
    4) If the account does NOT exist, we consume an OEC API to create the account, obtain the ID and set up a "DeepLink" style url to navigate to the Account Summary and make a HREF.Location to replace the html url.

    We upload the HTML file through File Import and get the invocation URL.

    To that url we add the parameters from the source system.

    In summary, the HTML works as a Listener of an event and based on that process the transaction.

    I hope it is useful for you if it is presented to you in the future.

    Regards.

    Comment

     

    • Reghu

      So if the Account doesn't exist, you need to show create account page?

      • Matias Buonavolonta

        Hi Reghu,

        In that case, I need that:
        1) Take the values of the parameters sent via URL GET.
        2) Create a new Account.
        3) Contextualize in Account Summary to the user.

        Thanks, Regards.

         

         

    • Reghu

      So do you mean to create new Account incase the Account is not found using the same parameters used on the GET method?  

    • Reghu

      I am not sure of the entire context.. But let me try to comprehend from the transcripts here

      You want to display Account page from within OEC object

      So you have kept a deep link to Account in that OEC object page.  Since the URL will always look for the Account identifier, incase the account is not present you get  a blank page.

      But you want to create a new account and show that new account page.  

      if the answer is yes, Before evaluating the URL for the link, do a check whether the Account is there in the system, if not, create the account and evaluate the URL with new Account's identifier. 

      Please correct if I have missed something here.

       

    • Reghu

      I think you missed my suggestion in the previous update.  Could you try this and let me know?  (if not done already)

       

      " Before evaluating the URL for the link, do a check whether the Account is there in the system, if not, create the account and evaluate the URL with new Account's identifier. "

      • Matias Buonavolonta
        Hi Reghu, I had not understood that it was a question. It would be ideal to be able to do that but the origin application is telephony for outgoing calls with little modification capacity ... This App only has the possibility of opening a browser with a url with parameters and dynamic values. Thanks.
    • Matias Buonavolonta

      Hi all,

      With my technical team we found a WA for this integration and I want to share. It is based on the following sequence of development:
      1) We create an HTML with JS that can receive parameters via GET and store them in variables.
      2) We consume an OEC API to validate if the Account exists.
      3) If the account exists, we obtain the ID and set up a "DeepLink" style url to navigate to the Account Summary and perform a HREF.Location to replace the html url.
      4) If the account does NOT exist, we consume an OEC API to create the account, obtain the ID and set up a "DeepLink" style url to navigate to the Account Summary and make a HREF.Location to replace the html url.

      We upload the HTML file through File Import and get the invocation URL.

      To that url we add the parameters from the source system.

      In summary, the HTML works as a Listener of an event and based on that process the transaction.

      I hope it is useful for you if it is presented to you in the future.

      Regards.

    • Reghu

      where is this HTML hosted?