The Study Secretz

UI Elements Simply, UI = U ser I nterface Consider any Application, Here I’m taking www.google.com as an example. If you navigate to Google URL on any browser, it should be look like below. From this, you can observe something like below in the application. Search box, buttons (Sign In, Google Search, I’m Feeling Lucky), Google Image, Links (Gmail, Images) and many more So, all these elements are available in user interface. Hence, we called them as “ UI ELEMENTS ” We can have categorized all above elements in 2 ways Input Elements : Search box, buttons, Google Image, Links Output Elements : Google Result Operations which you performed on input/output elements is called as Input / Output Actions Input Actions : Clicks, Text Typing, Mouse Hover, Key board Shortcuts Output Actions : Getting Text, Finding Elements, Getting Results From above, UI elements only constructs an application, if we know how to interact with them enables ...

  Name Spaces:             These are the CLASS TYPE or Library command which helps to use sub commands for the specific class. If you enter class file name/import library files, then it enables you to use their sub functions/commands in the activities. Example : If you import “ SYSTEM.DATA ” library, then it allows you to use DataTable , DataView , DataColumn , DataRow and other classes that are available in it, without having to always type System.Data.DataTable From above, you can find all listed commands in the Imports panel. Adding New Command: If you want to add new command to imports panel list, type some part of command and then select from dropdown list. It automatically added to the list Removing Command: Select a command, then Press DELETE button

Arguments: Ø   Simply we can call it as Parameter/data/value Ø   Used to pass data from Project to Project, Function to Function Ø   Dynamically pass/store the data Ø   Re-usability more, Time is less Ø   Having specific directions ( In, Out, In/Out, Property )             Creating Arguments                 1.        In the Designer panel, click Arguments . The Arguments panel is displayed                                   2.     Click the Create Argument line. A new argument with the default values is displayed.           Note : By default, all arguments are of String type and have an In direction.            Removing Arguments In the Arguments panel, select ...

Normal Variable to Global Variable: We create normal variables directly in an activity (from the context menu of an activity), has a smallest scope it belongs to. To make them available in your entire project, do the following: Click the smallest container in an automation. On the Design ribbon tab, in the Variables group, select Manage Variables > Promote to Global Scope . All the variables used in the selected container now have a global scope Best Naming Practice for Variables: When creating very large automations, it can be very easy to forget what every variable does. That is why it is important to have a good naming system in place. We recommend that you always use descriptive names, such as userName for a variable that stores the name of a user. Additionally, you might want to keep track of the type of variable you create, and that is why adding a short descriptor in the front of each variable name can be useful, such as int for integers. ...

Variable           Ø   Variable is nothing but a memory location             Ø   It holds multiple types of data             Ø   Data stored in Variable is named as ‘Value’             Ø   Supports a large amount of types, ranging from generic value, text, number, data table, time and date, UI                    Elements to any .Net variable type. Create a Variable: On the Design ribbon tab, in the Variables group, select Create Variable > [Type of variable] . The Create Variable window is displayed Fill in the required fields and click OK . The variable is created and you can view and edit it in the Variables panel. 1.In the Properties panel of any activity, right-click a field that can be edited, and select Create Variable from the context menu, or press Ctrl+K....

It is designed for recording in web apps and browsers (supported: Internet Explorer, Google Chrome), generates containers and uses the Simulate Type/Click input method by default. Examples for Web Recordings: Open an Internet Explorer instance. In UiPath Studio, create a new sequence. In the Design tab, in the Wizards group, select Record > Web . The Web Recording toolbar is displayed and the main view is minimized. Click Automatic Recording . The automating recording process starts. Navigate to www.amazon.com . Go to the Sign In page and input your e-mail and password. Note :                       When the Type Into pop-up is displayed for your password, make sure that you select the Type Password check box. Besides the Type Into activity, another activity, Get Password , is created in the sequence. This activity hides the password behind aste...

Automatic Recording: It is very useful & time saving as it provides you a skeleton for the business process We can easily customized & parameterized Below actions/activities are automatically generated, while user is in ‘Automatic Recording’ Click - when you click a button (Basic and Desktop) or a link (Web). TypeInto - typing into a text field or any editable UI element SelectItem – when you select an item from a drop-down list or combo box Check – when a radio button or check box is clicked User is able to add time delay (& many more) in Properties panel for the above actions/activities. Examples for Basic & Desktop Recordings: Open Notepad. In UiPath Studio, create a new sequence. a. In the Design ribbon tab, in the Wizards group, select Record > Basic . The Basic Recording toolbar is displayed and the main view is minimized. b. In the Design ribbon tab, in the Wizards group, select Re...