MENU
Universal Containers is trying to improve the user experience when searching for the tight status on a case. The company currently has one support process that is used for all record types on cases. The
support process has 10 status values. Service reps say they never need more than five depending on what kind of case they are working on.
How should the administrator improve on the current implementation?
Suggested Answer: C
Get Premium ADX-201 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Support processes allow you to define different status values for different record types on cases.
23 comments · newest first
RE
Reita
2 days ago
I feel B is the best balance.
SO
Socorro
7 days ago
B could reduce errors in status selection.
NI
Nichelle
13 days ago
I’m leaning towards C for comprehensive support.
WA
Walton
18 days ago
True, but A is quick to implement.
LE
Leota
23 days ago
But C allows for flexibility.
RE
Reita
28 days ago
Agreed, B is user-friendly.
SO
Socorro
1 month ago
B would enhance user experience for sure.
NI
Nichelle
1 month ago
C could be more efficient long-term.
WA
Walton
1 month ago
A would streamline things. Less clutter.
LE
Leota
2 months ago
D seems too direct. Might confuse users.
RE
Reita
2 months ago
I like B. A flow could guide reps better.
SO
Socorro
2 months ago
Option C makes sense. Tailored processes could help.
NI
Nichelle
2 months ago
But what if different cases need different statuses?
WA
Walton
2 months ago
I think option A is the simplest.
WH
Whitley
2 months ago
Not sure if a Screen Flow is the right move. Seems complicated.
AL
Altha
3 months ago
Surprised they haven't done this already! Why stick with 10?
AS
Ashleigh
3 months ago
Option C seems best—customizing for each record type makes sense.
AN
Angella
3 months ago
I think we need to keep all 10. What if a case needs a specific status?
AN
Annamae
3 months ago
Reducing to five status values sounds smart!
HE
Hector
3 months ago
Editing the status choices directly seems like a quick fix, but I don't think it addresses the underlying issue of user experience. I might lean towards a more structured approach.
VE
Veronika
4 months ago
I feel like option C makes sense because tailoring the support processes to each record type could really streamline things. But I wonder if it might be too complex to manage.
TA
Tamie
4 months ago
I think creating a Screen Flow could be useful, especially if it can dynamically show the right statuses based on the case type. We practiced something similar in class.
TA
Tawna
4 months ago
I remember we discussed how having too many status values can confuse users, so reducing them to five seems like a good idea. But I'm not sure if that's the best approach overall.