Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies reply
    1
  • Subscribers subscribers
    11
  • Views views
    108
  • Users 0 members are here
Related
Options

How to capture dynamic value in Truclient protocol

Naresh Ganugu

Hi,

I have scenario where I need to capture dynamic value from the server response in Truclient protocol. We can capture the same via web_reg_save_param in WebHTTP protocol. How the same can be achieved in Truculent protocol?

This is my server response from the rest api call. How can I capture "_id" which is in red below in Truclient protocol. 

[{"status":{"verified":true,"sentCount":1},"_id":"58e00b5f0aac31001185ed24","user":"58e007480aac31001185ecef","text":"When asked if her husband had any hobbies, Mary Todd Lincoln is said to have replied 

Thank you.

  • 0  

    Hi ,

    To my understanding, with TruClient protocol you work on the Browser's document (AUT.window or AUT.document), so TC is at a too high level to capture responses at HTTP level, unless the data that is received somehow finds its way into the DOM. When the API call is bound to an event, you might replace the JS at that event and call the API yourself, but that seems rather advanced.

    However you might execute that API call directly from a JS action in TC and then you have full control over the response.

    Maybe I missed something about TC, and someone else might have nice way to do this.

    How to ask questions

    Reward contributions via likes or 'verified answers'

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.