Skip to main content

Scope of a Variable



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:
  1. Click the smallest container in an automation.
  1. 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.

Finally, UI Studio recommends that you write variable names in Camel Case, so that you can read them easier. 


Example of how to name your variables


Variable Type
Variable Name
Generic Value
genVariableName
Text
strVariableName
Number
intVariableName
True or False
boolVariableName
Date and Time
timVariableName
Data Table
datVariableName





Comments

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)

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

Why RPA, Why not Other Tools

Like below there are several features compared to other tools RPA QTP/UFT SELENIUM Commercial Commercial Open Source Less Programming Moderate Programming More Programming License Cost is Less License Cost is More No license cost Free Version No/Minimal additional cost for extra bots Add-Ins Additional cost is very high Free/Paid Add-Ins are available ROI is more ROI is less compare to RPA ROI is more as Open Source Error rate almost to Zero Error rate is moderate Error rate is moderate Customer Satisfaction is high Customer Satisfaction is Moderate Customer Satisfaction is Moderate User Friendly User Friendly Complex 24*7 support 24*7 support No Support