Skip to main content

Macro - What, Why, Where

Macro:

What is meant by Macro: It is an excel/vba programming set of statements to perform specific task on a single button click

Why we need a Macro: Let’s consider a Scenario • In My Project, to do some activities such as Database cache clean activity, verify patch logs, check application behaviour on daily basis before getting into my work.

Just imagine, if all such activities handled daily by just a single BUTTON CLICK. Yeah this is possible with EXCEL MACRO programming Where to use a Macro: If any repetitive daily activity, you can use EXCEL MACRO in place of it with little bit programming.

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