UiPath Certified Professional - Developer Track Changed UiPath-ADAv1 Questions

The Compress/Zip Files activity is used to archive a set of files and send them as an attachment in an email. This activity allows the developer to specify the source folder that contains the files to be archived, the destination folder where the compressed file will be created, and the name of the compressed file. The activity also supports various compression formats, such as zip, tar, gz, bz2, xz, and 7z. The compressed file can then be attached to an email using the AttachmentsCollection property of the Send Mail activity. This way, the developer can reduce the size and number of the files to be sent, as well as protect them with a password if needed.

References:

• Compress/Zip Files - UiPath Activities
• Send Mail - UiPath Activities
• How to send multiple files in one attachment in uipath - UiPath Community Forum

The Write Line activity is used to write a specified text to the Output panel. The text can be a string literal, a variable, or an expression. In this case, the Write Line activity in the Main xaml file has the text "out_ShoppingBasket + “, “Orange””. The out_ShoppingBasket is a variable of type String, which is declared in the Main xaml file and has the default value of “Apple”. The variable is passed as an argument to the SuperMarket xaml file, where it is assigned a new value of “Orange”. The argument direction is Out, which means that the value of the argument is passed back to the Main xaml file after the execution of the SuperMarket xaml file. Therefore, the value of the out_ShoppingBasket variable in the Main xaml file is changed from “Apple” to “Orange”. The expression "out_ShoppingBasket + “, “Orange”” concatenates the value of the out_ShoppingBasket variable with a comma and a space, followed by the string literal “Orange”. The result of this expression is “Orange, Orange”. The Write Line activity writes this text to the Output panel. Therefore, the answer is B. Orange. References: Write Line, Variables, Arguments

The developer can use the Anchor functionality to improve the reliability of the Type Into activity for text input fields that are impacted by changing orientations. This is because the Anchor functionality allows the developer to specify a particular element as a reference point for the Type Into activity. This ensures that the activity will always be performed in the correct location, even if the orientation of the text input fields changes.

References:

• Type Into - UiPath Activities
• Anchor Base - UiPath Activities
• UiPath Anchor Base Tutorial & AnchorPosition Example

The argument name that follows UiPath best practices for argument naming conventions is out_ConfirmationNumber. According to the UiPath best practices, the argument name should be meaningful and include an indication of its type and direction. The type can be inferred from the argument’s data type, such as String, Int32, DataTable, etc. The direction can be one of the following: in, out, or io. The in direction means that the argument can only be used within the given project. The out direction means that the argument can be used to pass data outside of a given project. The io direction means that the argument can be used both within and outside of a given project4. The argument name should also follow the camel case convention, which specifies that each word in the middle of the argument name begins with a capital letter, with no intervening spaces or punctuation5. For example, the argument name out_ConfirmationNumber follows these best practices, as it indicates that the argument is of out direction, and that it stores a confirmation number value. The other argument names do not follow the best practices, as they either use incorrect or inconsistent prefixes, or do not use camel case convention. References: ST-NMG-002 - Arguments Naming Convention and Variables, arguments and workflows naming - best practice from UiPath documentation and forum.