<?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: Hi All, in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81985#M33481</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/13887"&gt;@NanjundaNarasim&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If you're interacting with a mainframe application, you're probably using Global Send Keys to submit your password, yes? If so, you have to remember that certain characters have a special meaning in Send Keys syntax (like + for SHIFT, ^ for CTRL and so on). So, if you send "1+1" by Global Send Keys, Blue Prism will actually send "1" followed by SHIFT-1, which is "!".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're sending a literal string via Global Send Keys, you should first "sanitize" it to make sure any special characters are converted to regular characters. There's an action called &lt;STRONG&gt;Escape Sendkeys String&lt;/STRONG&gt; in &lt;STRONG&gt;Utility - Strings&lt;/STRONG&gt; that'll do it for you. Or, you can do it yourself using the rules in the BP documentation here: &lt;A href="https://community.blueprism.com/HigherLogic/System/DownloadDocumentFile.ashx?DocumentFileKey=8e8ce98b-df70-4c69-9bb6-4448b8ffc98a" target="_blank" rel="noopener"&gt;Send Keys Cheat Sheet&lt;/A&gt;. But why re-invent the wheel?&lt;/P&gt;
&lt;P&gt;Hopefully, that will solve your problem.&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Andrew Pascal&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Tue, 30 Jan 2024 14:18:00 GMT</pubDate>
    <dc:creator>AndrewPascal</dc:creator>
    <dc:date>2024-01-30T14:18:00Z</dc:date>
    <item>
      <title>Getting incorrect password using blue prism in Mainframe application</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81980#M33476</link>
      <description>Hi,

i am getting an incorrect password error message using blue prism in mainframe application, but the same password i entered manually it is accepting. why it is happening that i don't know. actually this mainframe application is having two login windows one is System i sign on the other one is usual mainframe login.here, i need to enter the system i sign on login then only can access mainframe application.

Is there any problem if the password contains any special characters like "June_2016". 
i have uploaded screenshots what i am getting , please look into that and tell me what is the reason behind in the password or how to overcome in blue prism.


Thank in advance</description>
      <pubDate>Thu, 18 Aug 2016 19:53:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81980#M33476</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-08-18T19:53:00Z</dc:date>
    </item>
    <item>
      <title>I had an issue before sending</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81981#M33477</link>
      <description>I had an issue before sending the £ sign from BP into a mainframe, so other special characters may have the same problem</description>
      <pubDate>Wed, 24 Aug 2016 18:16:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81981#M33477</guid>
      <dc:creator>paul_fraser</dc:creator>
      <dc:date>2016-08-24T18:16:00Z</dc:date>
    </item>
    <item>
      <title>Paul,</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81982#M33478</link>
      <description>Paul,
Can you please tell us how you countered the issue? Did you change the password itself or made some other changes?</description>
      <pubDate>Thu, 25 Aug 2016 10:53:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81982#M33478</guid>
      <dc:creator>ShreyansNahar</dc:creator>
      <dc:date>2016-08-25T10:53:00Z</dc:date>
    </item>
    <item>
      <title>Hi All,</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81983#M33479</link>
      <description>Hi All,
If you are using ""navigate stage"" to write the password having special characters,BP wont recognize the special characters.
Kindly try using ""writer stage"".
Regards,
Ravinder Singh</description>
      <pubDate>Fri, 02 Sep 2016 19:00:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81983#M33479</guid>
      <dc:creator>Ravindersaini</dc:creator>
      <dc:date>2016-09-02T19:00:00Z</dc:date>
    </item>
    <item>
      <title>RE: Hi All,</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81984#M33480</link>
      <description>&lt;P&gt;Thank you Ravinder for the suggestion. I did do as you mentioned, but the password i sent was not accepted. I have to mention that, I am working with an old PICK db with a green screen.&lt;/P&gt;
&lt;P&gt;Let me know if you have any insight into it. Thanks&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Nanjunda Narasimhamurthy&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Mon, 29 Jan 2024 17:01:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81984#M33480</guid>
      <dc:creator>NanjundaNarasim</dc:creator>
      <dc:date>2024-01-29T17:01:00Z</dc:date>
    </item>
    <item>
      <title>RE: Hi All,</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81985#M33481</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/13887"&gt;@NanjundaNarasim&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If you're interacting with a mainframe application, you're probably using Global Send Keys to submit your password, yes? If so, you have to remember that certain characters have a special meaning in Send Keys syntax (like + for SHIFT, ^ for CTRL and so on). So, if you send "1+1" by Global Send Keys, Blue Prism will actually send "1" followed by SHIFT-1, which is "!".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're sending a literal string via Global Send Keys, you should first "sanitize" it to make sure any special characters are converted to regular characters. There's an action called &lt;STRONG&gt;Escape Sendkeys String&lt;/STRONG&gt; in &lt;STRONG&gt;Utility - Strings&lt;/STRONG&gt; that'll do it for you. Or, you can do it yourself using the rules in the BP documentation here: &lt;A href="https://community.blueprism.com/HigherLogic/System/DownloadDocumentFile.ashx?DocumentFileKey=8e8ce98b-df70-4c69-9bb6-4448b8ffc98a" target="_blank" rel="noopener"&gt;Send Keys Cheat Sheet&lt;/A&gt;. But why re-invent the wheel?&lt;/P&gt;
&lt;P&gt;Hopefully, that will solve your problem.&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Andrew Pascal&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Jan 2024 14:18:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Getting-incorrect-password-using-blue-prism-in-Mainframe/m-p/81985#M33481</guid>
      <dc:creator>AndrewPascal</dc:creator>
      <dc:date>2024-01-30T14:18:00Z</dc:date>
    </item>
  </channel>
</rss>

