<?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 Blue Prism 7.1 - Bug in field for action description in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Blue-Prism-7-1-Bug-in-field-for-action-description/m-p/56498#M10672</link>
    <description>&lt;P&gt;Hi guys,&lt;BR /&gt;&lt;BR /&gt;we are preparing our Environment for upgrade to BP 7.1. and I noticed one issue which is not mentioned in Known Issues yet.&lt;BR /&gt;&lt;BR /&gt;The bug is in description field for an action.&lt;BR /&gt;If an action's description field contains a &lt;STRONG&gt;curly brace&lt;/STRONG&gt; inside '&lt;STRONG&gt;{ }&lt;/STRONG&gt;', the whole object and actions inside becomes &lt;STRONG&gt;unavailable for all processes&lt;/STRONG&gt; and cannot be chosen form the list. For existing actions - when you double click it in a process, following message appears: 'Invalid Object: &amp;lt;object name&amp;gt;' and it's disappearing from object/action picker. But when you select it and choose 'View action in Object Studio', will successfully open the object, besides the error.&lt;BR /&gt;When you force to execute an action from the object, exception message is as follow:&lt;BR /&gt;Internal : The object '&amp;lt;object name&amp;gt;' is not valid. The last error message recorded was: Input string was not in a correct format.&lt;BR /&gt;&lt;BR /&gt;Adding a single character can make a lot of mess in production environment, especially when the object is commonly used by processes.&lt;BR /&gt;&lt;BR /&gt;We will upgrade from BP 6.6 and we didn't noticed in current version any problems with special characters in descriptions fields.&lt;BR /&gt;&lt;BR /&gt;As workaround, descriptions have to adjusted and curly braces removed.&lt;BR /&gt;&lt;BR /&gt;Best,&lt;BR /&gt;Ł&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Łukasz Kiciak&lt;BR /&gt;RPA Developer&lt;BR /&gt;UI&lt;BR /&gt;Europe/London&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Mon, 15 Aug 2022 14:21:00 GMT</pubDate>
    <dc:creator>l.kiciak</dc:creator>
    <dc:date>2022-08-15T14:21:00Z</dc:date>
    <item>
      <title>Blue Prism 7.1 - Bug in field for action description</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Blue-Prism-7-1-Bug-in-field-for-action-description/m-p/56498#M10672</link>
      <description>&lt;P&gt;Hi guys,&lt;BR /&gt;&lt;BR /&gt;we are preparing our Environment for upgrade to BP 7.1. and I noticed one issue which is not mentioned in Known Issues yet.&lt;BR /&gt;&lt;BR /&gt;The bug is in description field for an action.&lt;BR /&gt;If an action's description field contains a &lt;STRONG&gt;curly brace&lt;/STRONG&gt; inside '&lt;STRONG&gt;{ }&lt;/STRONG&gt;', the whole object and actions inside becomes &lt;STRONG&gt;unavailable for all processes&lt;/STRONG&gt; and cannot be chosen form the list. For existing actions - when you double click it in a process, following message appears: 'Invalid Object: &amp;lt;object name&amp;gt;' and it's disappearing from object/action picker. But when you select it and choose 'View action in Object Studio', will successfully open the object, besides the error.&lt;BR /&gt;When you force to execute an action from the object, exception message is as follow:&lt;BR /&gt;Internal : The object '&amp;lt;object name&amp;gt;' is not valid. The last error message recorded was: Input string was not in a correct format.&lt;BR /&gt;&lt;BR /&gt;Adding a single character can make a lot of mess in production environment, especially when the object is commonly used by processes.&lt;BR /&gt;&lt;BR /&gt;We will upgrade from BP 6.6 and we didn't noticed in current version any problems with special characters in descriptions fields.&lt;BR /&gt;&lt;BR /&gt;As workaround, descriptions have to adjusted and curly braces removed.&lt;BR /&gt;&lt;BR /&gt;Best,&lt;BR /&gt;Ł&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Łukasz Kiciak&lt;BR /&gt;RPA Developer&lt;BR /&gt;UI&lt;BR /&gt;Europe/London&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Aug 2022 14:21:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Blue-Prism-7-1-Bug-in-field-for-action-description/m-p/56498#M10672</guid>
      <dc:creator>l.kiciak</dc:creator>
      <dc:date>2022-08-15T14:21:00Z</dc:date>
    </item>
    <item>
      <title>RE: Blue Prism 7.1 - Bug in field for action description</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Blue-Prism-7-1-Bug-in-field-for-action-description/m-p/56499#M10673</link>
      <description>Hello &lt;SPAN&gt;Łukasz Kiciak,&lt;BR /&gt;&lt;BR /&gt;Yes, this has been identified as a bug in the 7.1 code base. As I understand it, there's a fix targeted for the 7.2 release.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Eric Wilson&lt;BR /&gt;Director, Integrations and Enablement&lt;BR /&gt;Blue Prism Digital Exchange&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Aug 2022 14:11:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Blue-Prism-7-1-Bug-in-field-for-action-description/m-p/56499#M10673</guid>
      <dc:creator>ewilson</dc:creator>
      <dc:date>2022-08-16T14:11:00Z</dc:date>
    </item>
  </channel>
</rss>

