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

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...

Types of Recording

Types of Recording: 4 types of recording modes are available Ø   Basic Ø   Desktop Ø   Web Ø   Citrix 2 ways of Recording Ø   Automatic Ø   Manual Basic – generates a full selector for each activity and no container, the resulted automation is slower than one that uses containers and is suitable for single activities. Desktop – suitable for all types of desktop apps and multiple actions; it is faster than the Basic recorder, and generates a container (with the selector of the top-level window) in which activities are enclosed, and partial selectors for each activity. Web – 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. Citrix – used to record virtualized environments (VNC, virtual machines, Citrix, etc.) or SAP, permits only image, text and keyboard automation, and requires explici...

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...