<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Return value from injected javascript, give elements to BP and get located elements hWnd in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Return-value-from-injected-javascript-give-elements-to-BP-and/m-p/74889#M27494</link>
    <description>Have the following ideas for enhancements that would be good quality of life changes (at least in my case)

Idea 1:
It would be fantastic if we could get the return value from injected javascript and store it in a data item.
Currently this doesn't seem to be possible, so I have a hacky work around of doing it:

1) Inject javascript
2) Javascript does it's stuff, then creates an element with a particular ID, setting the value to what I need to return
3) Blue Prism does a Read stage against that ID to get it's value

Idea 2:
Allow us to pass in self located elements to Blue Prism in both browser and win32 modes.
For browsers it would be an element reference, likely gotten from the above.
For win32, it would be the hWnd of the control we have found.

Idea 3:
Provide functionality to give the hWnd of any Blue Prism located control, so that it may easily be operated on within our own code stage.</description>
    <pubDate>Tue, 17 Oct 2017 13:15:00 GMT</pubDate>
    <dc:creator>DavidEdwards-Da</dc:creator>
    <dc:date>2017-10-17T13:15:00Z</dc:date>
    <item>
      <title>Return value from injected javascript, give elements to BP and get located elements hWnd</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Return-value-from-injected-javascript-give-elements-to-BP-and/m-p/74889#M27494</link>
      <description>Have the following ideas for enhancements that would be good quality of life changes (at least in my case)

Idea 1:
It would be fantastic if we could get the return value from injected javascript and store it in a data item.
Currently this doesn't seem to be possible, so I have a hacky work around of doing it:

1) Inject javascript
2) Javascript does it's stuff, then creates an element with a particular ID, setting the value to what I need to return
3) Blue Prism does a Read stage against that ID to get it's value

Idea 2:
Allow us to pass in self located elements to Blue Prism in both browser and win32 modes.
For browsers it would be an element reference, likely gotten from the above.
For win32, it would be the hWnd of the control we have found.

Idea 3:
Provide functionality to give the hWnd of any Blue Prism located control, so that it may easily be operated on within our own code stage.</description>
      <pubDate>Tue, 17 Oct 2017 13:15:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Return-value-from-injected-javascript-give-elements-to-BP-and/m-p/74889#M27494</guid>
      <dc:creator>DavidEdwards-Da</dc:creator>
      <dc:date>2017-10-17T13:15:00Z</dc:date>
    </item>
    <item>
      <title>Good ideas David. I had</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Return-value-from-injected-javascript-give-elements-to-BP-and/m-p/74890#M27495</link>
      <description>Good ideas David. I had similar thoughts to your hack #1 as a means to reach data that is difficult/slow to reach via application modeller.</description>
      <pubDate>Tue, 17 Oct 2017 14:54:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Return-value-from-injected-javascript-give-elements-to-BP-and/m-p/74890#M27495</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2017-10-17T14:54:00Z</dc:date>
    </item>
  </channel>
</rss>

