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 PEGAPCSSA87V1 Topic 6 Question 30 Discussion

Actual exam question for Pegasystems's PEGAPCSSA87V1 exam
Question #: 30
Topic #: 6
[All PEGAPCSSA87V1 Questions]

You are updating a system of record using a SOAP connector. If the system of record is unavailable, you want to retry after an hour. If it is still unavailable after an hour, a notification should be sent to a system administrator.

How do you implement this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: B, D, E

Contribute your Thoughts:

Kelvin
2 months ago
If the system of record is unavailable, just send the admin a notification saying 'System down, please flip the on/off switch.'
upvoted 0 times
...
Svetlana
2 months ago
B) all the way! Who wants to clutter up their data page with error handling code? Keep that stuff where it belongs - in the connector flow.
upvoted 0 times
Verlene
1 months ago
B) No way! Error handling should be kept separate from the data page logic for better maintainability.
upvoted 0 times
...
Pearly
1 months ago
A) But wouldn't it be easier to manage the retry logic in the data page's response data transform?
upvoted 0 times
...
Galen
1 months ago
B) Exactly! It's cleaner and more organized to handle errors directly in the connector flow.
upvoted 0 times
...
Zona
2 months ago
B) all the way! Who wants to clutter up their data page with error handling code? Keep that stuff where it belongs - in the connector flow.
upvoted 0 times
...
...
Emogene
3 months ago
I'd say B) is the way to go. Putting the retry and notification logic in the connector's error handler just seems like the cleanest and most logical approach.
upvoted 0 times
Felix
1 months ago
That's true, it keeps the logic centralized and makes it easier to manage.
upvoted 0 times
...
Andra
2 months ago
I agree, it makes sense to handle retries and notifications directly in the connector's error handler.
upvoted 0 times
...
Delmy
2 months ago
B) Implement the logic in the connector's error handler flow.
upvoted 0 times
...
...
Ranee
3 months ago
Definitely go with B. Having the error handling logic in the connector flow keeps things organized and makes it easier to maintain the code.
upvoted 0 times
Daren
29 days ago
C) Customize the standard pxErrorHandlingTemplate data transform.
upvoted 0 times
...
Antonio
1 months ago
B) Implement the logic in the connector's error handler flow.
upvoted 0 times
...
Rosendo
1 months ago
A) Implement the logic in the data page's response data transform.
upvoted 0 times
...
Jeannetta
2 months ago
B) Implement the logic in the connector's error handler flow.
upvoted 0 times
...
...
Isidra
3 months ago
B) Implement the logic in the connector's error handler flow seems like the most appropriate option. Handling the retry and notification in the connector's error handling makes sense to me.
upvoted 0 times
...
Evangelina
3 months ago
I'm not sure, but I think option D could also work by using a transition condition in the activity step.
upvoted 0 times
...
Lindsey
4 months ago
I agree with Freida. Option B seems like the most logical way to implement this requirement.
upvoted 0 times
...
Freida
4 months ago
I think option B is the best choice because the error handler flow is specifically designed to handle errors in connectors.
upvoted 0 times
...

Save Cancel