Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Pegasystems Exam PEGAPCRSA80V1_2019 Topic 8 Question 46 Discussion

Actual exam question for Pegasystems's PEGAPCRSA80V1_2019 exam
Question #: 46
Topic #: 8
[All PEGAPCRSA80V1_2019 Questions]

You are designing an automation that adds new customers to an online insurance web site. If a customer exists, a pop-up window is displayed with an error message, which closes automatically after 35 seconds.

While debugging the automation, you notice that you are receiving a control not created exception message in the Add Customer procedure after a page navigation occurs.

How do you resolve the exception?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

I'm not sure, but I think B) Ensure the waitForCreate timeout is longer than 35 seconds could also be a valid solution.
upvoted 0 times
...
Jodi
2 days ago
Haha, this one's a classic! I bet the developer who wrote this code was having a rough day. Anyway, I'd go with option B to make sure the waitForCreate timeout is longer than the pop-up window's auto-close time. Gotta love those edge cases that make you scratch your head!
upvoted 0 times
...
Glenn
2 days ago
I agree with Shakira. Adding a missing created event should resolve the exception.
upvoted 0 times
...
Shakira
4 days ago
I think the answer is A) Add a missing created event in the Add Customer procedure.
upvoted 0 times
...
Margot
6 days ago
Ah, I see. The control not created exception is probably because the page navigation is causing the control to not be available yet. I'd go with option C to make sure the isCreated timeout is longer than the pop-up window's auto-close time. Looks like a classic timing issue to me.
upvoted 0 times
...
Tamekia
8 days ago
Hmm, the key here is to ensure that the control is created before trying to interact with it. I think option B is the way to go, as the 35-second timeout for the pop-up window may not be long enough for the control to be created. Gotta love these tricky edge cases!
upvoted 0 times
...
Albert
8 days ago
I'm not sure, but I think D) Add a missing waitForEvent.Exists method might also help in resolving the exception.
upvoted 0 times
...
Crista
13 days ago
I agree with Gracia, increasing the timeout should give the control enough time to be created.
upvoted 0 times
...
Gracia
17 days ago
I think the answer is B) Ensure the waitForCreate timeout is longer than 35 seconds.
upvoted 0 times
...

Save Cancel