Keyword: SWITCHTOFOLDER
Description: This keyword or action instructs Avo Assure Client to switch to a particular folder in Outlook.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
SwitchToFolder | <Path of required folder> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, once the folder switches to the provided path, the execution status “True”/ “False” will be stored in variable {101}.
Note: This keyword must be used to fetch email from any folder in Outlook.
Keyword: GETEMAIL
Description: This keyword or action instructs Avo Assure Client to fetch the entire content of an email and save the email content in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
GetEmail | <From (Optional>; <To (Optional>; <Subject (Optional)>; <Index (Optional)> | {Variable}; {Status} |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the email content will be fetched and stored in the variable {mail}, and the execution status “True”/ “False” will be stored in variable {res}.
Keyword: GETSUBJECT
Description: This keyword or action instructs Avo Assure Client to fetch the email's subject and store it in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
GetSubject | <Output Variable Of GetEmail> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the subject of the specified email will be fetched and stored in variable {mail_subject}.
Keyword: GETBODY
Description: This keyword or action instructs Avo Assure Client to fetch the body content of the specified email and store the result in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
GetBody | <Output Variable Of GetEmail> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the body content of the specified email will be fetched and stored in the variable {mail_body}.
Keyword: GETFROMMAILID
Description: This keyword or action instructs Avo Assure Client to fetch from the mail ID of the specified email and store the value in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
GetFromMailID | <Output Variable Of GetEmail> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the mail ID of the specified email will be fetched and stored in variable {from_mail_id}.
Keyword: GETTOMAILID
Description: This keyword or action instructs Avo Assure Client to fetch the recipient mail ID of the specified email and store the value in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
GetToMailID | <Output Variable Of GetEmail> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the recipient mail ID of the specified email will be fetched and stored in variable {to_mail_id}.
Keyword: GETATTACHMENTSTATUS
Description: This keyword or action instructs Avo Assure Client to fetch the attachment status, whether the attachment is present or not in the specified email, and save the result in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
GetAttachmentStatus | <Output Variable Of GetEmail> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the attachment status of the specified mail will be fetched and stored in variable {mail_attch_status}.
Keyword: VERIFYEMAIL
Description: This keyword or action instructs Avo Assure Client to verify if the email (referenced in GetEmail) has an email saved in a particular folder.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
VerifyEmail | <Path of .msg folder>; <Output variable of GetEmail> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debugs, the email will be verified, the result will be stored in {80}, and the execution status “True”/ “False” will be stored in variable {hh}.
Keyword: SETTOMAILID
Description: This keyword or action instructs Avo Assure Client to set the mail ID in the ‘To’ field of the Outlook application.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
SetToMailID | <Mail ID 1>; <Mail ID 2> ; …; <Mail ID N> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the email ID will be set, and the execution status “True”/ “False” will be stored in variable {to_mail}.
Keyword: SETCC
Description: This keyword or action instructs Avo Assure Client to set the mail ID in the ‘Cc’ field of the Outlook application.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
SetCC | <Mail ID 1>; <Mail ID 2>; …; <Mail ID N> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the email ID will be set, and the execution status “True”/ “False” will be stored in variable {set_cc}.
Keyword: SETBCC
Description: This keyword or action instructs Avo Assure Client to set the mail ID in the ‘Bcc’ field of the Outlook application.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
SetBCC | <Mail ID 1>; <Mail ID 2>; …; <Mail ID N> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the email ID will be set, and the execution status “True”/ “False” will be stored in variable {set_bcc}.
Keyword: SETSUBJECT
Description: This keyword or action instructs Avo Assure Client to set the subject in the ‘Subject’ field of the Outlook application
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
SetSubject | <Subject> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the subject will be set in the ‘Subject’ field, and the execution status “True”/ “False” will be stored in variable {Set Sub}.
Keyword: SETBODY
Description: This keyword or action instructs Avo Assure Client to set the content of the email body in the ‘Body’ field of the Outlook application
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
SetBody | <Body> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the content of the email body will be set in the ‘Body’ field, and the execution status “True”/ “False” will be stored in variable {email_body}.
Keyword: SETATTACHMENTS
Description: This keyword or action instructs Avo Assure Client to set the attachments.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
SetAttachments | <Attachment Path 1>; <Attachment Path 2>;... <Attachment Path N> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the attachments will be set, and the execution status “True”/ “False” will be stored in variable {attachments}.
Keyword: SENDEMAIL
Description: This keyword or action instructs Avo Assure Client to send an email.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
SendEmail | NA or <Ignore Subject (Optional)> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debugs, the email will be sent, and the execution status “True”/ “False” will be stored in variable {send_email}.
Note: If the subject is not set, we see a pop-up warning: “Do you want to send this message without a subject?” This will not allow further automation unless clicked on either option. To ignore this pop-up message, ‘IgnoreSubject’ should be given in the input field.
Last updated
