We were founded in 2005 in a tiny apartment in Bucharest, Romania as DeskOver.

Fittingly, it was a customer who, in 2012, first saw the immense possibilities for us in the fledgling RPA market. Our desktop automation product launched in 2013. In 2015, we introduced our enterprise platform along with our new name.

Today, UiPath is the fastest-growing enterprise software company in history with scores of offices, thousands of employees, partnerships with the world’s best consulting and BPO firms, a 500,000-strong developer community, and 5MM+ robots at work in over 5,000 global enterprises.

Our mission is to deliver the leading Robotic Process Automation platform to our clients for an automation first mindset.

We build software robots that automate repetitive processes. Our software robots take on the tedious, mind-numbing work and free people to do the more stimulating, creative work worth doing.

But no matter how much we’ve grown, one thing hasn’t changed. We’re still building a company we love to work for

This package is part of a suite of reusable components and snippets:&nbsp;<ul><li><a href=https://go.uipath.com/component/login-ui-automation-for-sap target=_blank>UI Automation Login for SAP</a></li><li><a href=https://go.uipath.com/component/command-line-login-for-sap target=_blank>Command Line Login for SAP</a></li><li><a href=https://go.uipath.com/component/table-visible-rows-counter-for-sap target=_blank>Visible Rows Counter for SAP</a></li><li><a href=https://go.uipath.com/component/freeze-handler-snippet-for-sap target=_blank>Freeze Handler Snippet for SAP</a></li></ul>This package contains reusable workflows for performing a Login to SAP GUI using UI automation and the SAP Logon application.Using this package can help you accelerate your development on SAP related processes. It will offer an out-of-the-box solution for logging into SAP, and you can also use the UI interactions as a reference for how to interact efficiently with various types of SAP screensNOTE: Installation Guidelines for Snippets can be found <a href=https://dmtyylqvwgyxw.cloudfront.net/instances/214/assets/help-guides/UiPath-Go-Installation-Guide-Snippets.pdf target=_blank>here</a>

Reusable workflow package for SAP login using UI automation

RPA Developer Lead

hello i want to ask you, what is this "&lt;wnd app='saplogon.exe' cls='#32770' omit:title='License Information for Multiple Logon' /&gt;&lt;sap id='tbar[0]/btn[0]' /&gt;"?

Dear Mr. Mihai Radulescu, Thanks for sharing this great coding. I was able to run this on my PC but I don't know how to enter a value of password. At this moment I need to enter my password on the logon window. Is there any way to enter the password as the type is specified with securestring? BTW, I'm not a professional programmer but was just interested in using the UiPath to ease my life. So appreciate your clear explanation for non IT people (^.^)/ Regards,Jun

Dear Mihai, Thanks for your previous answer, it helped a lot! Now I'm thinking to create a messaging tool to inform approvers when they need to approve a PO created by ME21N.<ol><li>How to know when a new PO is created? </li><li>How to know when an approval is made per each approver? </li></ol>Regards,Jun Monji

Thank you for developing and publishing this component. Is there any documentation that I can look over to see how to use this? Appreciate it.

We developed all our workflows using manual sign-in and everything worked just fine but when we decided to swap over to SSO, SAP appears to be changing its internal control names/ids.

When SSO add-in is not installed, we have the following selector:

but when SSO add-in is installed, we have the following selector:

This is causing our workflows to fail as it is no longer finding the relevant element(s). Once we uninstall the add-in required for SSO, the control names/ids are back to their original states and everything works as expected.

Have you any ideas why and how to circumvant this problem?

Thanks for the reply and sorry for creating a new post but couldn't see an option to reply. Unfortunately, we've so many workflows using SAP that re-selecting all the selectors would be a nightmare, not to mention that we wanted to use manual sign-for dev and SSO for UAT & Production, so this is not really an option either. 

I still don't get why SAP would change its control names based on the type of sign in mechanism used. As stated, you'd think that all we would have had to do was change the sign-in part and based on an flag passed to the Main Process either use manual sign-in or use SSO but it's does not appear to be so which is a complete pain. Might get in touch with SAP but waiting on client to confirm what they want to do. 

Thanks again for taking the time to reply.

UI Automation Login for SAP® Solutions

UI Automation Login for SAP® Solutions

Help

How To