RobilityAI®

Header Example

Robility® Forum

Unleash your potential – connect, collaborate, and automate with our powerful solutions.

Web Automation - Al...
 
Notifications
Clear all

[Solved] Web Automation - Alternative methods for retrieving the attribute

5 Posts
2 Users
0 Reactions
256 Views
Posts: 73
Robility Support Team
Topic starter
(@abidurai)
Member
Joined: 1 year ago

Is there any alternative methods for retrieving the attribute, such as using different activities or custom scripts in Web Automation?

Reply
Topic Tags
4 Replies
4 Replies
 Hiba
Robility Support Team
(@iffhiba)
Joined: 1 year ago

Member
Posts: 37

Posted by: @abidurai

Is there any alternative methods for retrieving the attribute, such as using different activities or custom scripts in Web Automation?

Yes, alternative methods for retrieving attributes can be considered if the "Get Attributes" activity does not meet your needs.

  1. CheckAppState - This activity helps you to check whether the element is available or not on the specified website. And returns the result in Boolean values. This is similar to “Element Exist” activity, but in CheckAppState activity you do not need additional “IF, Else” condition activity.  

It provides you with two branches that will lead to perform actions based on the availability of the element.

  1. ExtractData -  This activity helps you to extract data from web applications that have a similar layout and structure across multiple pages. It helps in retrieving the value with URL from the website as output.
  2. GetText – This activity helps you in extracting the text value from the website.

If you are searching for any additional input, please provide more information.

 

Reply
Robility Support Team
(@abidurai)
Joined: 1 year ago

Member
Posts: 73

Posted by: @iffhiba

Posted by: @abidurai

Is there any alternative methods for retrieving the attribute, such as using different activities or custom scripts in Web Automation?

Yes, alternative methods for retrieving attributes can be considered if the "Get Attributes" activity does not meet your needs.

  1. CheckAppState - This activity helps you to check whether the element is available or not on the specified website. And returns the result in Boolean values. This is similar to “Element Exist” activity, but in CheckAppState activity you do not need additional “IF, Else” condition activity.  

It provides you with two branches that will lead to perform actions based on the availability of the element.

  1. ExtractData -  This activity helps you to extract data from web applications that have a similar layout and structure across multiple pages. It helps in retrieving the value with URL from the website as output.
  2. GetText – This activity helps you in extracting the text value from the website.

If you are searching for any additional input, please provide more information.

 

Hey, thanks for the suggestions! I am particularly dealing with a dynamically changing website. Is there any other activity or approach that can handle such scenarios more effectively?

 

Reply
 Hiba
Robility Support Team
(@iffhiba)
Joined: 1 year ago

Member
Posts: 37

Posted by: @abidurai

Posted by: @iffhiba

Posted by: @abidurai

Is there any alternative methods for retrieving the attribute, such as using different activities or custom scripts in Web Automation?

Yes, alternative methods for retrieving attributes can be considered if the "Get Attributes" activity does not meet your needs.

  1. CheckAppState - This activity helps you to check whether the element is available or not on the specified website. And returns the result in Boolean values. This is similar to “Element Exist” activity, but in CheckAppState activity you do not need additional “IF, Else” condition activity.  

It provides you with two branches that will lead to perform actions based on the availability of the element.

  1. ExtractData -  This activity helps you to extract data from web applications that have a similar layout and structure across multiple pages. It helps in retrieving the value with URL from the website as output.
  2. GetText – This activity helps you in extracting the text value from the website.

If you are searching for any additional input, please provide more information.

 

Hey, thanks for the suggestions! I am particularly dealing with a dynamically changing website. Is there any other activity or approach that can handle such scenarios more effectively?

 

To handle such scenarios, you can use  “Retry” scope. This activity helps you to execute a loop and delay with specified time limit to wait for the element to become available. You can checkout there documentation available on the Docs portal to view the detailed information.

 

Reply
 Hiba
Robility Support Team
(@iffhiba)
Joined: 1 year ago

Member
Posts: 37

Posted by: @iffhiba

Posted by: @abidurai

Posted by: @iffhiba

Posted by: @abidurai

Is there any alternative methods for retrieving the attribute, such as using different activities or custom scripts in Web Automation?

Yes, alternative methods for retrieving attributes can be considered if the "Get Attributes" activity does not meet your needs.

  1. CheckAppState - This activity helps you to check whether the element is available or not on the specified website. And returns the result in Boolean values. This is similar to “Element Exist” activity, but in CheckAppState activity you do not need additional “IF, Else” condition activity.  

It provides you with two branches that will lead to perform actions based on the availability of the element.

  1. ExtractData -  This activity helps you to extract data from web applications that have a similar layout and structure across multiple pages. It helps in retrieving the value with URL from the website as output.
  2. GetText – This activity helps you in extracting the text value from the website.

If you are searching for any additional input, please provide more information.

 

Hey, thanks for the suggestions! I am particularly dealing with a dynamically changing website. Is there any other activity or approach that can handle such scenarios more effectively?

 

To handle such scenarios, you can use  “Retry” scope. This activity helps you to execute a loop and delay with specified time limit to wait for the element to become available. You can checkout there documentation available on the Docs portal to view the detailed information.

 

Thanks once again, on the comparative case with “Robility6” and “Robility Enterprise” version activity, there is one such activity as “Inject JS”. Will this activity help me out on the aspect mentioned above?

 

Reply