Skip to main content

HELLOWORLD_Decision


Here you can find implementation of DECISIONS/CONDITIONS in the HELLO WORLD program

Steps:
1.       Delete arrows between the Input Dialog and the Message Box activities
2.       Add a Flow Decision activity between the Input Dialog and the Message Box activities
3.       Select the Flow Decision activity and, in the Properties panel, add a Condition to check if the variable name is empty, such as name = "".
4.       Connect the Input Dialog activity to the Flow Decision. This means that after the user is prompted to add his or her name, the condition added at step 3 is going to be checked.
5.       Connect the True branch of the Flow Decision activity to the Input Dialog. This means that if the name field is empty, the user is going to be prompted to type his name in the Hello World window until the field is filled in. You just created your first loop

6.       Connect the Message Box activity to the False branch of the Flow Decision. This means that if the name field is not empty, the Hello window can be displayed with the string added by the user.


Final Project should be look like below:




What we learn from above Example
Ø  Project can be stored based on user preference either in User defined/ Default (%USERPROFILE%\Documents\UiPath) location
Ø  ‘main.xaml’  file is automatically created for every new project which holds the entire workflow
Ø  All other .xaml  files included in project have to be linked to ‘main.xaml’  file (Only ‘main.xaml’  file will execute)
Ø  .Screenshots folder holds the screenshots for the respective program
Ø  .project.json contains information about Automation Project





Comments

Popular posts from this blog

Variables, Data Types and Math Operations

  In order to do anything interesting in a program, we must have the ability to store and manipulate values. What allows us to do that are what we call variables. Now a variable, simply put, is just named data storage. Now Java is a strongly ‑ typed language. Now what that means is that when we declare a variable like, in this case, we have a variable named data Value, we have to specify the type of that variable, in this case, it's what we call an int, something that can store integers. So, what that means is that the data Value variable can only store things that are compatible with the type int. As we go through the course, we'll talk about this idea of one type being compatible with another. Now when we declare a variable, we can, of course, then assign a value to it, so our variable data Value now holds the value 100. Now when we use variables, we can do it the way we've done here where we declare it, then assign it, or as a matter of convenience, we can declare them a...

Publish a Project

Publish a Project: Publishing means packaging/archiving the project. Why to Publish : Robot can execute only Packages, doesn’t run projects directly. So we need to archive all project files to a Single Package file. There are 2 Process are available 1.        If Orchestrator is connected through Robot, automatically Project archive file displayed in Packages folder. From here, we can distribute this to some other Robots 2.        If there is no connection between Orchestrator and Robot, we need place Project archive file in Packages folder manually How to Publish: 1.        Open UI Studio, Create New Project 2.        In the Setup ribbon tab, click Publish . If the project is published successfully, the Info dialog box is displayed and the project is copied to the NuGet location set in the NuGetServerUrl parameter, in the UiPath.settings...

AGILE Methodology

Agile:      Ø   Agile is nothing but a Multi Iterative Cycle      Ø   It breaks the entire project into Small pieces and then do implementation iteration by iteration      Ø   At the end of every Iteration, customer uses application and gives feedback      Ø   At the end of ALL Iterations, customer will get the application as desired Various versions of Agile: Scrum:                     In Scrum, each iteration is called ‘Sprint’. So, at the end of Sprint, Customer interacts with application and provides feedback (Unlike Waterfall) 3 Roles:   Ø   Product Owner   Ø   Scrum Master       Ø    Team