How to capture the status field

Help
, ,
1

Hi, I am stucking in a serious issue.
Where I am checking the the Eligibile and Not Eligible status. Against the number which I indicating by a yellow color arrow.
Scenario - Like I am login to the portal and fill the details. Then if you see this Not Eligible & Eligible when we check the result it’s showing Pending after 10-15 sec it’s giving the result Eligible or Not Eligible. So I have to capture this result.
If you can see, If I capture the Eligible. so it will give the result for the old request which already processed. I want the result for current number. Attache the screenshot.

image
image1115×529 38.4 KB

@Palaniyappan @Lahiru.Fernando @lakshman

Please help how can I check this.

1 Like
2

did data scrapping or Find children activity helped us on this
Cheers @balkishan

1 Like
3

Hi, can you pls show me the selector for that Eligible or Not Eligible field ,
If that selector is having an attribute for.Row number then the logic is easy

4

Hi Palani, I didn’t try to use the Find Children Activity here. But can you please suggest me. How can we accomplished this. Bcz every time I am inserting one I’d and checking the result. I want to store take the result in boolean like if Eligible status then my Element Exist give the True otherwise False. So how can we use here. I am confused because we have the Old history also in the same page. I don’t want the activity give the result based on the old history. I want to capture the result for current result checking against the Id number. @vinay_reddy

5

Hi Buddy , Didn’t understand what actually you want to get from there
Can you elaborate more
As per my understanding this is what you want to do , correct me if I am wrong

Check each record which is having that Number and get the value whether it is Eligible or Not Eligible

is it correct ?

1 Like
6

No bro,

I always want to check for the first record only. Like first I will login to the portal then insert the ID number, then will give me the result on first record only. First it will show the pending the later after 30 second it will give Eligible or Not Eligible.

we’re not checking for all the records, we’re checking only for the first records. Next time if we will check then the first records will go down. now the latest will on the top. Hope you understand bro.

image
image1105×338 20.6 KB

Note: - This status will change from pending to Eligible or Not Eligible after 30 seconds.

@Palaniyappan @vinay_reddy @lakshman @Lahiru.Fernando

7

Can you please post the Selector of the ‘Pending’ field
so can give you next steps what you can do to verify that

Open it in Ui Explorer and Please give all the Attributes that are displaying for that Element

1 Like
8

Here is the selectors.

image

9

Thank you
Once you do the Insert ID number , now
Please use Get attribute Activity and use the attributes in selector as
aaname , Parentclass,Tablerow, Tablecol

And in the Get Attribute use ‘aaname’ and take the Value as output String variable Ex: Status
Then use switch Activity to check the output of the variable
In the Switch Activity logic
Use
Status
Then create case for each expected Output like
“Pending”
“Not Eligible”
“Eligible”
And put the activities what you want to do in each case

2 Likes
10

sorry bro, didn;t get you properly.

As I suggested we’re checking only for the first records. bcz this is our latest record which we’re checking the status. IF Eligible then True if Not Eligible then False.

But this switch I didn’t understand. Pending will show only for the 20-30 sec After this it’s changed and give the result in Eligible or Not Eligible.

11

Main.xaml (9.6 KB)

Hi ,

Please see the Attached workflow
You need to add selector for Get attribute
if you add selector like the below , it will always check at 1st row only

ColName =‘Status’ , Parentclass = ‘eligibility’ ,Tablerow =1 , Tablecol =1

12

Hi , if you get solution , please mark the Topic as solved
so that other users can refer to the solution

Happy Automation
Cheers

1 Like
13

This I will try and let you know. Thanks for your response.