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

Post a Comment

We appreciate your valuable Suggestions/Feedback

Popular posts from this blog

Brief Overview of RPA

Brief Overview of RPA:     §   In short, it’s a way for machines to replace human workers in regular activities done across the organization.     §   It works on both Front End & Back End applications/operations.     §   BOT provides Virtual automation agents , it acts like MIMIC HUMANS .     §   BOT ’s available in Clouds/Servers     §   BOT is nothing but a configurable software set up, works only on rule-based triggers     §   It automates Non-Value –added works     §   It is a Sub Domain of BPMS (Business Process Management Software)
2 comments
Read more

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

RPA Life Cycle

RPA Life Cycle: It is similar to software development life cycle with some minor changes. Technically, we called it as ‘ Life Cycle of a Bot’   Analysis:           ·     RPA Cycle begins from ‘ Analysis ’ phase.           ·     In this, Business Team & RPA Strategist/Architect identifies business process to automate           ·     After finalizing feasibility on process, implement plan of work (which includes documentation, Resources count & Time  ...) Development:          ·       Dev. Team starts working on requirements wrt to Environment.          ·       We called this phase as ‘ Bot Development ’          ·       Based on Tool selection , Limited/No coding is required ...
Post a Comment
Read more