<?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 RE: BP Process Exposure against VM (resource) pools in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/BP-Process-Exposure-against-VM-resource-pools/m-p/59541#M13167</link>
    <description>&lt;P&gt;Hi Lukas,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;To run an exposed Process against a Resource Pool, you just have to direct the request to the designated Pool Controller -- we have a Knowledge Base article about how to do this here: &lt;A href="https://support.blueprism.com/en/support/solutions/articles/7000078336-how-can-i-run-a-process-which-has-been-exposed-as-a-web-service-against-a-resource-pool-" target="_blank" rel="noopener"&gt;https://support.blueprism.com/en/support/solutions/articles/7000078336-how-can-i-run-a-process-which-has-been-exposed-as-a-web-service-against-a-resource-pool-&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Steve Boggs&lt;BR /&gt;Senior Product Support Engineer&lt;BR /&gt;Blue Prism&lt;BR /&gt;Austin, TX&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Mon, 17 Jul 2023 14:27:00 GMT</pubDate>
    <dc:creator>steven.boggs</dc:creator>
    <dc:date>2023-07-17T14:27:00Z</dc:date>
    <item>
      <title>BP Process Exposure against VM (resource) pools</title>
      <link>https://community.blueprism.com/t5/Product-Forum/BP-Process-Exposure-against-VM-resource-pools/m-p/59540#M13166</link>
      <description>&lt;P&gt;Hello, community,&lt;/P&gt;
&lt;P&gt;Has anyone deployed a solution where Blue Prism process is exposed as Web-Service against Resource Pool but not a single exact resource?&lt;/P&gt;
&lt;P&gt;BP 7.1.1 in use with full on-prem deployment.&lt;/P&gt;
&lt;P&gt;Chorus, Hub, API etc. solutions do not fit to current architectural setup and can't be used, thus solution in scope should be designed in BP on-prem only.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Lukas Ramasauskas&lt;BR /&gt;RPA Software Engineer / Robotic Solutions Architect&lt;BR /&gt;Swedbank AB&lt;BR /&gt;Europe/Vilnius&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Jul 2023 13:22:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/BP-Process-Exposure-against-VM-resource-pools/m-p/59540#M13166</guid>
      <dc:creator>LukasRamasauskas</dc:creator>
      <dc:date>2023-07-14T13:22:00Z</dc:date>
    </item>
    <item>
      <title>RE: BP Process Exposure against VM (resource) pools</title>
      <link>https://community.blueprism.com/t5/Product-Forum/BP-Process-Exposure-against-VM-resource-pools/m-p/59541#M13167</link>
      <description>&lt;P&gt;Hi Lukas,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;To run an exposed Process against a Resource Pool, you just have to direct the request to the designated Pool Controller -- we have a Knowledge Base article about how to do this here: &lt;A href="https://support.blueprism.com/en/support/solutions/articles/7000078336-how-can-i-run-a-process-which-has-been-exposed-as-a-web-service-against-a-resource-pool-" target="_blank" rel="noopener"&gt;https://support.blueprism.com/en/support/solutions/articles/7000078336-how-can-i-run-a-process-which-has-been-exposed-as-a-web-service-against-a-resource-pool-&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Steve Boggs&lt;BR /&gt;Senior Product Support Engineer&lt;BR /&gt;Blue Prism&lt;BR /&gt;Austin, TX&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Jul 2023 14:27:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/BP-Process-Exposure-against-VM-resource-pools/m-p/59541#M13167</guid>
      <dc:creator>steven.boggs</dc:creator>
      <dc:date>2023-07-17T14:27:00Z</dc:date>
    </item>
  </channel>
</rss>

