Skip to main content

Arguments


Arguments:
Ø  Simply we can call it as Parameter/data/value
Ø  Used to pass data from Project to Project, Function to Function
Ø  Dynamically pass/store the data
Ø  Re-usability more, Time is less
Ø  Having specific directions (In, Out, In/Out, Property)


           Creating Arguments
                1.       In the Designer panel, click Arguments. The Arguments panel is displayed

                 


                2.     Click the Create Argument line. A new argument with the default values is displayed.


          Note: By default, all arguments are of String type and have an In direction.


          Removing Arguments
  • In the Arguments panel, select an argument and press Delete.
  • In the Arguments panel, right-click an argument and select the Delete option



 Example for Arguments:
  1. Create a new sequence.
  1. In the Arguments panel, create an argument, StoreValue.
  1. From the Direction list, select Out, and do not change the Argument Type from String.
  1. Add an Assign activity to the Designer panel.
  1. In the Properties panel, in the To field, add the StoreValue argument.
  1. In the Value field, type a string, such as "How does one use an argument?".
    The first project should look like in the screenshot below.
       
  1. Create a new sequence.
  1. Create a string variable, strFinalValue.
  1. Add an Invoke Workflow File activity to the Designer panel.
  1. On the activity, click the Browse (…) button and browse for the previously created sequence.
  1. Click Import Arguments. The Invoked Workflow’s Arguments window is displayed. Note that the argument of the first sequence is displayed here.
  1. In the Value field, add the strFinalValue variable and click Ok. The argument is imported and the value from it is going to be stored in the current project through the strFinalValue variable.
  1. Add a Message Box activity under the Invoke Workflow File.
  2. In the Properties panel, in the Text field, type strFinalValue + " This is how", for example 

The second automation should look like in the screenshot below.



Press F5 in the second sequence. The automation is executed correctly and the message box displays the desired text



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