Skip to main content

HELLO WORLD


As of now, you've learned some basics of RPA & UI Studio. Now, It's a time to create your first program (Obviously "HELLO WORLD") in UI Studio as below.

Creating a New Sample Project:

Here I’m displaying HELLO WORLD along with User Input with Flow Chart workflow
1)       Open UI Path studio


2)       On the Start tab, under the New section, click Blank. The New Project window is displayed.


3)       Enter NAME for the Project (say HELLOWORLD) & Select Project Location and Click on CREATE button. New Project (Main.xaml) is created in Chosen Location.
4)       Add/Drag and Drop any workflow/activity (like Flowchart) from Activities Panel
5)       Add Input Dialog activity
6)       Connect Input Dialog activity to Start node by selecting ‘Set as Start Node’   in Right Click menu of the Input activity


7)    On the Design tab, select Create Variable > Text to create a string variable which is used to store user’s name (name)
8)    On the Properties panel, under the Input section, add a Label for the activity, such as "Type your name," and a Title, such as "Hello, world!."
9)   Under the Output section, in the Result field, add the variable created at step 6


10)     Add a Message Box activity to the Designer panel and connect it to the existing Input Dialog activity.
11)    Make sure that the Message Box activity is selected. The Properties panel is updated accordingly.
12)    Under the Input section, add a Caption such as "Hello," and in the Text field add a string and the previously created variable, such as “Hello” + name.


13)     The Project  should be looks like below


14)     Run/Execute (F5) the project from Designer tab. “Hello World” pop-up asks the User for input


15)       Enter User input, then OK. Result will be displayed as 





From above steps, you've successfully created your first program in UI Studio.

 Note:
From above Sample HELLO WORLD program, we can conclude that
·         There is NO VALIDATION for user input.
·         If user gives blank, the Pop-up will accept it


It's like a flaw in the Project, To avoid such flaws, we need to implement Flow Decision / Conditions. So that UI Studio validates user input before processing.



Don’t forget to give your valuable feedback in Comments

Comments

Post a Comment

We appreciate your valuable Suggestions/Feedback

Popular posts from this blog

RPA Implementation Approach

RPA Implementation Approach: 1. Tool Selection o     Based on user requirements, features available in tools, you’ve to select TOOL from mentioned above         2. Process Prioritization o     After successful section of Tool, you’ve to consolidate & prioritize the all processes in current operation. Let’s start automating lowest first and most important to next
Post a Comment
Read more

Key Points of Leading RPA Tools

Key Points of Leading RPA Tools Automation Anywhere(AA) Blue Prism(BP) UI Path Developer friendly tool RPA Term was invented by Blue Prism Extremely User Friendly Offers Front and Back Office Robots It is an Enterprise grade RPA Solution tool Implementation Speed is high Script based, More Programming Skills required Supports only Back Office robots Re Usability is more since various integrations available with different workflows Smart Recorder Option available Code Insertion is difficult and not user friendly Free Community edition (PDF’s, Videos available for FREE) AA Bots can deploy in Physical Front Office machines & Cloud Extreme control over activities (Object Creation, Coding etc.) Con is - No Coding Annual support cost and license cost is higher What is Best RPA Tool...
4 comments
Read more

Defect/Bug Life Cycle

Bug Life Cycle: It is a cycle in which a defect goes through different phases during its lifetime The Journey of a Defect/Bug from its NEW (or Born/Found ) state to Close (or END/Fixed ) state, so this journey of a cycle is known as ‘ BUG LIFE CYCLE ’. We can also called it as ‘ DEFECT LIFE CYCLE ’ 1.        New:  When a defect is logged and posted for the first time. It’s state is given as new. 2.        Assigned:  After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to corresponding developer and the developer team. It’s state given as assigned. 3.        Open:  At  this state the developer has started analyzing and working on the defect fix. 4.        Fixed:  When developer makes necessary code changes and verifies the changes then he/she can make bu...
Post a Comment
Read more