Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Pegasystems Exam PEGAPCSA87V1 Topic 8 Question 58 Discussion

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

You are configuring duplicate case search logic in a case type. How do you ensure that resolved cases are not evaluated as potential duplicates?

Show Suggested Answer Hide Answer
Suggested Answer: A, B

by Royal at Jan 16, 2025, 12:12 AM

Limited Time Offer

25%

Off

Get Premium PEGAPCSA87V1 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Lettie
1 months ago
Option C all the way! Gotta love that weighted condition - it's like a little 'resolved' forcefield to keep those pesky closed cases at bay.
upvoted 0 times
Dean
2 days ago
User 3: I agree, Option C seems like the best way to make sure resolved cases are not considered duplicates.
upvoted 0 times
...
Van
6 days ago
User 2: Yeah, that weighted condition is a game-changer. Resolved cases won't stand a chance.
upvoted 0 times
...
Eliseo
20 days ago
User 1: Option C all the way! Gotta love that weighted condition - it's like a little 'resolved' forcefield to keep those pesky closed cases at bay.
upvoted 0 times
...
...
Phillip
2 months ago
Option C is the way to go. Checking the work status on both ends and giving 'Resolved' a weight of 0 is a smart way to avoid false positives.
upvoted 0 times
Jolene
22 days ago
Definitely, it's important to consider all possible scenarios when configuring duplicate case search logic.
upvoted 0 times
...
Karan
29 days ago
Definitely, it's important to carefully configure the duplicate case search logic to avoid any issues with resolved cases.
upvoted 0 times
...
Minna
29 days ago
That makes sense, by giving 'Resolved' a weight of 0, it ensures that it won't match as a potential duplicate.
upvoted 0 times
...
Myra
1 months ago
That makes sense, by giving 'Resolved' a weight of 0, it ensures that it won't match as a potential duplicate.
upvoted 0 times
...
Raylene
1 months ago
I agree, option C seems like the best way to make sure resolved cases are not considered duplicates.
upvoted 0 times
...
Muriel
1 months ago
I agree, option C seems like the best way to make sure resolved cases are not considered duplicates.
upvoted 0 times
...
...
Earleen
2 months ago
I'd go with Option C as well. It's the only one that addresses the work status of both the current and potential duplicate cases.
upvoted 0 times
...
Noah
2 months ago
Option C seems like the most comprehensive approach. Evaluating the work status of both the current and existing cases, and weighting 'Resolved' as 0, ensures that resolved cases are not considered duplicates.
upvoted 0 times
...
Fernanda
3 months ago
Hmm, that makes sense too. I guess it depends on how the logic is implemented in the case type.
upvoted 0 times
...
Frederick
3 months ago
I disagree, I believe the correct answer is D. We should check the potential duplicates, not the current case.
upvoted 0 times
...
Fernanda
3 months ago
I think the answer is A, because we need to make sure the current case is not resolved.
upvoted 0 times
...

Save Cancel