@Shubham_Akole
not all details can be identified from the screenshot so I will start to answer in a general way:
if we can grab a webtable to get the information on how many items we have to process and for an element index calculation, then it is a preferred way.
if an information cannot be scrapped by data scrapping then find children, get Attributes … activities will help to post process remaining information retrieval
if the green dot detection can be bound to evaluating an image source (image url) then we can incorporate it by adopting the data scrapping config from source attribute text to src
if it cannot be grapped in datascrapping we do use the other activies mentioned above and do using index info by dynamizing the selectors:
with a for while loop and the test if the element with this particular index exists we can setup a dynamic retreival.
In case of we do need to retrieve info different e.g. from CSS then it can be done with following: