<?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 Measures &amp; Metrics in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Measures-Metrics/m-p/101124#M48191</link>
    <description>Looking for standard industry terminology regarding completed tasks; planned &amp;amp; unplanned exceptions are self-explanatory, but how are folks referring to a successfully &amp;amp; fully completed workitem?&amp;nbsp; 'Clean Path' doesn't seem to work, as I would consider a planned exception to follow clean path.&amp;nbsp; 'Throughput' should measure the aggregate of completed workitems.&amp;nbsp; Is there a standard term in use?</description>
    <pubDate>Wed, 25 Aug 2021 14:46:29 GMT</pubDate>
    <dc:creator>kevincahill</dc:creator>
    <dc:date>2021-08-25T14:46:29Z</dc:date>
    <item>
      <title>Measures &amp; Metrics</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Measures-Metrics/m-p/101124#M48191</link>
      <description>Looking for standard industry terminology regarding completed tasks; planned &amp;amp; unplanned exceptions are self-explanatory, but how are folks referring to a successfully &amp;amp; fully completed workitem?&amp;nbsp; 'Clean Path' doesn't seem to work, as I would consider a planned exception to follow clean path.&amp;nbsp; 'Throughput' should measure the aggregate of completed workitems.&amp;nbsp; Is there a standard term in use?</description>
      <pubDate>Wed, 25 Aug 2021 14:46:29 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Measures-Metrics/m-p/101124#M48191</guid>
      <dc:creator>kevincahill</dc:creator>
      <dc:date>2021-08-25T14:46:29Z</dc:date>
    </item>
    <item>
      <title>Re: Measures &amp; Metrics</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Measures-Metrics/m-p/101125#M48192</link>
      <description>Hello Kevin,&lt;BR /&gt;&lt;BR /&gt;They way I understand it is:&lt;BR /&gt;
&lt;UL&gt;
&lt;LI&gt;Happy Path(Foreseen) - Where the digital worked executed the case end-to-end exactly the way it was intended yielding a successful outcome.&lt;/LI&gt;
&lt;LI&gt;Business Exception (Foreseen) - Where the digital worker encountered a scenario that was deemed out of scope for it to handle and required manual intervention and it successfully identified it and executed the steps for a manual handover.&lt;/LI&gt;
&lt;LI&gt;System Exception (Unforeseen) - Where the digital worked was unable to proceed with the automated steps due to unknown system issues. Could be from the BP platform or from the target applications.&lt;/LI&gt;
&lt;/UL&gt;
Some customers prefer to go deeper on error classification such as Validation errors, internal exceptions etc. but broadly speaking they can all be classified into the above three.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Harpreet</description>
      <pubDate>Thu, 26 Aug 2021 01:42:05 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Measures-Metrics/m-p/101125#M48192</guid>
      <dc:creator>HarpreetKaur</dc:creator>
      <dc:date>2021-08-26T01:42:05Z</dc:date>
    </item>
  </channel>
</rss>

